Three Hidden RMM Features, Part 2: Monitoring Templates

In the first portion of the underutilized RMM features series, we discussed the use of Site Concentrators and Data Overdue Cross-Checks. This time we’re going to discuss Monitoring Templates. MSPs have shied away from Monitoring Templates in the past because of the effort needed to set them up. I think this is the wrong way to look at them; we need to be thinking long-term here. Is it more appropriate to install the agent on devices and just accept that the Check Detection Scan will miss needed checks that we either have to do manually, machine by machine, or invest the time upfront to create the default templates that we will need upon install? Personally, I would say put in the sweat equity now and see better results in the future.

What are Monitoring Templates?

Monitoring Templates are designed to assist MSPs during the installation of the RMM software and the deployment of checks and automated tasks. While this topic could be its own blog, I want to introduce it here since most of our MSPs are not utilizing or are underutilizing monitoring templates.  Monitoring Templates can be created from an existing device in the RMM or created manually. The purpose of the templates is to target the checks and tasks that you need as an MSP, rather than allowing the RMM to alert on items you do not care about or need, creating white noise.  

The best use that I have seen for templates is to create your basic server and workstation templates that monitor the proper third-party apps, Windows Services, and performance, and provide self-healing based on those “fundamental” checks. Another use is to create additional templates for servers based on their roles, such as DC, Exchange, or SQL, and workstations, based on either functionality or packages. This allows you, using the New Device Installation settings, to make sure upon installation that all devices that get installed in the RMM have the needed functionality for you to monitor them, and as time passes to add the additional functionality you need quickly and easily.

This feature is not limited to Windows devices either. Macs and Linux boxes can have monitoring templates applied as well. Just like Windows devices, they can be applied with a simple right-click. Since there is no check detection scan for Macs or Linux boxes, the templates here ensure you are monitoring the proper items, like Daemons.

How to create Basic/Default Templates

There are two ways to go about creating default templates in N‑sight RMM. The first is to manually create them by going to Settings > Monitoring Templates > Manage Templates > Add New. The second is to create the template based on a test device already in your RMM by right-clicking on the device and selecting Monitoring Templates > Create Monitoring Templates.

Of the two methods above, the second is my preferred option, for a couple of reasons:

1. I do not expect any MSP or technicians/engineers to be able to rattle off a comprehensive list of every check and task that they use across servers and workstations. In the real world, there can be up to 35 to 40 checks on a device as a default template and 15 to 20 pieces of automation in the form of tasks. Manually adding all of these from memory to a template is a bear of a task.
2. In the same vein, can you tell me every Windows service that you need to monitor? I will be quite honest—I could not.
3. Testing the manually made template cannot be done during creation; you would have to add it to a machine to test.
4. It is just plain time-consuming.

Testing your templates once you’ve created them

I much prefer to find a server and a workstation that I, as the MSP, own and use those machines for testing/template creation. This allows me for more control and trial/error when creating my templates, while allowing me to assess my service offerings compared to my monitoring. The steps that I typically take here are as follows (note that while these steps are broken up over several days, the actual time spent should be about an hour total):

1. Find the proper machine(s) in the RMM and name them something to denote that they are a testing device. This can be done upon installation or by renaming the device with a right-click and editing the device.
2. Run a Check Detection Scan. This is done upon installation or by right-clicking on the device > Monitoring Templates > Run Check Detection Scan. It allows us to make sure that we have everything that the RMM can find.
3. Go through the Check Detection Scan’s found checks and delete the unneeded checks—Windows Defender checks, I’m looking at you.
4. Add any needed checks that you may have scripted or that the detection scan missed. For me, this typically includes items such as “Is this piece of mission-critical software installed,” RAID or VM checks, or what external hardware is plugged in.
5. Let the machine sit for a week or so. This is so you can track which checks are constantly failing due to either a botched setup or improper thresholds.
6. Take the information from the past weeks to update the existing checks and add your self-healing/automation.
7. Let the machine sit for another couple of days to test automation and self-healing concepts.
8. If everything is running smoothly, right-click the device > Monitoring Templates > Create Template.

Once these defaults are created and tested, you can right-click on a Client, Site, or machine to apply the template to existing devices or go to Settings > Monitoring Templates > New Device Installation > Apply Template at a machine type, Client, or Site level for all new installs.

I highly encourage folks to log into N‑able U to learn more about templates, as there is so much information to be found there. Also look to join our RMM Onboarding Boot Camps, as they go much more in-depth on one of the most useful features in N‑sight RMM.

Joseph Ferla is one of our Head Nerds. You can follow him on Twitter @headnerdjoe or LinkedIn.