We performed a comparison between Automox and Microsoft Configuration Manager 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."
"Its flexibility is most valuable."
"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."
"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."
"It's super easy to use and we haven't found anything easier."
"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."
"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."
"The biggest improvement to our organization involves the reduction in its man hours... We've probably saved hundreds of hours."
"The scalability to deploy the package."
"One of the standout features of SCCM is its application management capabilities. It allows us to create packages efficiently and deploy them to specific groups within our network. This streamlined process has significantly improved our software distribution workflows."
"Patching is the main feature because SCCM is made to control the entire environment without manually interpreting. So it is good to use for patching."
"It is easy to install, and quick to deploy."
"The solution is user-friendly and easy to learn."
"The initial setup is fairly straightforward."
"It is a very well-rounded product. It is a complete package with all the features using which we are able to manage our PCs very efficiently."
"The main, clear valuable feature is updating the latest, patches and updates from Windows. This is the main feature we really utilize a lot."
"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."
"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."
"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."
"The TSM component could be improved."
"It would be of benefit if Configuration Manager could be connected/integrated with multiple Microsoft Intune subscriptions rather than just one (the current limit)."
"On some hardware, we'd like an easier way to get peripherals attached."
"The cost of the product can be improved."
"This solution should be simpler, and more consistent across modules/sections."
"The setup was complex and I faced a lot of problems initially because I was new to the solution."
"Troubleshooting in general needs improvement. There's just a ton of logs to go through, and so finding the error log that corresponds with that you're doing can sometimes be difficult."
"There should probably be better remote support. They should also continue to improve on patch management, patching, and creating or turning products in software into deployable apps."
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, NinjaOne, Tanium and Qualys VMDR, whereas Microsoft Configuration Manager is most compared with Red Hat Ansible Automation Platform, ManageEngine Endpoint Central, BigFix, Microsoft Intune and Tanium. See our Automox vs. Microsoft Configuration Manager 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.