ConnectWise Automate Formerly LabTech vs ConnectWise Control Formerly ScreenConnect

• Desktop sharing / view with chat to the operator, file sharing and pass-through for keyboard strokes
• Computer/server monitoring with thresholds and warning
• Search - tracking down computers when you have many by name, logged in user, IP
• End user ticket raising is built into the tray icon which make access really easy

Read full review

• The interface is easy to use and makes sense. It's easy to understand how to organize a large number of machines involving multiple clients. But, it's also applicable for smaller set of machines too.
• The connection speed is very quick. I've used solutions in the past that take a variable amount of time to connect, or they just take a long time every time. Control is quick every time. It doesn't get in the way of being able to support the machines on the other end.
• The connections are reliable. I haven't experienced random disconnects throughout hundreds of instances. It was a breath of fresh air coming from the previous solution we used. I consider Control a gold standard for what a great remote connection solution can be.

Read full review

• They have conflicting scheduling paradigms. When scheduling patching for clients, the 1st Friday is interpreted as the very first Friday of the month, even if this is the 1st of the month. For scripting, the 1st Friday of the month is interpreted as the 1st Friday of the 1st FULL WEEK of the month. This makes no sense to have two different interpretations, and makes it unreliable to schedule recurring scripts to fall when recurring maintenance does. The scripts need to be done manually because of this.
• There is no way to dictate reboot orders for patch policies. This tied directly in with my first point. We have some clients that require reboot orders. This is not possible without having different patch policies for each server and specifying a time this way. But, there aren't small enough increments of time to make this reliable, plus patching duration might vary. Excluding reboots with patching and scheduling reboot scripts fixes this. However, this can't be done once on a recurring schedule due to the different scheduling paradigms already discussed. We have to schedule these manually each month.

Read full review

• I'd like to see the ability to selectively log off the remote machine via a button on the toolbar. Currently it's a setting to always lock on disconnect, or never lock on disconnect, requiring the tech to manually lock the machine if called for at the end of a session. Its a small time save that would add up!
• The chat feature could be expanded to be a lot more useful. Allowing clients to start conversations, and have conversations ping an email address if no one is monitoring the dashboard would be extremely valuable.
• Some clarity on licensing when providing host-passes to guest technicians would be a boon, especially for one-off support sessions with vendors.

Read full review

• We found we were able to provide good monitoring of our customers sites which was an objective. However, that came at a significant time investment that never seemed to be finished.
• We were able to negotiate a price that worked for us for an up-front purchase which was nice.
• We found the pricing to be very competitive.
• Bottom line for us was despite the pros of the product, we found other RMM solutions to be a better overall "value" due to not having to dedicate technicians to maintaining the product.

Read full review

• Instead of waiting 30+ seconds to initiate sessions, they initiate and display a desktop in two or three seconds. The amount of frustration this avoids is immeasurable.
• Once installed it doesn't need more handholding, i.e., having the remote enter a username/password. It is always just there.

Read full review