Intune Win32 App Deployment: Complete Guide - CyberSystem Blog

Win32 app management in Microsoft Intune enables you to deploy traditional Windows applications (MSI, EXE, script installers) to your managed devices. This capability provides advanced features like dependencies, detection rules, and delivery optimization that aren't available with traditional line-of-business apps.

Understanding Win32 Apps in Intune

Win32 app management in Intune allows you to deploy desktop applications packaged in the .intunewin format. This provides more flexibility and benefits compared to traditional app deployment methods.

Key Benefits

Advanced Detection Rules: Multiple detection methods (MSI, file, registry)
Dependencies: Define app dependencies and installation order
Requirements: Configure device and user requirements
Delivery Optimization: Leverage Windows Delivery Optimization
Enrollment Status Page: Support for Windows Autopilot ESP
User and Device Context: Deploy in user or device context

For an overview, see Win32 app management in Microsoft Intune.

Preparing Win32 Apps

Step 1: Prepare Application Files

Before packaging, ensure you have:

Application installer files (MSI, EXE, or scripts)
All required files and dependencies
Silent installation commands
Uninstall commands (if applicable)

Step 2: Use Win32 Content Prep Tool

The Microsoft Win32 Content Prep Tool converts your application files into the .intunewin format required by Intune.

Download and Install:

Download from GitHub: Microsoft-Win32-Content-Prep-Tool
Extract to a folder
Keep the tool separate from installer files

Run the Tool:

IntuneWinAppUtil.exe -c <setup_folder> -s <setup_file> -o <output_folder>

Parameters:

-c: Folder containing all setup files
-s: Setup file (e.g., setup.exe or setup.msi)
-o: Output folder for .intunewin file
-q: Quiet mode

Example:

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

For detailed guidance, see Prepare Win32 App Content for Upload.

Adding Win32 Apps to Intune

Step 1: Access Apps

Sign in to the Microsoft Intune admin center
Navigate to Apps > All apps
Select Create

Step 2: Select App Type

Select Windows app (Win32)
Select Select

Step 3: App Information

Configure app details:

Select app package file: Upload the .intunewin file
Name: Application name
Description: Application description
Publisher: Application publisher
App version: Version number
Logo: Upload app icon (optional)
Category: Select app category (optional)
Show this as a featured app: Yes/No
Information URL: URL with app information
Privacy URL: URL with privacy information
Developer: Developer name (optional)
Owner: Owner name (optional)
Notes: Additional notes (optional)

Select Next to continue.

Step 4: Program

Configure installation and removal commands:

Install command: Complete command line to install the app
- Example for MSI: msiexec /i "MyApp.msi" /quiet /norestart
- Example for EXE: setup.exe /quiet /norestart
Uninstall command: Complete command line to uninstall
- Example for MSI: msiexec /x "{GUID}" /quiet
- Example for EXE: uninstall.exe /quiet
Installation behavior:
- System: Install for all users
- User: Install for current user
Device restart behavior:
- Allow: Allow restart if needed
- Force: Force restart
- Suppress: Suppress restart
Installation time required: Minutes to wait (default: 60, max: 1440)
Allow available uninstall: Allow users to uninstall from Company Portal

Important: Test installation commands in a test environment before deploying.

Select Next to continue.

Step 5: Requirements

Configure device and user requirements:

Operating system architecture:
- 32-bit, 64-bit, or both
Minimum operating system:
- Windows 10/11 version requirements
Additional requirement rules:
- Add custom requirements using PowerShell scripts
- Configure disk space requirements
- Configure memory requirements

Select Next to continue.

Step 6: Detection Rules

Configure how Intune detects if the app is installed:

Detection Rule Format:

Manually configure detection rules: Use built-in detection methods
Use a custom detection script: Use PowerShell script

Detection Methods:

MSI: Detect based on MSI product code
- MSI product code: Enter product GUID
- MSI product version check: Verify version (optional)
File: Detect based on file or folder
- Path: Full path to file/folder
- File or folder: File or folder name
- Detection method:
  - File or folder exists
  - Date modified
  - Date created
  - Version
  - Size
