Tech Community Live: Endpoint Manager edition
Jul 21 2022, 08:00 AM - 12:00 PM (PDT)

Known Issue: Missing certificates after updating Samsung work profile devices to Android 12

Published Jan 20 2022 02:50 PM 12.3K Views

Updated 06/06/22: The content below has been updated, please use the workarounds provided if you run into this issue.

 

Environment

  • Microsoft Intune using client certificates to authenticate VPN and email
  • Samsung devices upgrading from Android 11 to Android 12

Overview

In Q3 2021, Google introduced the Android Keystore2 as a replacement for the current Keystore in Android 12. In an effort to harmonize with Google and the modernization of the Android Operating System, Samsung deprecated its custom Knox key store and certificate manager in favor of the Android Keystore2. The new Samsung devices starting on Android 12 and higher use the Android Project's default 'Keystore2' implementation.

 

Although there are no reliable software fixes to this issue, this article provides guidance to a manual workaround.

 

Cause

Microsoft Endpoint Manager uses the Android Management API as an underlying device management technology.


Currently, the Android Management API model does not have a way of initializing the low-level keystore. Therefore, when you upgrade Samsung devices from Android 11 to Android 12, the migration from the custom keystore to the new ‘Keystore2’ is not successful, and causes deployed apps to lose access to the stored certificates.

 

Resolution

After upgrading your Samsung devices from Android 11 to Android 12, remove and redeploy the impacted certificates or app configuration to the devices.

 

Android Enterprise personally-owned with a work profile configurations

First, uninstall the affected app.

  • If the affected app is a required app, it will automatically be reinstalled.
  • If the affected app is an available app, the device user has to manually reinstall from the corporate Play Store.

 

Android Enterprise fully managed, Android Enterprise corporate-owned with a work profile, and Android Enterprise dedicated configurations

  • If the affected app is an available app, the device user must manually uninstall and reinstall the app from the corporate Play Store.
  • If the affected app is a required app, your corporate admin must send a policy to remove the app and they must reinstall through policy. Follow these steps (as per Microsoft):
    1. In the Microsoft Endpoint Manager admin center, create an exclusion group for the affected app.
    2. Add the user(s) to the exclusion group.
    3. Sync the policy on the Android device.
    4. Confirm the affected app is removed from the device.
    5. Remove the user from the exclusion group.
    6. Confirm the app is added to the device.

Please contact your Microsoft representative if the issue continues to persist after the redeployment of the impacted app configuration. Samsung and Microsoft have a close cooperation on this issue. We appreciate your support and patience through this process.

 

If you have any questions, reply to this post or reach out to Microsoft Intune Support @IntuneSuppTeam on Twitter.

 

 

Additional information

If you are a developer using Samsung products, you can find more detailed information here:

 

Post updates:

03/02/22: Added update text at the beginning of this post.

06/06/22: Updated content and workarounds.

