Learn / RMM basics
What is remote monitoring and management (RMM)?
RMM software puts a small agent on every computer and server you manage, then gives your team one console to watch their health, fix problems remotely, keep them updated and prove what was done. This guide explains the category in plain language, with no assumed background.
Definition
What RMM software does.
Remote monitoring and management grew out of a simple problem: an IT team responsible for hundreds or thousands of machines cannot walk to each one, and cannot notice a failing disk or a missing update by hand. The agent on each device reports its state continuously, and the platform turns those reports into work: alerts when something crosses a threshold, update deployments when patches are missing, remote sessions when a person needs to look, and records of all of it.
The practical test of any RMM is whether an issue keeps its context. A disk alert is only useful if it arrives attached to the device, the customer or department it belongs to, and the history of what was already tried, so the person picking it up can act instead of investigating from zero.
Who uses it
Built for MSPs. Useful for internal IT.
The category was shaped by managed service providers, but the mechanics serve any team responsible for machines it cannot physically reach every day.
01
Managed service providers
MSPs run many customers from one console, so the platform has to keep every customer's devices, credentials and tickets separate, let technicians work across customers within their permissions, and turn recorded work into billing. Multi-tenancy is the defining requirement.
02
Internal IT teams
An internal team is its own single tenant: the same monitoring, patching and remote support, applied to offices, departments or subsidiaries instead of customers. The value is coverage and evidence, seeing every machine, and being able to show what changed and when.
Capability areas
The core capability areas.
Vendors bundle these differently, but a full RMM platform covers most of the following. Descriptions here are generic to the category, not a feature list for any one product.
01
Monitoring and alerts
Health checks on CPU, memory, disk, services and events, with thresholds set per customer or group, and alerts that resolve themselves when the condition clears.
02
Patch management
See which operating-system updates each device is missing, deploy them per device or across a fleet, and hold back the ones that should wait.
03
Remote control
Screen access to a device for hands-on work, ideally reaching the login screen and moving files in both directions.
04
Automation and scripting
A script library, your own scripts, and schedules, so routine fixes run without a person, under whatever safeguards the platform enforces.
05
Network monitoring
Switches, firewalls and printers that cannot run an agent, watched over SNMP and syslog beside the endpoints they serve.
06
Endpoint security state
Antivirus status, disk encryption and isolation actions across the fleet, usually alongside integrations with dedicated security vendors.
07
Service desk
Tickets from email, a portal or messages, attached to the device and its history so the request and the machine are one record.
08
Documentation and reporting
Runbooks, stored credentials, asset inventory and reports, the memory of the operation and the proof of the work.
Evaluation
What to evaluate in any RMM.
Feature checklists converge quickly in this category. The durable differences show up in four places.
01
Coverage of your actual fleet
Exact operating-system floors for the agent, what happens to devices that cannot run it, and how network gear and mobile devices are handled.
02
Security architecture
How commands reaching the agent are protected, how tenants are separated, how stored credentials are encrypted and how access is logged. Our security checklist gives the exact questions.
03
Workflow, not features
Take one real issue from alert to closed ticket in the demo. Count the tools, tabs and re-typed context the platform makes you touch along the way.
04
Honesty of claims
Every vendor says everything is easy. Prefer the ones who state limits in writing: what is not built yet, what is not claimed, and what the roadmap actually commits to.
Good to know
Common questions about RMM.
No. Remote desktop is one capability inside RMM. An RMM platform also watches device health continuously, deploys operating-system updates, runs scripts and keeps an inventory, whether or not anyone is connected to the screen.
The value shows up earlier than most teams expect. Even at fifty machines, checking update status or disk health by hand stops happening in practice. An RMM makes those checks continuous and turns misses into alerts.
RMM manages computers and servers through an installed agent with deep access to the operating system. MDM manages phones and tablets through the enrollment frameworks Apple and Google provide. Many platforms, ours included, do both from one console.
Usually not. Most RMM platforms report on the protection state of each device and integrate with security vendors rather than replacing them. Ask any vendor exactly where their monitoring ends and your security tooling begins.
It reports inventory and health readings on a schedule, raises alerts when a threshold is crossed, and carries out the actions a technician or policy sends it, such as installing an update or running a script.
Our approach
How Revolutionary RMM does this.
Revolutionary RMM is one workspace covering the capability areas above: monitoring, patching, remote control, automation, network monitoring, identity signals, service desk and documentation, built for MSPs and usable by internal teams as a single tenant. The design center is the context test from this guide: an issue keeps its device, customer and history from the first alert to the invoice.
We publish what is not built yet on our roadmap, and the platform page counts its capability areas from the product source code rather than marketing copy, so you can evaluate us the way this guide suggests evaluating anyone.
Evaluating RMM platforms?
Bring one workflow your team runs every week. Half an hour on a call, in the product, no slides.
