Prepare app content

Create a folder that will contain the payload:

• Agent msi package

• installerConfig.json

• install.cmd script

Agent msi package

This is the .msi file containing the agent installer.

InstallerConfig.json

This file contains information used to setup the initial environment configuration for the installed agent.

Refer to following location for more information: Agent - installerConfig.json

Install.bat

This is a batch file which will be used to execute the .msi installer after package is pushed to endpoints via Intune. A sample install.bat will look like this:

rem Stopping Getvisibility services if they are running
net stop "Getvisibility AutoUpdate Service"
net stop "Getvisibility Platform Service"
rem Using %~dp0 allows you to reference current working directory
GVClient.3.3.0-Getvisibility-windows.msi CONFIGFILE=%~dp0installerConfig.json /quiet

Use Microsoft Win32PrepTool to create .intune package

The tool can be downloaded from:

https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool/releases/latest

Run IntuneWinAppUtil.exe and provide the following:

• location where your 3 files are kept

• name of the setup file - in our case it’s install.bat

• output folder where .intune package will be stored

• if there is a package in output folder you will be asked if you want to overwrite it

• you can skip the last question by pressing Enter

Now check your output folder to locate .intune package

Troubleshooting problems when deploying agent with Intune

If you want to troubleshoot issues arising when deploying agent with Intune, you can adjust your install.bat file to request the installer to create logs during installation process:

rem Stopping Getvisibility services if they are running
net stop "Getvisibility AutoUpdate Service"
net stop "Getvisibility Platform Service"
rem Using %~dp0 allows you to reference current working directory
GVClient.3.3.0-Getvisibility-windows.msi CONFIGFILE=%~dp0installerConfig.json /lv c:\temp\install.log /quiet

After pushing the deployment check installation logs on the endpoint in C:\TEMP\install.log location.