A .intunewin file is used with Microsoft’s Intune to deploy Windows applications to Microsoft Windows devices managed by Intune, as an alternative to using apps from the Microsoft Store (i.e., for applications not available in the store).
Creating A .intunewin File
Microsoft provide a tool called “IntuneWinAppUtil.exe” that is used to create .intunewin files. The tool is available via their GitHub repository at https://github.com/Microsoft/Microsoft-Win32-Content-Prep-Tool .
I recommend cloning the repository (or downloading it as a zip archive if you don’t Git) and either placing the app in your environment path, or storing it on C:\ so that it is easy to find.
I use a folder structure of C:\Intune for storing the tool, and then within that folder I create a sub-folder for each application installer (.exe) and a sub-folder for each .intunewin file called application_out. For example if I was going to use the tool on the imaginary geektechstuff_installer.exe then I would have:
C:\Intune
C:\Intune\geektechstuff
C:\Intune\geektechstuff_out
The C:\Intune\geektechstuff folder would contain all the installer files, and the C:\Intune\geektechstuff_out folder would only populate after the IntuneWinAppUtil.exe had run. I recommend this set up as it stops any confusion between what the tool generates, where the original installer is and makes running the commands really easy.
If you use the same layout as above then the command to create a .intunewin file would be (from within C:\Intune):
.\IntuneWinAppUtil.exe -c geektechstuff -s geektechstuff_installer.exe -o geektechstuff_out
The -c is for the containing folder (e.g. the folder containing the installer), the -s is for the setup installer (e.g. the file that is run to install) and the -o is for the output destination.
Once created the .intunewin file needs uploading to Intune as an application so that it can then be deployed to devices.
GeekTechStuff 