Install the agent on Windows

The OpsMerge RMM agent runs as a Windows service and reports back to your tenant within a few seconds of installation. There are two supported ways to install it: an interactive PowerShell one-liner for ad-hoc installs, and a silent MSI for Group Policy, Intune, or any other deployment tool that consumes MSIs.

Both methods need a per-client registration token, which you generate inside OpsMerge.

Regional ingest hosts

This article uses ingest-eu.opsmerge.cloud throughout — the EU cell's agent ingest host. If your OpsMerge tenant is in another region (e.g. US), the ingest hostname will be different (ingest-us.opsmerge.cloud, and so on). Always use the host shown in OpsMerge → Add agent, which is pre-filled with your tenant's correct value — don't hand-copy from this article.

Prerequisites

• Windows 10 or later (any current Windows Server is also supported).
• The endpoint must be able to reach https://ingest-eu.opsmerge.cloud on port 443. This is the agent ingestion host — it does not go through Cloudflare, so firewalls that allow *.opsmerge.cloud outbound generally work without further changes.
• Local Administrator rights on the endpoint.
• A registration token for the client the endpoint belongs to (next section).

TIP

The agent is small (around 25 MB on disk), uses very little CPU at idle, and survives reboot, network loss, and laptop sleep. There's no separate "service account" to create — it runs as LOCAL SYSTEM.

Step 1 — Generate a registration token

1. Sign in to OpsMerge at app.opsmerge.cloud.
2. Open Clients in the left sidebar.
3. Open the client the endpoint belongs to (or create one first).
4. Click Add agent.
5. Copy the install command for the platform you want (PowerShell or MSI).

The dialog generates a token scoped to that one client. Tokens are single-use by default and expire after 24 hours — generate a fresh one when you're ready to install.

WARNING

A registration token lets anything that holds it enrol an endpoint into that client's tenant. Don't share tokens over email or chat history that survives the install — copy, install, done.

Step 2 — Install

Option A: PowerShell one-liner (interactive)

This is the fastest way to enrol a single machine — for example, a new laptop you're building, or a server you're on a remote session with.

1. Open PowerShell as Administrator. Right-click PowerShell in the Start menu and choose Run as administrator. Approve the UAC prompt.

2. Paste the command from the OpsMerge dialog. It looks like this (your RMM_TOKEN value will differ):

   $env:RMM_SERVER='https://ingest-eu.opsmerge.cloud'
   $env:RMM_TOKEN='YOUR-TOKEN-HERE'
   irm https://ingest-eu.opsmerge.cloud/scripts/install-agent.ps1 | iex

3. Press Enter. The installer downloads the agent binary, registers with OpsMerge, installs the Windows service, and starts it. Expected runtime is about 15 seconds on a fast connection.

If you see ==> Installing OpsMerge Agent followed a few seconds later by ==> Registration successful and ==> Service started, you're done. Move on to step 3.

Option B: Silent MSI (Group Policy, Intune, scripted)

Use the MSI when you need to push to many machines without operator interaction. The MSI is signed and accepts the same RMM_SERVER and RMM_TOKEN parameters as the PowerShell installer.

1. In the OpsMerge Add agent dialog, click Download MSI. The file is named opsmerge-agent.msi.

2. Distribute the MSI via your deployment tool (GPO Software Installation, Intune Win32 app, PDQ Deploy, etc.).

3. Configure the install command to pass both properties:

   msiexec /i opsmerge-agent.msi /qn RMM_SERVER="https://ingest-eu.opsmerge.cloud" RMM_TOKEN="YOUR-TOKEN-HERE"

The MSI runs the same registration flow as the PowerShell one-liner under the hood — just packaged for deployment tools.

Token re-use for MSI

Because Intune and GPO often roll out to dozens of machines from one job, the MSI flow honours non-single-use tokens. Generate the token from the OpsMerge dialog with Multi-use selected so the same MSI command works for the whole rollout window.

Step 3 — Verify

Back in OpsMerge:

1. Open Agents in the left sidebar.
2. Filter by the client you installed against.
3. The new endpoint should appear within 30 seconds, with Online status and current hostname, OS, and IP.

On the endpoint itself, you can also confirm the service is running:

Get-Service RMMAgent

Expected output: Status Running RMMAgent.

Re-installing or repairing

If you need to push a fresh install over an existing one — for example, after a tenant move or a corrupt config — set RMM_FORCE before the one-liner:

$env:RMM_SERVER='https://ingest-eu.opsmerge.cloud'
$env:RMM_TOKEN='YOUR-TOKEN-HERE'
$env:RMM_FORCE='1'
irm https://ingest-eu.opsmerge.cloud/scripts/install-agent.ps1 | iex

This stops and removes the existing service, clears the local config, and runs a clean registration. The endpoint will appear as a new agent in OpsMerge — old history stays under the previous agent record.

Common installation issues

"Access is denied" during install. The PowerShell session is not elevated. Close it and re-open via Run as administrator.

"Unable to connect to remote server" or TLS errors. The endpoint can't reach ingest-eu.opsmerge.cloud:443. Check the egress firewall and any TLS-inspecting proxy. The agent uses standard HTTPS — there's no protocol oddity to allow-list.

Installer reports success but the agent doesn't appear in OpsMerge. The PowerShell wrapper's "success" can be misleading if the underlying registration fails silently. The authoritative source is the agent log at C:\ProgramData\rmm\rmm-agent.log — look for registration successful or any line containing error. If the log shows registration succeeded but the agent still doesn't appear, the token may have expired; generate a new one and re-run with RMM_FORCE=1.

Installer runs on a non-English Windows and fails on permissions. This was a bug in versions before 0.4.18 and is fixed; if you hit it, update the install script (the irm URL above always points at the latest) and re-run.

See Troubleshooting agents for more.

Next steps

• Install the agent on macOS
• Install the agent on Linux
• MSI deployment — patterns for GPO, Intune, and scripted rollouts
• Updates & rollouts — how agent updates work after install