Install on Windows

Every installation starts from an installer link for the customer. The link carries the customer's enrollment secret, so devices installed from it land in the right customer automatically.

Create an installer link

1. Open the customer's workspace, then Customer settings → Install agent (or Install the agent on the Devices page; in the portfolio it asks which customer).
2. Choose Create installer link. By default a link is valid for 30 days (the maximum) and 25 installs; you can allow up to 500.
3. Pick the method below.

Installers are built from the newest release on the customer's release channel, so new devices start where their customer is.

Requirements

• Windows 10 or 11, or Windows Server, on x64; or Windows 11 on Arm (ARM64, agent 0.7.0, beta channel today).
• Windows PowerShell 5.1.
• Administrator rights to install. The service runs as LocalSystem.
• Direct outbound HTTPS to Revo (no proxy support).

Install by hand

Download the EXE from the installer link and double-click it. It asks for confirmation and administrator approval, installs the service and enrolls the device.

Install from PowerShell or your RMM

Copy the PowerShell command from the installer link and run it in PowerShell as Administrator, or in your RMM's script runner as SYSTEM. It's one short line:

irm https://<your Revo address>/i/<link key>.ps1 | iex

It downloads a small script from Revo that stages the MSI (with the server and token built in) in a new folder under Program Files, runs it silently, reports a non-zero exit code as an error and cleans up. It never restarts the device. To read the script before running it, open its link from the installer dialog.

Some security tools block "download and run" commands like irm … | iex. If yours does, use Full command in the installer dialog instead: the same install as one self-contained line.

Prefer your RMM's own software deployment? Push the MSI and run:

msiexec /i RevoAgent.msi /qn

Running the EXE with the single argument install is silent too.

The MSI and the PowerShell command don't take the local opt-out switches. To switch patching, restarts, remote uninstall or Windows upgrades off on a device, edit its config.toml after installing (Local controls).

Windows on Arm

Use the PowerShell command: on an ARM64 machine it downloads the native ARM64 EXE instead of the MSI (it detects the real processor, even from an emulated x64 PowerShell), checks it against the published release digest and installs it. Or download the EXE for Windows on Arm from the link.

• There's no ARM64 MSI.
• The x64 MSI and x64 EXE refuse to install on an ARM64 machine and point you to the PowerShell command.
• The native ARM64 build is on the beta channel today, so set the customer (or the device) to beta.
• An x64 agent installed earlier and running emulated moves itself to the native build once one is published on its channel. Such a device shows as Windows on Arm (x64 emulated) until then.

Where it installs

Re-running any installer on an enrolled device upgrades it in place and keeps its enrollment.

Allowlisting tools

Every installer of a release contains the same binary, so one SHA-256 per release and platform covers every device. The hashes are listed under ThreatLocker / allowlisting in Settings → Agents and on each customer's Install agent page. See Allowlist RevoAgent.

Check it worked

Within a minute the device appears in the customer's Devices with a recent last seen time. If it doesn't, see Troubleshooting devices.

Get-Service RevoAgent