# Intune Win32 App Packaging & Detection Rule Pre-Flight Checklist

AdminSignal operator template. Work through it for each app before you assign it beyond a pilot group. Replace every `REPLACE-` value. Test in a lab tenant or an approved pilot group first.

## App

| Field | Value |
| --- | --- |
| App name and version | REPLACE |
| Installer type | REPLACE (MSI / EXE / script) |
| Packager | REPLACE-NAME |
| Pilot group | REPLACE-GROUP |

## 1. Package

- [ ] Source folder contains only what the install needs; installer hash recorded
- [ ] Packaged to `.intunewin` with the Microsoft Win32 Content Prep Tool
- [ ] Install command runs silently from an elevated prompt with no user interaction
- [ ] Uninstall command works and leaves nothing that makes the detection rule still pass
- [ ] Install behaviour (system or user) matches what the installer needs to write to
- [ ] Return codes reviewed; non-zero success codes (for example reboot required) added where the installer uses them

## 2. Detection rule

The detection rule decides whether Intune believes the app is installed. A wrong rule is the most common cause of an app that installs but reports failed, or reinstalls on every sync.

- [ ] Rule tests something only this version leaves behind (MSI product code, file version, registry value or script)
- [ ] File or registry rule uses the real path as a 64-bit process sees it; the 32-bit-on-64-bit setting checked if the app is 32-bit
- [ ] Rule fails on a clean device before install and passes after install
- [ ] Rule fails again after the uninstall command has run
- [ ] A newer version of the app would not satisfy the rule for the old version, and the reverse
- [ ] If a script rule is used: exits 0 and writes to STDOUT only when the app is present

## 3. Requirements and dependencies

- [ ] Minimum Windows version and architecture set
- [ ] Disk space and any prerequisite (runtime, driver, other app) set as a requirement or dependency
- [ ] Supersedence configured if this replaces an older app, with the uninstall-previous choice made deliberately
- [ ] Conflicts with an existing ConfigMgr or manual install of the same app considered

## 4. Assignment and evidence

- [ ] Assigned to the pilot group only, as required or available as intended
- [ ] Install tested on at least one device of each hardware model in the pilot
- [ ] Checked `IntuneManagementExtension.log` and `AgentExecutor.log` under `C:\ProgramData\Microsoft\IntuneManagementExtension\Logs` for the install and detection result
- [ ] Reported status in the Intune portal matches the state on the device
- [ ] Rollback decided: remove the assignment, or assign the uninstall intent to the pilot group
- [ ] Service desk told what the app is, when it lands, and what a failed install looks like

Result: REPLACE (Ready for broad assignment / Needs rework)  
Reviewer: REPLACE-NAME  Date: REPLACE-DATE