I will try out the Honeywell UEM Connect tomorrow and then report back here in the forum.

Not sure if i get your issue correctly here, may i ask you to write me via PM in german the exact issue you see?

But i guess enrollment folder is different then the final one?
So the configurations are all Android Enterprise profiles and all also assigned to the relevant folder(s)?

Also not sure I got the question...but, if you managed to make the configuration load from the Honeywell folder I assume you used a script with sendintent to load it. (eg. sendintent -b "intent:#Intent;action=com.honeywell.ezconfig.intent.action.IMPORT_XML;S.path=/sdcard/honeywell/DeviceConfig.xml;launchFlags=0x1400020;end").

Do you have the same script running via Android Enterprise (never done one like this, so not sure how the setup works)? Also, as far as I understand you need the files to be placed in the Honeywell folder and they need to the have the proper naming with "DeviceConfig.xml" at the end if renaming it (e.g. "xxxx_DeviceConfig.xml" - allowed, "DeviceConfig_xxxx.XML" - not allowed). 

Hi Sascha, 

would recommadn to use a App Policy and set the Device settings over the "Honeywell UEM Connect"

You can use a Profile to upload the file to the Device but then you have to apply the Config with an intent command to the Device.

Managing with Hoenywel UEM Connect of the App Policy applys the changes after the next sync to the Device and you do not have to create a XML file from the Enterprice Provisioner.