No more typing reviews! Try our Samantha, our new voice AI agent.

Ivanti Autonomous Endpoint Management vs Ivanti Patch for Configuration Manager [EOL] comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Aug 4, 2026

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

Ivanti Autonomous Endpoint ...
Average Rating
8.0
Reviews Sentiment
6.1
Number of Reviews
53
Ranking in other categories
IT Asset Management (8th), Vulnerability Management (16th), Mobile Device Management (MDM) (6th), Enterprise Mobility Management (EMM) (3rd), Mobile Threat Defense (5th), Patch Management (3rd), Attack Surface Management (ASM) (18th), Unified Endpoint Management (UEM) (5th), Application Security Posture Management (ASPM) (8th), Autonomous Endpoint Management (2nd)
Ivanti Patch for Configurat...
Average Rating
7.6
Reviews Sentiment
6.4
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Mahmudul Hoque Khan - PeerSpot reviewer
Lead Engineer at intelQong Technology
Automation has reduced repetitive endpoint maintenance and keeps our educational devices compliant
Every software has some drawbacks and cons. For Ivanti Autonomous Endpoint Management, I think the first improvement I would suggest is to simplify initial configuration. The process to make endpoint enrollment, device grouping, and configuration easier, particularly for organizations managing different categories of devices, would be helpful. If the initial configuration is simplified, better workflows for shared computers, labs, faculty workstations, and administrative devices would make it easier to apply different software and security policies without duplicating configuration. For my work, I would suggest one improvement that would make my experience with Ivanti smoother than before. I would want Ivanti to clearly explain the root cause when something fails, such as when a patch deployment or automated remediation fails. It shows the error code, but when we are doing a lot of work, it kind of makes a lot of hassle to read the documentation or ask an AI what kind of error it is facing. My recommendation here is to show the issue, show the full explanation of how it is working, where it failed, and show whether the issue can be safely resolved automatically without needing a third party. I think it needs a lot of improvement. First of all, centralized management and scalability can be improved, particularly the ability to manage endpoint configuration, which would be more helpful for my field of work. Regarding scalability, centralized deployment and policy enforcement can help maintain consistency across larger device fleets without configuring every endpoint individually. I think another improvement would be detailed failure diagnostics, flexible maintenance scheduling, controlled policy rollouts, and clearer reporting on whether the fix will cause any issues.
reviewer2019633 - PeerSpot reviewer
Director at a tech services company with 1,001-5,000 employees
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

"The most effective feature of Ivanti Neurons for Patch Management is its reactivity when a patch is released before its due date."
"Ivanti Autonomous Endpoint Management portal management is the best portal for security endpoints I can use."
"Ivanti Neurons for UEM has positively impacted my organization by saving time and improving efficiency."
"Ivanti Autonomous Endpoint Management has positively impacted our organization by allowing us to reduce the volume of daily tasks."
"Ivanti Autonomous Endpoint Management is a great tool for managing our team and company assets."
"The most valuable features are device management and support for upgrading applications."
"When comparing Ivanti Autonomous Endpoint Management with other MDM solutions like Intune, I would say it is on par or better in almost all respects."
"It has saved time, reduced errors, and improved security significantly, which are some of the improvements I have seen with Ivanti Autonomous Endpoint Management."
"The most valuable feature of Ivanti Patch for SCCM is the detection logic."
"This solution is stable."
 

Cons

"The MDM, asset management, and software spend management are areas that could have more improvement in Ivanti Neurons for MDM."
"The release of new versions often goes in the wrong direction with Ivanti. The test team or the testing procedures are flawed because they release new versions with numerous basic issues."
"Sometimes there is a lag with the environment, and we need to refresh before using it."
"The product's support and configuration need to improve. It needs to be more scalable."
"There are a few areas where Ivanti Autonomous Endpoint Management could be further improved, including custom reporting, dashboard flexibility, and UI navigation for new admins."
"From my perspective of having just moved away from the product, I would probably give it a six."
"Customer support is really poor."
"In terms of improvement, I would recommend better documentation. During the time I used it, there were issues with up-to-date patching, and the documentation around those specific errors was quite confusing."
"We have some problems with patches not installing successfully."
"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."
 

Pricing and Cost Advice

"For the one that works with SCCM, it is relatively inexpensive at $8 USD per node, yearly. The standalone product has two versions; the one that patches servers is about $45 USD annually and the version that patches workstations is about half that price at $22 USD."
"The solution is affordable."
"My impression is that MobileIron is very expensive."
"The license can get expensive if you have a lot of nodes."
"The solution is expensive compared to other products."
"While the price is a bit high, it may be equitable with the features one gets with the product, such as that involving the interface."
"The price of MobileIron UEM is very good."
"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.
921,523 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
12%
Manufacturing Company
10%
Outsourcing Company
9%
Financial Services Firm
9%
Financial Services Firm
13%
Retailer
11%
Legal Firm
10%
Outsourcing Company
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business19
Midsize Enterprise12
Large Enterprise35
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Ivanti Neurons for UEM?
The overall experience with pricing and licensing was good. The transparent pricing based on the number of managed endpoints, the features included with each license, and the additional seat cost f...
What needs improvement with Ivanti Neurons for UEM?
One challenge we've found here regarding handling problems with Ivanti Autonomous Endpoint Management is actually the question of pagination or the size of endpoint results, which limits us bec...
What is your primary use case for Ivanti Neurons for UEM?
My main use case for Ivanti Autonomous Endpoint Management is opening and managing tickets for the IT area. My team provides support in handling tickets, errors, and problems that we find in the sy...
Ask a question
Earn 20 points
 

Also Known As

Ivanti Neurons for Patch Management,Ivanti Neurons for RBVM,Ivanti Neurons for VULN KB,Ivanti Mobile Threat Defense,Ivanti Neurons for Spend Intelligence, Ivanti Neurons Patch for Intune, Ivanti Neurons for EASM
Patch for SCCM, Shavlik Patch for SCCM, Ivanti Patch for MEM
 

Interactive Demo

Demo not available
 

Overview

 

Sample Customers

Frontier Airlines
University of Pittsburgh
Find out what your peers are saying about Qualys, Microsoft, Ivanti and others in Patch Management. Updated: October 2026.
921,523 professionals have used our research since 2012.