Android devices still restricted after disenrollment from HexnodeSolved

Participant
Discussion
9 hours ago Aug 31, 2026

I disenrolled several Android devices from Hexnode, but the devices still look managed. The Hexnode app is still there and the restrictions are still active, so users cannot remove apps, install new apps, or add email accounts. The devices are not showing under Disenrolled Pending Devices anymore. Is there any way to remove the remaining Hexnode configurations from the Android devices without formatting/factory resetting them?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
2 hours ago Aug 31, 2026
Marked SolutionPending Review

For Android devices, disenrollment removes management policies and configurations only when the device receives and processes the disenrollment command from Hexnode.

A few points are important here:

1. The device must be online and actively checking in with Hexnode when the disenrollment action is initiated.

2. If the device is offline, turned off, disconnected from the internet, or not syncing with Hexnode, the policy removal command may not reach the device.

3. For managed apps, the policy option to remove apps on policy removal must be enabled before disenrollment if those apps should be removed automatically.

4. If the device has already been fully removed from the Hexnode portal and it is no longer listed under Disenrolled Pending Devices, Hexnode can no longer send remote cleanup commands to that device.

In that situation, if the Android device is still enforcing MDM restrictions and cannot be cleaned up from the portal, the reliable way to remove the remaining management configuration is to factory reset the device directly.

For future disenrollments, keep the device online, confirm it is checking in, enable app removal settings where required, and wait for the restrictions to be removed before deleting or fully removing the device from the portal.

Regards,

Mary Romero

Save