What Remote Monitoring and Management Means
Remote monitoring and management, RMM, is the software a provider uses to watch device health, push patches, and often to control a screen remotely. It is the tool behind a managed IT service. It is not the service agreement. A firm can have an RMM agent on every laptop and still have no written scope, no after-hours rule, and no idea who else can open a remote session.
Outsource IT Canada uses this kind of tooling as part of managed IT for firms of about 15 to 75 users. Group 4 Networks is 100% Canadian-owned. This entry explains the power the tool represents so you can ask the right questions. We do not name a specific product price and we do not imply the tool is a security operations centre.
What the agent can do
A typical agent reports whether a disk is full, whether updates are missing, and whether the machine is on. It can install patches and software. It can often let a technician see the desktop to fix a problem without a site visit. That is why remote support works across Canada from a Toronto team. The same capability is why access to the RMM console must be limited to named staff and protected with multi-factor authentication.
You should know which devices have an agent and which do not. A server that is 'too important to touch' and has no monitoring is a blind spot. A personal laptop with an agent and no policy is a different problem. Ask for the list. Ask how an agent is removed if you leave the provider. Leaving a former provider's agent in place is a doorway you forgot.
Monitoring is not the whole service
Alerts need a person. Our standard help desk is weekdays from 9 AM to 5 PM ET. 24/7 support is a paid add-on if you want that queue covered overnight. An unread alert at 2 AM is not coverage. The priority one response target of 15 minutes is the time to start work on a business-wide outage or an active security incident under the plan, not a property of the software.
Patching through RMM is daily IT. A project to replace the line-of-business server is not. The MSP entry describes the service. The SLA entry describes how response targets should be written. PIPEDA matters because remote control can see personal information on a screen. Technicians should have a reason to connect, and the console should not be a shared password.
How to use the term
Ask three things: who can open the console, whether you can get a copy of your device and admin data if you leave, and which hours a human looks at alerts. A demo of a dashboard is not an answer.
Read the managed IT page. Call (416) 623-9677 or use the contact form if you want those three answers for your fleet.
FAQ
Is RMM the same as managed IT?
No. RMM is a tool. Managed IT is the responsibility, the hours, and the scope. The tool without the responsibility is just software.
Can we see what the provider can do remotely?
You should be able to ask and get a straight answer: which devices, which technicians, and how access is protected.