I uploaded a new .p7m token for an ADE account into Hexnode UEM, but it’s throwing an error saying, “invalid token.” Has anyone else faced this?
22 Views
Replies (3)
Marked SolutionPending Review
Participant
1 day ago
Feb 19, 2026
Marked SolutionPending Review
We had something similar. Try syncing the ADE accounts manually, sometimes that clears the error right away.
Marked SolutionPending Review
Hexnode Expert
1 day ago
Feb 19, 2026
Marked SolutionPending Review
Hello everyone, thanks for reaching out.
If you’ve already updated the new token but still see the “invalid token” error, it usually comes down to either a caching delay or a mismatch between the token and the account. Please try the following:
- Verify the token matches the correct account: The token you download from a service profile in the Apple Business/School Manager (ABM/ASM) portal must be uploaded to the same ADE account in Hexnode UEM that was tied to that service profile. If there is any mismatch in this, the handshake will fail.
- Manually sync the ADE account: In the Hexnode UEM portal, go to Admin > Apple Business/School Manager > Automated Device Enrollment > Accounts. Either click Sync all ADE Accounts at the top or click the sync icon that appears in the corresponding row of an account when you hover over it. A manual sync often clears the previous error state.
- Allow sync lag: If you’re certain the token is correct, but the error persists, wait about 30 minutes and try syncing again. This delay is usually caused by a sync lag between Apple’s servers and Hexnode.
Regards,
Simon Scott
Hexnode UEM
Marked SolutionPending Review
Participant
1 day ago
Feb 19, 2026
Marked SolutionPending Review
Got it. I’ll double‑check the account and token match, then run a manual sync.
Save
