Auvik vs ConnectWise Automate

• Auvik is the big pic tool of choice for network diagramming, helps layout of our network infrastructure, and we'll know immediately the status of the devices that are successfully communicating, and those that may have, for example, credentials issues.
• Auvik's "Traffic Insights" are key accelerators for intuitively isolating and resolving traffic-related issues quickly and easily, and the historical information makes it simpler to deduce what aspects may need replacement, capacity improvement, or possibly even re-architecture.
• Auvik integration tools are excellent solution enhancers - that are of particular interest to our company, as we make use of MS Teams and Connectwise products; we would like to see some features to integrate to ServiceNow as well.

Read full review

• 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

• Feature request platform needs more management, I see lots of duplicates.
• Pressing enter after typing my password should move to the 2FA screen, seems like an easy fix but still not.
• Deploy on an RPi! Making sub-100$ Auvik appliances would be great instead of relying on workstations or containers.

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

• the ROI for Auvik comes from the time it saves in updating documentation and onboarding, new clients. We no longer have to spend a day investigating a network and documenting it, this is life and up to date so you always have true information for reporting and troubleshooting.

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