ADE device sync failing due to expired server tokenSolved

Participant
Discussion
6 months ago Jan 17, 2026

Hi everyone. Automated Device Enrollment (ADE) stopped syncing devices in Hexnode. The ADE account page shows the server token has expired. What is the correct way to renew the ADE token from Apple Business Manager and update it in Hexnode so device sync works again? Are there any common mistakes to watch out for during this process?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
6 months ago Jan 17, 2026
Marked SolutionPending Review

Hello,

Thanks for reaching out to Hexnode Connect.

If ADE device sync is failing and the ADE account shows an expired token, you will need to renew the server token from Apple Business Manager (ABM) and upload the renewed token into Hexnode.

Here is the exact workflow to renew and update your token:

  1. Download from ABM: Sign in to Apple Business Manager and navigate to Devices.
  2. Select Management from the left pane.
  3. Under Device Management Services, choose the relevant MDM server. (Crucial tip: Make sure you select the exact MDM server that is connected to your Hexnode portal. If the wrong server token is downloaded, the ADE account will not sync).
  4. Click the ellipsis icon in the upper-right corner and select Download Token.
  5. When prompted that downloading a new server token will reset the existing one, confirm by selecting Download server token.
  6. Upload to Hexnode: In the Hexnode portal, go to Admin > Automated Device Enrollment > Accounts.
  7. Hover over the relevant ADE server/account and click Edit.
  8. On the Edit ADE Account page, use Choose File next to Upload Token and upload the new token file you just downloaded from ABM.
  9. Save the changes.

After the renewed token is saved, try syncing your ADE devices again. The sync should start working normally once the active Apple Business Manager server token is updated in Hexnode.

I hope this helps or resolves your issue. Feel free to reach out if you have any more doubts or need further assistance.

Best regards,
George,
Hexnode UEM

Save