I’m testing a silent migration of Windows 11 23H2 devices from another MDM into Hexnode before rolling it out to production. The Hexnode Gateway app installs and appears to run the unenrollment step, but the enrollment only seems to complete halfway.
In the Hexnode portal, the device appears with the correct user and receives policies, but it still has the “Limited” tag, which makes it look like the previous MDM association is still present. On the device, I don’t see the expected Hexnode enrollment parameters in the registry, and there is no active MDM profile visible in Windows settings.
The devices are Microsoft Entra joined and use user-based MDM enrollment assignments. They were set up through Windows Autopilot Device Preparation, not the older Autopilot device registration flow. Autopilot sync in Hexnode also doesn’t show these devices.
Has anyone seen this kind of partial enrollment during Windows silent migration?