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 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.
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 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.
Business Development Manager at a comms service provider with 5,001-10,000 employees
Real User
2021-12-17T17:43:00Z
Dec 17, 2021
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.
Learn what your peers think about Datto Remote Monitoring and Management. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
General Manager at a tech services company with 1-10 employees
Real User
2021-12-15T02:48:00Z
Dec 15, 2021
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.
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 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.
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 primarily use this product for project management, task management, billing, and CRM.
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.
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 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.