Can any one plese address this query ?.

As I don't have any CT50 device or EZ Config to do any test, I can only share the general idea what I would try if I were you.

Directory access permission has always been a limitation for some MobiControl policies such as pcg deployment, file-sync rules, etc.  This is unavoidable as MobiControl device agent is not a kernel module but just an ordinary app that  can initiate calls to   some specialized EMM API to kernel modules to perform some limited supervisory tasks.  

You can use web-console to send copy script command to the device to test which internal directory on CT50 can be written by Mobicontrol device agent.  Then you can check if EZ Config/XMLConfig can use the xml file in that directory to configure you device.  If so,  re-create you .pcg package with this new directory found to have no access permission issue.

I've had luck just placing the xml file(s) in /sdcard/honeywell/persist - After placing files here and restarting the device, the settings take effect.

check this article for more info:

https://support.honeywellaidc.com/s/article/Persistent-scanner-and-wedge-settings-on-Android-Devices

Also... If persistence is not an absolute requirement for your use case, you can also apply the xml files via soti script/intent (still requires pushing the file, and is path/case sensitive):

https://support.honeywellaidc.com/s/article/How-to-run-DeviceConfig-with-a-SOTI-MobiControl-script-on-an-Android-device

Hi Sherry,

You can use File Sync rule, where you will specify where exact location you need the file in the device. 

You will have to put the config files into the server via Content Library. so when you will push the files via fileSync it will pull it from directly from the server. 

For example : %sdcard%Honeywell/Persist

%sdcard% is the macro used for internal storage.

This will resolve the issue.

Thank you.