Windows device won’t fully enroll in Hexnode when another MDM is already connectedSolved

If the Windows device is already enrolled in another MDM, Hexnode may not be able to take full management of the device. In that case, you can either keep the device in a co-managed state with limited functionality, or remove the existing MDM enrollment and then enroll it into Hexnode for full management. For full Hexnode management, try the following:

1. On the Windows device, open Settings.
2. Go to Accounts > Access work or school.
3. Select the existing work/school or MDM connection.
4. Choose Disconnect and complete the removal.
5. Restart the device.
6. Download and run the Windows enrollment installer from the Hexnode portal.
7. After enrollment, confirm that the device appears under the Manage tab in Hexnode.

Once the device is fully enrolled, you can proceed with kiosk-related policies such as multi-app kiosk, application allow/block lists, and website restrictions. Also verify the Windows edition before finalizing kiosk requirements, as some kiosk capabilities can differ between Windows Pro, Enterprise, and Education editions.

One thing that confused us during setup: the installer enrollment did not ask for a username or password. Is that expected?

Yes. With the Windows installer enrollment method, authentication can be handled through the enrollment package downloaded from the portal, so the device may enroll without prompting for separate user credentials during installation. If a different IT engineer is handling the setup, make sure they have technician access to the Hexnode portal first. The technician invite email for portal login is separate from the device enrollment flow. After they can access the portal, they can download the Windows enrollment package and continue enrolling the pilot devices.