KIOSK OVERSEER // BUILD 1.6.2

TASKBAR
FILE EXPLORER
APPLICATION TYPE
EDGE KIOSK
BREAKOUT CONTROL
PINNED SHORTCUTS
desktopAppLink (?)
Advanced Options
EDGE SITE TILE
NOTE: Secondary tiles use the normal Edge profile (not InPrivate by default). Apply Edge policies if you need private-session behavior.
PIN LIST
No pins added yet. Add a desktop shortcut or UWP app above.
TASKBAR PINS
Advanced Options
TASKBAR LIST
No taskbar pins configured. Add a desktop app or UWP app above.
Profile
Name
Account
Application
Kiosk Mode
Allowed Apps
Layout
Start Pins
Taskbar Pins
Show Taskbar
File Explorer
DEVICE SETTINGS
EXPORT
Download the XML and paste it into an Intune OMA-URI custom policy. See Deploy Guide for full steps.
AssignedAccess XML Configuration

The core kiosk configuration file that defines allowed apps, pins, taskbar settings, and account restrictions.

When to use:
• Intune OMA-URI deployment (paste XML into custom policy)
• Provisioning Package (PPKG) creation via Windows Configuration Designer

What it does:
• Defines the kiosk profile and restrictions
• Gets applied via MDM or PPKG to configure the device

Note: For Intune/PPKG, you may also need Shortcut Creator and/or Manifest Override scripts deployed separately.
All-In-One PowerShell Deployment Script

Complete deployment script for local/standalone devices. Does everything in one step.

When to use:
• Local deployment on standalone devices
• Testing kiosk configurations
• Non-Intune environments

What it does:
• Creates Start menu and Taskbar shortcuts (.lnk files)
• Applies Edge Manifest Override if needed
• Applies AssignedAccess XML configuration
• Enables diagnostic event logs for troubleshooting
• Sets up KioskOverseer Sentry (if enabled)
• Generates detailed CMTrace-compatible log file

Note: Must be run as SYSTEM using psexec or similar tool.
Shortcut Creator Script

Creates Start menu and Taskbar .lnk shortcut files for Intune/PPKG deployments.

When to use:
• Required if your pins use desktopAppLink (reference .lnk file paths)
• Intune OMA-URI or PPKG deployments

Why needed:
• Intune OMA-URI policies can only apply XML, not create files
• StartPins with desktopAppLink require actual .lnk files to exist
• Must be deployed separately as Win32 App or Intune Script

What it does:
• Creates .lnk files in Start Menu Programs folder
• Sets custom names, icons, and arguments
• Creates detection sentinel file for Win32 App tracking
• Generates CMTrace-compatible log file
Edge Manifest Override (Advanced/Unsupported)

Forces Windows to use your custom shortcut names and icons for Edge pins instead of defaulting to "Microsoft Edge" branding.

When to use:
• You're using Edge with custom .lnk shortcuts
• You want custom names/icons in Start menu or Taskbar
• Needed for Intune/PPKG deployments (use Win32 App or Intune Script)

Important:
• NOT supported by Microsoft
• Edge updates may break this workaround
• Creates a scheduled task that runs at startup
• Includes install and remove scripts

Downloads two PowerShell scripts to apply/remove the workaround.