Add apps for Windows PCs that run the Intune software client
|Applies to: Intune in the classic portal|
|Looking for documentation about Intune in the Azure portal? Go here.|
Use the information in this topic to learn how to add apps to Intune before you deploy them.
The information in this topic helps you add apps for Windows PCs that you manage by using the Intune software client. If you want to add apps for enrolled Windows PCs and other mobile devices, see Add apps for mobile devices in Microsoft Intune.
To install apps to PCs, they must be capable of being installed silently, with no user interaction. If this is not the case, the installation will fail.
Add the app
You use the Intune Software Publisher to configure the properties of the app and upload it to your cloud storage space by using the following procedure:
In the Microsoft Intune administrator console, choose Apps > Add Apps to start the Intune Software Publisher.
You might need to enter your Intune user name and password before the publisher starts.
On the Software setup page of the publisher, under Select how this software is made available to devices, choose Software installer, and then specify:
- Select the software installer file type. This indicates the type of software that you want to deploy. For a Windows PC, choose Windows Installer.
- Specify the location of the software setup files. Enter the location of the installation files, or choose Browse to select the location from a list.
- Include additional files and subfolders from the same folder. Some software that uses Windows Installer requires supporting files. These must be located in the same folder as the installation file. Select this option if you also want to deploy these supporting files.
For example, if you want to publish an app named Application.msi to Intune, the page would look like this:
This installation type uses some of your cloud storage space.
On the Software description page, configure the following.
Depending on the installer file that you are using, some of these values might have been automatically entered, or they might not appear.
- Publisher. Enter the name of the publisher of the app.
- Name. Enter the name of the app as it will be displayed in the company portal.
Make sure all app names that you use are unique. If the same app name exists twice, only one of the apps will be displayed to users in the company portal.
- Description. Enter a description for the app. This will be displayed to users in the company portal.
- URL for software information (optional). Enter the URL of a website that contains information about this app. The URL will be displayed to users in the company portal.
- Privacy URL (optional). Enter the URL of a website that contains privacy information for this app. The URL will be displayed to users in the company portal.
- Category (optional). Select one of the built-in app categories. This will make it easier for users to find the app when they browse the company portal.
- Icon (optional). Upload an icon that will be associated with the app. This is the icon that will be displayed with the app when users browse the company portal.
On the Requirements page, select the requirements that must be met before the app can be installed. Choose from:
- Architecture. Select whether this app can be installed on 32-bit, 64-bit, or both operating systems.
- Operating System. Select the minimum operating system on which this app can be installed.
On the Detection rules page, you can configure rules to detect whether the app that you are configuring is already installed on a PC. Or, you can use the default detection rules to automatically overwrite any previously installed versions of the app. This option is for Windows Installer (.exe files only).
The rules that you can configure are:
- File exists. Specify the path to the file that you want to detect. You can search under %ProgramFiles% (which searches Program Files<path> and Program Files (x86)<path>) on the PC or %SystemDrive% (which searches from the root drive of the PC, typically drive C).
- MSI product code exists. Choose Browse to choose the Windows Installer (.msi) file that you want to detect.
- Registry key exists. Specify a registry key that begins with HKEY_LOCAL_MACHINE</strong>. Both 32-bit and 64-bit registry paths are searched. If the key that you specified exists in either location, the detection rule is satisfied.
If the app satisfies any of the rules that you have configured, it will not be installed.
For the Windows Installer file type only (.msi and .exe): On the Command line arguments page, choose whether you want to supply optional command-line arguments for the installer. The following parameters are added automatically by Intune:
- For .exe files, /install is added.
- For .msi files, /quiet is added. Note that these options will only work if the creator of the app package enabled functionality for this.
For the Windows Installer file type only (.exe only): On the Return codes page, you can add new error codes that Intune interprets when the app is installed on a managed Windows PC.
By default, Intune uses industry-standard return codes to report the failure or success of an app package installation: 0 (Success) or 3010 (Success with restart). You can also add your own return codes to this list. If you specify a list of return codes and the app installation returns a code that isn't on the list, it is interpreted as a failure.
On the Summary page, review the information that you specified. When you are ready, choose Upload.
Choose Close to finish.
The app is displayed on the Apps node of the Apps workspace.
After you've created an app, the next step is to deploy it. To find out more, see Deploy apps in Microsoft Intune.
If you want to read more information about tips and tricks to deploy software to Windows PCs, see the blog post Support Tip: Best Practices for Intune Software Distribution to PC’s.