Microsoft Intune guidelines: DisplayNote Launcher

Please refer to official Microsoft documentation for using Win32 apps with Microsoft Intune: Add, assign and monitor a Win32 app with Microsoft Intune.

The following information may be used in conjunction with official documentation to deploy Launcher using Microsoft Intune as a required, system-context Win32 app that installs the full installer silently for all users with no user interaction.

Scope: This guide covers Launcher-specific packaging and Intune configuration only. It assumes your Microsoft 365 tenant, Intune licensing, and device enrollment are already in place.
 

Useful links:
 

• Microsoft Intune documentation
• Prepare Win32 app content for Intune
• Add, assign, and monitor Win32 apps
• Troubleshoot Win32 apps
• Microsoft Win32 Content Prep Tool (GitHub releases)
• Microsoft Intune admin center

1. Overview

The three key differences from an interactive install are:

• Silent — the /q flag suppresses all UI.
• All users — the /all-users flag provisions the MSIX machine-wide, so every user profile on the device gets Launcher.
• System context — Intune runs the installer as the local SYSTEM account, providing the elevation the installer needs without a UAC prompt.
   

Why the full installer (not the MSIX directly)?

The full installer DisplaynoteLauncherInstaller.exe does more than install the app:
 

1. Installs and starts the SpotService Windows service (SpotWin32Service.exe).
2. Installs the KioskStarter component.
3. Enables Windows sideload mode so the bundled MSIX can install.
4. With /all-users, provisions the MSIX machine-wide and records the flag in HKLM\SOFTWARE\DisplayNoteTechnologies\Launcher.
5. Registers a Launcher Service Add/Remove Programs entry for clean uninstall.

Deploying the raw MSIX via Intune's Line-of-business app type skips the service, sideload, and all-users provisioning steps — it is not equivalent.
 

Install command

DisplaynoteLauncherInstaller.exe /q /all-users

Installer flags reference

2. Prerequisites

1. A Microsoft 365 tenant with Intune-capable licensing (Intune Plan 1, M365 E3/E5, Business Premium, or EMS E3/E5), with licenses assigned to relevant users.
2. An account with Intune Administrator permissions or equivalent.
3. Windows 10/11 Pro, Enterprise, or Education devices enrolled into Intune. Windows Home is not supported.
4. Entra ID security groups already created and populated with target users or devices.
5. A packaging machine with the Microsoft Win32 Content Prep Tool.
6. The DisplayNote Launcher full installer 

Minimum device OS: the full installer requires 64-bit Windows 10 1903 (build 10.0.18362) or later. Set the Intune requirement rule to match.

3. User-based vs device-based targeting

For an all-users, system-context install, device-based targeting is the natural fit — the app follows the machine, not the user.
 

Do not assign to All devices or All users unless you are certain every device/user in the tenant should receive Launcher.

4. Obtain the Launcher full installer

1. Get the full installer from your DisplayNote contact for your version
2. Rename it to DisplaynoteLauncherInstaller.exe for predictable commands.
3. Verify the silent install locally on a test machine (not your packaging host) in an elevated Command Prompt:

DisplaynoteLauncherInstaller.exe /q /all-users

After a minute or two, confirm:
 

dir "C:\Program Files (x86)\DisplayNoteTechnologies\Launcher"

You should see SpotWin32Service.exe and KioskStarter.exe. Always validate the silent command manually before packaging.

5. Set up packaging folders

Recommended structure
 

• Put only the installer (and optional .lsf) in the Source folder. The prep tool packages the entire source folder — keep it clean.
• Do not place IntuneWinAppUtil.exe inside the source folder.
   

Download IntuneWinAppUtil.exe from the GitHub releases page and copy it to C:\IntuneApps\Tools.

6. Package as a Win32 app

Open Command Prompt as Administrator and run:

C:\IntuneApps\Tools\IntuneWinAppUtil.exe ^
 

  -c "C:\IntuneApps\Launcher\Source" ^
 

  -s "DisplaynoteLauncherInstaller.exe" ^

  -o "C:\IntuneApps\Launcher\Output"

Expected output: C:\IntuneApps\Launcher\Output\DisplaynoteLauncherInstaller.intunewin

7. Add the Win32 app to Intune

Start the app wizard
 

1. Open intune.microsoft.com.
2. Go to Apps → Windows → Add.
3. For App type, select Windows app (Win32) and click Select.
    

Upload the package
 

Select App package file and browse to C:\IntuneApps\Launcher\Output\DisplaynoteLauncherInstaller.intunewin.

App information
 

Program commands
 

Why System context is required: the installer installs a Windows service, toggles machine-wide sideload mode, and provisions the MSIX for all users — all of which need administrator rights. SYSTEM provides that elevation without a UAC prompt.
 

Requirements
 

Detection rules

Choose one option. Option B or C is preferred for all-users deployments.

Option A — File (simplest)

Option B — Registry, all-users-specific (recommended)
 

Confirms the /all-users provisioning flag specifically.
 

Option C — Registry, version-aware (best for upgrades)

Lets Intune re-install automatically when you ship a newer version.
 

