What device agent and enrollment procedure were you using?   Were the results similar when you used another (say older) device agent?

I don't have your hardware to do any tests.  However, I think you need to provide at least the following information for anyone else to help or comment:

- MobiControl agent version and build numbers

- Device firmware version

- MobiControl server version and build number

- MobiControl agent version and build numbers

    14.1.4 Build 1010

- Device firmware version

    Brand ZEBRA  Model ET5X

    Security Patch August 5,2018

    Kernel version 3.14.55-x86_64+

    Build Number 03-21-20-M-0R-M1-U00-STD

    Android version 6.0.1 (NON-GMS version)

- MobiControl server version and build number

    SOTI MOBICONTROL version 15.0.2.1049

Hi Rathasatekun,

Thanks for posting your query!

Can you please confirm if you have downloaded the right MobiControl agent on the ZEBRA ET50 device? If not, please select the first option - Zebra, as shown below and try enrolling it again.

Not sure about 14.1.4 but I can confirm that agent 14.1.1.1003 had a MAJOR bug that after a specific combination of feature control profile with wifi profile assigned caused the agent to crash (and then enter a continuous crash/restart loop), essentially causing the device to be orphaned from the server.  Manual intervention to disable WiFi on the device was required to get the agent to an operational state.  I orphaned about 500 devices before I realized what was happening.  Major PITA.  Agent 14.1.6 contained the fix.