Win32 Application Creation

This guide will provide background information on creating an application package deployment that will be carried out to the specified device group.

Win32 Apps

If you would like to deploy applications down to computers, you must package the application in a method that is recognizable to Intune. This involves gathering the application itself, and then using the Microsoft Win32 Content Prep Tool to package the app.

Role Requirements

Procedure Scope: Administrators

Required Group Membership: Admin.Security

Handbook Reference

Package: TBD

Domain: TBD

Modifies: TBD

Deploying Win32 Apps

Now that the app package is created, it is time to deploy the app with Intune.

1.  Navigate to the Apps – Intune portal, select Add, followed by selecting the Windows App (Win32) from the drop down. Click Select to continue.
   
2. Click Select App Package File, followed by the Blue Folder Icon, then select the file with Open, and click OK.
   
3. Information about the app will need to be filled in. At a minimum, fill in the Publisher box with the correct publisher. Other items may be entered if desired.
   
4. The next step will ask for the install and uninstall command. This part will be fully dependent on the software creator and revolves around the command line support the application has. For EXE files, searching for {App Name} Command Line Silent Install will usually yield helpful results in deciphering an install and uninstall command. For MSI files, the field should be pre-populated, and you are good to go. Ensure the fields are filled and click Next.
   
5. Options for system requirements will be shown. At a minimum, the Operating System Architecture and Minimum Operating System fields must be filled in. These fields are at the discretion of the creator, as requirements may be unique to each deployment. Click Next.
   
6. The detection rules must be set to detect if the application has installed correctly. For MSI files, clicking Manually Configure Detection Rules, clicking Add, selecting MSI as the rule type, and using the auto populated field should usually work. It is recommended that the File rule type is used though, inputting the path to the program within program files, the executable name itself, and the detection method to File or Folder Exists. This method is more effective because updates will not sidetrack the detection process. When filled in, click Ok followed by Next.
   
7. You will be able to configure software dependencies for application installation, a device will have to have a prerequisite software before it will allow installation of another application; if you want to create a dependency the other software must have an Intune Application Deployment in place so that it can be used as a reference; click Next.
   
8. You can also create a requirement that will replace or update a software with a newer application, if you want to create a supersedence you will need to specify the previously created deployment package that the current package will be replacing; click Next.
   
9. Specify the way in which the app should be deployed, and to whom. Required will ensure that the app is installed on the devices included in the groups, while Available for Enrolled Devices will show the app in the company portal. For either, the assignment group of Devices.Corporate is recommended to install the application on corporate devices. Other groups may be used. Once selected, click Next.
   
10. The review page will allow you to see all configured settings for the application creation process, if you detect a discrepancy at this stage make note of the section and select Previous to go back to make alterations before finalization. If everything checks out, select Create to publish the application.
    
11. The application has been created and should begin pushing installation to computers; this deployment could take up to 8 hours.

Need Assistance?