The installer processes are 64-bit so both registry keys are written to the native 64-bit hive (not WOW6432Node) even though the app installs under Program Files (x86). Keep Associated with a 32-bit app on 64-bit clients: No for all registry rules.
 

Assignment

8. Confirm installation on the device

On an assigned, enrolled device — sign in as any user and force a sync, then run each check:

Files exist

dir "C:\Program Files (x86)\DisplayNoteTechnologies\Launcher"

Expect SpotWin32Service.exe and KioskStarter.exe.

Service running
 

Get-Service -Name SpotService
 

All-users provisioning flag

reg query "HKLM\SOFTWARE\DisplayNoteTechnologies\Launcher" /v InstallForAllUsers

Expect InstallForAllUsers    REG_DWORD    0x1.

Add/Remove Programs entry

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\DisplayNote_Launcher" /v DisplayName

Expect DisplayName    REG_SZ    Launcher Service.

9. Monitor deployment

Check status in Intune

Go to Apps → Windows → DisplayNote Launcher (All Users) → Monitor and review Device install status and User install status. Allow 10–30 minutes before assuming failure.

Force a sync

• On the device: Settings → Accounts → Access work or school → [account] → Info → Sync
• In Intune admin center: Devices → Windows devices → [device] → Sync

Intune Management Extension logs

C:\ProgramData\Microsoft\IntuneManagementExtension\Logs
 

Most useful: IntuneManagementExtension.log and AppWorkload.log. Search for DisplaynoteLauncherInstaller, Win32App, Detection, Exit code.

Useful indicators

• Detection rule evaluated
• Application is not detected
• Start install command
• Installation completed
• Exit code 0
   

The full installer does not intentionally set a custom process exit code, so Intune should treat the detection rule as the source of truth for Installed / Failed. If you observe consistent non-zero codes in the IME logs (for example, from a crash/timeout), add them under Return codes in the app's Program settings.

Installer logs

C:\ProgramData\DisplayNoteTechnologies\Temp\DisplaynoteLauncherInstaller_*.txt

Useful when the IME reports failure — shows which phase failed (service install, MSIX install, or all-users provisioning).

10. Troubleshooting

App reports Failed

1. Confirm Install behavior = System. A per-user context cannot install the service or provision for all users.
2. Confirm the device is 64-bit and meets the minimum OS (Windows 10 1903 / build 18362).
3. Check SpotService installed: Get-Service -Name SpotService.
4. Review IntuneManagementExtension.log and the installer's own logs.
    

App installs but Intune keeps reporting "not detected" / reinstalls

1. Verify the detection rule path/value with the reg query / dir commands in section 8.
2. If using a registry rule, confirm Associated with a 32-bit app on 64-bit clients: No.
3. Avoid per-user detection paths for an all-users/system app.

App stuck at Pending

1. Confirm the device has internet access and has checked in (force a sync).
2. Confirm the user/device is in the assigned group.
3. Restart the Intune Management Extension service:
    

Restart-Service -Name IntuneManagementExtension

Sideload / MSIX provisioning failures

1. Check for an MDM/Group Policy that blocks sideloaded apps.
2. Re-run a sync; the all-users provisioning path is designed to retry.
3. Inspect the installer logs for the provisioning step.

/all-users had no effect

1. Confirm the install command includes /all-users (check the Program tab).
2. Confirm InstallForAllUsers = 1 in HKLM\SOFTWARE\DisplayNoteTechnologies\Launcher. If absent or 0, re-check System context.

11. Uninstall

Via Intune
 

Open the app → Properties → Assignments. Add the target group under Uninstall. Save and sync. Intune will run:
 

DisplaynoteLauncherInstaller.exe /uninstall
 

Manual (elevated Command Prompt on the device)

"C:\Program Files (x86)\DisplayNoteTechnologies\Launcher\Uninstaller.exe"

Or re-run the packaged installer:

DisplaynoteLauncherInstaller.exe /uninstall

12. Deployment checklist

Packaging

• Launcher full installer obtained and verified silent locally (/q /all-users).
• Installer renamed to DisplaynoteLauncherInstaller.exe (or known name) in Source.
• Source folder contains only the installer (and optional .lsf).
• .intunewin created with the content prep tool.

Intune app

• App type Windows app (Win32), package uploaded.
• Install command: DisplaynoteLauncherInstaller.exe /q /all-users.
• Uninstall command: DisplaynoteLauncherInstaller.exe /uninstall.
• Install behavior: System.
• Requirement: 64-bit, min OS Windows 10 1903.
• Detection rule configured (file SpotWin32Service.exe, or registry InstallForAllUsers=1 / version).
• Assigned Required to your target group.
   

Verification

• Device synced; app shows Installed in Intune.
• C:\Program Files (x86)\DisplayNoteTechnologies\Launcher\SpotWin32Service.exe exists.
• SpotService service running.
• HKLM\SOFTWARE\DisplayNoteTechnologies\Launcher\InstallForAllUsers = 1.
• Launcher Service entry present in Add/Remove Programs.
• Launcher runs for the signed-in user.