KIOSK OVERSEER // BUILD 2.0.0

APPLICATION TYPE
EDGE KIOSK
BREAKOUT CONTROL
FILE EXPLORER
TASKBAR
PINNED SHORTCUTS
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.

These settings are applied by the On-Demand Kiosk Script, not the Assigned Access XML. For Intune/MDM deployments, configure these separately via Configuration Profiles or registry policies.

TOUCH INPUT
Profile
Name
Account
Application
Kiosk Mode
Allowed Apps
Layout
Start Pins
Taskbar Pins
Show Taskbar
File Explorer
EXPORT
AssignedAccess XML Configuration

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

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

Note: You may also need Shortcut Creator and/or Manifest Override deployed separately.
Upload to Intune OMA-URI or Windows Configuration Designer
On-Demand Kiosk Script

Run directly on a device to immediately set up the kiosk. Does everything in one step.

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.
Run on a device to set up the kiosk immediately — does everything in one step
Shortcut Creator Script

Creates Start menu and Taskbar .lnk shortcut files.

Why needed:
• StartPins with desktopAppLink require actual .lnk files to exist on the device
• Intune OMA-URI can only apply XML, not create files

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
Creates .lnk shortcut files — deploy as a separate Intune app alongside the XML
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.

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.
Custom Edge shortcut branding — deploy as a separate Intune app (optional)

Recommended for enterprise. Deploy via Microsoft Intune using a custom OMA-URI policy.

1

Navigate to Intune

2

Create Profile

  • Click + Create profile
  • Platform: Windows 11
  • Profile type: TemplatesCustom
3

Configure OMA-URI

FieldValue
NameAssignedAccess Configuration
OMA-URI./Vendor/MSFT/AssignedAccess/Configuration
Data typeString
Value(Open downloaded XML file and copy entire contents)
4

Assign & Deploy

  • Assign to a device group
  • Device will sync and apply configuration
5

Deploy Shortcut Creator (If Needed)

Required if: Your Start or Taskbar pins use desktopAppLink (reference .lnk file paths)

Deployment options:

  • Option A (Simpler): Deploy as Intune Script (Devices → Scripts → Add PowerShell script)
  • Option B (More Control): Package as Win32 App with detection rules and dependencies (see Step 7 below)

Click Shortcut Creator in the Export section above to download the script

6

Deploy Manifest Override (Optional)

Only needed if: You want custom names/icons for Edge shortcuts instead of "Microsoft Edge" branding

Deployment: Same as above - deploy as Intune Script or Win32 App (see Step 7 below)

Click Manifest Override in the Export section above to download both install and remove scripts

7

Win32 App Creation Guide (Shortcut Creator & Manifest Override)

For Option B above: Follow these steps to package both scripts as Win32 apps

7a. Get IntuneWinAppUtil Tool
  1. Download from Microsoft GitHub
  2. Extract IntuneWinAppUtil.exe to a folder (e.g., C:\IntuneTools\)
7b. Package Shortcut Creator
  1. Create source folder: C:\IntunePackaging\ShortcutCreator\
  2. Place downloaded Shortcut Creator script in folder (e.g., CreateShortcuts_Lobby-Kiosk.ps1)
  3. Run IntuneWinAppUtil (replace filename with your actual script name):
    IntuneWinAppUtil.exe -c "C:\IntunePackaging\ShortcutCreator" -s "CreateShortcuts_YourConfigName.ps1" -o "C:\IntunePackaging\Output"
  4. Upload the generated .intunewin file to Intune

Install command (replace filename with your actual script name):

powershell.exe -ExecutionPolicy Bypass -File "CreateShortcuts_YourConfigName.ps1"

Uninstall command:

powershell.exe -Command "Write-Host 'Shortcuts remain in place'"

Detection script (PowerShell):

# Detect Shortcut Creator - checks for sentinel file
$sentinelPath = "$env:ProgramData\KioskOverseer\ShortcutCreator.installed"
if (Test-Path $sentinelPath) {
    Write-Host "Shortcut Creator installed"
    exit 0
} else {
    exit 1
}

