What is RMM software? A plain-English guide.

In short: RMM (remote monitoring and management) software puts a small agent on every computer you look after and brings them all into one console. From there you watch their health, install updates, run scripts and help users remotely, without visiting anyone's desk.

1. What RMM stands for
2. How an RMM works
3. What an RMM does
4. Who uses RMM software
5. RMM vs PSA
6. RMM vs remote desktop tools
7. How to choose an RMM
8. Getting started

What RMM stands for

RMM stands for remote monitoring and management. It is the main tool managed service providers (MSPs) and internal IT teams use to look after computers they are not sitting in front of: desktops and laptops in offices and homes, servers in a cupboard or a data centre, and increasingly the network devices around them.

The two halves of the name describe the two jobs. Monitoring means knowing what is happening on every computer: is it online, is its disk filling up, is its antivirus working, has it installed its updates? Management means doing something about it from a distance: installing updates, running a fix, changing a setting or connecting to help the person using it.

How an RMM works

Almost every RMM has the same three parts:

1. An agent — a small program installed on each computer. It collects information about the computer and carries out the jobs you send it.
2. A server — usually run by the RMM vendor in the cloud. Agents report to it, and it stores the history, the alert rules and the audit log.
3. A console — the screen your technicians use, normally in a web browser. It shows every computer for every customer in one place.

A well-designed agent only makes outgoing connections, over the same encrypted HTTPS traffic that a web browser uses. Nothing has to listen for incoming connections on the computer, so you do not need to open firewall ports or set up a VPN to manage a laptop on someone's home Wi-Fi.

What an RMM does

The exact features vary, but these are the core jobs:

• Monitoring and alerts. CPU, memory and disk usage, offline devices, antivirus and encryption status, Windows event log errors. When something crosses a threshold you get an alert by email, chat tools such as Teams or Slack, or a phone notification.
• Patch management. Finding the Windows and application updates each computer is missing, installing them on a schedule, and reporting on which computers are up to date.
• Automation. Running scripts (usually PowerShell on Windows) on one computer or hundreds, on a schedule or automatically when an alert fires.
• Remote support. Seeing and controlling a computer's screen, chatting with the user, transferring files and running commands.
• Inventory and reporting. Hardware, software and warranty details for every device, and reports you can share with customers or managers.

Together these turn IT from reactive (“the server is down, someone come quickly”) into planned work (“the server's disk was cleaned up automatically last night before it filled”).

Who uses RMM software

Managed service providers are the biggest users. An MSP looks after many small and medium-sized businesses at once, so it needs one console that keeps each customer's computers separate, lets technicians move between customers quickly, and turns the work into something it can bill.

Internal IT teams use RMM to look after their own organisation, especially when staff work across several offices or from home. Even a one-person IT department gains a lot: the routine checks happen by themselves, which leaves time for projects.

RMM vs PSA

RMM is often mentioned alongside PSA — professional services automation. If RMM looks after the computers, PSA looks after the business of looking after them: tickets, time tracking, contracts, quotes and invoices.

The two work best together. An alert in the RMM can open a ticket in the PSA; the technician who fixes it logs their time against that ticket; the time ends up on the customer's invoice. When they are separate products, someone has to keep customers, devices and contacts in step between them. That is why many MSPs now choose a platform that does both.

RMM vs remote desktop tools

Remote desktop tools let you see and control a screen, and that is all. An RMM includes remote access, but it also knows the computer's health, history and update status before you connect, and it can fix many problems without connecting at all. If you are paying separately for a remote desktop tool and an RMM, it is worth checking whether the RMM's built-in remote support covers what you need.

How to choose an RMM

Every vendor will show you a polished demo, so compare them on the things that matter after the first month:

• Security of the RMM itself. An RMM can reach every computer you manage, which makes it a target. Look for two-factor sign-in for every technician, role-based access, a tamper-evident audit log and code-signed agents.
• Respect for the people at the computer. Can you require their permission before a session? Do they see who is connected, and can they end it? This matters for trust, and in many countries for the law.
• Operating systems. Check that it covers the computers you actually manage — Windows workstations and servers, and any Mac or Linux machines.
• Pricing model. Per device, per technician, minimum commitments and contract length all change the real cost. See our guide to RMM pricing.
• Deployment. How quickly can you get the agent onto a customer's computers? A one-line command or Group Policy deployment saves hours.
• Data location and compliance. Where is your data stored, is there a data processing agreement, and does the vendor publish its sub-processors?
• Support and roadmap. Who answers when something goes wrong, and how often does the product improve?

Getting started

The best way to judge an RMM is to use it on real computers. Most vendors offer a free trial. Pick one or two customers (or departments), install the agent on 10 to 25 computers, and spend two weeks with it:

1. Tune the alert rules until the alerts you get are ones you would act on.
2. Set a patch schedule and check the compliance report after the first run.
3. Use it for a few real support calls.
4. Ask your technicians what they would miss if you took it away.

That tells you far more than any feature list.

Related

• Remote monitoring — Health, alerts and automatic fixes for every Windows computer and server.
• Windows patch management — Windows and third-party updates on schedules, with approvals and reports.