What do you like best about Ivanti Autonomous Endpoint Management?
1. "Silent" Self-Healing & Autonomous Remediation
Instead of waiting for an employee to submit a help desk ticket because a background service crashed, disk space ran low, or a policy fell out of compliance, Ivanti detects and resolves routine issues automatically in the background.
G2
Why it matters: The best ticket is the one that never gets opened. End users stay productive without interruptions, and IT support spends far less time handling repetitive, low-tier fixes.
Ivanti
2. Risk-Based Autonomous Patching
Deploying patches across remote, hybrid, and fragmented worker fleets can be a constant headache. Ivanti takes the guesswork out of patching by prioritizing updates based on actual vulnerability threat risk rather than just release date or severity vendor scores.
G2
Why it matters: Critical security vulnerabilities are patched much faster, and updates deploy smoothly in the background without abruptly interrupting users in the middle of their workday.
G2
3. Unified "Single Source of Truth" Visibility
Tracking down off-network laptops or unmanaged shadow IT devices usually requires jumping across three or four separate tools. Ivanti unifies asset discovery, software inventory, real-time telemetry, and patch compliance into one pane of glass.
Why it matters: Having continuous visibility—even for devices off the corporate VPN—eliminates security blind spots and gives teams total confidence in their operational data before running automated bulk actions.
Ivanti
The Bottom Line: What people love most isn't just the automation itself—it's the time and mental bandwidth reclaimed. By taking routine maintenance off the team's plate, IT can shift focus away from endless daily maintenance to higher-value infrastructure projects and strategic security goals.
G2 Review collected by and hosted on G2.com.
What do you dislike about Ivanti Autonomous Endpoint Management?
While Ivanti Autonomous Endpoint Management (AEM) / Ivanti Neurons promises a lot on paper, administrators, sysadmins, and security teams frequently point out real-world pain points. Here are the most common drawbacks and criticisms associated with the platform: 1. Steep Learning Curve & Clunky UI The Issue: The interface can feel fragmented, cluttered, and non-intuitive. Because Ivanti has grown through acquisitions over the years (stitching together legacy products like LANDesk, Heat, and Shavlik), navigating between policy setup, asset discovery, and task rules often feels inconsistent. Impact: Onboarding new IT staff takes longer, and basic administrative tasks often require more clicks or steps than they should. 2. Complex Initial Setup & Customization The Issue: Getting the platform fully customized and aligned with an organization's specific environment is rarely a "plug-and-play" experience. Fine-tuning automated self-healing triggers and granular policy rules takes significant time and testing. Impact: Organizations often require dedicated professional services or extensive internal lab testing to get automation rules working reliably without causing unintended software breakages. 3. Reporting and Analytics Limitations The Issue: Out-of-the-box reporting dashboards can feel rigid. While the system collects a massive amount of endpoint telemetry, pulling tailored, executive-ready, or highly specific operational reports can be tedious. Impact: Admins often find themselves exporting raw data to third-party BI tools or writing custom queries just to get clear visibility into specific patching compliance or inventory metrics. 4. Occasional Status Sync Delays & Agent Glitches The Issue: Real-time data syncs across large endpoint fleets can sometimes lag. Administrators report occasional delay gaps between taking an action in the console and seeing the status update across endpoints, along with occasional agent deployment errors. Review collected by and hosted on G2.com.
