Adding Software to Intune with PsADT

After doing several tests and trying to understand the best way of adding software to our company portal I put together the following process: This process starts with PsADT or the PowerShell App Deployment Toolkit which as its name implies, helps you deploy apps. (It’s nice when names of things describe what they do right?) 

The one thing that Is inconvenient when using the PsADT is that you need to include all of the files that come packaged with PsADT in every software package you are deploying. Which means that either we have to adapt PsADT each time we want to make a new package or we can customize it one time and then reuse that template for each new package we want to deploy.

Enter Post Haste a software to help you create templates out of a folder and set of files. Using Post Haste we can quickly get our template coppied into our local deployment package folder including an output folder where we will hold our intune win file, and a folder for any downloads we might have acquired in putting this package together. 

After we have put everything together we can use Microsoft’s Content Prep Tool to compile our setup file.

Once we have an .intunewin file we want to test it and make sure that it works which is where we will use the Windows Sandbox in conjunction with Run-In-Sandbox to create a throw-away sandbox to test our new app package. We will also use this opportunity to capture the MSI Install code that we will use in the next step…

With everything there happy, We can upload our app package to the Intune Portal, assign it to a group of users, and Bob’s your uncle.