Category filter

Getting started with Windows kiosk management

Windows kiosk management refers to the process of configuring Windows devices into a specific, restricted environment known as “Kiosk Mode.” By leveraging Hexnode UEM, administrators can transform standard PCs into dedicated purpose-built terminals. This configuration enhances security by limiting user interaction to only approved applications and settings, making it ideal for public-facing displays, digital signage, or task-specific workstations.

Prerequisites: Enrollment and App Setup

To successfully deploy a Windows kiosk configuration, specific foundational steps must be completed.

  • Device Enrollment:
    • Devices must first be enrolled in the Hexnode UEM console.
    • Supported OS: Windows 10 and Windows 11.
  • App Installation:
    • Before activating kiosk mode, the target applications must be installed on the device.
    • App Sources: Administrators can deploy Microsoft Store apps or Enterprise (in-house) apps via the UEM console prior to locking the device.

Single App Kiosk Mode

This mode is designed for devices that perform a solitary function, such as a self-check-in station or an interactive information board.

  • Definition: Locks the Windows kiosk device to a single application.
  • Behavior: The application launches automatically upon login. All other system functionalities, including the Start menu, taskbar, and desktop, are completely inaccessible.
  • Use Case: Digital signage, ATM-style interfaces, and public web browsers.

Multi-App Kiosk Mode

This This mode offers a restricted yet flexible environment suitable for frontline workers or shared corporate devices.

  • Definition: Restricts the Windows kiosk device to a curated list of essential applications.
  • Behavior: Users can switch between the allowlisted apps via a simplified Start menu or tile interface. Access to non-approved apps, system settings, and the file explorer is blocked.
  • Use Case: Shared workstations, inventory management tablets, and educational devices.

Exiting Kiosk Mode

Administrators maintain control over the device lifecycle and can disable the Windows kiosk environment when necessary.

  • Policy Removal: Disassociating or archiving the Kiosk Lockdown Policy from the Hexnode console automatically reverts the device to its standard interface.
  • User Switching: If configured, the device screen can be locked (CTRL+ALT+DEL), allowing a different user account to sign in to a non-restricted desktop session.

Troubleshooting Windows Kiosk Issues

The following table addresses common errors encountered during Windows kiosk deployment and their respective resolutions.

Symptom / Error Probable Cause Resolution Strategy
Black screen upon login Explorer.exe shell conflict or app path error. Check App Path: For enterprise apps, ensure the file path (AUMID or executable path) provided in the policy is exact. Reboot the device remotely.
Cannot exit Kiosk Mode Network disconnection prevents policy removal. Network Check: Ensure the device has internet access to receive the “Disassociate Policy” command. If offline, a local administrator login (if enabled) may be required.

Frequently Asked Questions (FAQs)

Q: Which operating systems support Windows kiosk mode via Hexnode?

A: Hexnode UEM supports Windows kiosk configuration on devices running Windows 10 (Pro, Enterprise, and Education editions) and Windows 11.

Q: Can a Windows kiosk device run multiple applications?

A: Yes. By using Multi-App Kiosk mode, administrators can allowlist a specific set of applications, enabling users to switch between them while blocking all other system software.

Q: What happens if the Kiosk app crashes?

A: In a properly configured Windows kiosk environment, the OS is often set to automatically restart the designated kiosk application immediately if it closes or crashes, ensuring continuous service availability.

Q: Is it possible to deploy Microsoft Store apps in Single App Kiosk mode?

A: Yes. Microsoft Store apps can be utilized for Single App Kiosk mode, provided they are installed on the device prior to the policy being applied.

Get Started