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.

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 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.

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.

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.

We primarily use this product for project management, task management, billing, and CRM.