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
Note
Before Attempting to create a new MDM Application Deployment, please verify that you have created the proper .intunewin file type derived from a desired application, this will be a necessary component during the creation process. The following guide for package creation can be found here.
Deploying Win32 Apps
Now that the app package is created, it is time to deploy the app with Intune.
- Navigate to the All Apps – Intune portal, locate and select Add followed by selecting the Windows App (Win32) from the App type drop down. Click Select to continue.
- Click Select App Package File, followed by the Blue Folder icon. Locate and select the desired .intunewin file from the housed directory, finalize the file explorer selection by clicking Open. Complete the App Package File selection by clicking OK.
- 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. Select Next to proceed.
- 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 possesses. For .exe files, searching for {App Name} Command Line Silent Install from a desired web browser will usually yield helpful results in deciphering Install and Uninstall commands. For .msi files, the field should be pre-populated, and you are good to go. Ensure the fields are filled and click Next.
- 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.
- 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 utilized, 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.
- 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.
- 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.
- You will be able to configure Group Assignments or Exclusion for the policy. 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. Locate and select the Add groups action. A pop-up will be displayed where you will supply the name of the group in the provided search bar, make sure to select the Group from the list. If done correctly they will be generated in the Selected Items section, finalize the addition by clicking Select. Select Next to proceed to revisions.
- 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.
- The application has been created and should begin pushing installation to computers; this deployment could take up to 8 hours.
Need Assistance?
Reach out to your Customer Success Manager to discuss how a Sittadel cybersecurity analyst can assist in managing these tasks for you. New to our services? Inquire about arranging a consultation to explore optimizing your Azure environment for painless management.