What's new 
A Windows device was removed from the Hexnode portal, but re-enrollment still will not complete due to stale local data. Is there a specific permission change needed, or is there another local cleanup step for stale Hexnode endpoint files?
10 Views
Replies (1)
Marked SolutionPending Review
Hexnode Expert
2 weeks ago
Jul 22, 2026
Marked SolutionPending Review
Hi @jimena,
Stale Windows MDM enrollment data can remain locally on the device even after the device no longer appears in the Hexnode portal. This can block a fresh enrollment attempt.
For this scenario, check both of the following on the affected Windows device:
- Open Registry Editor as an administrator and review:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments - Remove the old enrollment entries associated with the previous MDM enrollment, if they can be deleted.
- On the C: drive, remove leftover Hexnode endpoint-related local files or folders, especially the
OMADfolder if it is present. - Retry the Hexnode enrollment.
Regards,
Sienna Carter
Hexnode UEM
Save