Android Pie and EHS using MobiControl does not work

L
Leroy
CaptureTech Corporation B.V.

Hello,

We are having issues configuring EHS on a TC52, running Android Pie and build 02-11-01.00-PG-U06 (with update 06), using MobiControl. TC52 are Android Enterprise enrolled using the afw#mobicontrol.

It seem that somewhere access to the /Enterprise/usr folder is blocked when MobiControl is used.

Settings made in enterpsiehomescreen.xml and wallpaper are not imported like on versions before Android Pie

It is not possible to make an export (when APK is installed through MobiControl), see screenshots below:

 

We have pushed a logo and enterprisehomescreen.xml to the /enterprise/usr folder, but when accessing the files using the file browser on the device, the file logo.png cannot be opened.In example below the files are put in the root of the device, where the preview of the png file is there and wallpaper will open like it should.

 

       

Screenshots below are from the /enterprise/usr folder, where the preview of the png file is not there and the wallpaper cannot be opened.

  

Also files cannot be copied from and to /enterprise/usr folder:

If we don’t connect the device to MobiControl and we install EHS manually it works fine, so is probably related to some permission setting in MobiControl.

Does any one has any idea what can be the problem?

Edited 5 years ago
Android
ANSWERS
MD
Matt Dermody Diamond Contributor
5 years ago

I hardly leverage EHS anymore as most of our deployments have migrated to the SOTI Lockdown. With that said, I do find this problem intriguing because a similar situation was encountered recently with custom Enterprise Keyboard layouts not being recognized in /enterprise/ directory either. I'm thinking it might have to do with the specific enrollment method that you employed (DPC identifier). Can you unenroll, factory reset, and then re-enroll one of the devices using the StageNow based enrollment method for AEDO instead and see if that produces any different results? The StageNow method is superior to the dpc identifier anyway as it can perform your whole enrollment process, including connecting to Wifi in a couple of trigger pulls, whereas typing in a dpc identifier and manually connecting to a wireless network is a fairly manual process.