The default in Android Enterprise Managed-Device/Device-Owner mode is to hide/disable most apps bundled with the phone.  To re-enable a hidden app , use the script command with the bundle ID of the app as its argument:

 
  enable_system_app    BundleID

Welcome to the fun world of Android Enterprise!

do i send that script to the device or what do you mean? 

Yes. So example would be you noticed your Samsung Email Client is missing.  So send:

enable_system_app com.samsung.android.email.provider

** If you use Samsung KME you can allow the system apps to stay in with Enterprise App. You just have to create your enrollment profile a tad different than you would for a standard Enterprise enrollment.

Also if you plan to use AFW then you will also get an enterprise agent enrollment with that so what I do there is create a package with just scripts of the system apps I want enabled as soon as it pushes the profile.

Does anyone happen to know what the Camera equivalent? I've tried a few things and nothing seems to have worked and there seems to be virtually nothing online about it.

Another question, I tried sending the email example script to a pre-enrolled phone and the email app hasn't appeared. Do these scripts have to be deployed at time of enrolment?

I'm using Samsung A6's (SM-A600FN).

Any advice would be really helpful! 

They don't need to be sent at the time of enrollment but they do need to utilize the specific BundleId value. Given that it is a Samsung device there are likely to be a number of Samsung specific applications that would have a different BundleId than what you would find in stock AOSP or GMS builds of Android. To re-enable the Samsung Email app you would need to know the Samsung specific BundleId for that app. I'm not aware of any way for gleaning those app BundleIds from SOTI after the device has enrolled as they are not reported to the SOTI server at that point. You may have to use ADB on an unconfigured device for pulling all the BundleIds. 

adb shell pm list packages  should give you what you're looking for:

Thanks Matt. It took me a while to figure it out but it worked in the end and I've managed to re-enable the camera on the Samsung A6's.

If anyone else stumbles across this post the BundleID for the camera package (at least in this instance) was:

com.sec.android.app.camera

The bundle-ID of all hidden/uninstalled apps in an Android-Enterprise device just enrolled can easily be found by looking into the "installed application" tab of that device in the web console.

I may be mistaken, but I feel like the last time I checked, the hidden/disabled applications weren't actually reported in the Installed Applications list in MobiControl until I enabled them. 

Hi Daniel,

For info, I apply this in a script via a package for my samsung tablets and smartphones:

; Enable Samsung OEM applications that were disabled by Android Enterprise
enable_system_app com.android.mms
enable_system_app com.sec.android.app.myfiles
enable_system_app com.samsung.android.providers.contacts
enable_system_app com.sec.android.widgetapp.easymodecontactswidget
enable_system_app com.sec.android.app.camera
enable_system_app com.sec.android.gallery3d
enable_system_app com.sec.android.app.voicenote
enable_system_app com.sec.android.app.popupcalculator
enable_system_app com.sec.android.app.clockpackage
enable_system_app com.sec.android.app.magnifier
enable_system_app com.sec.android.daemonapp
enable_system_app com.samsung.android.app.memo
enable_system_app com.samsung.android.messaging
enable_system_app com.samsung.android.calendar
enable_system_app com.samsung.android.app.notes
enable_system_app com.samsung.android.weather
enable_system_app com.samsung.android.app.galaxyfinder
enable_system_app com.samsung.android.app.reminder
enable_system_app com.samsung.android.lool
enable_system_app com.diotek.sec.lookup.dictionary

Only re-enable the ones you want of course :)

John.

This is a great thread, I was banging my head trying to get Gallery back and couldn't figure out why it wasn't there.

I appreciate the script but I can't figure out how to send it as a package. Each individual line, of course, can be sent directly tot he device but how to do ti all at once? In Package Studio I see where to specify preinstall scripts, is that where? Or do I create a text file with the script contained inside? But then how do I build a package, do I add a file (instead of an .apk)? What format is the file?

Thanks,

Matt

You can basically create an empty Package with no files whatsoever and then have a script containing all of the lines together. In both the integrated send script option and the Post/Pre Install scripts within a package you can have multi-line scripts. Because it is an empty Package containing just the scripts it doesn't matter if you use a Pre or Post Install script for your purpose, although I usually opt for  Post-Install script for consistency. 

Thanks for your reply Matt.

I was told specifically by SOTI that it is not possible to send multiple commands at once via the console send script feature. So much for tech support.

As for the package, I still don't know what format the file needs to be, is it .txt? ps1? js? or no extension at all?

I have other scripts that I typically send when configuring a new device (Samsung Tab S4), I disable Dex and Max Power Save modes, sending them via package would save me a lot of time and prevent the "oops I forgot to send the script" face plant that happens from time to time LOL

Best,

Matt

Hi Matt,

I don't know which Soti guy gave you that seemingly inaccurate answer.  In general, it is perfectly OK  to send multiple commands at once via the console send script. I have successfully sent scripts with 100-120 lines via console send script.  However, it is true that not the whole set of script commands are supported in all scenarios requiring scripts in MobiControl.  

I usually use .cmd as the file extension of the MobiControl script included in .pcg package and other scenarios using scripts.  This works perfectly for me in the last few years in every occasion, such that I don't have the need to check if there is any other better file extension choice.

Depending on what enrollment method your using you can utilise the following line to leave system apps enabled:

android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED=true

This has been copied from our NFC enrollment but I believe to change this for QR enrollment it simple changes to:

'android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED:"true",

Wow, great tip. 

Hi Adam,

Where are you applying this script? I have tried it in the console section of the device (remote control) and also sending as a script via the console. Neither script is having any effect on my Zebra MC93 devices. 

Thanks,

Hi Paul,

This line is present within our NFC enrollment cards, if the devices are already enrolled within MobiControl I believe you will need to run the scripts provided by John Aiston above.

We originally used these these scripts to restore the apps we required but then found we can automate the restore of apps via the line I provided during enrollment process.

Thanks,

Adam

En Samsung con Android 9, los siguientes casos no funcionan:

enable_system_app com.sec.android.app.popupcalculator
enable_system_app com.samsung.android.app.notes

En Android 8 funcionan correctamente. Los programas se llaman igual en ambas versiones de Android.

¿Alguna solución?

This script also works in Zero-Touch setup, DPC Extras.

android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED=true