Windows enrollment fails with No authentication settingsSolved

Participant
Discussion
4 weeks ago Oct 14, 2026

I’m trying to enroll a Windows device in Hexnode and got a bit stuck with the enrollment setup. I was looking for the managed enrollment option and only have device details like IMEI/EID, but I’m not sure that’s the right path for Windows.

I changed the enrollment authentication setting to No authentication, but the page wouldn’t let me save it unless I used Enforce authentication. I also wanted to know whether I should send a QR code or link to the user, and whether the user would need to log in or have an account created first.

Replies (3)

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Oct 14, 2026
Marked SolutionPending Review

Hello @sebastin ,

For Windows enrollment using the Hexnode installer, you do not need to use a QR code or enroll the device using IMEI/EID.

Use the account-specific enrollment URL instead: https://<portal name>.hexnodemdm.com/enroll/

This URL must be opened directly from a browser on the Windows device that you want to enroll. The user can then download and run the Hexnode installer to complete enrollment.

For the No authentication enrollment mode:

  1. Go to the enrollment settings in the Hexnode UEM portal.
  2. Set authentication to No authentication.
  3. Select a default user.
  4. Ensure Windows enrollment is enabled under Enrollment Restrictions.
  5. Save the settings.

The default user selection is required for saving the No authentication configuration. Once this is saved, the end user should not be prompted to log in while enrolling through the installer.

Regards,
Simon Scott
Hexnode UEM

Marked SolutionPending Review
Participant
4 weeks ago Oct 14, 2026
Marked SolutionPending Review

I followed the URL method and got past the authentication part, but then the installer showed a message that the device limit was reached. Is that still related to the enrollment settings?

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Oct 14, 2026
Marked SolutionPending Review

A device limit reached message is not caused by the No authentication setting or the enrollment URL.

It usually means the portal currently does not have available enrollment capacity. This can happen if the trial or subscription has expired, or if the licensed device limit has already been reached.

In that state, new device enrollments are blocked until the portal has an active trial/subscription or available device licenses. Once the account limit issue is resolved, the same Windows enrollment URL and installer method can be used again.

Save