Datto Remote Monitoring and Management Reviews

We use Datto for several things, one of which is to automate services. One of the primary uses is to automate upgrading and patching computers to roll out new software. We do all the Windows patches using Datto. It also has a monitoring component to look at the various services running on our servers. If the monitor shows a service is no longer running, you can set up a script and have it automatically restart that service. You can be proactive on a random problem to prevent outages that keep the staff from working.

We support nine different nonprofits, and the billing took the manager three or four days working on spreadsheets. When I finished automating everything with Datto, we cut everything down to a couple of hours. That's a substantial cost savings on the billing side. It has also helped us track tickets, so stuff doesn't get lost, and we're spending a lot less time on PC maintenance and patching.

We originally had around three techs supporting probably about 150 or so PCs. We're currently supporting 600 PCs with the same amount of techs. The bottom line is you can do a lot of extra work without increasing your staffing.

My use case is deployment and management of updates and patches, as well as remote support. Currently, it is still in the test phase. I haven't put it into production, but I've been working with it closely as far as production is concerned. I do have seven different machines and/or servers integrated into the product for test purposes with different known configurations. To test the thoroughness of the product, I'm emulating different geographic locations and sites that have specific needs. So, I have it on a sample base. If it works out for me, I will deploy it across all clients. I'm still waiting to see if it's going to solve my needs. 

I am using its latest version. The software is cloud-based, and it's deployed through agents that connect to their cloud-based service.

We can get more done in less time. It increases productivity, which ultimately increases our revenue.

Datto Remote Monitoring is a little more robust compared to Automate. Datto has components that let you audit inventory and stuff like that. You can see which customer had which device or what devices haven't been rebooted within the last 30 days. It lets you access and run scripts on any device across the whole site. 

For example, I had to do updates for a credit union on the first Sunday of every month, so I created an MSI script, added that to a component, and ran that component across all the devices. It updates every device instead of requiring me to each one manually. I can also access the Splashtop agent through Datto, go to the command line, and do it that way, which takes only an hour or two. 

If you make the component, you can save it to Datto. Once you save it, you can go to that particular site, check the component list, click that one, click the site, check the site off, and send. You can set it up to send you an alert if it fails. If you don't want to build your own components, you can use the ones Datto provides you. Every month, the component store updates with different components, like removing passwords, Kaspersky removal, BitDefender removal, etc.

I also like how Datto integrates seamlessly with the Autotask ticketing system. It was simple to get it configured. They implemented something within Datto to where you could go straight to the RMM management console and pick up the ticket associated with a particular device or the history of tickets that was involved with that device. You could add a device to a ticket by clicking on the device within the ticket unless a person sent the ticket for somebody else, like if an administrator sent the ticket for one of their users there. But, a lot of the time, when the users send a ticket in, they send it from the device that has the issue. Within the ticket, we can click the actual device that was in there. 

Sometimes we have some downtime when Datto is doing updates. Maybe it's because of the cloud service they use. I'm not sure if they're going through AWS or Azure or what. That's happened, but the outages have been few and far between. But sometimes, we kind of needed it when it happened because it gave us a valid excuse to take a break.

We manage dental clients with our MSP model. We use Autotask Endpoint Management to maintain, monitor, and connect to over 1500 devices. AEM will alert us based upon customized alerts that we have set up, as well as some of the built-in alerts which come with it. We are able to have high level alerts text the on-call technician's phone and respond to downed servers very quickly. 

This service also tells us when servers are running hot and are ready for dust to be blown out.

• AEM improved our organization as we switched from N-able. N-able had very poor Mac support, and since we have a lot of Macs, AEM came in handy as their support is great for Macs. 
• It shaved off some costs. Although, it is pretty comparable in pricing to N-able. 
• We like their support team much more than N-able.

The software is a standard RMM tool that can be installed on various devices belonging to our clients. It is capable of monitoring anything, including the CPU and other components. Even when the connection to the server is lost, the monitoring continues without interruption. Additionally, the software can connect to devices that use SMPP. As long as a device provides a diagnostic, I can support it and apply the necessary patches. Overall, I am satisfied with the software. I appreciate the solution's ability to connect to a client's desktop remotely. The software offers a couple of options for connection depending on the client's setup. All in all, I find the software to be a valuable tool.

The only area where I see room for improvement is the ability to delay the application of patches for a set number of days. Currently, when patches become available, you have to either approve or reject them immediately without any waiting period. Additionally, the third-party patching application used by the software lacks support for a sufficient number of apps. This means that you may need to install an additional tool, such as Chocolatey, to patch more applications effectively.

We use it to remote into people's machines when we're troubleshooting. We use it to push out changes to machines, which is through scripts. We also use it for monitoring and for hardware inventory to pull statistics reports. It is our all-in-one tool.

It is on-prem. We put the software inside a master image, and when we image a new machine, it'll auto-install the software when the machine first boots up. That's how we do it.

At the start of the pandemic, when our office went remote, we were using an older solution to push changes or a group policy, but they had to be on the VPN for it to work. With Datto, I can write up a script, and it can change a file and install a program on any machine as long as they have an internet connection. So, there is no need to be on the VPN or in the office. It has helped us to be a more remote IT group.

I use Datto Remote Monitoring and Management as an MSP for our customers' patch management. We switched to Datto Remote Monitoring and Management from VSA because it better addresses our specific patch and inventory management needs.

The tool's main valuable features are its ease of use and intuitive console. It's very easy to implement and create policies. I don't need highly technical staff to manage the tool, which is a big advantage.

We use it for remote management and remote monitoring. In terms of deployment, we put an agent on the machines, so it would probably be a cloud deployment.

It monitors the machine, and it tells us if the memory is full. It tells us how long it has been online and if it needs to be rebooted. If there is a problem with the machine, we're able to remote in. A person can contact us through the machine, and then we can remote in the machine by using this tool.