Try our new research platform with insights from 80,000+ expert users

Automox vs Microsoft Configuration Manager comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 9, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Automox
Ranking in Patch Management
17th
Average Rating
8.8
Reviews Sentiment
8.1
Number of Reviews
10
Ranking in other categories
Vulnerability Management (50th), Endpoint Protection Platform (EPP) (61st), Enterprise Mobility Management (EMM) (18th)
Microsoft Configuration Man...
Ranking in Patch Management
1st
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
81
Ranking in other categories
Server Monitoring (6th), Configuration Management (3rd)
 

Mindshare comparison

As of April 2025, in the Patch Management category, the mindshare of Automox is 3.6%, down from 3.6% compared to the previous year. The mindshare of Microsoft Configuration Manager is 15.0%, down from 18.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Patch Management
 

Featured Reviews

Jack Leung - PeerSpot reviewer
Easy to use and deploy agents but needs more stability
We just need to deploy the agent to the endpoints. We don't need to set up anything. For a single agent, it takes one or two minutes. However, we deployed globally, and you need to take into consideration the time it will take to deploy across each endpoint. It's very simple to deploy. We had three or four engineers take care of the implementation.
MikeNelson2 - PeerSpot reviewer
Deployment recovery works well but requires configuration improvements
While I do not use the product frequently, many issues were due to configuration rather than the product itself. I cannot give an exact recommendation as it is not my area of responsibility. The team that uses it finds it adequate. It is presently good enough for us not to investigate other options. Overall, I rate the product a six out of ten.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Its flexibility is most valuable."
"The fact that it's just one product that can patch multiple operating systems is really great."
"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."
"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."
"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."
"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."
"The solution is user-friendly and easy to learn."
"It uses detailed descriptions of the workstations, and that is good for me."
"It is a good choice for deployment that performs very well."
"I manage software updates and operating systems for devices, and within seconds, we can remotely deploy a system for, say, 2,000 devices. Not only that, but we can also deploy scripts and create comprehensive compliance rules."
"Patching is very effective and reporting is very good."
"The most valuable feature of Microsoft Endpoint Configuration Manager is it's incredibly simple to configure and execute changes in bulk, allowing for seamless deployment. With this solution, you can easily track the status of all modifications and send them with ease, making it a comprehensive and efficient solution for any necessary adjustments."
"I like its ease of use. It does what you need it to do, and it's a one-stop-shop for the company and for all your deployments. If you incorporate Intune into it, you can have both. You can bring your own devices and corporate devices, and everything runs out of SCCM and Intune."
"SCCM is a stable solution."
 

Cons

"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."
"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 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."
"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 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."
"They need to improve the automation features."
"It should have integrated workstation access. So, there should be a remote desktop feature."
"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 solution is a bit heavy on the sources such as RAM or CPU and the software needs to be a bit lighter."
"There's no way to say, "I want this maintenance window to be on the second Tuesday of the month." It's strict. This window is this and that's it. You can't fluctuate."
"Our company would prefer not rebooting computers while people are using them. There seems to be no strategy behind it."
"The App to upgrades to the server needs to be improved."
"I'm looking for a single solution for all discovery needs. It fulfills about 40% of the requirements, and I'd like to see the other 60% so that I don't have to keep doing this."
"It does seem a bit buggy from time to time."
"SCCM can improve on third-party application support."
"I would like to see some improvements in WSUS and control of other, non-Microsoft, product updates."
 

Pricing and Cost Advice

"The pricing and licensing costs have been great for us... My advice to others who are evaluating or thinking of implementing Automox is to give it a shot. If a free trial is still available, definitely use it, because it makes life a lot easier."
"There are no additional costs in addition to the extended licensing fees with Automox. You get your support and your per endpoint license with what you purchased."
"Its licensing for a year was nine grand. There was no additional fee."
"The cost is very reasonable compared to the competition."
"Automox just charges us a set amount per user, per month, for using the product. That is very important to us. Because it's a cloud-native solution, you're saving on the cost of hosting an on-premises solution on your servers."
"We are on the premium licensing, which is the one that has the API capability that we use."
"We're doing it annually directly through Automox. It is per endpoint. It is $2 and some change per endpoint, but I believe the cost is right around $28,000. Everything is covered in this fee."
"The product is a great value."
"We have a support license from Microsoft Endpoint Configuration Manager and the overall price of the solution is reasonable."
"The price could be better."
"Pricing and licensing are horrible. You have to not look at dollar value to use SCCM. It's super-duper expensive but it works. The acquisition cost is expensive, it's labor-intensive. But it works."
"When you compare this solution with other tools in the market you might actually find a lot of variation in the pricing and that's why people opt for the other tools rather than Microsoft tools."
"As far as I know, it is an annual operating expense license."
"Pricing and licensing are a downside of SCCM. It's expensive. I'd have to confirm this, but I think they changed the licensing to core-based instead of socket-based. It's not cheap, because you have to buy the software, you have to buy SQL. Another thing we learned from talking to Microsoft is that they provide you a license for SQL if you run it on the same box as the primary server. If you run it outside that box, you have to buy SQL. Microsoft does recommend you running it on the same box because of performance. But then, in order to run SQL, SCCM, and everything on the same box, you better have some resources. It's an expensive solution. There's no doubt about it."
"Pricing is negotiable with Microsoft, depending upon which of their packages you choose."
"The price of Microsoft Endpoint Configuration Manager is expensive."
report
Use our free recommendation engine to learn which Patch Management solutions are best for your needs.
847,772 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Financial Services Firm
8%
Government
8%
Manufacturing Company
8%
Financial Services Firm
13%
Computer Software Company
11%
Government
11%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Automox?
It's easy to deploy agents to endpoints.
What is your experience regarding pricing and costs for Automox?
We do pay a monthly licensing fee. I'd rate the pricing as average. It's not cheap yet not too expensive. You can also pay for more support if you require them to provide consultancy services.
What needs improvement with Automox?
They need to improve the automation features. It could be more stable.
How does Ansible compare to Microsoft Endpoint Configuration Manager (SCCM)?
Microsoft Endpoint Configuration Manager takes knowledge and research to properly configure. The length of time that the set up will take depends on the kind of technical architecture that your org...
How to choose between ManageEngine Desktop Central and Microsoft Endpoint Configuration Manager (formerly SCCM)?
ManageEngine Desktop Central is very easy to set up, is scalable, stable, and also has very good patch management. What I like most about ManageEngine is that I can log on to every PC very easily a...
What do you like most about SCCM?
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 ...
 

Also Known As

No data available
Microsoft Endpoint Configuration Manager, System Center Configuration Manager (SCCM )
 

Overview

 

Sample Customers

Information Not Available
Bank Alfalah Ltd., Wªrth Handelsges.m.b.H, Dimension Data, Japan Business Systems, St. Lucie County Public Schools, MISC Berhad
Find out what your peers are saying about Automox vs. Microsoft Configuration Manager and other solutions. Updated: March 2025.
847,772 professionals have used our research since 2012.