What can I do if device enrollment fails in Hexnode UEM?
This article will guide you with the necessary steps that should be taken if device enrollment fails in Hexnode UEM.
Solutions to Common Device Enrollment Failures
- Try connecting the devices to a different network connection. The devices need an active internet connection to communicate with the Hexnode UEM server.
- If the allowed device limit for enrolling devices in the portal is reached, try disenrolling the inactive devices in the portal. This will give you extra slots for enrolling other devices.
- For iOS devices, try uninstalling the Hexnode MDM app from the device and then reinstall it. Check out the most common errors encountered during iOS enrollment and their possible remedies. Refer to the documentation for troubleshooting errors while enrolling iOS devices using Apple Configurator or Apple Business Manager (ABM).
- For Windows devices, try removing the Work or School account and add the account again. Make sure that the user has chosen ‘Enroll in Device Management only’. For more details, refer to the troubleshooting guide on Windows enrollment failures.
- For Mac devices, make sure the device platform (macOS) is not restricted under Enrollment Restrictions (Enroll > Settings). Also, ensure that an APNs certificate is configured on the Hexnode portal. Check out the documentation for troubleshooting errors encountered during ABM enrollment. Also, have a look at the possible solutions regarding other failures during Mac enrollment.
- For Android devices, verify that the ports 5228, 5229, and 5230 are open on the Firewall to establish the communication between the devices and the FCM. Also, check out the common errors occurring in Android Enterprise and G Suite enrollments.