Hey everyone, we recently purchased several iPads, but two are failing to enroll in Hexnode. One shows an error stating it has been “released” from our organization’s ABM, and the other doesn’t appear in the Hexnode portal at all, despite being correctly assigned to the Hexnode MDM service in Apple Business Manager. Does anyone know how to fix this?
19 Views
Replies (4)
Marked SolutionPending Review
Hexnode Expert
4 days ago
Jan 05, 2026
Marked SolutionPending Review
Hi @alice_grey , these are common but distinct enrollment hurdles. For the first iPad, a Released status means the device was permanently removed from your Apple Business Manager pool. To fix this, you must use Apple Configurator on a Mac to manually add the device back into ABM. Once it is re-registered, you can assign it to your MDM server and proceed with the standard setup.
Regarding the second iPad, the delay is likely due to a synchronization gap between your ABM and Hexnode. Even if the assignment is correct in ABM, you often need to trigger a manual sync. Navigate to Admin > Apple School/Business Manager> Automated Device Enrollment in your Hexnode portal and click Sync with ADE to refresh the device list. If it still doesn’t appear, verify that the iPad is connected to a stable Wi-Fi network and perform a factory reset to ensure it checks for the management profile during activation.
Regards,
Elle Reed,
Hexnode UEM
Marked SolutionPending Review
Participant
4 days ago
Jan 05, 2026
Marked SolutionPending Review
@elle_reed , I tried the manual sync for Device 2, but it’s still not showing up in the Hexnode portal. I also checked ABM, and it definitely says it’s assigned to our Hexnode server. Any other thoughts?
Marked SolutionPending Review
Hexnode Expert
4 days ago
Jan 05, 2026
Marked SolutionPending Review
@alice_grey , If a manual sync doesn‘t bring the device in, there are usually three hidden culprits to check:
1. New Terms and Conditions
Apple frequently updates its Business Manager terms. If there is an unaccepted agreement in the ABM portal, Apple will silently block the sync with your MDM. Log into business.apple.com and check for any banners at the top asking you to “Review and Accept” new terms.
2. Expired DEP token
Check the status of your Apple DEP token. If the token has expired (they last 365 days), the sync will fail without a specific error message. You’ll need to download a new token from ABM and upload it to Hexnode to restore the connection.
3. License Count
Finally, verify your Hexnode license. If you have reached the maximum number of devices allowed by your current plan, Hexnode will not pull in new serial numbers from ABM. You can check this under Admin > License.
If none of that work, try unassigning the device in ABM, waiting for a few minutes , and then re-assigning it to Hexnode before clicking Sync with ADE again. This often pokes the API into recognizing the change.
Marked SolutionPending Review
Participant
4 days ago
Jan 05, 2026
Marked SolutionPending Review
That did it! It turned out we had a pending “Apps and Books” agreement in ABM that I hadn’t seen. Once I accepted that and hit “Sync with ADE” again, the device appeared immediately. I’m also downloading Apple Configurator now to fix the “released” iPad.
Thanks so much for the help, @elle_reed !
Save