Registry: Detect based on registry key
- Key path: Registry key path
- Value name: Registry value name
- Detection method:
  - Key exists
  - Value exists
  - String comparison
  - Integer comparison
  - Version comparison

Best Practice: Use MSI product code when available for most reliable detection.

Select Next to continue.

Step 7: Dependencies

Configure app dependencies (optional):

Add dependency: Select apps that must be installed first
Auto install: Automatically install dependencies
Dependency groups: Organize dependencies

Note: Dependencies must be Win32 apps already added to Intune.

Select Next to continue.

Step 8: Supersedence

Configure app supersedence (optional):

Add superseded app: Select apps this app supersedes
Uninstall previous version: Uninstall superseded apps
Upgrade behavior: Configure upgrade settings

Select Next to continue.

Step 9: Assignments

Assign the app to groups:

Required: Apps installed automatically
- Add groups for required installation
- Configure end user notifications
- Set installation deadline
Available for enrolled devices: Apps available in Company Portal
- Add groups for available apps
- Users can install from Company Portal
Uninstall: Remove app from devices
- Add groups for uninstallation

Best Practice:

Use device groups for device context installations
Use user groups for user context installations
Test with small groups first

Select Next to continue.

Step 10: Review and Create

Review all settings
Select Create to add the app

For step-by-step guidance, see Add, Assign, and Monitor a Win32 App in Microsoft Intune.

Deployment Contexts

Device Context

When to Use:

Apps needed for all users on a device
System-level applications
Apps that require administrator privileges

Requirements:

Device must be enrolled
App must support device context installation
Assign to device groups

User Context

When to Use:

User-specific applications
Apps that don't require system-level access
Per-user installations

Requirements:

User must be signed in
App must support user context installation
Can assign to user or device groups

Monitoring Win32 Apps

App Status

Monitor app installation status:

Go to Apps > All apps
Select the Win32 app
Review Device install status and User install status

Status Types

Installed: App successfully installed
Failed: Installation failed
Not installed: App not yet installed
Installing: Installation in progress
Uninstalled: App removed

Detailed Reports

View detailed installation reports:

Device install status: Per-device installation status
User install status: Per-user installation status
Installation errors: Detailed error information

Best Practices

1. Test Installation Commands

Test in isolated environment first
Verify silent installation works
Test uninstall commands
Document any issues

2. Use Reliable Detection Rules

Prefer MSI product code when available
Use file detection as backup
Test detection rules before deployment
Avoid registry detection when possible

3. Configure Dependencies

Identify all dependencies
Add dependencies to Intune first
Configure auto-install for dependencies
Test dependency installation order

4. Use Appropriate Context

Use device context for system apps
Use user context for user-specific apps
Consider user experience
Test both contexts if needed

5. Monitor Deployments

Monitor installation status regularly
Address failures promptly
Review error messages
Adjust deployment as needed

Troubleshooting

Common Issues

Installation Fails
- Verify installation command syntax
- Check device requirements
- Review installation logs
- Test command manually
Detection Rules Not Working
- Verify detection rule configuration
- Test detection manually
- Check file paths and registry keys
- Use alternative detection methods
Dependencies Not Installing
- Verify dependencies are added to Intune
- Check dependency assignments
- Review installation order
- Test dependencies independently

For troubleshooting guidance, see Support Tip - Understanding the flow behind deployment, delivery, and processing of a Win32 application through Intune.

Additional Resources

Conclusion

Win32 app management provides powerful capabilities for deploying traditional Windows applications in Intune. By following these best practices:

✅ Prepare apps properly using the Win32 Content Prep Tool
✅ Test installation commands before deployment
✅ Use reliable detection rules
✅ Configure dependencies appropriately
✅ Monitor deployments regularly

You can successfully deploy and manage Win32 applications across your organization while leveraging advanced features like dependencies, requirements, and delivery optimization.

Remember: Win32 apps provide more flexibility than traditional line-of-business apps. Take advantage of advanced features like detection rules, dependencies, and requirements to create robust application deployments.