Skip to main content

Microsoft Intune

Deploy the agent as a Win32 app in Intune. Package the MSI, set an install command, and detect by the Windows service.

Use the Windows app (Win32) type

The agent's install command needs several properties, and the Line-of-business (LOB) MSI app type takes one command-line argument.

First, download and verify the MSI.

Single-org procedure​

  1. Package the .msi with the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil) into a .intunewin.

  2. Intune admin center, then Apps, then Add, then Windows app (Win32), then upload the .intunewin.

  3. Install command:

    msiexec /i SparkLogsAgent-x64-1.14.13.msi /qn /norestart EULA=ACCEPT REGISTRATION_TOKEN=us_97... USEPARENTORG=1 /l*v %TEMP%\SparkLogsAgent-install.log
  4. Install behavior: System. Device restart behavior: No specific action.

  5. Detection rule: custom script. Check the service, not the MSI product code (its GUID changes across versions):

    if (Get-Service "SparkLogsAgent" -ErrorAction SilentlyContinue) { exit 0 } else { exit 1 }
  6. Assign the app to the target device groups, or to All devices.

Behavior

Installs at the next device check-in; status reports in the Intune console.

Client-org (MSP) differences​

  • The install command carries the client's identifiers instead of USEPARENTORG:

    msiexec /i SparkLogsAgent-x64-1.14.13.msi /qn /norestart EULA=ACCEPT REGISTRATION_TOKEN=us_97... RMMCLIENTID=<RMM_CLIENT_ID> CLIENTNAME="<CLIENT_NAME>" /l*v %TEMP%\SparkLogsAgent-install.log
  • Create one app per client tenant and assign it to that tenant's device groups. Each client tenant is a separate Intune environment, so each one needs its own app.

These commands accept the SparkLogs Agent license (EULA=ACCEPT).

See Deployment scope for the property meanings and Troubleshooting for common failures.