Enrollment on Intune disabling Android systems app
Hello everyone, Some explanation first: We use some handheld Unitech EA520 rugged smartphones with built-in scanners and when i enroll these into Intune, half of the built-in system apps are disabled. This includes the Unitech scanner service which is used to control the scanner. When i check under system apps on the device it says "Not installed for this user". I haven't setup any restrictions ofr the device yet and when i do, there is no possibility to enable these system apps. Even weirder is that i enrolled 5 of the exact same devices with same android version about half a year ago and they had no issues what so ever. These are also fully dedicated, company owned devices. Did anyone experience something similar before, as i am quite stuck ?
OneDrive won't sign out users on Android multi-user kiosk mode
Hello, We are trying to configure multiple tablets to be used at a multi-user level in kiosk mode. The devices we're working on are running Android 11 and are model SM-T220. We have enrolled these devices with the Corporate-owned dedicated device enrollment profile and have created a specific configuration profile for the tablets' intended use. One issue we are running into is when a user is logged out and another signs in, the old user's OneDrive account continues to stay logged in where it can be accessed when another user signs in. Looking to see how access to other users' OneDrive accounts can be made inaccessible when logged in with another account. Thank you, Jess
Outlook and MSLauncher crashing if intune is also installed on a x86/x86_64 Android 11 device
We are running into an issue with Intune and Android 11 on our x86_64 devices. The devices are still in test but issue was also reproduced on a chromebook. More specifically, if Intune is installed along with Outlook or Microsoft launcher, then both these apps crash upon launch on Android 11 x86_64. Without Intune, they work fine. You just have to install Intune …don’t need to register the device or anything to get the crash. Our devices are x86_64 based and when we install Microsoft launcher/Outlook, we get an ARM version of the app from playstore. The ARM emulator( houdini ) in our device makes this work. But with Intune also installed, they crash. Without Intune, they work fine on our Android 11 x86_64 device For apps where playstore gives us a x86_64/86 version of the app, they work fine with intune. word/excel/teams etc all work fine with intune on our Android 11 x86_64 device. I have also reproduce the problem on a Chromebook ( HP Chromebook x360 ) if the underlying android image it uses is Android 11 to run android apps….so it is not just our device showing this issue. I believe any x86_64/x86 based Android device will show this issue on Android 11 with the ARM emulator. Following is the crash from adb log. Please note that device encryption is enabled and other apps like word/teams/excel do not show this issue. Only arm based apps ( outlook/mslauncher ) are showing this issue. I also do not understand why playstore is giving us arm version of outlook when an x86_64 version is also available. Also would like to mention that this issue is not seen on a Android 9 x86_64 device. 03-31 11:48:17.937 2057 2057 D AndroidRuntime: Shutting down VM 203-31 11:48:17.937 2057 2057 E AndroidRuntime: FATAL EXCEPTION: main 303-31 11:48:17.937 2057 2057 E AndroidRuntime: Process: com.microsoft.launcher, PID: 2057 403-31 11:48:17.937 2057 2057 E AndroidRuntime: java.lang.RuntimeException: Unable to instantiate application com.microsoft.launcher.LauncherApplication: java.lang.IllegalStateException: MAM was unable to initialize file encryption with error 0x3a1540200000026 503-31 11:48:17.937 2057 2057 E AndroidRuntime: at android.app.LoadedApk.makeApplication(LoadedApk.java:1268) 603-31 11:48:17.937 2057 2057 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6686) 703-31 11:48:17.937 2057 2057 E AndroidRuntime: at android.app.ActivityThread.access$1300(ActivityThread.java:237) 803-31 11:48:17.937 2057 2057 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913) 903-31 11:48:17.937 2057 2057 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106) 1003-31 11:48:17.937 2057 2057 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223) 1103-31 11:48:17.937 2057 2057 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7660) 1203-31 11:48:17.937 2057 2057 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 1303-31 11:48:17.937 2057 2057 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592) 1403-31 11:48:17.937 2057 2057 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947) 1503-31 11:48:17.937 2057 2057 E AndroidRuntime: Caused by: java.lang.IllegalStateException: MAM was unable to initialize file encryption with error 0x3a1540200000026 1603-31 11:48:17.937 2057 2057 E AndroidRuntime: at com.microsoft.intune.mam.client.ipcclient.MAMClientImpl.initialize(MAMClientImpl.java:285) 1703-31 11:48:17.937 2057 2057 E AndroidRuntime: at com.microsoft.intune.mam.client.ipcclient.MAMClientSingletonImpl.ensureInitialized(MAMClientSingletonImpl.java:74) 1803-31 11:48:17.937 2057 2057 E AndroidRuntime: at com.microsoft.intune.mam.client.app.ApplicationBehaviorImpl.attachBaseContext(ApplicationBehaviorImpl.java:115) 1903-31 11:48:17.937 2057 2057 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 2003-31 11:48:17.937 2057 2057 E AndroidRuntime: at com.microsoft.intune.mam.InterProxy$InterInvocationHandler.invoke(InterProxy.java:88) 2103-31 11:48:17.937 2057 2057 E AndroidRuntime: at java.lang.reflect.Proxy.invoke(Proxy.java:1006) 2203-31 11:48:17.937 2057 2057 E AndroidRuntime: at $Proxy6.attachBaseContext(Unknown Source) 2303-31 11:48:17.937 2057 2057 E AndroidRuntime: at com.microsoft.intune.mam.client.app.MAMApplication.attachBaseContext(:11) 2403-31 11:48:17.937 2057 2057 E AndroidRuntime: at androidx.multidex.MultiDexApplication.attachBaseContext(:1) 2503-31 11:48:17.937 2057 2057 E AndroidRuntime: at com.microsoft.launcher.LauncherApplication.attachBaseContext(:2) 2603-31 11:48:17.937 2057 2057 E AndroidRuntime: at android.app.Application.attach(Application.java:351) 2703-31 11:48:17.937 2057 2057 E AndroidRuntime: at android.app.Instrumentation.newApplication(Instrumentation.java:1159) 2803-31 11:48:17.937 2057 2057 E AndroidRuntime: at android.app.LoadedApk.makeApplication(LoadedApk.java:1260) 2903-31 11:48:17.937 2057 2057 E AndroidRuntime: ... 9 more