Deployment with an RMM
If you manage devices with a remote monitoring and management (RMM) platform, you can deploy the Acium sensor at scale using a script maintained in the rmm-scripts repository. Each script downloads the sensor package, installs it silently, and is safe to run on a recurring schedule — it checks whether a device is already up to date before doing any real work.
Available scripts
| Platform | Status |
|---|---|
| Datto RMM | Production-tested |
| Generic (any RMM, scheduled task, or manual) | Production-tested |
| NinjaOne | Untested — validate in a lab/pilot before production use |
| ConnectWise RMM | Untested — configuration mechanism unverified, validate before production use |
| Microsoft Intune | Untested — validate in a lab/pilot before production use |
| Syncro | Untested — validate in a lab/pilot before production use |
| N-Able | Untested — parameter mechanism unverified, validate before production use |
Every platform above now has a dedicated script. The five marked Untested work as designed, but haven't yet been run against a live deployment of that platform — treat the setup steps as a starting point and validate end-to-end on a test device before rolling out broadly. If you validate one of these, consider updating its status in the rmm-scripts CHANGELOG and its folder's readme.
What the scripts have in common
- Idempotent: a device that's already current does almost nothing on a re-run (a quick check, then exit), and a machine-wide lock prevents overlapping runs from racing each other.
- They install the sensor's
.zippackage by extracting it and running the bundledAciumSensorInstall.msiviamsiexec— not a simple installer double-click. - They automatically install the ASP.NET Core 8.0 Runtime first if it's missing — a hard requirement for the sensor to run — and defer the sensor install to the next run if that install needs a reboot.
- They verify the downloaded package's Authenticode signature and check for corruption via SHA256, in addition to an ETag-based change check.
- They must run with System/Administrator privileges, not as the logged-in user.
- They write their own logs to
C:\ProgramData\AciumSensor\Logs\on the endpoint, independent of whatever RMM ran them.
Adding a new platform
The rmm-scripts repo's README documents how a new platform folder gets added (script + its own readme documenting prerequisites, variables, and exit codes).
The sensor requires administrator/system privileges on the target device — deploy it using a policy or job that runs as SYSTEM, not as the logged-in user.