{"id":23080,"date":"2021-09-01T11:09:14","date_gmt":"2021-09-01T10:09:14","guid":{"rendered":"https:\/\/www.n-able.com\/?p=23080"},"modified":"2025-02-20T20:54:39","modified_gmt":"2025-02-20T20:54:39","slug":"5-things-you-maybe-didnt-know-n-able-rmm-could-do","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/es\/blog\/5-things-you-maybe-didnt-know-n-able-rmm-could-do","title":{"rendered":"5 things you (maybe) didn\u2019t know N‑able RMM could do"},"content":{"rendered":"

Throughout the training sessions I hosted at Empower 2021, I heard a lot of partners say things like, \u201cI didn\u2019t know we could do this\u201d or \u201cThis is super useful and nice to know.\u201d So I wanted to write a couple blogs to share some of the things partners were happy to learn about N‑able\u2122<\/sup> RMM.<\/p>\n

Before I start, you can watch most of the sessions in N‑able U. So if you\u2019d like to dig in a little deeper, go to success.n-able.com<\/span><\/a> and click on N‑able U button.<\/p>\n

Below are some of the things our partners found most useful:<\/p>\n

1. You can use Web Protection as an easy sales tool<\/h2>\n

One of the main things people didn\u2019t know is that you can use web protection as an easy sales tool. It\u2019s something that costs a few bucks for a few licenses, but when you use the report only mode of the product, you can produce reports after two to four weeks that will show trends on what the end users are doing, giving an incentive for your customers to use the product full time. (Learn more at N‑able U in the RMM Optimization<\/span><\/a> course.)<\/p>\n

2. Using templates as a route to standardization<\/h2>\n

Standardization leads to better efficiency, saving time and money in the long run. You can use templates in RMM to standardize your thresholds as much as possible. A lot of MSPs seem to be missing out on the benefits of templates, either because they aren\u2019t using them at all or they\u2019re using them ineffectively. Treating each of your customers as unique slows deployment, configuration, and maintenance and makes them all more difficult. (Note: this also applies to patch management.) It\u2019s best to have templates in place to speed up the process, and you can set those up in RMM. (Learn more at N‑able U in the RMM Optimization<\/span><\/a> course.)<\/p>\n

3. Using network devices to extend your monitoring<\/h2>\n

In RMM, you can use network devices to monitor each device in a customer\u2019s environment, or you can use a server on which you can add SNMP monitoring against network devices, reducing your cost. Although it will also reduce the granularity of alerting, this workaround will give you what you need to get some monitoring going. You can also monitor websites, ports, etc. (at no additional cost since you already paid for the license for those RMM devices). You can do this by taking an existing device and having it monitor the customer\u2019s intranet, websites, firewall port (internal and external), and more. This is something you already pay for, so why not leverage it? (Learn more at N‑able U in the RMM Patching course<\/span><\/a>.)<\/p>\n

4. Controlling when patches are installed<\/h2>\n

On the patch side, you have the ability to control when patches get installed, when the device reboots, and also you can push patches<\/span><\/a> if a user\u2019s devices misses its install window. We\u2019ve seen there has been a huge decrease in the time it takes for bad actors to create attacks against Windows vulnerabilities, so doing patching quickly is important. If you patch at night, but those devices are offline most nights, you may end up unpatched for weeks. This is potentially putting your customer at risk. If you say, \u201cPatch at night\u2014but if you miss your window, patch the next morning,\u201d at least you help reduce the delay between the time the patch came out, the time it was approved, and (more importantly) when you install the patch. (Learn more at N‑able U in the RMM Patching course<\/span><\/a>.)<\/p>\n

5. Remember to reboot<\/h2>\n

Finally on patching, the most misunderstood fact is that most patches require reboot. What that means is if the device is not rebooted, the patch is not technically installed, since the DLLs and other files that are updated by that patch won\u2019t be \u201creplaced\u201d in memory until a reboot occurs. In short, this means the device is not at its most secure until it reboots. (Learn more at N‑able U in the RMM Patching course<\/span><\/a>.)<\/p>\n

In the next article I\u2019ll cover some more tips for:<\/p>\n