Win32 content prep tool Next step will be to use the Win32 content prep tool to wrap everything together in to a.INTUNEWIN file that we will be uploading in to Intune. Upload and create a Win32 app in Intune As we would do with any Win32 app in Intune we create a new app and upload the content and assign it to our devices or users. Microsoft Win32 Content Prep Tool. The content prep tool allows Intune Administrators to wrap install files for Win32 Applications, and use silent install switches or custom install scripts to install the wrapped application. Solution Breakdown. Intune runs the the Configure.ps1 PowerShell Script (shown below).

Use the Intune App Wrapping Tool for Mac to enable Mac apps to be managed by Microsoft Intune. Important The.pkg file must be signed using 'Developer ID Installer' certificate, obtained from an Apple Developer account.
Microsoft recently released the Microsoft Intune App Wrapping Tool for Android that allows you to take your Line of Business (LOB) apps and make them managed. By making an app managed, you add an extra layer of restrictions around the app to restrict operations like cut, copy and paste or open web links in a managed browser.

Win32 Apps, What Are they?

If you’re familiar with Configuration Manager/MEMCM then think of these files as your source directory, the difference being you are effectively zipping it up and then uploading to Intune.

According to Microsoft, if you decide to use Win32 Apps, it is advised that you use these exclusively and NOT ‘Mix and Match’ these with Line of Business applications when using Autopilot (See Microsoft Doc link below).

What content can be in a Win32 App Package?

The answer to that is well pretty much anything to a certain extent. These files are just proprietary files for Intune however under the hood they are just zip files that are then hashed and encoded.

What uses are there for Win32 Apps?

Well put, to Install apps. Now don’t be thrown by the 32 as these are not just for 32-bit apps, they can be used for any app.

You can use Win32 apps to just launch PowerShell scripts, Batch scripts, VBScripts etc. as long as you have a detection method if they succeed.

Mainly they are used for installing custom app packages like Greenshot, Citrix, PSADT Apps etc.

Microsoft Doc: Win32 app management in Microsoft Intune | Microsoft Docs

Package Creation Methods

IntuneWinAppUtil Application

The first method is creating a packaged using the GUI (Well kind of GUI) that is mentioned in the Microsoft Doc. Yiu can grab the utility from the below link;

If you clone/download the files, and extract them to a suitable location to work with.

Let’s get started. The below works on the assumption you have your files in a folder with noting other than those required for the app. (You don’t want to be uploading your entire desktop do you :P)

Launch the IntuneWinAppUtil.exe
Type/Paste your Source Directory (e.g. C:/Win 32 Apps/7-Zip), hit Enter.
Type/Paste you setup file name (e.g. 7z2002-x64.exe or MyScript.ps1), hit Enter
Type/Paste your Output Directory (e.g. C:/Win 32 Apps), hit Enter.
When prompted about catalogue files type N unless you are deploying to Windows S Mode, hit Enter

The window will automatically close when your .intunewin file is finished if you head over your output folder you will be able to get your file for upload.

PowerShell

For you command-line gurus and script lovers out there, you will be pleased to know that there is a PowerShell module for bundling these your apps up, you can even go a step further and import them via a script, but we will save that for another post :D.

You can install the module using the following command;

Once you have the module installed you can type a command like this;

This command will create a .intunewin file in the output location named 7z2002-x64.intunewin, this is because it takes the installers name for the output. Unfortunately at the time of writing this, you can’t do it natively with this module. However, you can add a Rename-Item into your script to change it.

Using the packages with Intune

Head over to Microsoft Endpoint Manager admin center (Intune) to to get started

Select Apps from the navigation pane
Select All Apps, Click Add
Select App type Other>Windows app (Win32), Click Select
Click Select app package file, Click the Blue Folder icon to open the browse windows
Select the .intunewin file you have created, Click Open and then click OK
Fill out the Name and Publisher mandatory fields, and any other fields you desire
Upload an icon if you desire, I would recommend doing this if you are deploying this to users via the Company Portal
Click Next
Enter your install command (e.g. 7z2002-x64.exe /S)
Enter your uninstall command (e.g. 'C:Program Files7-ZipUninstall.exe'/S)
Select your install behavior, if this is a machine wide installation you will need to select System, otherwise select User if this is installing to the user profile
Select your desired restart behavior, Adding custom return codes if required
Click Next
Complete your OS Requirements, At a minimum you need to specify the Architecture (x86/x64) and the minimum OS Version (e.g. 1607/1703 etc.)
Click Next
For Detection rules, See the Detection Rules section below, Once complete click Next
Add any dependent Intune Apps you may require, Click Next
Assign the application to your desired group, just as a NOTE if you want to display the app in the company portal, it MUST be assigned to a group containing that user. Required Assignments will force the app to install, whereas Available will show this in the Company Portal. Click Next
Click Create

That is your app finished and deploying, it is worth noting it may take 15/20 minutes

Microsoft Intune App Wrapping Tool For Ios

to be available on the device, the device must also perform a sync to check for the app.

Detection Rules

Detection rules have 4 options, you can use a Custom Detection Script, Registry, File(Folder) and MSI, lets look at them in a little bit more detail.

When you first reach the Detection Rule Screen you will have a single Drop-Down box with two options, Use a custom detection script and Manually configure detection rules. File, Registry and MSI are all available under the Manual option, it is worth noting that you can can mix and match these rules, however there are considered AND methods. If you are looking to do a AND/OR detection you will need to use a custom PowerShell Script.

We will dive into all of the options below.

File

As you can see above using this detection method is fairly straight forward, however it can get a bit messy if you use the Date Created/Modified options.

Lets put a rule together.

Rule Type - File
Path - 'YourPath' (e.g. C:Program Files7-Zip)
File or Folder - 'YourFileFolder' (e.g. 7z.exe)
Detection Method - File or Folder Exists
Associated with a 32-bit app on a 64-bit client, No.

Now that rule is very quick and simple, as mentioned you can use the date modified or created option, and that would look something like below.

Rule Type - File
Path - 'YourPath' (e.g. C:Program Files7-Zip)
File or Folder - 'YourFileFolder' (e.g. 7z.exe)
Detection Method - Date Modified
Operator, select the option that you wish to validate against (e.g. Equals, Greater than etc.)
Select the date using the date picker and enter the time using the 12 hour format
Associated with a 32-bit app on a 64-bit client, No.

Registry

The registry option