Catalog files are used to enable Win32 apps in Windows 10 S mode -- they are specific to Application Control which is the mechanism that S Mode uses to enforce and control applications. Running the Microsoft Win32 Content Prep Tool Finally, the AcroRead.intunewin file has been generated. When the process is complete, you will see a screen that looks like this. C:\IntuneWinAppUtil: This folder is for the tool which we will be using for converting the file to INTUNEWIN. It is a single exe file with no dependencies on other libraries, components, etc. For the following steps login to the Microsoft Azure Portal. 2. If -a is specified, all catalog files in that folder will be bundled into the .intunewin file. IntuneWinAppUtil -c <setup_folder> -s <source_setup_file> -o <output_folder> <-q> This will generate the .intunewin file from the specified source folder and setup file. You can see Detection.xml and the install source files. For MSI setup file, this tool will retrieve required information for Intune. Step 7. The encrtypted .intunewin (located in the content folder) can be distributed safely to the Intune back-end services responsible for content distribution without getting exposed to others, only the tenant who uploaded the file has the EncryptionInfo and can decrypt the file. Endpoint Manager Now its time to distribute the application using Endpoint Manger. You will see a progress bar as the .intunewin file is being created. Open up the Azure Portal and navigate to Intune>Client Apps>Apps and click Add. Lots of details on this at https://docs.microsoft.com/en-us/mem/intune/apps/apps-win32-s-mode. Once complete I have my .intunewin file ready for consumption. Step 2: Put the file in the respective folder. Compressing the source folder and its files to a sub folder 'content' with the new extension .intunewin. Navigate to: Microsoft Intune > Client apps > Apps and click the + Add button. The setup file is the actual executable and you need to specify an output folder where the .IntuneWin file will be saved. The Intunewin file is compressed and encrypted with a SHA256 hash (Intune Win32 App Deployment more details are available in the following section) Intune Application Deployment using MSI EXE IntuneWin Formats 4 You can use tools like 7-zip to extract the Intunewin file and see what's inside. Give it the name of the installer to run. Give it an output folder to put the .intunewin files in. Compressing the source folder of the Win32 apps and its files to a sub folder 'Contents' with the new extension .intunewin. Use the Microsoft Win32 Content Prep Tool to pre-process Windows Classic apps. Intune Win32 Package File Caching In \Incoming Folder. Note: The Intune Management Extension will be used for installing the Win32 app. Intune.intunewin.intunewin. Step 9- Select app type "Windows app (Win32)". Click OK to confirm. All files in this folder will be treated as catalog file for Win10 S mode. This tool is Intune Win 32 Prep Tool. Only the setup files for this app should be in this folder. Do you want to specify catalog folder - Type N. Wait for a few minutes while the Win32 Content Prep Tool runs. Compressing the source folder of the Win32 apps and its files to a sub folder 'Contents' with the new extension .intunewin. Compressing complete working folder and create again an .intunewin file. Generating a detection.xml file in a sub folder 'Metadata'. Step 8. Specify the output folder - The Win32 Content prep tool will place the final .intunewin file in this folder. Choose a different location than your source folder; For catalog folder . Your folder should now look like this Step 7- Sign in to the Azure portal and select the Intune blade. Manage Windows Apps (.intunewin) with Intune. -a <catalog_folder> Catalog folder for all catalog files. At this point we do not need a Catalog folder. The following 17 steps walk through all the steps to configure the Win32 app, by using the .intunewin file. The tool will wrap the application with a progress bar at the bottom of the screen. From App Package File Blade, Browse and select the IntuneWin package you want to upload (created above). 2. Create the . Enter N for the catalog folder and press enter. Even . Encrypting the compressed file. The packaging tool converts application installation files into the .intunewin format. Step 13- Detection rules tab. Copy, paste the path of Output Folder and press Enter. Now you will have Copy.intunewin created for deployment. Once the package has been created, you can use it in Endpoint Manager / Intune under Apps > Windows . 3. Step 11- On the program tab, follow as below screenshot. Important The Microsoft Win32 Content Prep Tool zips all files and subfolders when it creates the .intunewin file. The output folder is C:\Users\rob\Downloads, enter this path and press enter. From the Add app blade - Select the options called "Windows App (Win32)" from the drop-down list to upload the IntuneWin package. Press OK. Generating a detection.xml file in a sub folder 'metadata'. The tool also detects some of the attributes that Intune requires to determine the application installation state. setup.exe or setup.msi). Click the browse icon and upload the .intunewin file. See release notes for more information. If you don't specify command line arguments, a command prompt will pop up to ask you for the info it needs: Give it the folder your install files are in. Have a look at the detailed output there you can see exactly what the tool does: 1. From the list of App types, select Windows app (Win32). IntuneWinAppUtilGUI has a simple and clear interface. Step 12- Requirement tab. Source folder: specify the files which contains your installation files; Setup file: is the Dropbox offline installer files; Output folder: a folder where you want to save the intunewin file. Next, click Select file from the App package file section. Open the App package file blade and browse for the just created .intunewin file. There is 2 browse buttons and a create . Encrypting the compressed file. After the Utillity is ready you will end up with an .IntuneWin file. Computing SHA265 hash. For more information, see Win32 app management - Prepare the Win32 app content for upload. .exeIntune.intunewin Step 15- Review + create tab. Step 10 - Select the app package file which we created in step 6. Step 9. Generating a detection.xml file in a sub folder 'Metadata'. Now that you have prepared the files its time to wrap them into a intunewin file. App Package File - "Remote Desktop Connection Manager.IntuneWin" Name: Remote Desktop Connection Manager After you use this tool on the app installer folder, you'll be able to create a Win32 app in the Intune console. You don't need to type folders/files path. S Mode is more or less dead though so this is pretty much moot. Once completed you will find the application on the Output folder with an extension " intunewin ". Features. Step 14- Assignments. Therefore i created a little GUI frontend which will simply call the IntuneWinAppUtil.exe with the use values defined of a browse button. When generating the .intunewin file from the specified source folder and setup file, you can provide a separate folder containing only catalog files by using the -a cmdline option. Computing a SHA265 hash. Encrypting the compressed file. Compressing complete working folder and create again an .intunewin file. The setup file specified will result in the naming of your intunewin file, so if that has any importance to you, you can customize the name by creating a .txt file and naming that as you desire and specifying it instead - the setup file specified here does not impact your installation command line configured later. Type N for specifying Catalog folder and press Enter. The EncryptionInfo is used to store it with your Intune tenant to gain access to the uploaded .intunewin package. The GUI is very basic. It can be used to Pack files/folders into an .intunewin file and to extract original files/folders from an ".intunewin" file. -o <output_file> Output folder for the generated .intunewin file. <setup_folder> <setup_file> <output_folder> I found it a little inconvenient to use the tool when having to copy/pasting folder paths and so on. Computing a SHA265 hash. Enter the path to the storage of the .intunewin file; If there is already a file with the corresponding name, you can delete / overwrite it; For the Catalog Folder question, we choose No (N) Done, that was creating the Win32 App / "intunewin". CD C:\tmp IntuneWinAppUtil.exe Please specify the source folder: C:\package Please specify the setup file: Copy.cmd Please specify the output folder: C:\package Do you want to specify catalog folder (Y/N)?n. C:\IntuneApps: This folder is for the Output file which will be generated and then we can use this file to deploy on Microsoft Intune. Hi all, I've been building out a bunch of Win32 apps and I've run into issue with the Intune Management Extension not updating the .bin files in C:\Program Files (x86)\Microsoft Intune Management Extension\Content\Incoming after I've updated the .intunewin file in the Intune console. Inside this folder you need to create a folder "spanishgames" Copy everything you have inside this folder Create a powershell script (install.ps1) inside the c:\intunepackages\ folder Inside the script,-first create a new directory where the files need to be copied to (destination) New-Item -Path "c:\" -Name "SpanishGames" -ItemType "directory . Step 8- Select Client apps -> Apps -Add. 4. -s <setup_file> Setup file (e.g. Run the Win32 Content Prep Tool's IntuneWinAppUtil.exe. Select Windows app (Win32) as App type. After configuring the app, make sure to assign the app to a user group.