Windows 10/11 App Deployment Using Intune

Microsoft Intune is a 100% cloud-based mobile device management and mobile application provider for your apps and devices. It lets you control features and settings on Android, Android Enterprise, iOS/iPadOS, macOS and Windows 10 devices. It integrates with other services, including Azure Active Directory (AAD), mobile threat defenders, ADMX templates, Win32 and custom LOB apps and more. As part of Endpoint Manager, use Intune to create and check for compliance, and deploy apps and features and settings to your devices using the cloud.

Prerequisites 

• An active Intune License

In this article, we will see how to create and assign Win32 apps. Before you can add a Win32 app to Microsoft Intune, you must prepare the app by using the Microsoft Win32 Content Prep Tool. You use the Microsoft Win32 Content Prep Tool to pre-process Windows classic (Win32) apps. The tool converts application installation files into the .intunewin format.

Scenario 1: Using Windows Installer MSI file

Step 1

Before you can add a Win32 app to Microsoft Intune, you must prepare the app by using the Microsoft Win32 Content Prep Tool

Download GitHub - microsoft/Microsoft-Win32-Content-Prep-Tool: A tool to wrap Win32 App and then it can be uploaded to Intune

Step 2

Create a New Folder and place the Win32 Content Prep tool

Step 3

Place the MSI file downloaded from Google Chrome in Input folder shown above

Step 4

Open IntuneWinAppUtil by double clicking on it

Step 5

Copy, paste the path of Input Folder and press Enter

Step 6

Enter the name of the setup file, in our case “5. Googlechrome.msi”

Step 7

 Copy, paste the path of Output Folder and press Enter. Type N for specifying Catalog folder and press Enter

Step 8

The tool will wrap the application with a progress bar at the bottom of the screen. Once completed you will find the application on the Output folder with an extension “intunewin”

Step 9

Visit the Microsoft Endpoint Manager Admin portal and click Apps->All Apps blade.

Step 10

 Click on + Add button and in the App type dialog box select Windows app (Win32) and click Select

Step 11

 In the App Information tab, click Select app package file and upload the file obtained from Step 8

Step 12

 Enter the necessary details such as Name, Description, Publisher and upload the Logo and click Next

Step 13

Since it is an MSI, Install and Uninstall commands are populated automatically, in device restart behavior select No Specific Action and click Next

Step 14

Select the minimum OS architecture and OS version and click Next

Step 15

Here we are configuring rules used to detect the presence of the app so that Intune will stop trying to install and return a Success code.

Since it is an MSI, product code is populated automatically. In addition to this, we can also use Rule Type as File to detect the file location (more in scenario 2).

Step 16

Dependencies is left untouched as there are no requirements for this application. However, application involving additional patch (mst files) can be uploaded here.

*Software dependencies are applications that must be installed before this application can be installed. ​

Step 17

Supersedence (Preview) is left untouched as there are no requirements for this application

*When you supersede an application, you can specify which app will be updated or replaced. To update an app, disable the uninstall previous version option.

Step 18

Assignments tab has:

Required – App will be automatically installed without user intervention on enrolled devices

Available for Enrolled devices – App will be available for download from Company Portal application

Uninstall – Will remove the application from the enrolled device

We will select Available for enrolled device and proceed.

Step 19

We can review the summary of the conditions we have chosen and click Create

Step 20

User who enrolled the device with Company Portal installed will have the option to download the app.

Scenario 2: Using executable program EXE file

Step 1

Once the exe file is downloaded repeat Steps 4 to 12 from Scenario 1

Step 2

Since this is an exe file, in the Program tab fill the Install and Uninstall commands respectively.

Step 3

Select the minimum OS architecture and OS version in Requirements Tab and click Next

Step 4

In the Detection rule tab, we select the type as File. Enter the default complete path created once the application is installed in our device and also the executable application in that folder, in our case “teamviewer.exe”. (These folders are created when we install an application either in Program Files or Program Files (x86))

Step 5

In Assignment tab, we will select Available for enrolled device and proceed.

Step 6

We can review the summary of the conditions we have chosen and click Create

User Experience

Scenario 3: Microsoft 365 Apps for Windows 1 and later

Step 1

Click + Add blade from All Apps from Endpoint Manager Admin Center

Step 2

In App suite information tab, fill the required information and choose Yes for Show this as a featured app in Company Portal

Step 3

In Configure App Suite tab, under settings format select Configuration Designer.

(Alternatively, you can upload a custom XML data from Office Customization tool)

Access, Excel, OneNote, Outlook, Powerpoint, Publisher, Teams, Word are installed as default 8 apps. If you have license for Visio Online Plan 2 and Project Online Desktop Client they can be chosen.

Select the Architecture as 64-bit and Update Channel as Monthly Enterprise Channel, Click Next

Step 4

In the Assignments tab, select the Groups for which we want to enroll. As Office application is a part of daily activity it can be set as Required app.

Step 5

Users will have the suite installed silently on the background once their device syncs in.

Troubleshooting

The Intune Troubleshoot pane provides failure details, including details about managed apps, to help you address user help requests.

Once you select the user you can see the list of apps and by clicking on the app you can view installation issues, such as when the app was created, modified, targeted, and delivered to a device.

For further information on troubleshooting and collecting logs refer this article