Deployment Methods
Pick the method that matches how you manage endpoints. Every method installs the same agent; they differ in how properties are supplied.
| Method | Best for | Notes |
|---|---|---|
| Single machine | One-off or testing | GUI run, or a silent command. |
| RMM mass-deploy | Fleets via an RMM | Silent command as SYSTEM, per-client variable mapping. |
| Group Policy (GPO) | AD-joined Windows | MSI only, properties go in an MST transform. One MST per client. |
| Microsoft Intune | Intune-managed Windows | Win32 app, install command, service-based detection. One app per client tenant. |
| CLI / scripted | Automation | One PowerShell snippet that downloads, verifies, and installs. |
Before you start
- Confirm endpoints meet the minimum system requirements.
- Choose your deployment scope so you know which properties to pass.
- Download and verify the installer, and keep the expected SHA-256 handy.
GPO and Intune bind values at package time
With Group Policy and Intune, the registration token and client identifiers bind when you build the package (the MST transform or the Win32 app), not per endpoint. Build one package per client when you deploy to client organizations.
Accepting the license
Every silent command includes EULA=ACCEPT, which accepts the
SparkLogs Agent license. The interactive GUI installer prompts for the
license instead.