What did I do wrong when adding a DEP account to Hexnode?Solved

Participant
Discussion
10 months ago Jan 13, 2026

Let me get straight to the point here, we’re trying to add a DEP account in Hexnode and we followed all the steps exactly as documented. Below is the flow I followed.

Provided an account name and downloaded the PEM file from Hexnode.

Signed into ABM, created the MDM server, uploaded the PEM file, and downloaded the MDM server token.

But when I upload the server token back in Hexnode, it throws an error saying Invalid token.

I’m honestly confused because everything I did was by the book. People, am I missing something here or doing anything wrong?

Replies (4)

Marked SolutionPending Review
Participant
10 months ago Jan 13, 2026
Marked SolutionPending Review

@remy-parker , the steps you mentioned are correct only. But sometimes this error comes from small things. Just double-check one thing. In a few cases, naming causes issues. Make sure the name you used in Hexnode and the one in ABM are exactly the same and try again.

Marked SolutionPending Review
Participant
10 months ago Jan 13, 2026
Marked SolutionPending Review

@leo_scott, to be on the safe side I already used the same name in both Hexnode and ABM, but I’m still getting the same error. Also, I feel it’s not naming related because neither Apple nor Hexnode docs mention anything about this Invalid token issue.

Marked SolutionPending Review
Participant
10 months ago Jan 13, 2026
Marked SolutionPending Review

@remy-parker , your steps look fine. I’ve seen this error pop up in some cases even when everything is done correctly.

A couple of things to check. Make sure you didn’t upload a different token file by mistake. Also ensure there are no connectivity issues while uploading. One important thing, after uploading the token, wait a minute before moving to the next step. Try doing it slowly and see if it works.

Marked SolutionPending Review
Participant
10 months ago Jan 13, 2026
Marked SolutionPending Review

@pepijn, thanks a lot mate. That was it. I uploaded the token, waited for a bit, and then continued. The error is gone now.

Save