Install the desktop agent on Windows

To manage one Windows computer, generate its customer-specific installer in your workspace, install it with administrator permission, then verify later telemetry. The remote-access controller is a separate program and does not enroll a managed computer.

Before you start

You need an OWNER or ADMIN workspace account, an existing customer, and permission to install software on the target computer. Obtain the current approved Windows artifact and release-trust procedure from your platform operator. A generated download or advertised version does not establish signing, installation or remote-control acceptance.

Install one computer

  1. Open Generate an installer on Dashboard, or open /installers on your workspace host.
  2. Under Generate installer & enrollment token, select the correct Client, optional Location, and Windows Operating system. Leave Distribution type at Setup launcher (.cmd) for this first installation.
  3. Optionally enter a Label, then choose Generate. Check the customer again before distributing the result.
  4. Choose Download RevolutionaryRMM-Setup.cmd. Run it on the authorized target computer and approve the administrator prompt under your organization's software policy.
  5. Open Monitoring > Devices, clear filters and find that hostname under the selected customer. Open Overwatch and check CPU/memory and a later performance sample. Refresh after another check-in and confirm last seen advances.

Enrollment itself sets last seen. An immediate Online badge, an Enrolled attempt or a completed download is insufficient. The agent normally checks in every 60 seconds; allow several minutes for setup and refresh without treating that interval as a delivery guarantee.

Roll out after the pilot

The installer table offers Copy silent deploy (Intune/GPO), Download .msi and Copy MSI command. Use the actual generated command and approved deployment process. The EXE silent path uses /S; do not reuse its parameters for a different distribution.

Generated enrollment tokens are reusable for 30 days. Protect the token, download links and copied commands. Revoke prevents new enrollment with that token and does not uninstall existing agents. Duplicate short hostnames within one customer are refused with 409 hostname_already_enrolled. Preserve saved agent configuration on reinstall; if it is lost, retire the stale record through an authorized administrator or use a distinct short hostname before retrying.

If installation or reporting fails

Check the workspace URL, token validity, outbound HTTPS, service state and the redacted installation error. Use Onboarding troubleshooting for the failing stage. Native remote capture and input require separate verification; a working heartbeat is insufficient. See Desktop agent for update trust and removal, or Getting started for workspace setup.