20 Views
If a device is not actively checking in with Hexnode UEM, the disenrollment command may remain in the initiated state because the device has not received or executed the command.
For devices that are no longer communicating with the portal, you can force-remove them by marking them as disenrolled:
This removes the device records from the Hexnode UEM portal and frees up the associated device licenses.
Use this option only when you are sure the devices do not need to complete the normal disenrollment flow through check-in. If the devices are online and expected to communicate with Hexnode, allowing them to check in and complete the command is the cleaner approach.
Regards,
Mary Romero
Don't have an account? Sign up
What's new 
