Intune: Create a Win32 .intunewin File

Key insights

• Intune Win32 (.intunewin)
  Packages traditional Windows installers into a single file that Intune accepts for centralized deployment.
  Use this to deploy .msi, .exe or script-based installers with detection rules and dependencies.
• IntuneWinAppUtil.exe
  Run the Microsoft Win32 Content Prep Tool to convert your app files into a .intunewin package.
  Download the latest release, extract the tool, and run it from a command prompt.
• source folder
  Place the installer and all supporting files in one folder, using relative paths for extra assets like licenses or scripts.
  Keep the structure tidy so the tool captures everything needed for install and detection.
• command-line parameters
  Use -c for the source folder, -s for the setup file, -o for the output folder and -q for quiet mode. Example: IntuneWinAppUtil.exe -c C:\app\v1 -s C:\app\v1\setup.exe -o C:\output\v1 -q
  Check the output folder for the generated .intunewin before uploading.
• App configuration
  In Intune, upload the .intunewin and set install/uninstall commands, detection rules (file, registry, or MSI product code), requirements, dependencies, and group assignments.
  Use silent install switches or PowerShell scripts to ensure automated, reliable installs.
• Advantages
  Packing apps reduces upload size, supports complex installers, and enables robust detection and deployment controls.
  Verify packages and test deployments on a pilot group before broad rollout.

Video overview

In a concise YouTube tutorial, Dean Ellerby [MVP] walks viewers through creating a .intunewin package for deployment with Intune. The video focuses on the practical steps using the Microsoft Win32 Content Prep Tool, and it targets IT admins who need to wrap installers, scripts, or full application folders for centralized deployment. Consequently, the content is useful for teams managing legacy desktop apps as well as custom tools that do not ship as native MSIs.

Step-by-step process

First, Ellerby emphasizes obtaining the latest version of the prep tool from Microsoft's official repository and extracting the executable named IntuneWinAppUtil.exe. Then, he shows how to build a clear source folder that contains the installer file and any supporting assets, such as license text or helper scripts, which helps avoid missing-file errors later. Finally, he runs the prep tool from Command Prompt to produce a compressed .intunewin output file ready for upload.

In the demo, the presenter highlights key command parameters like the source folder, the setup file name, and the output folder, and he demonstrates a typical command using those options. He also points out a quiet mode useful for automation, which suppresses prompts during packaging, and he suggests verifying the resulting .intunewin file before proceeding. After packaging, the video shows the general steps needed to upload the package to Intune and to configure install and uninstall commands within the admin console.

Key options and detection rules

Ellerby explains that the packaging tool supports several installer formats including MSI, EXE, and PowerShell scripts, and that the uploaded package relies on properly defined install and uninstall commands. He stresses the importance of detection rules—such as checking for files, registry entries, or MSI product codes—because they determine whether Intune considers an app installed or not. Therefore, thoughtful detection logic reduces false positives and avoids repeated, unnecessary installs.

Moreover, the tutorial shows how to set requirements like operating system and architecture and to define dependencies so that prerequisites install first. These settings give admins control over which devices receive the app and under what conditions, but they also add configuration overhead and require testing to ensure expected behavior. As a result, accurate metadata and well-formed detection rules are key to reliable deployments.

Advantages and tradeoffs

The main advantage Ellerby presents is flexibility: packaging with the Win32 Content Prep Tool lets admins manage traditional desktop apps that do not fit into modern packaging models. Additionally, the tool compresses content, which can speed upload and reduce bandwidth, and it extracts useful metadata automatically for many MSI files. These benefits make the approach practical for many real-world scenarios where legacy tools remain critical.

However, there are tradeoffs to consider. Creating robust detection rules and precise install commands can be complex, and troubleshooting failures often takes more time than simply deploying a native MSI or an MSIX package. Furthermore, larger or more complex applications increase packaging and testing effort, and admins must balance that investment against alternatives like modern re-packaging or using built-in enterprise store options.

Common challenges and practical tips

Ellerby calls out a few common pain points: silent installation flags that differ between installers, elevated privilege requirements, and inconsistent return codes that complicate automation. To manage these issues, he recommends testing installs in a lab environment, capturing logs, and validating detection rules on sample machines before broad rollouts. These steps reduce unexpected re-deployments and help identify missing dependencies early.

He also suggests versioning the source folders and keeping a clear output area for generated .intunewin files so teams can track releases, and he recommends automating packaging for repeatability where possible. While the video is short, these practical tips underscore that packaging is part of a larger release process that includes testing, monitoring, and iterative fixes.

Conclusion and next steps

Overall, Dean Ellerby's tutorial offers a clear, practical walkthrough for admins who need to prepare Win32 apps for Intune deployment. The video balances hands-on commands with configuration tips, while also hinting at the tradeoffs between control and complexity that come with managing legacy installers. For teams adopting this method, the next steps are to practice with a few representative apps, refine detection rules, and document the process so deployments scale reliably across the organization.

Keywords

Intune Win32 app package, create .intunewin, how to create intunewin, Intune Win32 packaging tutorial, Microsoft Intune intunewin converter, Win32 app deployment with Intune, packaging Win32 apps for Intune, step-by-step intunewin guide