Automation has reduced repetitive endpoint maintenance and keeps our educational devices compliantEvery 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.
