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

Automox vs Microsoft Windows Server Update Services comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 16, 2024

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 Windows Server Up...
Ranking in Patch Management
3rd
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
49
Ranking in other categories
No ranking in other categories
 

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 Windows Server Update Services is 6.8%, down from 12.9% 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.
Chuck Colby - PeerSpot reviewer
Efficient patch management, potentially scalable, and free is using Microsoft servers
Whether to use the solution or not is going to be context-sensitive. If you have a strong Microsoft team, you can probably handle this. If, like my team, you also have a dozen other vendors to consider, it's not just the operating system. The pattern I've seen over time with WSUS is that it has the potential to be a fantastic product, yet it doesn't feel finished. People try to implement WSUS, and context is important. In my context, we're a small business without teams of Microsoft-certified people. We are just trying to use what's available to achieve a goal, and WSUS is fine, however, not the best product out there. The business in America often tries to do more with less. I would not recommend it to a team of my size. If a company had half a dozen or a dozen Microsoft-certified people, I'd say, run with it. For a team of my size, no, absolutely not. I would rate the overall solution a solid eight 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

"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."
"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."
"Its flexibility is most valuable."
"The fact that it's just one product that can patch multiple operating systems is really great."
"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 biggest improvement to our organization involves the reduction in its man hours... We've probably saved hundreds of hours."
"The most valuable feature is Server Update's stability."
"It's a scalable product."
"Provides the ability to create multiple downstream servers."
"The product reduced the number of crashes on our applications that were not able to use the latest versions of Windows updates."
"I would rate the overall solution a solid eight out of ten."
"The noteworthy aspect is the system's capability to handle an extensive range of services and workloads, with the potential for almost unlimited scalability."
"Microsoft Windows Server Update Services is an easy-to-use and stable solution."
"The solution has great potential and leaves the user with almost limitless possibilities. It is truly a product with a million uses."
 

Cons

"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."
"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."
"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 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. \"
"I would like to see support for other operating systems such as Linux."
"There are several areas needing improvement, including the management of third-party patches."
"Microsoft Windows Server Update Services needs to improve its reporting feature. The tool's competitor has better reporting capabilities."
"The main problem with WSUS is that the management console doesn't allow you to do a lot of operations. It's actually quite a primitive console, and has been since day one. In order to be more effective, you need to use another tool from Microsoft that can take advantage of WSUS and also offer you the extra features you need."
"The product should improve its third-party management."
"Having the ability to group updates by the operating systems would be very helpful."
"The product needs to improve its user interface."
"The ability to have more fine control within this solution is very important. It is not available for the solution in its current state."
 

Pricing and Cost Advice

"For all these software tools, it is usually a subscription model. There is a monthly charge that we need to pass along to our clients because we are doing all this for their benefit. It is only a couple of bucks a month per computer, and that is a low enough price point where our clients, without exception, have accepted it, and said, "This is great. We will pay that. It sounds like a worthwhile thing.""
"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."
"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 are on the premium licensing, which is the one that has the API capability that we use."
"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."
"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."
"Its licensing for a year was nine grand. There was no additional fee."
"Because it is not open-source, it has to compete with open-source solutions. Relatively it is expensive to open-source."
"This product comes included with Windows and can be used free of charge."
"The licensing of WSUS is free of charge because it comes with the Windows Server operating system, included as a feature of the operating system itself. It's simply a role that you enable within Windows Server."
"We need one single key for Windows deployments, which is a better option. Buying a license with the same key for all systems, like Windows and Windows Desktop, makes configuring easier. Otherwise, it isn't easy to manage multiple keys for different systems."
"Configuration Manager is less expensive than Microsoft Windows Server Update Services."
"The integration is included in the Windows Server system, and there are no additional fees."
"The product is expensive."
"It doesn't need a license. It's offered for free with Microsoft."
report
Use our free recommendation engine to learn which Patch Management solutions are best for your needs.
847,862 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%
Computer Software Company
14%
Government
12%
Manufacturing Company
9%
Financial Services Firm
9%
 

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.
What is your experience regarding pricing and costs for Microsoft Windows Server Update Services?
It's a free service. You just buy the Windows Server operating system, and it is an internal feature.
What needs improvement with Microsoft Windows Server Update Services?
Sometimes, I encounter issues with the Windows internal database, which occasionally does not load, leading to the Pandit console stopping. I have to repair the database and perform export and impo...
 

Also Known As

No data available
Windows Server Update Services, Microsoft WSUS, WSUS, Microsoft Software Update Services, Software Update Services, Microsoft SUS, SUS, MS Windows Server Update Services
 

Overview

Find out what your peers are saying about Automox vs. Microsoft Windows Server Update Services and other solutions. Updated: March 2025.
847,862 professionals have used our research since 2012.