Preparing and Deploying Win32, LOB and Store Apps

What it is

Intune deploys several kinds of apps, and each needs different preparation. Win32 apps are packaged as .intunewin files and offer the most control. Line of business (LOB) apps are single installer files such as MSI. Microsoft Store apps come from the Store. Choosing the type, then setting the intent (required or available) and the rules that detect installation, decides whether the app arrives correctly.

How it works

Preparing a Win32 app

1. Get the installer files and the silent install command.
2. Use the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe) to wrap the folder into a .intunewin file.
3. In Intune, add an app of type Windows app (Win32) and upload the file.
4. Set the install command and uninstall command, the install behavior (system or user) and the device restart behavior.
5. Add requirement rules, detection rules, return codes, and optional dependencies and supersedence.
6. Assign the app.

Detection rules

At least one detection rule is required, and all rules must be true for the app to count as installed. Types:

Detection runs before the download (so an app that is already present is skipped) and after the install (to confirm success). Detection runs as SYSTEM, so a per user path such as one with %username% will not resolve to the signed in user.

Requirement rules

Requirement rules decide whether the app applies to a device, before it downloads. You can require a minimum OS architecture and version, disk space, memory, processors, and add file, registry or script based rules. A device that does not meet them reports Not applicable.

Return codes, dependencies and supersedence

• Return codes map installer exit codes to results: Success, Failed, Hard reboot, Soft reboot and Retry. Retry tries again up to three times, waiting 5 minutes between attempts. A hard reboot blocks the next Win32 app until the device restarts, while a soft reboot does not.
• Dependencies install another app first. They are checked before detection.
• Supersedence replaces an older app with a newer one. Toggle Uninstall previous version off for an in place update, or on to remove the old app first. A chain can have up to 10 nodes, and you need the Relate permission.

Line of business apps

An LOB app is a single file you upload: MSI, MSIX or APPX for Windows, .ipa for iOS and .apk for Android. Intune detects installation by product code or bundle ID. LOB apps are simpler and have fewer options than Win32. Do not mix LOB (MSI) and Win32 installs during Autopilot with the ESP, because they compete for the same installer.

Microsoft Store apps

Add a Microsoft Store app (new), which searches the Store and uses the package manager, rather than the retired Store for Business flow. Windows apps can install in user or device context. Store apps update automatically, and are good for apps the Store already publishes.

Assignment intent

Assign to users for apps the person needs, and to devices for apps that belong to the machine, such as drivers or kiosk apps. Use assignment filters to exclude devices, and scope tags to limit who sees the app.

A worked scenario

An engineer packages a CAD tool as .intunewin, sets the silent switch, and adds a detection rule for the executable file version and a requirement rule for 64 bit Windows 11 with 16 GB of memory. She adds the Visual C++ runtime as a dependency and marks the app Required for the engineering group. When version 2 arrives, she adds supersedence with Uninstall previous version off. A second tool is only occasionally needed, so it is Available in the Company Portal.