We have a few test devices that were used during our initial Hexnode setup. Some of them are no longer available and are not checking in with MDM anymore. They show as Disenrollment Initiated, but I still want to clean them up from the portal. Is there a way to remove these devices manually when they can’t be contacted?
10 Views
Replies (4)
Marked SolutionPending Review
Hexnode Expert
2 days ago
Jun 01, 2026
Marked SolutionPending Review
Yes. If a device is in the Disenrollment Initiated state and can no longer be contacted, you can mark it as disenrolled from the Disenrollment Pending Devices report.
Steps:
- Go to Reports > Device > Disenrollment Pending Devices.
- Select the devices that you want to remove.
- Click Actions and select Mark as Disenrolled.
This updates the device status in Hexnode and removes the pending disenrollment entry from the portal. This is useful for devices that are offline, lost, retired, or otherwise unable to complete the normal disenrollment process.
Best Regards,
Isabel Lora
Hexnode UEM
Marked SolutionPending Review
Participant
2 days ago
Jun 01, 2026
Marked SolutionPending Review
That’s exactly what I needed. These were mostly demo devices that we used before our actual deployment, and a few of them are not physically available anymore.
Marked SolutionPending Review
Participant
2 days ago
Jun 01, 2026
Marked SolutionPending Review
Just to add, this does not send a command to the device again, right? It only clears the pending disenrollment state from Hexnode?
Marked SolutionPending Review
Hexnode Expert
2 days ago
Jun 01, 2026
Marked SolutionPending Review
Correct. Mark as Disenrolled is used when the device cannot complete the disenrollment workflow by communicating back to Hexnode. It does not require the device to be online. It is mainly a portal-side cleanup action for devices already pending disenrollment.
Best Regards,
Isabel Lora
Hexnode UEM
Save
