Windows 11 silent migration shows partial enrollment with Limited tagSolved

Participant
Discussion
1 month ago Oct 10, 2026

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?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
1 month ago Oct 10, 2026
Marked SolutionPending Review

Hi @remi,

For Windows silent migration, the “Limited” tag usually indicates that Hexnode has received some device information, but the device has not completed full MDM enrollment into Hexnode.

A few points are important in this scenario:

1. If the device receives policies but still shows as Limited, verify whether Windows itself shows an active MDM profile for Hexnode under the work or school account settings. If no Hexnode MDM profile is present, the enrollment did not complete fully on the client side.

2. Devices enrolled using Windows Autopilot Device Preparation may not appear in the traditional Autopilot device list used for Autopilot sync. Autopilot sync in Hexnode is intended for Autopilot-registered devices, so it may not list devices that were onboarded only through Device Preparation.

3. If the same test device has gone through multiple migration attempts, manual profile removals, or partial unenrollments, Windows can be left in an inconsistent MDM enrollment state. In that condition, the migration may create a partial device record in Hexnode while the local MDM profile is not established correctly.

For testing, start from a clean and stable source-MDM enrollment state before running the Hexnode Gateway migration again. Avoid manually removing provisioning packages or MDM profiles in between migration attempts unless you are rebuilding the test environment.

Regards,
Sienna Carter
Hexnode UEM

Save