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

Automox vs Ivanti Patch for Configuration Manager 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)
Ivanti Patch for Configurat...
Ranking in Patch Management
25th
Average Rating
7.6
Reviews Sentiment
6.4
Number of Reviews
2
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 Ivanti Patch for Configuration Manager is 1.1%, down from 1.7% 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.
Gaurav Chandola - PeerSpot reviewer
Provides detection logic that tells us which customer will record an update and is less expensive than other solutions
I haven't had experience with customer service and support, however, we did have an advisory case with one of their technical support staff. We were publishing and getting the full metadata for the patch. We were getting the full updates for the patch release. There was confusion as to why we were seeing that in the SCCM, instead of in the full metadata patch. The support person was able to help us in understanding what we were doing wrong, highlighting it could be a certificate issue. We generated a new certificate, and after they were applied, the issue was fixed. Overall, I would rate their customer service and support a five out of five.

Quotes from Members

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

Pros

"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."
"The biggest improvement to our organization involves the reduction in its man hours... We've probably saved hundreds of hours."
"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."
"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."
"Its flexibility is most valuable."
"It's easy to deploy agents to endpoints."
"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."
"This solution is stable."
"The most valuable feature of Ivanti Patch for SCCM is the detection logic."
 

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 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."
"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."
"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. \"
"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."
"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."
"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."
"In future releases, I would like to see improvements with the feature upgrade for the SCCM, which Microsoft has already integrated. Currently, Ivanti does not give us information about the enablement package."
"We have some problems with patches not installing successfully."
 

Pricing and Cost Advice

"Its licensing for a year was nine grand. There was no additional fee."
"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."
"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."
"We are on the premium licensing, which is the one that has the API capability that we use."
"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."
"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.""
"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 do not have a license with Ivanti, instead we buy just the plugins for the consoles, making it a much less expensive option versus other solutions."
report
Use our free recommendation engine to learn which Patch Management solutions are best for your needs.
849,600 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Government
9%
Financial Services Firm
8%
Manufacturing Company
8%
Financial Services Firm
21%
Computer Software Company
10%
Real Estate/Law Firm
9%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Also Known As

No data available
Patch for SCCM, Shavlik Patch for SCCM, Ivanti Patch for MEM
 

Overview

 

Sample Customers

Information Not Available
University of Pittsburgh
Find out what your peers are saying about Automox vs. Ivanti Patch for Configuration Manager and other solutions. Updated: April 2025.
849,600 professionals have used our research since 2012.