Pro edition. Creates a Microsoft Intune Win32 app package.
Step 1: Source Files #
Upload the setup files, for example the MSI, EXE, scripts and configuration files.
Step 2: App Information #
Enter Name (required), Publisher, Version and Description. These are shown in the Intune admin center.
Step 3: Program #
| Field | Description |
|---|---|
| Setup file (required) | The installer, chosen from the uploaded files (picked automatically if there is only one) |
| Install command (required) | The silent install command line, for example msiexec /i "setup.msi" /qn |
| Uninstall command (required) | The silent uninstall command line |
| Install behavior | System or User |
For MSI installers, the product information and a product-code detection rule are filled in automatically.
Step 4: Detection Rules #
Intune uses detection rules to find out whether the app is installed.
- Add as many rules as you need with + Add detection rule. All rules must match.
- Rule types:
- msi: the MSI product code
- file: the full path of a file
- registry: a registry key, for example
HKLM\SOFTWARE\… - script: a detection PowerShell script
- At least one rule is required to publish the app in Intune.
Step 5: Requirements #
| Field | Description |
|---|---|
| Minimum OS | Windows 10 1607 up to Windows 11 24H2 |
| Architecture | x64, x86 or arm64 |
| Minimum disk space (MB) | Free disk space required for the installation |
Step 6: Preview & Build #
Review the build plan and click Finish.
Result:
{name}.intunewin: the encrypted package{name}.intune.json: all app details, commands and detection rules, ready for automated publishing
To deliver a PSADT package through Intune, you don’t need an IntuneWin package. Upload the PSADT package to Intune directly (see Connections & uploads). It is wrapped as
.intunewinautomatically.