Android Enterprise enrollment - system apps
The system apps that were installed on the device before enrollment are still installed but suppressed. You can use the enable_system_app package.name script command for each app to allow them to be available.
Assuming you are using the DPC Token or AFW#Mobicontrol enrollment method.
You can avoid this issue altogether by using the Honeywell Enterprise Provisioner application to enroll your devices or by including the android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED=true in your DPC extras string if using another method.
Hope this helps.
sound like you had enrolled the Device over GooLGe Enterprise with Silent enrollment and as Shawn wrote with the enrollment command to Disabel all APPS.
Or how do you enroll your Device?
Open the Enrollment Page from the MobiControl Server and Download the Agent from the Side?
And is there may a Policy /Profile in your instance that disable all Apps or some Apps ?
The default for most AE enrollment approaches is to hide most bundled apps for most device brands. However, some approaches (e.g. QR-code-/NFC-based enrollment using MobiControl Stage Programmer app running on a parent device) allow overriding the default.
Thanks for your answer. We enroll our android devices with Android Enterprise, through AFW#Mobicontrol enrollment method. I'm gonna try to use the script,
Where can I configure the DPC strings ?
See my response to Shawn. Also I've downloaded the INI file from the agent (mcsetup), it shown ''SilentAdminActivation=1''. Does this means it automatically removes all the system apps ? How to disable that
I would highly recommend to use the honeywell enterprise provisioner for enrollment and configuration.
Kind Regards John
Understanding that this happens, has anyone heard the logic behind why this occurs and how it's determined which apps get removed?
I never put much effort into trying to influence it since the other methods for enrollment are faster and result in the system apps remaining enabled. For that reason I find its easier to just not use afw#mobicontrol than to try to manually re-enable system apps after the fact. I think we know why it is happening with the DPC Identifier method (afw#mobicontrol) but we aren't entirely clear on why some apps are affected while some aren't.
Got it. And if anyone else is curious, this occurs over Zero Touch enrollments too (because DPC). What's curious is that if you perform a factory reset and re-enroll, you may see some apps previously disabled during the initial enrollment, suddenly enabled. I've seen this on Zebra handhelds with one of the BT system apps.
I think you can resolve it using this command, get one device without AE enroll to collect the correct apps name and release it by script after the enrollment.
To collect the correct bundle ID you have this script sended by legacy on device tab: identify_acitivity after that look at the logs on the device to get the correct bundle ID. This script will return the app on foreground in the device, you can also use it to collect precisous information about the user behavior.
When you are using Samsung KME you can choose this option like de image:
Jorge Hussni Innovation Manager Soluções & Tecnologia Gestão de Mobilidade Corporativa, Telecom & TI Rua Alvorada, 1289 conj. 404 - Vila Olímpia São Paulo - SP - CEP: 04550-004 T: (11) 4328-7378 C: (11) 975 721 349 E: firstname.lastname@example.org Novo Email! www.safirast.com Novo Site!
in the Meantime i have more Expereienc with the CT40* Devices & Android 10.
As in the Prevously Comments is the Honeywell Enterprise Provisioner verry Helpfull, here you have 3 "Wizard" to set in more or less 10 Steps to Enroll your Android Device with scanning a QR Code.
Factory Resset your Device, Press Start an Scan the QR Code, all will be Setup on the Device.
Wifi, MobiControl Agent will be Downloadend and Enrolled to MobiControl. Disabeling or Enabeling from Apps you can set a Profile in MobiControl.
This Method setup your Scanner as "(Full) Work Managed" no Work Profile ;)
Here you can Download the Software and the Android Update Packages:
Or you use Silent Enrollment from Google then you can Configure ist with this: