We performed a comparison between Automox and Microsoft Configuration Manager based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, HCLTech, Kaseya and others in Patch Management.
"The fact that it's just one product that can patch multiple operating systems is really great."
"It's super easy to use and we haven't found anything easier."
"The biggest improvement to our organization involves the reduction in its man hours... We've probably saved hundreds of hours."
"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."
"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."
"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."
"It's easy to deploy agents to endpoints."
"Among the most valuable features are its ease of use and the Worklets. Both of them are time-savers. Worklets enable us to customize things for a given environment. It's something like when Apple lets other people create applications. Other peoples' Worklets can be used in our environment and in our customers' environments. That saves a lot of time, and it's really cool."
"It's helped us solve problems surrounding patching, installing, and reporting different patches, etc., on the virtual machines."
"The solution doesn't require any maintenance from our end because it is a cloud-based solution and Microsoft takes care of everything."
"SCCM is a stable solution."
"Software deployment and WSUS are most valuable."
"It works well for the endpoints for the customer I'm consulting. It has a bunch of knobs, and you can tune it to do lots of things."
"It saves a lot of money when you can install things automatically and they are installed the exact same way on every computer."
"There have to be made some improvement in WSUS and control in other non-Microsoft products updates."
"The most valuable feature of Microsoft Endpoint Configuration Manager is patch management."
"The biggest area they need to fix, without a doubt, is the ability to copy and sync profiles and worklets between all of the organizations you manage, and the ability to have top-level user access control across all of the companies that you manage."
"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. \"
"They need to improve the automation features."
"As concerns the patching concepts, there's a bit of a learning curve in terms of working out how Automox wants you to work within the console, not only splitting up everything into groups, but then having the various policies assigned."
"The stability has come a long way from what it was like when it started and now it's really good."
"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."
"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."
"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."
"The main thing is that SCCM has to become an appliance instead of a server. When I say appliance, it has to come preconfigured so that it is drop-shipped into the enterprise and then you activate the feature sets that you want. It should pull down all the latest binaries. Once that is all there, it should have a discovery tool which goes out and discovers the assets within an enterprise. If the server, workstation, and applications are all coming from the same vendor, why not have the vendor do this work for us and automate it as much as it possibly can?"
"Microsoft should extend support for additional platforms."
"The main room for improvement is the on-screen display. I think it would be good if some improvements were made."
"Microsoft Endpoint Configuration Manager can improve by allowing us to schedule the scripts, we don't have a script scheduling option and have to do it manually."
"The solution can be improved by speeding up the synchronizing of the policies on the devices."
"The solution is a bit heavy on the sources such as RAM or CPU and the software needs to be a bit lighter."
"As far as load balancing across, they don't have that support yet, so that you can actually build multiple primaries and have it load balance across. They don't have any of that functionality yet. That would be a nice feature, to scale that way."
"Some of the capabilities aren't fully developed yet. It's an ongoing work in progress. I think they are making some steps in the right direction as far as managing workstations centrally, like Intune."
More Microsoft Configuration Manager Pricing and Cost Advice →
Automox is ranked 11th in Patch Management with 10 reviews while Microsoft Configuration Manager is ranked 1st in Patch Management with 78 reviews. Automox is rated 8.8, while Microsoft Configuration Manager is rated 8.2. 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 Microsoft Configuration Manager writes "Seamless system updates, useful integration, and reliable". Automox is most compared with Microsoft Intune, BigFix, Tanium, NinjaOne and Qualys VMDR, whereas Microsoft Configuration Manager is most compared with Red Hat Ansible Automation Platform, ManageEngine Endpoint Central, Microsoft Intune, BigFix and Tanium.
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.
