I’m losing my mind here. My MacBook Pro M1 got locked through Hexnode, I used the unlock code they gave me, but the device still isn’t checking in. I can’t log in, can’t update the password, and all the actions are stuck pending. Support told me to restart, switch networks, open the Hexnode app, and sync..but nothing works. I even asked about disenrollment, and they said forced disenrollment removes it from the portal but might not execute if the device is offline. What’s the point then? I’m stuck with a useless laptop!
19 Views
Replies (3)
Marked SolutionPending Review
Participant
2 days ago
Jan 17, 2026
Marked SolutionPending Review
I had something similar with my team’s Macs. Forced disenrollment looked scary, but once we did it, the device dropped out of the portal and we could re-enroll it fresh. It didn’t fix the pending actions, but it gave us a clean slate for a new user. Maybe that’s the way forward here.
Marked SolutionPending Review
Participant
2 days ago
Jan 17, 2026
Marked SolutionPending Review
Sounds like the device isn’t communicating with the UEM at all. If it’s offline or blocked from syncing, no commands will push. That’s why your unlock worked locally but nothing else is happening. Did you check if FileVault was enabled? If so, the recovery key might be your only way back in.
Marked SolutionPending Review
Hexnode Expert
2 days ago
Jan 17, 2026
Marked SolutionPending Review
Thank you all for your valuable input.
Since the device wasn’t checking in, no remote actions could execute. Forced disenrollment removed the MacBook from the Hexnode portal, but because the device was offline, those commands didn’t apply locally. The workaround is to use the FileVault recovery key if enabled, or otherwise re-enroll the device manually. Once disenrolled, the MacBook can be set up again for a new user, as confirmed by your teammate. In short: forced disenrollment clears the portal record, and re-enrollment is the path forward.
Regards,
Mary Romero
Save
