27 Views
This can happen if the device has pending MDM commands in its queue. Hexnode sends the disenroll command to the device, but the device processes queued commands in order when it checks in and has an active network connection.
If the affected devices have checked in recently, allow a few minutes for the queued commands to complete instead of repeatedly triggering the action. Re-sending the same action multiple times may not make the device process it faster.
Recommended checks:
1. Confirm that the device has a recent check-in time.
2. Make sure the device is online and not restricted from communicating with the MDM server.
3. Wait a few minutes and refresh the device status in the Hexnode portal.
4. Confirm whether the device gets removed from management after the command queue is processed.
In similar cases, the disenrollment completed successfully after the pending MDM commands were processed.
Regards,
Mary Romero
Don't have an account? Sign up
What's new 
