No Matches Found!
Try with a different search term
Hi,
has anyone experienced difficulties in enrolling a device such that it becomes "Non-Compliant"? This is a Zebra TC21, running Android 10, MX 10.4. Enrollment fails, the device DOES end up in the device list however, but cannot be controlled via Soti at all. The enrollment process on the device gives an error.
We've tried to enroll on the latest version of the Soti Mobicontrol server, as well as on 15.4.
Regards,
Daníel
Did you use OEM Specific (Zebra in your case) device agent or generic Android-Enterprise device agent to enrol your device? According to the information found at the URL
https://androidenterprisepartners.withgoogle.com/device/#!/DrawkKSTqKaRia3Fg9yP
your device running Android 10/11 should have no problem getting enrolled as AE device.
If the device get enrolled with a new device icon added in your web-console, what are the active MDM api's reported in the device information tab for the enrolled device, even though it is totally out-of-control as you said?
Have you successfully any other Android-Enterprise devices (i.e. different brand or model) onto your MobiControl server? If so, are there many such devices and what are their brand/model(s)?
You also need to check your add-devices rule policy to confirm that the device platform as well as various advanced options are properly set. Otherwise, you might get error related to compliance check.