Packaging & Deploying Win32 Apps in Microsoft Intune | EndPoint Sphere

We’ve explored compliance, Conditional Access, and app-level protection. We move into one of the most practical and high-impact areas of endpoint management:


Win32 App Deployment in Microsoft Intune

If your organization uses custom apps, legacy software, or enterprise tools, this is a must-know skill.




What is a Win32 App in Intune?


A Win32 app is any traditional Windows application packaged as:

intunewin format


This format allows Intune to:

  • Deploy apps silently
  • Track installation status
  • Apply detection logic
  • Manage dependencies


Why Win32 Apps Matter


Modern enterprises rely on:

  • Legacy business applications
  • Custom-built internal tools
  • Third-party EXE/MSI installers

Intune Win32 apps provide full control over deployment lifecycle




Real-World Scenario


An organization wants to deploy:

  • Custom finance app (EXE)
  • VPN client
  • Internal IT tool

Requirements:

  • Silent install
  • Detect if already installed
  • Auto-reinstall if removed

Win32 app deployment solves this.




Win32 App Packaging – Overview


Before deployment, apps must be converted.


Process:

Original App (EXE/MSI)

        ↓

Intune Packaging Tool

        ↓

.intunewin file




Step-by-Step: Create a Win32 App Package




Step 1: Download Tool


Get: Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe)




Step 2: Prepare Source Folder


Organize files:

C:\AppSource\

├ setup.exe

├ install.cmd (optional)

├ config files




Step 3: Package the App


Run command:

IntuneWinAppUtil.exe -c C:\AppSource -s setup.exe -o C:\Output

Output: appname.intunewin




Upload & Configure in Intune




Step 4: Upload App


Intune Admin Center →
Apps → Windows → Add → Win32 app

Upload .intunewin file




Step 5: Configure App Info


  • Name
  • Description
  • Publisher
  • Category


Step 6: Program Settings


Define commands:


Install Command:

setup.exe /silent /install


Uninstall Command:

setup.exe /uninstall /quiet




Step 7: Detection Rules (Critical)


Tell Intune how to verify installation.


Options:

  • File existence
  • Registry key
  • MSI product code

Example:

Path: C:\Program Files\App\

File: app.exe




Step 8: Requirements Rules


Define device conditions:

  • OS version
  • Architecture (x86/x64)
  • Disk space

Example:

Install only on Windows 10/11 x64





Step 9: Dependencies (Optional)


Apps that must install first:

  • .NET Framework
  • VC++ Redistributable


Step 10: Assign App


Assign to:

  • User groups
  • Device groups

Modes:

  • Required (auto install)
  • Available (user installs)
  • Uninstall


Deployment Flow


User logs in

     ↓

Device checks Intune

     ↓

Policy + App assigned

     ↓

App downloads silently

     ↓

Detection rule validates

     ↓

Status reported (Success/Failed)



Advanced Features




1. Supersedence (App Updates)


Replace old apps automatically:

  • Old version → removed
  • New version → installed

Useful for:

Version upgrades without user action



2. App Monitoring


Track:

  • Install success rate
  • Failures
  • Device status

Reports → App install status




3. Return Codes


Customize install results:


Code

Meaning

0

Success

3010

Soft reboot required

1641

Hard reboot




4. Retry & Error Handling


  • Auto retry failed installs
  • Capture logs
  • Troubleshoot using Intune logs


Common Mistakes




1. Incorrect Detection Rules

App installs repeatedly if detection fails




2. No Silent Install Switch

Installation stuck waiting for user input




3. Ignoring Dependencies

App fails due to missing prerequisites




4. Poor Packaging Structure

Missing files cause deployment errors




Enterprise Strategy



Layered Deployment Design


Core Apps (Required)

  • Security tools
  • VPN
  • Monitoring agents

Business Apps (Required/Available)


  • CRM
  • Finance tools


Optional Apps (Self-Service)

  • Utilities
  • Productivity apps


Real Use Case


IT Department:

  • Auto install admin tools

Employees:

  • Access apps via Company Portal


Best Practices

Always test locally before packaging
Use clear naming convention (AppName-Version)
Validate detection rules carefully
Use dependencies for prerequisites
Monitor deployment continuously




What You Learned Today


What Win32 apps are in Intune
How to package apps into .intunewin
Deployment configuration steps
Detection rules & dependencies
Real-world enterprise strategies




Final Thought:


"Automation isn’t just about deploying apps. it’s about delivering the right tools, at the right time, silently and securely."

Post a Comment

Previous Post Next Post