Hi @bram,
Yes, this is expected behavior. On Windows, if a device is enrolled into MDM using a local user account, the enrollment context is tied directly to that specific user profile. The MDM enrollment certificates and related registry entries are associated with the account that performed the enrollment. If that original local account is deleted, Windows breaks or removes the MDM enrollment profile.
A device wipe is not required. You can restore management by simply opening the Hexnode enrollment URL on the device and installing the MDM profile again.
Managing Duplicate Records
Please note that re-enrolling the Windows device will create a new device record in Hexnode. After re-enrolling:
- Go to Manage > Devices in the Hexnode UEM portal.
- Identify the newly enrolled entry that is checking in correctly.
- Delete and disenroll the old, non-working duplicate entry (the one showing “MDM profile removed“).
Preventing This on Other Devices
If the enrolling local account is deleted, re-enrollment is the only option to restore management. For the other laptops that are still enrolled and syncing, do not delete the local account that was used for enrollment unless you are prepared to re-enroll the device and clean up the duplicate records afterward.
Best regards,
Eden Pierce
Hexnode UEM