Guys

Solution found... 

When using Google enterprise Agent on Zebra android device you have 2 choices :

- using Google enrollment process (not simple)

- using Zerba StageNow

If you don't use 1 of these methods, you agent is defined as DA and DO ... Which is causing troubles.

Thx for your support.

Hello steve,

perhpas black list the app camera on the profile ?

If the camera is present on the lock screen , change the lock screen to none ..

this is what I tried ... without success.

It seems that using Entrprise Enrollment (&profile) blocks some features of SOTI.

Any other idea ?

This is abnormal.  What are the version & build numbers of your device agent and your MobiControl server?

Is there any difference if you reboot the device after deploying the profile with the new feature control options?

Agent Version   13.6.0

Agent Build      1844

Rebooting device does not help

SOTI Version is the last one (Cloud)

So I know on Samsungs I had to put 2 in the application run control:

com.sec.android.app.camera

com.sec.factory.camera

And then Raymond was kind enough to help me with a script on removing the Camera launcher off the lock screen because I had about 1K units I had to do and didnt want to go in and manually take each one off.

Dumb question, but did you create the SOTI Profile as an Android Enterprise or Android Plus profile? You'll need to create it as an AE profile for it to apply to an AEDO device. 

With it being an Oreo TC52 I would venture to bet that it enrolled as Android Enterprise Work Profile instead of Work Managed (DO) and not Android+ (DA). Work Profile devices are managed under a BYOD use case and therefore you have much less configurable control than you would over a COSU/Dedicated Device use case using Work Managed (DO). 

Hi Steve,

Maybe you can save yourself much time for debugging similar problems in the future if you first check the active MDM API from the device agent "configuration" tab or from device's information tab on the MobiControl web-console.   Most of the policies required for enterprise use are supported only in the managed-device mode (also called device-owner mode), which will be reported as "Android for Work Managed Device" in the active MDM API field.