However, I like to have my applications all under the Intune Applications blade instead of the configuration blade for ease of management and administration purposes. If you decided to use Intune configuration PowerShell scripts, you also would not need to wrap anything in the INTUNEWIN format or specify install directories.

Configure the application with any install switches, or uninstall switches within the Intune blade.

Find the uninstall process and switches.

However, if we used Chocolatey, a package manager and installer for software packages, we could considerably speed up the Intune application package deployment process because we would no longer need to: This process may need to be replicated when the application is upgraded, and you want to push out the updated app to your Intune devices.

Configure the application with the install and uninstall switches as well as the directory it creates to Intune knows if it installed correctly or not.

Wrap the executable in an ‘INTUNEWIN’ format.

Find the uninstall executable and any switches it has as well.

Find the install directory or registry key to tell Intune if it installed correctly or not.

Find the install switches – most common one is the silent switch, but some applications may have other switches you will need as well.

Currently, if the application is bundled as an executable (exe), the steps to get it into Intune is as follows: One of the most time-consuming tasks with Intune is the application portion, where you package applications up to deploy to your end-user machines. Recently, I have been doing a lot of Microsoft Intune deployments and write up’s.

2 – Install Applications Using Intune + Chocolatey – Examples.

Ninite adobe reader