Android enrollment error when configuring kiosk policy in HexnodeSolved

Hi @v_collins ,

This usually happens when the enrollment authentication settings do not match the intended enrollment flow.

For open enrollment, update the enrollment settings and try again:

1. Go to Enroll > Settings in the Hexnode UEM portal.
2. Select No Authentication.
3. Choose Set up Password if the option is shown for the enrollment setup.
4. Scroll to the bottom of the page and save the changes.
5. Try enrolling the Android device again.

After the device enrolls successfully, you can associate the Android kiosk policy with the device or device group and continue testing the kiosk configuration.

Regards,
Isabel Lora
Hexnode UEM

That got the device past the enrollment error. We’re now looking at the actual kiosk setup.

For rollout, we may need a configuration phase where a few apps/settings are available, and then later switch the device to a single app only. Also, should Android and iOS devices be managed under the same policy or separate ones?

For mixed-platform deployments, it is best to create separate policies for Android and iOS. This keeps platform-specific kiosk, restriction, and OS update settings easier to manage and troubleshoot.

For the Android workflow you described:

• Use Multi-app kiosk mode during the onboarding or staging phase if technicians need access to multiple apps or device settings.
• Include only the required apps/settings during this phase.
• Once setup and testing are complete, move the devices to a stricter single-app kiosk policy that launches only the required work app.

For update control:

• On Android Enterprise devices, configure OS update behavior and maintenance windows so updates do not interrupt active work hours.
• On iOS devices, use iOS update deferral or update management settings separately in the iOS policy.

If devices must remain on a specific time zone, you can test the force time zone option under Android restrictions before production rollout.

Regards,
Isabel lora
Hexnode UEM