intunemdms.com

Intune Deployment Guide

Silent install switches for common installers

Overview

Silent install switches let installers run without user interaction. They are essential for Intune Win32 app deployment because the install command must complete without prompts.

Different installer technologies use different silent switches, so always validate the command before assigning the app broadly.

Why silent switches matter

Intune cannot click through setup dialogs. If an installer waits for UI input, the app may time out or fail.

Common patterns

MSI installers usually use msiexec quiet parameters. EXE installers vary by vendor, so use vendor documentation or installer help output when available.

How the flow works

01Identify installerMSI, EXE, wrapper
02Find switchQuiet or silent mode
03Test locallyNo prompts
04Add commandProgram tab

Intune UI examples

These compact mockups show the Intune settings that matter for this topic.

MSI example□ ×
msiexec /i "app.msi" /qn /norestart
msiexec /x "{PRODUCT-CODE}" /qn
MSI
EXE example□ ×
setup.exe /quiet /norestart
setup.exe /uninstall /quiet
EXE
Wrapper script example□ ×
cmd.exe /c install.cmd
cmd.exe /c uninstall.cmd
Multiple commands
Test behavior□ ×
No
0
True

Practical reference

AreaWhat to check
MSImsiexec /i app.msi /qn /norestart
InstallShield EXEsetup.exe /s or vendor-specific switch
NSIS/Inno/Custom EXEUse vendor help or documentation
Script wrappercmd.exe /c install.cmd or powershell.exe -File install.ps1

Quick checklist

  • Never assume /quiet works for every EXE.
  • Test the command from an elevated prompt or System context when needed.
  • Confirm the installer exits instead of waiting in the background.

Troubleshooting checks

IssueWhat to check
Install times outInstaller may be waiting for UI input.
Works manually but fails in IntuneTest under the same context Intune will use.
Wrong exit codeReview return codes and installer logs.

Leave a feedback

Include versions, steps, and any error text if you have them.