![datto rmm splashtop download datto rmm splashtop download](https://www.achab.it/wp-content/uploads/imported_images/KB/KB52033/6.jpg)
In many RMMs, when you learn to create scripts, you learn that platform's scripting interface. I still keep tabs on the workings, but it no longer requires daily maintenance to keep functional. Now that I've configured stuff to work at scale and with minimal touch points, I could go quite some time without needing to make any adjustments to the platform. When I first started managing Datto RMM, it was not set up this way and I was working in the RMM day in, day out, just trying to keep things working properly. That is only because I've taken the time to configure it to work at scale. We could have 10x the endpoints we have now, and my day to day work wouldn't be much different than it is now. So while Datto could use some improvement around "site" monitoring, we have been OK the last several years without it.Īt this point, I have our RMM configured to scale quite well. (You have to monitor it from a device outside the local network, and then it is difficult to link this to the correct site for alerts and ticket creation.) Other RMMs have this sort of functionality built into their platform, but not Datto. So monitoring things like WAN connections on routers are extremely difficult. Every monitor or script works between the endpoint and the platform. Some RMMs have a notion of "client" or "site", but while there are site specific settings, nothing in Datto RMM really works at a "site" level. Everything in it is designed to work at the endpoint level. It is much more scalable now and a lot less hands-on than it was previously.ĭatto RMM is device-centric. Since I've taken it over, I've completely reconfigured everything. Prior to that, our CEO set it up and maintained it. I've been managing it exclusively for the past 3 years.