Getting started: from your welcome message to your first reporting device
Video guide: Prepare enrollment and verify reporting prerequisites
Recorded November 11, 2026 in the fictional Summit Managed IT staging workspace, App 0.432.427. The deployed demo can differ from the current product; use the written guide for current behavior. Installer form preparation only; no enrollment token shown, installer generated or real device installed.
Full narration captions are included in the video. Open video full screen · Download subtitles · Download transcript
Video transcript
Start in Organizations and find the customer and location that should own the endpoint. This is the fictional staging workspace, not a customer environment. Enrollment scope matters because later policies, permissions and reporting depend on that customer assignment.
Open Installers. Select the intended customer, location and operating system, then inspect the distribution choices. We do not press Generate. Enrollment links are credentials and should not appear in a public training video.
After installing an authorized package on a real test machine, return to Devices and verify the correct customer and a later heartbeat. The old offline record shown here is an example of insufficient evidence. A download, an installer exit code or an initial device row alone is not verified ongoing reporting.
For the owner or administrator of a Revolutionary RMM workspace. You need your workspace welcome message, an authenticator app, and administrator access to one computer you are authorized to manage.
1. Open your workspace and finish sign-in
Open the workspace URL in your welcome message. Bookmark it. Each MSP has its own workspace address; app.revolutionaryrmm.com shows “Find your workspace”, where you can enter your workspace address to reach your sign-in page. If you have not received a workspace, contact Revolutionary RMM.
- Enter Work email and Password, then choose Sign in.
- If you see Set your password, enter the temporary password in Current password. Choose a different password of at least 12 characters, repeat it in Confirm new password, and choose Save password.
- On Two-factor authentication, scan the QR code with your authenticator app. Enter its current 6-digit code and choose Enable two-factor.
- Save the displayed backup codes somewhere private and recoverable. Each works once if you lose your authenticator. Choose Go to dashboard →.
If you reach Dashboard before saving the codes, or leave the security page without saving them, open /account/security on your workspace address. Choose Regenerate backup codes and save the replacement set immediately. Regenerating replaces the previous backup codes.
The security screen also offers passkeys. This walkthrough uses an authenticator app. If your administrator configured single sign-on, follow your organization's sign-in instructions instead; the password flow above may not apply.
You are ready to continue when: you can open Dashboard. If you reach the client portal instead, you have a client account; ask your workspace owner for the appropriate staff access.
2. Create the customer that will own the computer
Your workspace is your MSP's RMM environment. A customer, also called a client organization, groups that customer's computers and records inside the workspace. Adding a customer does not create another MSP workspace or install an agent.
- On Dashboard, choose Create your first customer, or open Administration > Organizations (
/admin/organizationson your workspace address). - Choose New customer.
- Enter Company name, choose the appropriate Type, and fill in the business details you need. Email domain (optional) is used to trust inbound ticket email; leave it blank unless you intend that behavior.
- Choose Create customer. Confirm the customer appears in the list. If the customer already exists, use it rather than creating a duplicate.
- Optionally use add location in that customer's Locations column and choose Add. You can enroll without a location.
These setup actions require an OWNER or ADMIN account. If the controls are missing, ask your workspace owner to check your role.
3. Generate an installer for that customer
- On Dashboard, choose Generate an installer. You can also open
/installerson your workspace address, including after the Getting started checklist disappears. - Under Generate installer & enrollment token, select Client, optional Location, and Operating system. Check the client carefully: it determines where the computer appears.
- For a first Windows computer, leave Distribution type at Setup launcher (.cmd). For macOS, use PKG. Linux uses the generated shell command described below.
- Optionally add a Label, then choose Generate.
The generated enrollment token is reusable for 30 days and can enroll multiple computers into its customer. There is no expiry selector in this form. Protect the token, generated link, and copied commands as credentials. Use a different customer-specific installer for another customer. In the installer table, Revoke stops further enrollment with that token; it does not uninstall already enrolled agents.
The form also shows Linux distribution/architecture choices and additional macOS choices. These do not establish that a separate DEB, RPM, DMG or MDM package has been generated. Use the shell command or PKG path here for desktop-agent enrollment. Phone/tablet MDM enrollment is a separate workflow.
4. Install on one authorized computer
Windows
In the generated result choose Download RevolutionaryRMM-Setup.cmd. Run it on the target computer and approve the administrator prompt. To install on another computer, copy the generated link and open it in that computer's browser.
Linux
Copy the full generated command, including its workspace address and token. Run it in a terminal on the target computer with permission to use sudo. It downloads the shell installer and invokes it with the workspace and token.
macOS
Choose Download RevolutionaryRMM-Agent.pkg, open it on the target Mac, and complete the administrator-authorized installation. If macOS blocks it, follow your organization's software approval process or contact support.
The installer must reach your workspace over HTTPS. Installing the remote-access controller from Downloads is a separate task; it does not enroll this computer as a managed endpoint. Remote-control permissions on macOS are also separate from confirming basic monitoring.
For later managed Windows rollout, the installer table offers Copy silent deploy (Intune/GPO), Download .msi, and Copy MSI command. Start with one computer and verify reporting before distributing the same customer-specific installer more widely.
5. Verify reporting, then continue setup
- Open Monitoring > Devices (
/devices). Clear any search, customer, location or status filters that could hide the new computer. Find its hostname under the intended customer. - Open the computer and select Overwatch. Check CPU and Memory for reported values rather than dashes.
- Leave the computer awake and connected. After another check-in, refresh the page and confirm last seen advances and performance history gains later samples. The agent normally checks in every 60 seconds; allow several minutes for installation, reporting and page refresh. This is a troubleshooting interval, not a delivery guarantee.
Success means the correct computer is reporting later telemetry in the correct customer. An installer link, an Enrolled attempt, an Online badge immediately after enrollment, or a completed checklist step alone does not establish that. Enrollment itself sets last seen before the first metric arrives. A steady CPU value can be normal; look for later timestamps/history rather than requiring the value to change.
Dashboard's Getting started panel disappears once a customer and device exist. You can still use the workspace paths above. Connect Microsoft 365, Invite your team, and Connect the support mailbox are separate next steps; they are not required to prove this first computer is reporting.
If any step fails, use Onboarding and first-device troubleshooting. Return to the Learn guide index for further configuration.
