What apps can be kept after enrollment?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2023 12:05 AM
Hi everyone
We are using Android Enterprise, and we find out that after enrollment, no matter by scanning the QR code or using ZT, some apps will be removed, even we configured to keep the apps by using this ""android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED":true"
So I want to know, why the apps will be removed and what will be remained? Is there a way for me to predict what apps will be remainded? Like some non entertainment app will be kept, while the others are not?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2023 12:36 AM - edited 09-07-2023 12:37 AM
I assume the starting and ending " are just for the post here, so you use (otherwise change it and try again):
"android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED":true
For those apps are missing there must be somthing to re-enable them after enrollment as our MDM provides such a functionality but can't find it currently in the API documentation. (We prefer to set this to keep this on false and enable what we really need).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2023 12:47 AM
Does your term "re-enable them" mean deploy app via google play policy?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2023 01:13 AM - edited 09-08-2023 01:15 AM
No, our MDM provides a script which can re-enable them. (System apps are disabled not uninstalled so they just get enabled again and available without the need to provide them via play store again).
enable_system_app Allows a system application on the device to be used in the Android Enterprise container. Note: Only applications that are included in the device's firmware can be used in this command. | enable_system_app appBundleID Example To add Google Chrome to the Android Enterprise container: enable_system_app com.android.chrome |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2023 01:09 AM
If your policies are set to Allowlist/whitelist for play instead of black/Blocklist, and your EMM is based on AMAPI, you'll see the apps should be present, but AMAPI will still disable them after enrolment.
If you want it as open as possible, set the app policy for play to block only specified apps. If you want to keep it locked down, find the apps you want to allow on devices and add them as system apps to be enabled.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2023 12:50 AM
As far as I know, the play mode will only affect the apps in the play store, whitelist mode means only apps deployed by admin can be accessed, while blacklist mode means the user can access to all apps, will it also affect the original system apps as well during enrollment? I though this play store mode only takes effect after enrollment
Though I can use the policy to deploy apps, but not all these system apps from the device itself are available on play store, I can't find and deploy it, that is what really troubles me
- Getting issue in Finding Device enrolment status in Admin discussions
- Why Zero Touch enrollment not start automatically? in Admin discussions
- Zero-touch Enrollment Training Status not checked in. in Admin discussions
- Managed Google Play Android enrollment by intune.microsoft.com in Admin discussions
- Changing the Primary Contact for My Company in Admin discussions