Mass Deployment

The same one-line install command used for a single machine works unmodified across a fleet — there’s no separate “bulk install” feature, because none is needed. The pattern is: create one token sized for your rollout, then run its command everywhere.

1. Create a fleet-sized token

Go to Settings → Add Device and create a token with:

• Max agents set to your rollout size (up to 1000).
• Expiry long enough to cover the whole rollout window.
• Optionally, auto-assign to a group, so every machine lands in the right department without a manual sort afterward.

2. Push the install command

Use whatever tool already reaches your fleet:

• SSH fan-out (pssh, a for loop, or similar) — run the Linux/macOS one-liner on each host.
• Ansible — drop the same command into a shell or raw task.
• Group Policy (GPO), Intune or SCCM — deploy the Windows installer package (.msi) silently, passing the token and hub address as properties (see Silent installs), or run the PowerShell command as a startup script.
• Linux package managers — install the .deb or .rpm with GT_ENROLLMENT_TOKEN and GT_HUB_URL in the environment (see Linux), from a repository, Ansible, or configuration management.
• MDM on macOS — place an enroll.env file before the .pkg runs (see macOS).
• Golden image / VM template — bake the install into the image so every clone enrolls automatically on first boot. Since each machine gets its own identity on first contact with the hub, cloned machines don’t collide with each other.

3. Confirm the rollout

Re-running an installer or package over an existing install keeps each machine’s identity, so a second pass does not create duplicates.

Watch Agents in the dashboard — each machine appears within about 30 seconds of running the install command. If a machine doesn’t show up, check that its outbound network access allows reaching your hub URL and downloads.gtarsenals.com.