Generally, mobile devices used for work have built-in cameras and support Google Play Services. However, in a few organizations, such as those related to Defence and high-security red zones, devices with cameras are prohibited for security reasons. Google Play Services may also not be supported in specific devices or regions. In some cases, a device may not support both. For management of these devices using MDM, different enrollment methods are available to suit each case. The cases and methods have been discussed below.
This method is recommended for Device Owner provisioning only when the Android device cannot be provisioned using Near-Field Communication (NFC). This Android provisioning method can also be used for enrolling devices without Google Services as Device Owner (fully managed corporate device). As the name suggests this method uses Android Debug Bridge (or ADB) to provision devices as Device Owner and is applicable for devices running 5.0 or later versions.
In this case, the devices can be enrolled using EMM Token Enrollment, Android Debug Bridge (ADB), or Near-Field Communication (NFC) methods. Prior to enrollment, on the MDM console, navigate to Enrollment->ME MDM app (under Android), set Communication Type to Periodic, and save the changes.
These device can be enrolled using any of the enrollment methods listed here.
NOTE:
Android devices that do not support Google Mobile Services can be added via NFC enrollment or Android Debug Bridge(ADB) enrollment methods. To enroll devices running android 9.0 and above via EMM Token enrollment, contact Support.
The following functionalities are also different for these devices: