Onboarding and first-device troubleshooting
Video guide: Follow the first-device troubleshooting guide
Documentation navigation recorded October 22, 2026. Public diagnostic guide walkthrough; no actual installer failure is reproduced or endpoint recovered.
Full narration captions are included in the video. Open video full screen · Download subtitles · Download transcript
Video transcript
Open the onboarding and first-device troubleshooting guide. Identify whether the failure is finding the workspace, signing in, generating an installer, installing the agent or receiving later telemetry. These are different stages and need different evidence.
Read the section matching the actual symptom and record the time, platform and non-secret error. Use the workspace and customer scope from the original enrollment. Do not put passwords, enrollment tokens or session cookies into a support request.
A device row is not enough. Confirm a later heartbeat and telemetry under the intended customer after the repair. Return to the first-device guide for the full sequence, and retain any unresolved stage honestly instead of reporting installation success from a downloaded package.
Use this with Getting started. Start at the stage that failed; repeated reinstallations can hide the original cause.
Workspace and sign-in
“Find your workspace”
Open the workspace URL from your welcome message. Or enter your workspace address under Find your workspace at app.revolutionaryrmm.com. Ask your administrator for the exact address if needed.
No welcome message or no usable workspace address
Check junk/quarantine and the email address supplied during setup. Contact the administrator or Revolutionary RMM through the contact link below. A request or an email-send acknowledgement does not prove the workspace and message reached you.
Temporary password expired or password forgotten
At your workspace's sign-in page choose Forgot your password?, enter Work email, then Send reset link. Use the reset message you receive. The confirmation is deliberately generic; it does not prove the account exists or the message was delivered. If no message arrives, contact your administrator rather than repeatedly submitting requests.
Authenticator code rejected
Use the current code for this workspace account and check your phone's automatic time setting. At sign-in you can enter a saved backup code in Authentication or backup code. Each backup code works once. If you have no usable factor, ask your administrator for account recovery. A password reset does not remove two-factor authentication.
Signed in, but you did not save your backup codes
While you still have access, open /account/security on your workspace address, choose Regenerate backup codes, and save the replacement set immediately. This replaces the previous codes; it does not recover an already locked-out account.
Client portal instead of technician Dashboard
Ask the workspace owner to check your account role. Client accounts use the portal; they do not perform workspace setup.
No customer-creation or installer-generation control
Setup requires OWNER or ADMIN. Ask your workspace owner to check your role. Do not share someone else's sign-in.
Installer generation and enrollment
Open /installers on your workspace address. Below the installer list, Recent enrollment activity shows the latest 25 attempts with When, Outcome, Host, OS, Client, and IP. Compare the time and hostname with your attempted installation. This is enrollment history, not proof of continuing check-ins.
Token expired or Token revoked
Generate a new installer for the same intended client and use its new link/command. UI-generated tokens last 30 days. Revoked tokens cannot enroll more computers.
Invalid token
Recopy the complete generated link/command from the correct workspace. Check that it belongs to the intended client. Do not substitute an Automation API token for an enrollment token.
Bad request
Use the current generated installer or full copied command. Retain the time, hostname and error for support if it repeats.
No matching recent attempt
Check that installation actually ran with administrator privileges and that the target can resolve and reach the correct workspace over HTTPS. Also check the time and workspace you are viewing. Only 25 attempts are shown, so absence here is not proof the endpoint never contacted the server.
Install refused because the hostname is already enrolled
An installer token can enroll new devices but cannot replace an existing device's credential by reusing its short hostname; a conflicting install is refused because the hostname is already enrolled. Ordinary reinstalls keep their saved agent configuration. A cloned computer, lost configuration or lost first enrollment response requires a distinct short hostname, or authorized retirement of the stale device record after reviewing its billing impact.
Enrolled, but no separate new computer
Clear Devices filters and check the client. Enrollment uses client plus short hostname: two computers with the same short hostname in one client receive 409 hostname_already_enrolled instead of replacing an existing credential. Retain saved configuration on reinstall; lost configuration requires a distinct short hostname or authorized retirement of the stale record after reviewing billing implications. Resolve duplicate hostnames before enrolling again.
Installer download fails or is blocked
Retain the exact error and selected OS. Follow your organization's software approval process; contact support if the generated download remains unavailable. Do not change endpoint security policy merely to complete this guide.
If an enrollment token or generated link was exposed, ask an OWNER or ADMIN to use Revoke on its installer row and generate a replacement. Already enrolled devices have their own credentials; revoking the enrollment token stops new enrollments rather than disconnecting those devices.
Enrolled but not reporting
- Open Monitoring > Devices, find the intended client and hostname, then open Overwatch.
- Confirm that CPU and Memory have values and that last seen advances after a later check-in. If the values are dashes, or last seen stops advancing while the computer is awake, monitoring is not yet verified.
- Check the installed agent service is running and the computer can reach its workspace over HTTPS. Allow several minutes for normal check-ins and refresh the page. Confirm the endpoint is not asleep or offline.
- Check for a duplicate short hostname in the same client, especially after a reinstall or cloned-machine deployment. Enrollment cannot replace the credential for that device record; it returns 409 hostname_already_enrolled. Retain the saved configuration on reinstall. If configuration or the initial response was lost, review the stale record and billing implications with an authorized administrator before retiring it, or use a distinct short hostname.
An Online badge immediately after enrollment and the Dashboard checklist are insufficient checks: the registration updates last seen even before metrics arrive. Remote-control success or failure is a separate check from basic telemetry.
Get help with useful evidence
Ask your workspace administrator first, or use Contact Revolutionary RMM. Provide the workspace address, client name, endpoint OS, hostname, time and time zone, the step that failed, the visible error or attempt outcome, and whether later metrics appeared. Share customer/device details only through your approved support channel.
Remove passwords, enrollment tokens, full generated installer URLs/commands, reset links, authenticator QR codes and backup codes from screenshots or log excerpts. A generated link contains a credential even if it looks like an ordinary download URL.
Return to the Learn guide index.
