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.
"It's super easy to use and we haven't found anything easier."
"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."
"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 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."
"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 fact that it's just one product that can patch multiple operating systems is really great."
"The solution has a very good set of features."
"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."
"This has made the management of our environment easier."
"Valuable features include configurations enforcement, compliance data gathering, and deployment of a standardized OS."
"Endpoint Manager is valuable to our organization because it allows us to connect to our enterprise from remote locations securely. The most useful feature is its robustness and scalability. It is highly scalable and flexible, allowing us to use it in various environments. Additionally, we can specialize the policies related to each device group. This ensures that each group has access to the applications they need for their work and non-work hours."
"The initial setup is straightforward and not too complicated."
"Technical support was helpful and responsive."
"It has the ability to perform mass distribution."
"It should have integrated workstation access. So, there should be a remote desktop feature."
"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."
"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. \"
"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 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."
"They need to improve the automation features."
"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."
"A lot of experience is needed in terms of troubleshooting, as this is one of the most difficult tasks in MECM. We were seven people in a group and I was the only one that had the patience to do the troubleshooting at times."
"I want the system to provide some dependency relations. I would also like to see the relationship between different machines."
"The TSM component could be improved."
"The time the solution takes for updating systems could be quicker. For example, the system information status is not updating as it should. Additionally, the database synchronization querying is slow and could be improved."
"It needs to be able to load faster during deployment."
"The ability to integrate MDM would be great."
"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."
"Microsoft should extend support for additional platforms."
More Microsoft Configuration Manager Pricing and Cost Advice →
Automox is ranked 12th 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, Qualys VMDR and NinjaOne, 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.
