Deployment

Installing on a single machine

For machines your RMM can't reach. Download one file, double-click it, done — nothing to type, no key to hand over.

When to use this

Bench machines, demo laptops, home workers — anything where sending a file beats pushing a script. For a fleet, use the wrapper script. Both install the same signed agent into the same account.

Get the installer

  1. Tenants → <customer> → Install agents.
  2. Manual install card → Download installer.

You get SnitchOS_<code>.exe. Under Advanced options you can label it, cap how many machines it may install on, or set an expiry; by default it has neither.

Run it on the machine

Double-click and approve the prompt — it elevates itself. No arguments, no key to type. The device appears on the tenant overview in about 60 seconds.

Do not rename the file

The customer's identity is the code in the filename, so a renamed installer has no account to join and stops before installing. Browser suffixes (… (1).exe, … - Copy.exe) are fine; nothing else is.

The wrapper script is the opposite — identity is inside the file, so rename it freely.

Reuse and revoke

Keep the file; it works on every machine at that customer. Download more whenever — each one is revocable on its own, and older copies keep working until revoked.

Install agents → Downloaded installers lists each one with its install count, last use and expiry, plus a Revoke button. Revoking is immediate and never affects machines already enrolled — they authenticate with their own device credential.

Send the installer to the customer, not to a public link — but it is not a master key. The filename code only buys a single-use permission to enroll one machine that expires in minutes. It never yields the reusable enrollment key your RMM deployment uses.

If nothing shows up

Run & "C:\Program Files\SnitchOS\SnitchOS.HealthCheck.ps1" on the endpoint, and check it can reach api.snitchos.com and cdn.snitchos.com over HTTPS. More in troubleshooting.

Removing it

Uninstall from Settings → Apps, or with the msiexec /x command in the deployment guide. Data already collected stays until retention removes it.