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
Intune UI examples
These compact mockups show the Intune settings that matter for this topic.
Practical reference
| Area | What to check |
|---|---|
| MSI | msiexec /i app.msi /qn /norestart |
| InstallShield EXE | setup.exe /s or vendor-specific switch |
| NSIS/Inno/Custom EXE | Use vendor help or documentation |
| Script wrapper | cmd.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
| Issue | What to check |
|---|---|
| Install times out | Installer may be waiting for UI input. |
| Works manually but fails in Intune | Test under the same context Intune will use. |
| Wrong exit code | Review return codes and installer logs. |

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