10 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-3067935%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Missing%20certificates%20after%20updating%20Samsung%20work%20profile%20devices%20to%20Android%2012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3067935%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20add%20Outlook%20to%20the%20list.%20The%20SMIME%20certificate%20deployed%20with%20MEM%20is%20no%20longer%20available%20in%20the%20Outlook%20SMIME%20settings.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EWorkaround%20%26nbsp%3Bis%20removing%20and%20reinstalling%20Outlook.%20No%20need%20to%20delete%20the%20work%20profile.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EOn%20the%20other%20hand%2C%20removing%20certificate%20assignments%20and%20re-assigning%20does%20not%20fix%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3071192%22%20slang%3D%22de-DE%22%3ESubject%3A%20Known%20Issue%3A%20Missing%20certificates%20after%20updating%20Samsung%20work%20profile%20devices%20to%20Android%2012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3071192%22%20slang%3D%22de-DE%22%3E%3CP%3EDo%20you%20have%20a%20list%20of%20affected%20Samsung%20devices%3F%20This%20issue%20seems%20not%20to%20persist%20on%20every%20device.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3072278%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Missing%20certificates%20after%20updating%20Samsung%20work%20profile%20devices%20to%20Android%2012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3072278%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1286085%22%20target%3D%22_blank%22%3E%40JKS97%3C%2FA%3E%26nbsp%3BWe%20can%20currently%20confirm%20the%20issue%20on%20an%20A52s%205G%20and%20A52%20that%20was%20enrolled%20with%20Android%2011%20and%20was%20updated%20to%2012.%20The%20certificates%20were%20assigned%20and%20deployed%20before%20the%20update.%20Devices%20enrolled%20after%20upgrading%20to%20Android%2012%20are%20not%20affected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3104702%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Missing%20certificates%20after%20updating%20Samsung%20work%20profile%20devices%20to%20Android%2012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3104702%22%20slang%3D%22en-US%22%3E%3CDIV%3E%3CP%3ESamsung%20told%20us%20that%20the%20issue%20can%20be%20addressed%20by%20UEM%20partners%20by%20using%20the%20Knox%20API%20addPermissionApplicationPrivateKey.%20It's%20possible%20to%20grant%20permission%20for%20apps%20to%20use%20installed%20keys.%3C%2FP%3E%3C%2FDIV%3E%3CDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CDIV%3EMore%20details%3A%3CBR%20%2F%3E%3CA%20title%3D%22https%3A%2F%2Fdocs.samsungknox.com%2Fdev%2Fknox-sdk%2Ftima-ccm-keystore-deprecation.htm%22%20href%3D%22https%3A%2F%2Fdocs.samsungknox.com%2Fdev%2Fknox-sdk%2Ftima-ccm-keystore-deprecation.htm%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%20nofollow%22%3Ehttps%3A%2F%2Fdocs.samsungknox.com%2Fdev%2Fknox-sdk%2Ftima-ccm-keystore-deprecation.htm%3C%2FA%3E%3CBR%20%2F%3E%3CA%20title%3D%22https%3A%2F%2Fdocs.samsungknox.com%2Fdevref%2Fknox-sdk%2Freference%2Fcom%2Fsamsung%2Fandroid%2Fknox%2Fkeystore%2Fcertificatepolicy.html%23addpermissionapplicationprivatekey(com.samsung.android.knox.keystore.permissionapplicationprivatekey)%22%20href%3D%22https%3A%2F%2Fdocs.samsungknox.com%2Fdevref%2Fknox-sdk%2Freference%2Fcom%2Fsamsung%2Fandroid%2Fknox%2Fkeystore%2FCertificatePolicy.html%23addPermissionApplicationPrivateKey(com.samsung.android.knox.keystore.PermissionApplicationPrivateKey)%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%20nofollow%22%3Ehttps%3A%2F%2Fdocs.samsungknox.com%2Fdevref%2Fknox-sdk%2Freference%2Fcom%2Fsamsung%2Fandroid%2Fknox%2Fkeystore%2FCertificatePolicy.html%23addPermissionApplicationPrivateKey(com.samsung.android.knox.keystore.PermissionApplicationPrivateKey)%3C%2FA%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3115153%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Missing%20certificates%20after%20updating%20Samsung%20work%20profile%20devices%20to%20Android%2012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3115153%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1290471%22%20target%3D%22_blank%22%3E%40Sanitar2034%3C%2FA%3E%26nbsp%3Bthe%20OnePlus%2C%20OPPO%2C%20etc%20issue%20is%20not%20the%20same%20as%20what's%20described%20here%20with%20Samsung%20(we%20thought%20it%20was%20too%2C%20but%20checked%20with%20Intune%20engineering%20and%20they've%20confirmed%20they%20are%20different).%20Intune%20engineers%20just%20checked%20with%20Google%20and%20they%20are%20actively%20reviewing%20the%20issue%20and%20working%20with%20OnePlus%20and%20OPPO.%20We're%20hoping%20that%20they'll%20provide%20documentation%20on%20soon%20we%20can%20point%20you%20to.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3247178%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Missing%20certificates%20after%20updating%20Samsung%20work%20profile%20devices%20to%20Android%2012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3247178%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F226779%22%20target%3D%22_blank%22%3E%40Intune_Support_Team%3C%2FA%3E%26nbsp%3B%20could%20you%20please%20let%20us%20know%20more%20details%20of%20the%20issue%20and%20the%20remediation%20steps.%20We%20have%20Samsung%20devices%20enrolled%20with%20Android%20enterprise%20BYOD%20instance%20and%20all%20the%20devices%20are%20facing%20issues%20with%20connecting%20to%20WIFI%20(%20Cert%20based%20authentication)%20impacted%20devices%20are%20newly%20enrolled%20Android%2012%20and%20upgraded%20devices%20from%20Android%2011.%20(%20S21%2C%20S22%2C%20A5%20etc)%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3248950%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Missing%20certificates%20after%20updating%20Samsung%20work%20profile%20devices%20to%20Android%2012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3248950%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1236270%22%20target%3D%22_blank%22%3E%40Karan_m123%3C%2FA%3E%3CSPAN%3E%2C%20sorry%20to%20hear%20you%20are%20experiencing%20issue.%20We've%20followed%20up%20with%20you%20over%20a%20private%20message%20with%20more%20info%20in%20relation%20to%20OPPO.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3262387%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Missing%20certificates%20after%20updating%20Samsung%20work%20profile%20devices%20to%20Android%2012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3262387%22%20slang%3D%22en-US%22%3E%3CP%3EAndroid%20Enterprise%20work%20profile%20%3A%20Pulse%20secure%20Certificate%20missing%20issue%20and%20Samsung%20Gallery%20application%20showing%20your%20device%20is%20not%20supported.%20This%20issue%20occur%20on%20all%20Samsung%20devices%20Which%20comes%20with%20Android%2012.%3C%2FP%3E%3CP%3EPlease%20suggest%20me%20how%20to%20fix%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3039834%22%20slang%3D%22en-US%22%3EKnown%20Issue%3A%20Missing%20certificates%20after%20updating%20Samsung%20work%20profile%20devices%20to%20Android%2012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3039834%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3E%3CSTRONG%3EUpdated%2006%2F06%2F22%3C%2FSTRONG%3E%3A%26nbsp%3BThe%20content%20below%20has%20been%20updated%2C%20please%20use%20the%20workarounds%20provided%20if%20you%20run%20into%20this%20issue.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3EEnvironment%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EMicrosoft%20Intune%20using%20client%20certificates%20to%20authenticate%20VPN%20and%20email%3C%2FLI%3E%0A%3CLI%3ESamsung%20devices%20upgrading%20from%20Android%2011%20to%20Android%2012%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3EOverview%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EIn%20Q3%202021%2C%20Google%20introduced%20the%20Android%20Keystore2%20as%20a%20replacement%20for%20the%20current%20Keystore%20in%20Android%2012.%20In%20an%20effort%20to%20harmonize%20with%20Google%20and%20the%20modernization%20of%20the%20Android%20Operating%20System%2C%20%3CA%20href%3D%22https%3A%2F%2Fdocs.samsungknox.com%2Fdev%2Fknox-sdk%2Ftima-ccm-keystore-deprecation.htm%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ESamsung%20deprecated%20its%20custom%20Knox%20key%20store%20and%20certificate%20manager%3C%2FA%3E%20in%20favor%20of%20the%20Android%20Keystore2.%20The%20new%20Samsung%20devices%20starting%20on%20Android%2012%20and%20higher%20use%20the%20%3CA%20href%3D%22https%3A%2F%2Fsource.android.com%2Fsecurity%2Fkeystore%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EAndroid%20Project's%20default%20'Keystore2'%3C%2FA%3E%20implementation.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlthough%20there%20are%20no%20reliable%20software%20fixes%20to%20this%20issue%2C%20this%20article%20provides%20guidance%20to%20a%20manual%20workaround.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3ECause%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EMicrosoft%20Endpoint%20Manager%20uses%20the%20Android%20Management%20API%20as%20an%20underlying%20device%20management%20technology.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3ECurrently%2C%20the%20Android%20Management%20API%20model%20does%20not%20have%20a%20way%20of%20initializing%20the%20low-level%20keystore.%20Therefore%2C%20when%20you%20upgrade%20Samsung%20devices%20from%20Android%2011%20to%20Android%2012%2C%20the%20migration%20from%20the%20custom%20keystore%20to%20the%20new%20%E2%80%98Keystore2%E2%80%99%20is%20not%20successful%2C%20and%20causes%20deployed%20apps%20to%20lose%20access%20to%20the%20stored%20certificates.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3EResolution%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EAfter%20upgrading%20your%20Samsung%20devices%20from%20Android%2011%20to%20Android%2012%2C%20remove%20and%20redeploy%20the%20impacted%20certificates%20or%20app%20configuration%20to%20the%20devices.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EAndroid%20Enterprise%20personally-owned%20with%20a%20work%20profile%20configurations%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EFirst%2C%20%3CSTRONG%3Euninstall%3C%2FSTRONG%3E%20the%20affected%20app.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20the%20affected%20app%20is%20a%20%3CSTRONG%3Erequired%20app%3C%2FSTRONG%3E%2C%20it%20will%20automatically%20be%20reinstalled.%3C%2FLI%3E%0A%3CLI%3EIf%20the%20affected%20app%20is%20an%20%3CSTRONG%3Eavailable%20app%3C%2FSTRONG%3E%2C%20the%20device%20user%20has%20to%20manually%20reinstall%20from%20the%20corporate%20Play%20Store.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EAndroid%20Enterprise%20fully%20managed%2C%20Android%20Enterprise%20corporate-owned%20with%20a%20work%20profile%2C%20and%20Android%20Enterprise%20dedicated%20configurations%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20the%20affected%20app%20is%20an%20%3CSTRONG%3Eavailable%20app%3C%2FSTRONG%3E%2C%20the%20device%20user%20must%20manually%20uninstall%20and%20reinstall%20the%20app%20from%20the%20corporate%20Play%20Store.%3C%2FLI%3E%0A%3CLI%3EIf%20the%20affected%20app%20is%20a%20%3CSTRONG%3Erequired%20app%3C%2FSTRONG%3E%2C%20your%20corporate%20admin%20must%20send%20a%20policy%20to%20remove%20the%20app%20and%20they%20must%20reinstall%20through%20policy.%20Follow%20these%20steps%20(as%20per%20Microsoft)%3A%3COL%3E%0A%3CLI%3EIn%20the%20%3CA%20href%3D%22https%3A%2F%2Fendpoint.microsoft.com%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20Endpoint%20Manager%20admin%20center%3C%2FA%3E%2C%20create%20an%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fintune%2Fapps%2Fapps-inc-exl-assignments%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Eexclusion%20group%3C%2FA%3E%20for%20the%20affected%20app.%3C%2FLI%3E%0A%3CLI%3EAdd%20the%20user(s)%20to%20the%20exclusion%20group.%3C%2FLI%3E%0A%3CLI%3ESync%20the%20policy%20on%20the%20Android%20device.%3C%2FLI%3E%0A%3CLI%3EConfirm%20the%20affected%20app%20is%20removed%20from%20the%20device.%3C%2FLI%3E%0A%3CLI%3ERemove%20the%20user%20from%20the%20exclusion%20group.%3C%2FLI%3E%0A%3CLI%3EConfirm%20the%20app%20is%20added%20to%20the%20device.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EPlease%20contact%20your%20Microsoft%20representative%20if%20the%20issue%20continues%20to%20persist%20after%20the%20redeployment%20of%20the%20impacted%20app%20configuration.%20Samsung%20and%20Microsoft%20have%20a%20close%20cooperation%20on%20this%20issue.%26nbsp%3BWe%20appreciate%20your%20support%20and%20patience%20through%20this%20process.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20have%20any%20questions%2C%20reply%20to%20this%20post%20or%20reach%20out%20to%20Microsoft%20Intune%20Support%20%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2FIntuneSuppTeam%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%40IntuneSuppTeam%3C%2FA%3E%20on%20Twitter.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EAdditional%20information%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EIf%20you%20are%20a%20developer%20using%20Samsung%20products%2C%20you%20can%20find%20more%20detailed%20information%20here%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.samsungknox.com%2Fdev%2Fknox-sdk%2Ftima-ccm-keystore-deprecation.htm%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EDeprecation%20of%20TIMA%2FCCM%20Keystore%20support%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.samsungknox.com%2Fdev%2Fknox-sdk%2Fkbas%2Fkba-642-tima-ccm-keystore-andoid-12-update-app-issue.htm%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EApp%20fails%20to%20retrieve%20CCM%20certificate%20after%20Android%2012%20OS%20upgrade%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.samsungknox.com%2Fdev%2Fknox-sdk%2Fabout-keystores.htm%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ETIMA%20Keystore%20dev%20guide%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CDIV%20class%3D%22lia-message-body-wrapper%20lia-component-message-view-widget-body%22%3E%0A%3CDIV%20id%3D%22bodyDisplay%22%20class%3D%22lia-message-body%22%3E%0A%3CDIV%20class%3D%22lia-message-body-content%22%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EPost%20updates%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E03%2F02%2F22%3A%20Added%20update%20text%20at%20the%20beginning%20of%20this%20post.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E06%2F06%2F22%3A%20Updated%20content%20and%20workarounds.%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-3039834%22%20slang%3D%22en-US%22%3E%3CP%3ERead%20this%20post%20to%20learn%20more%20about%20a%20known%20issue%20about%20missing%20certificates%20after%20updating%20Samsung%20work%20profile%20devices%20to%20Android%2012.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3039834%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%20Customer%20Success%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EKnown%20Issue%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Jun 06 2022 03:34 PM
Updated by: