ADE sync failed in Hexnode after Apple Business Manager token issueSolved

Welcome to the Hexnode Community. Yes, this type of ADE sync failure is commonly resolved by renewing the Apple Business Manager server token and uploading the renewed token to Hexnode.

Renewing the ADE server token does not remove or unenroll devices that are already enrolled in Hexnode. It restores the connection between Apple Business Manager and Hexnode so that ADE device assignments and sync operations can continue.

To renew the token:

1. Log in to Apple Business Manager.
2. Go to the Devices section.
3. Open Management from the sidebar.
4. Under Device Management Services, select the MDM server used with Hexnode.
5. Click the ellipsis icon in the top-right corner.
6. Select Download Token.
7. Confirm the prompt that says downloading a new server token will reset the existing one.
8. In Hexnode, go to Admin > Apple Business/School Manager > Automated Device Enrollment.
9. Upload the new server token file for the corresponding ADE account.

After the token is uploaded, run or wait for the ADE sync again. The sync should resume once the renewed token is accepted.

The Apple Business Manager prompt says downloading a new server token will reset the existing one. That wording made me hesitate. Does “reset” mean devices already assigned to the MDM server will lose their enrollment?

No. In this context, “reset” means Apple invalidates the previous server token and generates a new token for the same MDM server connection. Existing enrolled devices are not wiped, unenrolled, or removed from management because of the token renewal. The main impact is that Hexnode must have the latest token to continue syncing ADE data from Apple Business Manager. Until the renewed token is uploaded, ADE sync may fail and newly assigned devices may not appear or update correctly in Hexnode.