Creating a Win32 app or ".intunewin" file for is very easy.
The hardest part of any package is the installation logic itself. You can handle this in a PowerShell script or CMD file, for example. I personally prefer the way via PowerShell and call the installation file "install.ps1".
You can find an explanation of the structure here: my take on win32 apps - Intune
Once you have created your routine, proceed as follows:
- Load the current one Microsoft Win32 Content Prep Tool down
- Open the downloaded "IntuneWinAppUtil.exe"
- Provide the path to your package
- Enter the installation file, for me in each case: install.ps1
- 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".
Once the package has been created, you can use it in Endpoint Manager / Intune under «Apps > Windows apps" Add.
The parameters within the apps are then different depending on the application.
As install and uninstall command you can use in most cases use the following:
|install command||%SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -windowstyle hidden -executionpolicy bypass -command .\install.ps1|
|uninstall command||%SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -windowstyle hidden -executionpolicy bypass -command .\uninstall.ps1|
Pingback: Excel standard template with Intune | scloud
Pingback: "Proactive Remediation for Business" | scloud
Pingback: Install Worksheet Crafter with Intune | scloud
Pingback: chocolatey - basic installation with Intune | scloud
Pingback: My take on Intune Win32 apps | scloud
Pingback: How to: winget & Intune | scloud
Your install and uninstall commands include %SystemRoot%\sysnative in the path to powershell. I've never seen a folder 'sysnative' before?
That folder is invisible and used to call PowerShell in x64-bit mode.
For the custom detection rules should we use the check.ps1?
This depends on the app you'd like to install. You can either use a manual rule for simple validation, or a script like I use in a lot of packages.
Here are some examples: https://scloud.work/custom-detection-script-intune-win32/