1. Home
  2. Knowledge Base
  3. SureMDM
  4. How to Configure the Kiosk Policy on Windows using Custom Settings via Profiles 
  1. Home
  2. Knowledge Base
  3. Windows Management
  4. How to Configure the Kiosk Policy on Windows using Custom Settings via Profiles 

How to Configure the Kiosk Policy on Windows using Custom Settings via Profiles 

The Custom Settings Payload allows administrators to configure advanced Windows policy settings using custom XML payload configurations. This profile enables granular control over device behavior by allowing administrators to define a custom configuration for the Multi kiosk to lock down the device and restrict it to only allowed applications.

This feature is particularly useful for deploying advanced Windows management policies, enforcing security baselines, or configuring settings using SureMDM profiles.

Purpose

This Article provides a step-by-step guide on how to configure kiosk policy using the Custom settings on Windows devices

Prerequists

XML configurations for the custom settings. Kindly refer to the sample XML below

Note: In the KioskModeApp tag, replace the application path or add multiple applications based on the requirement.

Additionally, if you want to apply the kiosk policy to an already existing account, replace the Kioskuser with the username present on the device

<AutoLogonAccount rs5:DisplayName=”KioskUser” />

Steps

  1. Log in to  SureMDM Web Console.  
  2. Navigate to the Profile section and select the Windows platform.
  3. Modify the existing profile or create a new profile 
  4. Navigate to the Custom settings and click on configure.
  5. Click on Import and browse the XML file with the kiosk configurations.
  6. Upload the file, save the profile, and deploy it onto the device.
  7. Once the profile has been successfully deployed on the device, Logout and try logging to the device, or reboot the device for the changes to take place.


NOTE: XML file can be configured for both Single and multi-app kiosk enablement.

Conclusion:

If the AutoLogonAccount has been used as a KioskUser in the XML, a new user will be created on the device, which will auto-log in when clicked on Login, and the Kiosk configurations can be seen only for that specific user.

If the already existing account has been used, then the kiosk policy will be applied to the specific user

Need more help? Here’s how to get help from our experts. 

CONTACT US

Was this helpful?
YesNo
Updated on March 2026
Need Support?
Can't find the answer you're looking for?
Contact Support