How to Test Device Enrollment Using TestDPC on ZTE(Zero Touch Enrollment) Devices

TestDPC is used to validate whether a ZTE device can be successfully enrolled using the standard Android Enterprise APIs. It helps isolate whether an enrollment issue is caused by the device or OEM implementation, or by the EMM solution. If enrollment succeeds with TestDPC but fails with the EMM solution, the issue is likely related to the EMM configuration or implementation. If the issue is reproduced with TestDPC, it indicates a device or Android Enterprise limitation.

Purpose

The purpose of this article is to provide a guide on how to perform enrollment using TestDPC on ZTE devices to verify the enrollment. 

Prerequisites

ZTE portal access, and the device should be present in ZTE.

Steps

1. Log in to the ZTE Portal using your credentials.
2. Navigate to the Configuration section and click Add New.
3. Enter a Configuration Name and select TestDPC as the EMM DPC.
4. Leave the DPC Extras field empty and save the configuration.
5. Assign the newly created configuration to the affected device.
6. Factory reset the device and complete the initial setup.
7. During the setup process, verify that the device is enrolled as a Device Owner using TestDPC.
8. If the device does not receive the assigned configuration, verify the following:
   1. Ensure the device model and serial number/IMEI are correctly added to the ZTE portal.
   2. Confirm that the device’s OS build supports ZTE Zero-Touch/enterprise enrollment.
   3. Check for any synchronization or configuration assignment issues in the ZTE portal.
9. If the device enrolls successfully with TestDPC but fails when using the MDM solution, in such cases, contact techsupport@42gears.com and provide the device logs, configuration details, and the observed behavior for further investigation.

Conclusion

If the device successfully enrolls with TestDPC, it confirms that Android Enterprise provisioning on the device is functioning correctly. This helps isolate whether the enrollment issue is related to the MDM solution or to the device, its firmware, or the OEM enrollment configuration.

Need more help? Here’s how to get help from our experts. 

CONTACT US