Note: The Shortcut Creator script automatically creates this sentinel file - no manual modification needed.

7c. Package Manifest Override
  1. Create source folder: C:\IntunePackaging\ManifestOverride\
  2. Place both install and remove scripts in folder
  3. Run IntuneWinAppUtil:
    IntuneWinAppUtil.exe -c "C:\IntunePackaging\ManifestOverride" -s "KioskOverseer-EdgeVisualElements-Install.ps1" -o "C:\IntunePackaging\Output"
  4. Upload the generated .intunewin file to Intune

Install command:

powershell.exe -ExecutionPolicy Bypass -File "KioskOverseer-EdgeVisualElements-Install.ps1"

Uninstall command:

powershell.exe -ExecutionPolicy Bypass -File "KioskOverseer-EdgeVisualElements-Remove.ps1"

Detection script (PowerShell):

# Detect Manifest Override - checks for backup file and scheduled task
$taskExists = Get-ScheduledTask -TaskName "KioskOverseer-EdgeVisualElements" -ErrorAction SilentlyContinue
$backupExists = Test-Path "$env:ProgramFiles\Microsoft\Edge\Application\msedge.VisualElementsManifest.xml.kioskoverseer.bak"

if ($taskExists -and $backupExists) {
    Write-Host "Manifest Override installed"
    exit 0
} else {
    exit 1
}
8

Reboot & Validate

  • Device reboots to apply kiosk configuration
  • Sign in with kiosk account to test
Requirements: Device must be Azure AD joined or Hybrid Azure AD joined.
Deployment Summary: The OMA-URI policy applies the kiosk XML configuration. Shortcut Creator and Manifest Override must be deployed separately as scripts or Win32 apps because OMA-URI policies cannot create files or run commands on the device.

For standalone devices or testing. Simple two-step process: download the On-Demand Kiosk Script and run it as SYSTEM.

1

Download On-Demand Kiosk Script

Click On-Demand Kiosk Script in the Export section above to download. This script handles everything: applies XML, creates shortcuts, and configures the kiosk.

2

Run as SYSTEM

Execute the script using PsExec to run as SYSTEM:

psexec -i -s powershell.exe -ExecutionPolicy Bypass -File "C:\path\to\Apply-AssignedAccess.ps1"

The device will reboot to apply the kiosk configuration.

Why SYSTEM context? The MDM WMI Bridge requires SYSTEM (LocalSystem account, SID S-1-5-18) privileges to apply AssignedAccess configurations. Running as Administrator is not sufficient - you must use the SYSTEM account. PsExec (-s flag) provides an easy way to run PowerShell as SYSTEM.
Download PsExec: Microsoft Sysinternals PsExec (free tool from Microsoft)

For bulk deployment during OOBE or to existing devices.

1

Install Windows Configuration Designer

2

Create Provisioning Package

  • Open Windows Configuration Designer
  • Select Advanced provisioning
  • Navigate to: Runtime settingsAssignedAccessAssignedAccessSettings
  • Paste your XML configuration
3

Export & Apply

  • Export → Provisioning package → Create
  • Apply by double-clicking the .ppkg file or during Windows setup
TIP: Provisioning packages can be applied during OOBE by placing them on a USB drive.

Intune OMA-URI Deployment

Create OMA-URI Profile
Deploy XML via OMA-URI
Deploy Shortcut Creator (Win32/Script)*
Deploy Manifest Override (Win32/Script)**
Device reboots and applies kiosk

Local/PowerShell Deployment

Download On-Demand Kiosk Script
Run as SYSTEM (psexec -i -s)
Script creates shortcuts + applies XML
Reboot and validate
* Shortcut Creator is required if your pins use desktopAppLink (.lnk file paths).
** Manifest Override is optional - only needed if you want custom Edge shortcut names/icons instead of "Microsoft Edge" branding.