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

Ivanti Autonomous Endpoint Management vs Ivanti Patch for Linux, UNIX, Mac [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
7.8
Reviews Sentiment
6.2
Number of Reviews
52
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 Linux, UNI...
Average Rating
9.0
Reviews Sentiment
7.5
Number of Reviews
4
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.
KU
Linux admin at Ameex Technologies
With good website development capabilities, the solution also provides exceptional stability
The initial setup is straightforward. The time taken for deployment for the website depends on the website code files and database. It may take four hours to eight hours for a single site to migrate from another solution. We used to do the migration from the cloud only and not on-premises. For deployment, we used to compress the code files, and using SFTP, we used to transfer the files. We then configure the same with that, and after transferring the code files, we used to have the UAT, staging, and production URL. Once everything is fine, we will switch the DNS for the live website. For the deployment and maintenance, we need support from the client's side and from the management side to make the DNS switch. We also need help from third-party vendors to provide access.

Quotes from Members

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

Pros

"Ivanti Autonomous Endpoint Management has positively impacted my organization primarily through the ability to report on patch compliance."
"Ivanti Neurons for UEM has positively impacted my organization by providing customers with tools to scan, perform remote desktop functions, conduct patch analysis, and manage software deployment along with network scanning."
"For those looking into using Ivanti Autonomous Endpoint Management, I would recommend just going for it, as it is the best tool available in the market right now with all the features, and despite needing a few improvements, I encourage people to use it."
"The solution is good, it's effective in what it is able to achieve and it's easy to use."
"This product helps us to create a streamlined process and it is working as expected."
"Ivanti Autonomous Endpoint Management has positively impacted my organization by being highly effective because now everything is mapped out and managed."
"MobileIron UEM is a scalable solution."
"Ivanti Patch's most valuable features are the patch module and the package distribution."
"Compared to other software options, this is not exactly a cheap solution, however, the value you get is good, and therefore it's worth the cost."
"The tool is a stable product."
"Ivanti Patch for Linux, UNIX, and Mac helps to ensure that everything is up to date."
"The website development section is the most valuable feature of the solution."
"The solution is easy to implement."
 

Cons

"I have not seen a return on investment with Ivanti Autonomous Endpoint Management."
"MobileIron UEM could improve the monitoring of devices."
"I would also like to see more integrations, plugins, and user-friendly automation, similar to the multiple integration scripts that Rapid7 has."
"There are times when there is an update that causes some issues. These issues should be sorted out before the release."
"Customers sometimes ask about non-existent features, and we pass these requests on to Ivanti."
"Sometimes I find that the reporting in Ivanti Autonomous Endpoint Management is too detailed, and I would appreciate the ability to customize my reporting a little bit more."
"From my perspective of having just moved away from the product, I would probably give it a six."
"The biggest problem that I have with technical support is that it is not regional and we are dealing with time differences."
"The solution can be quite expensive, compared to other options on the market."
"The tool needs to improve its visual system."
"The better way to improve the solution is by working on an area where it lacks, which includes the migration part."
 

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."
"The price of MobileIron UEM is very good."
"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 solution is open-source, so we do not need any licensing."
report
Use our free recommendation engine to learn which Patch Management solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
12%
Manufacturing Company
9%
Outsourcing Company
9%
Financial Services Firm
9%
No data available
 

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 because...
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
HEAT Patch, PatchLink
 

Interactive Demo

Demo not available
 

Overview

 

Sample Customers

Frontier Airlines
Information Not Available
Find out what your peers are saying about Qualys, Microsoft, Ivanti and others in Patch Management. Updated: October 2026.
920,769 professionals have used our research since 2012.