Windows device enrolled under previous user in HexnodeSolved

Participant
Discussion
2 days ago Aug 31, 2026

A technician enrolled a Windows device for a domain user, but after enrollment the device appeared under the previous enrolled user’s name in Hexnode. We manually changed the owner afterward, so the current device is fine, but we want to prevent this from happening again.

The enrollment request link was created for the intended user, and the user’s name was selected while generating the link. Why would the device still show up under the previous user, and what enrollment settings should be changed for domain users?

Replies (3)

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

Hi @ame-lie,

For Windows enrollments, user assignment depends on the User Authentication settings configured in the enrollment profile.

If authentication is not enforced, selecting a user while generating or sending the enrollment link may not be enough to ensure that the device enrolls under that user’s account. To make sure domain users are mapped correctly during enrollment, enable enforced authentication in the Windows enrollment profile.

Configure it as follows:

  1. Go to Enroll > Platform-Specific > Windows > Windows PCs and Tablets > Enrollment Profiles.
  2. Open the enrollment profile used for the device.
  3. Go to the User Authentication tab.
  4. Under Authentication Modes, select Enforce Authentication.
  5. Save the enrollment profile.

After this, send the enrollment request directly to the domain user:

  1. Go to Users.
  2. Open the required domain user’s details page.
  3. Select Actions > Other > Enrollment Request.
  4. The user should open the enrollment URL and authenticate with their domain credentials.

Once the user authenticates during enrollment, the Windows device should enroll under the correct user account in Hexnode.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
2 days ago Aug 31, 2026
Marked SolutionPending Review

That explains it. So if the profile was not enforcing authentication, the enrollment link alone would not guarantee the right user ownership?

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

Correct. The enrollment request can be associated with a user, but for domain-user-based assignment to be reliable, the user must authenticate during the enrollment flow. Enforcing authentication ensures Hexnode can verify the enrolling user and map the Windows device to that user’s account.

For devices that are already enrolled under the wrong user, you do not need to re-enroll just to fix ownership. You can use the Change Owner action:

Manage > Devices > select the device > Actions > Edit > Change Owner

Then select the appropriate domain and user, and assign the device to the correct owner.

Regards,
Isabel Lora
Hexnode UEM

Save