We performed a comparison between Automox and Kaseya VSA based on real PeerSpot user reviews.
Find out in this report how the two Patch Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The fact that it's just one product that can patch multiple operating systems is really great."
"Coming from prior solutions that were a lot more effort, Automox's patch management abilities are transformational. When I took over patching at my company, they were using on-premise architecture to patch. As the workforce shifted from being in the office into their home offices, I was able to lift and shift with no effort other than deploying the new agent out into the environment."
"Previously, we would run a report, scan it, and compare it. We were spending 15 to 30 minutes a month on each machine on this stuff because you would find stuff that wasn't up to date, then you had to fix it. This solution takes that time down to minutes. Automox saves us easily many hours a month."
"Its flexibility is most valuable."
"The biggest improvement to our organization involves the reduction in its man hours... We've probably saved hundreds of hours."
"It's easy to deploy agents to endpoints."
"The flexibility in creating tools to make changes on remote machines is most valuable to me. The reporting feature is also fantastic because on any given day I can bring up a list of machines that don't have patches, for example. Or I can bring up a list of machines that are in my environment on a certain day. The solution helps me with not only my own role, and what I look for internally myself, but it also helps during audits. I can go in and look at the number of machines in there, and their owners and timelines. It certainly helps tell a story for anything that IT requires."
"They've been adding some new features lately, which I'm not nearly as familiar with, but the ability to just deploy patches and exempt certain machines from certain patches is helpful. For instance, for our servers, we may not want to roll out zero-day patches. We are able to exempt those and make sure that they don't get those policies. We've got certain servers that have to run a particular version of Java, and being able to exempt those servers from receiving Java updates is pretty fantastic."
"Being able to connect to client computers without them necessarily needing to be there and being able to put in the patches and manage different information systems is valuable."
"The patching is very efficient and we can rely on the alerts that we receive."
"The most valuable part of this solution is the security features that it offers."
"The most valuable features of Kaseya VSA are remote control, live connect, and automation."
"Provides efficient automation."
"Kesaya is highly configurable."
"The product's support team is very quick to respond, especially because the tool's technical team operates in the same time zone where I am located."
"The way Kaseya VSA treats application vulnerabilities is good. They have released some new features that have been a benefit, such as updates from the Microsoft repository directory."
"They need to improve the automation features."
"The only thing that we've ever truly wanted is an onsite repository. Currently, all updates are provided directly from the internet. So, if you have 1,000 devices, all 1,000 devices go directly out to the internet. We would love the option of being able to put the updates on local storage so that we're not consuming as much bandwidth. That is literally the only thing that we've ever wanted."
"It should have integrated workstation access. So, there should be a remote desktop feature."
"There should be better inventory capabilities. Right now, they only allow you to have insight into software out-of-the-box. It would be nice to also extend that into custom inventory that can be modified and managed by the practitioner."
"When we bring on a new client, we need to go into that client and manually set up my account, my chief engineer's account, three technicians' accounts, and a billing person's account all over again, which is annoying. We have probably up to 15 or 16 of our clients on Automox now. For every single one of those, we have had to go in and set this up. Then, if anything changes, we have to remember to go to Automox and change it 15 or 16 times. So, we just want inheritable permissions, and that is it. We have talked to them about this, and they are like, "Yeah, we hear a lot of complaints about it." I am thinking, "Guys, I have been complaining about this for a year and a half. When are you going to do it?" It must be some tricky thing or not an easy fix, because I can only assume if it were easy, then they would have done it by now."
"The stability has come a long way from what it was like when it started and now it's really good."
"We would like to see additional detailed reporting for Service providers like us. We had to build our own reports via their APIs to meet our needs."
"Asset management would be a great feature to add to Automox. We would run easier scripts or more out of the box scripts that would help us in audits. \"
"The product's user interface is an area with certain shortcomings where improvements are required."
"Some configurations and abilities from the system are not of use. The solution should offer webinars or some sort of training offerings to help users learn what the system can do and how it can be done."
"The solution is hard to use at first until you understand how it works."
"It's very difficult to update the third-party software on every device."
"I believe we should include a VSA license to provide complete endpoint management."
"The agent-based monitoring solution can be improved."
"Its scripting language kind of sucked. They have their own version of PowerShell inside VSA. if you want to reach out and grab endpoint information, for instance, to know how many end devices have a program installed, you actually have to write a script for that. It wasn't like how it is in CrowdStrike where you can just do a search, and it just happened. In VSA, you have to write your own script to do it. In terms of new features, an integrated MDM for mobile devices would be awesome."
"The main difference would be the addition of audio transfer between the end-user and the remote connectivity software. That is the one critical piece that we are currently lacking."
Automox is ranked 11th in Patch Management with 10 reviews while Kaseya VSA is ranked 5th in Patch Management with 29 reviews. Automox is rated 8.8, while Kaseya VSA is rated 7.6. The top reviewer of Automox writes "Monitors our devices irrespective of the location and the environment, allows us to exempt certain machines from certain patches, and has perfect patch management abilities". On the other hand, the top reviewer of Kaseya VSA writes "Broken from the beginning and never functioned as anticipated". Automox is most compared with Microsoft Intune, BigFix, Microsoft Configuration Manager, Tanium and NinjaOne, whereas Kaseya VSA is most compared with Microsoft Configuration Manager, ConnectWise Automate, NinjaOne, Microsoft Windows Server Update Services and Datto Remote Monitoring and Management. See our Automox vs. Kaseya VSA report.
See our list of best Patch Management vendors.
We monitor all Patch Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.