Roll out to many computers (IT)¶
For a whole office, push the signed MSI with your existing tools. Every method uses the same idea: install the MSI silently and pass your enrollment token so each machine joins your workspace on first run.
Get your token and the ready-made command from the dashboard: Add computers → Rolling out to many computers? (IT).
The command¶
/qn— silent, no UI.ACUTIS_ENROLL— your reusable deploy token (copy it from the dashboard). It enrolls each machine up to your seat cap, then stops.- Direct MSI download: get.acutisgo.com/dl/Acutis-Go-Setup.msi
It's a proper upgrade
The MSI keeps a stable upgrade code, so re-running a newer version upgrades in place and keeps the enrollment. (You rarely need to, though — agents self-update.)
PDQ Deploy¶
- New package → Install step → point it at
Acutis-Go-Setup.msi. - In Parameters, add:
ACUTIS_ENROLL=<your-token> BACKENDURL=https://app.acutisgo.com - Deploy to your target collection. PDQ runs as SYSTEM, so the silent enroll just works.
Microsoft Intune¶
- Wrap
Acutis-Go-Setup.msias a Line-of-business app (or.intunewin). - Install command:
- Assign to your device group.
Group Policy (GPO)¶
Use a startup script (runs as SYSTEM) rather than the Software Installation policy, so the token reaches the installer:
msiexec /i "\\server\share\Acutis-Go-Setup.msi" /qn ACUTIS_ENROLL=<your-token> BACKENDURL=https://app.acutisgo.com
Command-line one-liner¶
For scripted or ad-hoc installs (runs as admin, one UAC prompt if interactive):
macOS & Linux¶
- macOS:
curl -fsSL https://get.acutisgo.com/install-mac.sh | sudo bash(signed + Apple-notarized). - Linux / Raspberry Pi:
curl -fsSL https://get.acutisgo.com/install.sh | sudo bash(installs a systemd service).
Pass the token the same way: ACUTIS_ENROLL=<your-token> in the environment before the command.
After rollout¶
- Machines appear in your fleet dashboard within a minute of first check-in.
- They update themselves from then on — you don't re-push for new versions.
- To stop new enrollments, Rotate or Revoke the token in the dashboard (already-enrolled machines are unaffected).
One machine not enrolling?
A silent MSI needs to run elevated (PDQ/Intune/GPO startup scripts already do). See Troubleshooting.