Intune Deployment

Intune Deployment Guide

This guide walks through the process of packaging and deploying the M365 Apps Deployment Toolkit via Microsoft Intune as a Win32 application.

Prerequisites

• Microsoft Intune administrator access
• Microsoft Win32 Content Prep Tool
• The M365 Apps Deployment Toolkit files
• Proper licensing for the Microsoft 365 applications you want to deploy

Step 1: Prepare the Package

1. Download or clone the toolkit repository to your local machine
2. Make any necessary customizations to the XML configuration files:
   • Modify config/install-office365.xml for your organization's needs
   • Update settings like update channel, language, and excluded apps
3. Verify your script parameters in the commands you plan to use

Step 2: Package with the Win32 Content Prep Tool

1. Download the Microsoft Win32 Content Prep Tool
2. Open Command Prompt or PowerShell and navigate to the Win32 Content Prep Tool location
3. Run the preparation tool with the following command:

IntuneWinAppUtil.exe -c "C:\Path\To\M365-Apps-Deployment-Toolkit" -s "Install-Microsoft365Apps.ps1" -o "C:\Path\To\Output\Folder"

This creates an .intunewin file that contains the entire toolkit.

Step 3: Create the Intune Application

1. Log in to the Microsoft Endpoint Manager admin center
2. Navigate to Apps > All apps > + Add
3. Select Windows app (Win32) for the app type and click Select
4. Upload your package file:
   • Click Select app package file
   • Browse to your .intunewin file location and select it
   • Click OK
5. Enter app information:
   • Name: Microsoft 365 Apps for Business (or your preferred name)
   • Description: Add description from the assets/description.md file
   • Publisher: Your organization name
   • Category: Office (or your preferred category)
   • Logo: Upload the logo from assets/microsoft365-logo.png
   • Click Next

Step 4: Configure Program Settings

1. Install command: Use one of the following commands based on your deployment needs:

# Standard installation
PowerShell.exe -NoProfile -ExecutionPolicy Bypass -File "Install-Microsoft365Apps.ps1" -ConfigXMLPath "config\install-office365.xml"

# Installation with consumer Office removal
PowerShell.exe -NoProfile -ExecutionPolicy Bypass -File "Install-Microsoft365Apps.ps1" -ConfigXMLPath "config\install-office365.xml" -RemoveConsumerOffice

# Force installation even if Office is already installed
PowerShell.exe -NoProfile -ExecutionPolicy Bypass -File "Install-Microsoft365Apps.ps1" -ConfigXMLPath "config\install-office365.xml" -Force

# Uninstall existing Office products first
PowerShell.exe -NoProfile -ExecutionPolicy Bypass -File "Install-Microsoft365Apps.ps1" -ConfigXMLPath "config\install-office365.xml" -UninstallExisting

2. Uninstall command:

PowerShell.exe -NoProfile -ExecutionPolicy Bypass -File "Install-Microsoft365Apps.ps1" -ConfigXMLPath "config\uninstall-office365.xml" -Uninstall

3. Additional configuration:
   • Install behavior: System
   • Device restart behavior: Determine behavior based on return codes
   • Installation for system: Yes
   • Installation for user: No
   • Run as 32-bit app on 64-bit clients: No
   • Click Next

Step 5: Configure Requirements

1. Operating system architecture: 64-bit
2. Minimum operating system: Windows 10 1809 or higher (as appropriate for your environment)
3. Disk space required (MB): 4000 (or your preferred value)
4. Click Next

Step 6: Configure Detection Rules

Use registry detection for the most reliable results. You need to select the appropriate registry key based on the product and language you're installing.

1. Rule format: Use the manually configured detection rules
2. Click Add
3. Choose Registry
4. Configure the rule:
   • Key path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\O365BusinessRetail - en-us (Replace en-us with your deployment language if different)
   • Value name: DisplayName
   • Detection method: Value exists
   • Associated with a 32-bit app on 64-bit clients: No
5. Click OK and then Next

Note: For Visio or Project, use the appropriate key path:

• Visio: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\VisioProRetail - en-us
• Project: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ProjectProRetail - en-us

Step 7: Configure Dependencies and Supersedence

1. Configure any dependencies if needed (typically none required)
2. Configure supersedence if replacing an older version
3. Click Next

Step 8: Configure Assignments

1. Select the appropriate groups for deployment
2. Choose the assignment type:
   • Required: Will automatically install on devices in the selected groups
   • Available: Users can install from the Company Portal
3. Configure installation deadlines and delivery optimization if using required assignment
4. Click Next

Step 9: Review and Create

1. Review all settings
2. Click Create to finish

Deployment Tips

• Test in a controlled environment before broad deployment
• Consider staged rollouts to different groups
• Monitor deployment through the Intune reporting interface
• Create separate applications for Visio and Project if needed
• Use available-intent assignments for optional installs like Visio/Project
• Leverage your README descriptions for Company Portal information

Troubleshooting Intune Deployments

• Check installation logs located in %TEMP%\Microsoft365Install_*.log
• Verify detection rules are correctly configured for your language and product
• Use the Intune Management Extension logs for troubleshooting:
  • %ProgramData%\Microsoft\IntuneManagementExtension\Logs
• Test the script locally with the same parameters to verify functionality

Multiple Product Deployments

If you need to deploy Microsoft 365 Apps, Visio, and Project, consider these approaches:

1. Separate applications: Create individual Intune applications for each product

   • Pros: Flexible assignments, clearer reporting
   • Cons: More management overhead

2. Single application with dependencies: Create a base Office app and dependent Visio/Project apps

   • Pros: Ensures proper installation order
   • Cons: More complex setup

3. Combined configuration: Modify your XML to include all products

   • Pros: Simplest setup
   • Cons: Less flexibility for targeted deployments

---

For more information on Intune Win32 app management, see the Microsoft documentation.