Ivanti Endpoint Manager [EOL] Reviews

I have been working with the Ivanti Endpoint Manager product for almost four years. Initially, I started to have good exposure in Ivanti Endpoint Manager in on-premises server. We deployed the appliance to manage more than 250 servers and 700 plus workstations and devices. We mainly used it for patching and fetching asset inventories. Later, we utilized many of its capabilities such as scheduling tasks and getting historical data.

Recently we moved from EPM on-premises to cloud, the unified endpoint manager console, Ivanti Neuron Cloud. We are in the transition phase. Our team really appreciated the Ivanti Endpoint Manager, so we continue to do automation. We are moving from on-premises to cloud, to SaaS.

From the features perspective, distribution packages is the best feature in the Ivanti Endpoint Manager. We create tasks for patching or distributing software, appliances, or MSA files and schedule them. We create repair groups, push appliances, create drives, and map shared drives to distribution packages. It distributes the groups included in those packages across our entire network. It is easy to deploy appliances or applications, including OS to workstations within a single click.

We can see any missing patches or vulnerabilities. It is very useful for troubleshooting and identifying patches, whether missing or installed.

I would suggest including an option to manage multiple clients in future releases. For example, as a managed service provider, if I use Ivanti Endpoint Manager for one client, can I deploy or use the same server to manage other clients or multiple sites or region clients? That feature would be beneficial for managing multiple domains within a single appliance.

Despite the good features, I would suggest improvements in the console interface of the Ivanti Endpoint Manager as it appears outdated, reminiscent of the early 2000s. If they improved the UI in Ivanti Endpoint Manager or implemented any UI/UX development in the console, it would be beneficial. There are numerous unwanted options or repeated tabs visible in all sessions.

I have been working with the Ivanti Endpoint Manager product for almost four years.

Overall, I have not experienced any crashes, downtimes, or performance issues with it.

Regarding scalability, I am unable to comment on whether it is easy to scale up or scale out, or if there are any limitations.

I would evaluate customer service and technical support of Ivanti Endpoint Manager as eight or nine out of ten.

Positive

Ivanti Endpoint Manager is my first product experience. I did not have any other solution in place before.

The Ivanti team handled everything from end to end. They guided us through configuration and asked questions about our needs and desired configuration settings.

We received input from Ivanti support engineer and sales team. They set up the initial configurations, including patch deployment, task scheduling, and many other features. We maintained that process and later modified many configurations based on our environment requirements.

Apart from Ivanti Endpoint Manager, I have recent exposure to Enable Tech, Enable Halo PSA, and Enable Patching. I also have basic knowledge of Intune for two clients. For Windows machines, they use Windows patching through Intune, which offers options for quality updates, feature updates, and driver updates.

The main benefits of Ivanti Endpoint Manager include patch management and security benefits such as vulnerability management. It is particularly useful for managing devices in a centralized console. For production purposes, it enables easy software distribution to endpoints and simplified management of user profiles and settings.

The self-service portal for endpoint devices allows users to request software or services during maintenance windows. For inventory management, it helps track software expiration, device expiry, missing patches, and generates reports for regulatory compliance.

Regarding automation capabilities for routine tasks such as software deployment and patching, we initially used automation. However, we later switched to a manual process for deploying patches and software to specific test phase groups, moving from one group to another through test, pilot, and production phases.

The patch management functionality allows us to create scopes and identifies missing patches. Ivanti Endpoint Manager delivers patches for Microsoft products and third-party vendors, which is beneficial for managing business applications such as Adobe, Zoom, or VPNs.

For asset discovery, the system offers IP scanning and network scanning options. By entering network subnet information, it fetches all device details including serial numbers, vendors, and expiration dates. The reporting section includes default queries and customized reports that can be scheduled periodically.

The remote management capabilities are effective for managing distributed workforce environments. The device portal allows administrative tasks through remote control options, similar to Teams or Zoom, enabling operations such as file checking, machine rebooting, and resource usage monitoring.

While there were some security concerns regarding automatic critical patch deployment, these were addressed by disabling automation when necessary.

I give Ivanti Endpoint Manager a rating of 9 out of 10 and recommend it for centralized device management, automated task scheduling for patch distribution, software deployment, and inventory management. It is suitable for both small business organizations and enterprises.

I have been using Ivanti Endpoint Manager in my career for about five years, where I completed the whole migration from on-prem to the hybrid migration within a configured company.

This included taking on-prem and doing the hybrid configuration, configuring all the profiles and everything else within the device, including enrolling the device, setting up the policies, and all the compliance policies and BYOD deployment and app protection within Ivanti itself.

What I appreciate most about Ivanti Endpoint Manager is that it's easy to enroll the device.

The patch is very impressive, and the patching part of Ivanti Endpoint Manager is much easier compared to InTune, where in InTune, you have to create the app deployment, but Ivanti Endpoint Manager makes it much easier to update any patch, patch updates, and application updates.

The initial deployment with Ivanti Endpoint Manager was easy and straightforward.

I took the training, and immediately, I was able to manage it, although there were some things I had to call support for.

The implementation from on-prem to their SaaS application was very straightforward, where you create the profile, the compliance, and all the components, allowing the device to enroll automatically from there.

The pricing differs from InTune. Ivanti Endpoint Manager charges a flat fee for the implementation and product purchase, followed by yearly maintenance, whereas InTune charges per license, with the license included with the intra ID and everything else.

In terms of areas where Ivanti Endpoint Manager could improve, it's the wiping or locking of the system.

For instance, when we offboard a user, sending the wipe command or lock command is slightly slower than Workspace ONE, as Workspace ONE automatically processes the lock or device wipe command instantly, while InTune is similar too.

I have been using Ivanti Endpoint Manager in my career for about five years.

For stability, once you get the system up and running, it's consistently stable without any lagging, crashing, or downtime.

Regarding scalability, Ivanti Endpoint Manager is very scalable.

I have contacted the technical support frequently.

Regarding the quality and speed of the support, they are excellent.

Once you place the request, you usually get a call back right away.

In terms of support quality, they are very knowledgeable, regardless of the questions or issues you're having.

It's always better to jump on a call and share screen, which they are willing to do rather than just going through a list of troubleshooting steps.

Positive

I have used something similar to Ivanti Endpoint Manager.

The initial deployment with Ivanti Endpoint Manager was easy and straightforward.

I took the training, and immediately, I was able to manage it, although there were some things I had to call support for.

The implementation from on-prem to their SaaS application was very straightforward, where you create the profile, the compliance, and all the components, allowing the device to enroll automatically from there.

I don't remember exactly how long it took to deploy it for the first time, but I know it didn't take long to manage it to that point.

For this type of job, you need a team.

While the configuration part is easy, enrollment depends on the size.

If we're looking at 200 users, I believe one individual could do it, but for 300, 400, or 500 and up, it's always best to have a second eye and at least two people to get a second opinion on everything to ensure nothing is missed.

On a scale from 1 to 10, I would give them a 9 or 10.

The pricing differs from InTune.

Ivanti Endpoint Manager charges a flat fee for the implementation and product purchase, followed by yearly maintenance, whereas InTune charges per license, with the license included with the intra ID and everything else.

If I were to compare Ivanti Endpoint Manager with anything else, the closest competitor is InTune.

Microsoft is doing a great job with InTune, improving all aspects, and where Ivanti Endpoint Manager was neck-and-neck with InTune two to three years ago, I believe InTune has implemented much of what they have, so I would say InTune is the top competitor.

If I were to pick between them, I would choose InTune.

I am just a customer with no partnerships with Ivanti.

I rate Ivanti Endpoint Manager 10 out of 10.

Currently, I am using Ivanti Endpoint Manager as a consultant, handling deployments and designing policies. If I am unable to fix or complete a task, I connect with the Ivanti vendors directly.

My usual use cases for Ivanti Endpoint Manager involve mainly working with the patching side of things, ensuring required custom settings are present in the agent, as well as agent configuration, device patching, and reporting. I design queries to get the right data that gives a picture of the compliance of the devices.

The most valuable features of Ivanti Endpoint Manager are its customization options for the agent, as you can customize patching cycle settings, maintenance windows, and reboot policies. Within a device group, all these settings can be customized based on the agents.

The user interface of Ivanti Endpoint Manager is very practical and easy to understand, providing comprehensive information without clutter. It is simple enough for me to conduct a knowledge session for teammates, and they quickly grasp where each option is located.

Regarding automated patch management, it allows me to download patches without manual intervention. Whenever a fresh list of patches is available on the server, I can schedule a task that automatically pulls all the new patches, but I prefer to manually control the deployment of these patches.

Reporting in Ivanti Endpoint Manager allows me to create LDAP-based queries, and once I have a bit of knowledge, I can build my queries to determine what version of Chrome is installed on how many devices. It provides CSV files that serve as raw data for building reports, and I can set it to automatically email reports on a weekly or monthly basis as per my schedule.

The area that could be improved within Ivanti Endpoint Manager is integration, particularly with tools such as Splunk or potentially ServiceNow. Although I have not worked with these integrations, I believe Ivanti could enhance its capabilities in this area.

I have been working with Ivanti Endpoint Manager technology since 2016, when it was called LANDesk Management Suite, an on-prem setup. Since then, Ivanti moved into cloud as a software as a service platform, so I have been working with it for about nine years.

Regarding stability and reliability, I have never seen the server go down or any functionality taken offline. It functions as if I am building my server in my own environment with Ivanti licenses connected to their database.

I rate the scalability of Ivanti Endpoint Manager around seven to eight because it offers options to manage the devices effectively, requiring only the addition of licenses. Ivanti's support is prompt; if I raise a ticket, they help me immediately with adding more devices or servers.

My interaction with Ivanti's technical support has been positive, especially when I needed assistance enabling the remote control functionality. They provided detailed information that helped me convince the security team to approve the necessary port openings, allowing me to enable remote control across all devices.

Positive

The initial setup and deployment of Ivanti Endpoint Manager require opening a significant number of ports, which can complicate things for the information security team when seeking approvals. If I can open all the necessary ports, it works incredibly well, allowing total control of all devices from one console.

I haven't had a chance to work on the integration of Ivanti Endpoint Manager so far; it appears to be standalone tooling. I'm not sure about its integration capabilities with other solutions because my exposure to projects requiring integration has been limited.

In terms of pricing and licensing, I find that Ivanti Endpoint Manager is quite economical considering the service and customization options it offers. The in-depth granular reporting and understanding of the system it provides make it difficult to consider replacing it with other tools.

My customers now prefer Ivanti Endpoint Manager in the cloud, where Ivanti provides it as software as a service. The patches are pulled from their database, and the server can be set up in an on-premise environment, such as a VM setup on Azure, with connectivity established easily.

On a scale of 1-10, I rate Ivanti Endpoint Manager a 9.5.

My use cases for the Ivanti Endpoint Manager include software distribution, Windows updates, remote control, inventory reporting, imaging, and software packaging.

The most valuable feature of the Ivanti Endpoint Manager is the Windows update patching.

The Ivanti Endpoint Manager allows us to perform rollouts, starting small with a group of devices and expanding to a larger set of devices. It provides the ability to download updates while pinpointing which updates we need and don't need.

Ivanti can improve the product by making it independent of Microsoft Active Directory because we have some sites where we don't need devices on Active Directory, but we still must have them there to utilize many Ivanti features, such as assigning users to devices to manage.

For larger environments such as ours, the pricing for the Ivanti Endpoint Manager should be more competitive considering how much we pay every year, making it a constant challenge to get the product and license renewed.

I have been using the Ivanti Endpoint Manager for approximately seven years in my career.

The initial deployment of the Ivanti Endpoint Manager took us a couple of months due to the number of devices we have, but we didn't encounter any major problems.

The agent installation itself takes approximately 15 minutes, but the complete deployment took about four months because of our large device count.

We experience problems with lagging sometimes. Due to the large number of devices in our environment, when we load the console for the first time, it takes a while to update the database.

The scalability of the Ivanti Endpoint Manager is straightforward.

I have contacted their technical support.

Their technical support is generally good in terms of quality and speed. However, in some situations, the technicians could provide better assistance instead of simply sharing links to knowledge articles. They could demonstrate more understanding about the situation or reasons for support requests.

Positive

I have tried using alternative products.

The agent installation itself takes approximately 15 minutes, but the complete deployment took about four months due to our large number of devices.

The deployment of the Ivanti Endpoint Manager was handled solely by me. Many of our sites are remote, which made coordinating timing challenging.

We have used Microsoft InTune, which offers better pricing, and TeamViewer for environments where we only need remote access to devices.

The closest alternative to the Ivanti Endpoint Manager for us is InTune. We evaluated IBM BigFix, but its installation complexity is excessive compared to Ivanti, while Microsoft is extremely straightforward.

The overall rating for this solution is 9 out of 10.

We are using Ivanti Endpoint Manager for patch management in my current organization. In my previous organizations, I was using Ivanti Endpoint Manager for software distribution, patch management, software license management, and many other features. In the current company, we are using it specifically for workstation patching.

The user-friendly interface of Ivanti Endpoint Manager contributes to minimizing the administrative overhead for me because it's a one-time task; I configured it once in the beginning, and it's very easy to handle. There is no impact on users; the reboot policy prompts users to save their work before rebooting the device forcefully, giving them a time frame to prepare.

Patch management is one of the greatest features of Ivanti Endpoint Manager because we have Rollout Projects in the Management Console that we are using for the patching process. It's an automation kind of thing; once you configure the Rollout Project, it continues from the next month onwards by itself. You do not have to worry about it—no manual tasks are needed after the initial configuration based on the criteria.

The reporting tools help me identify potential security threats by allowing me to extract a report on how many patches are missing or installed on a particular system. I create queries that collect all patches information and select vulnerabilities detected, which I then compare to identify systems with missing updates.

I do not think there is much to improve in Ivanti Endpoint Manager; however, they should create instructional videos for every feature such as software management and patch management to help beginners who are new to Ivanti Endpoint Manager.

I have been working with Ivanti Endpoint Manager since 2012, which amounts to more than 13 years of experience.

Ivanti Endpoint Manager is a reliable and stable product; organizations should consider using it for long-term processes and they will benefit from it.

Ivanti Endpoint Manager is indeed scalable; from what I have learned, it can accommodate growth effectively.

Besides Ivanti Endpoint Manager, I have worked with Qualys for vulnerability management, which we integrated a few months back for patch management. Qualys is a nice tool that helps us identify various threats and vulnerabilities.

The initial setup of Ivanti Endpoint Manager is not complex at all; you just need the setup file and to click through some options. It is very easy to configure or set up Ivanti Endpoint Manager.

Ivanti Endpoint Manager is doing very well in my organization; it competes effectively against older companies such as Microsoft. I see potential in Ivanti Endpoint Manager, especially since they are releasing many new products, including ITSM and Xtraction as part of Ivanti.

We do not utilize automated software distribution in Ivanti Endpoint Manager; I need to check because we have to schedule it manually. Once we have the package, we create a scheduled task, and that's how we deliver it. Any software package is scheduled using the package distribution and the scheduled task, and we deliver it to the required users or systems.

I do not use Ivanti Endpoint Manager's integration with other Ivanti solutions; I haven't had a chance to be involved in projects that required it.

I am very familiar with Ivanti Endpoint Manager; I have not had much experience with Microsoft products, but I find Ivanti Endpoint Manager to be reliable compared to what I know about other tools. Every tool has its pros and cons, but I think Ivanti Endpoint Manager's pros outweigh the cons.

On a scale of one to ten, I rate Ivanti Endpoint Manager an eight out of ten.

My main use case for Ivanti Endpoint Manager is managing mobile devices, including iOS and Android, deploying apps on mobile devices, managing compliance and security configuration, deploying certificates to devices, and creating OEM configurations, making it my MDM management solution.

A specific example of how I use Ivanti Endpoint Manager includes deploying line of business apps, third-party apps, certificates, Wi-Fi profiles, SCEP certificates, and wallpapers to the devices as I utilize it as an MDM solution.

My team interacts with Ivanti Endpoint Manager by creating configuration profiles, compliance profiles, rolling out Apple devices, implementing Zero-Touch, creating Shared iPads, and setting up Kiosk devices.

Ivanti Endpoint Manager offers excellent features, working well with both iOS and Android, positioning itself as a market leader and providing a range of deployment features, including quick deployment of business apps, configuration profiles, compliance profiles, password policies, iOS and Android upgrades, and jailbreak device detection.

The speed at which Ivanti Endpoint Manager deploys apps and configurations significantly impacts my daily operations, saving my IT team time and allowing them to utilize their effort in other activities. Deploying an app to 100 devices only requires pushing it through Ivanti Endpoint Manager, and once the device is online, it auto-installs the configuration item.

Ivanti Endpoint Manager provides features for Apple DEP devices including Apple auto enrollment and integrates well with Zero-Touch for Android, allowing new devices to be preconfigured for out-of-box experiences and OS level security to be controlled, enhancing my management capabilities.

Ivanti Endpoint Manager has positively impacted my organization as it is my main tool for managing mobile devices, reducing IT effort, ensuring devices needing updates receive the proper updates, and blacklisting non-compliant devices. It deploys configuration items including Wi-Fi profiles, SCEP profiles, root certificates, app-related profiles, and DLP policies to safeguard my infrastructure from malicious access.

I have seen a reduction in time spent on device management because Ivanti Endpoint Manager automates small tasks and supports scripts, saving my IT employees time and effort compared to manual management.

Ivanti Endpoint Manager can improve support for Mac and Windows devices, as it currently excels with iOS and Android. Additionally, better integration with M365 solutions, such as Teams, SharePoint, OneDrive, and Office apps, would be a very useful feature.

While Ivanti Endpoint Manager supports Mac and Windows, it does not match the capabilities of JAMF. Focusing on these areas will help it become a more complete MDM management solution.

I have been using Ivanti Endpoint Manager for the last seven years.

Ivanti Endpoint Manager is stable in my experience as a Linux product. Since I use it on-premises, I can add resources based on my requirements.

Ivanti Endpoint Manager is scalable for my organization. I can easily add resources such as CPU, memory, and RAM as needed when I power off the server.

Customer support for Ivanti Endpoint Manager is quite good, with comprehensive documentation and ticket support. If I cannot find a solution, support engineers will join calls to help fix issues.

I have not used a different solution, as I have been using Ivanti Endpoint Manager, which was previously known as MobileIron.

The initial setup and implementation process for Ivanti Endpoint Manager is quite easy as it is a Linux-based appliance. I only needed to follow the vendor documentation, which is good, and to purchase a license for use, with customer support readily available to assist with any issues.

I handle updates and maintenance for Ivanti Endpoint Manager straightforwardly by using Ivanti Endpoint Manager portal, where my Ivanti VSP and cores point to the update server for deployment when updates are available.

I have seen a return on investment with Ivanti Endpoint Manager, as users now spend less time configuring devices and can access emails and SharePoint sites on mobile devices, allowing them to check their mails while traveling and saving time and increasing ease of use.

My experience with pricing, setup cost, and licensing shows that it is competitive. I need to purchase software, a license, and usage licenses on a per-user or per-device basis, but it competes well with other vendors.

I did not evaluate other options before choosing Ivanti Endpoint Manager, as it was the market leader.

Ivanti Endpoint Manager handles security and compliance requirements by checking for jailbroken or rooted devices, password complexity, pattern lock usage, and evaluating compliance scores to determine compliant or non-compliant devices.

I find that the reporting in Ivanti Endpoint Manager is quite good, as my infrastructure is segregated, allowing me to generate reports using all attributes available, which can also be used later with Power BI for better visibility.

The integration with other tools in my environment is quite smooth, as it is an API-based product, providing an easy way to integrate with my monitoring tool.

Ivanti Endpoint Manager has an intuitive user interface that is easy to navigate, as the names of applications and functionalities are clear and the documentation is good, which does not cause any issues with UI navigation.

I would advise others looking into using Ivanti Endpoint Manager that it is a market leader for mobile device management solutions, with less vulnerability as a Linux-based product, requiring no separate database servers. If you seek stability in your mobile device management solution, Ivanti Endpoint Manager is a robust choice. I would rate this product a 9 out of 10.

We used Ivanti Endpoint Manager for application packaging, deployment, patching, asset inventory, asset management, and software update deployment.

The best feature is creating applications .exe and .msi and deploying them through the environment. It's easy to deploy on the targeted collections. We can troubleshoot easily, find out the compliance report, and work on patch failures. The interface is good and easy to understand.

With patch management, we deploy patches across the environment and get the compliance report. We get device details and application version details. We start working on the EOL (end-of-life) software and remove those from the backend. We use this tool with PowerShell scripting to remove software in bulk. With patching, we make devices compliant and keep our environment up to date.

It's very easy to remote into devices with Ivanti Endpoint Manager. They have a remote agent tool which is installed with the Ivanti client. Administrators can perform admin-related troubleshooting, work on patch failures, install software, and remove software.

The rollout project feature allows monthly patches to go directly to production. We create automatic rollout projects where whenever Microsoft releases patches or product updates, it tests them, makes a package, and rolls out to production automatically.

The license cost is lower than other products in the market. The interface is intuitive for administrators to understand patching, package creation, deployment, troubleshooting, remote access, and PowerShell scripting automation. It integrates with other products such as Power BI for reporting and can be configured with SQL. It helps organizations stay up-to-date and compliant with Infosec requirements.

Improvements could be made in creating collections and enhancing patch packaging. Microsoft uses detection rules, supersedence rules, and dependencies in their products. With detection methods, you can determine if software deployment reaches the endpoint. In Ivanti Endpoint Manager, when deploying a package, it shows success or failure but doesn't show specific issues or detect if another version of the application is already available. This can be done through scripting, but it would be better to have built-in rules for detecting older versions of software.

I have been using Ivanti Endpoint Manager for two and a half years.

I have had many calls and generated community tickets with Ivanti community. We had an issue with the registry part where Windows patch was failing regularly. They helped us resolve it. The support team was calm, cool, and very supportive in a professional manner.

Neutral

In my previous organization, users were using Microsoft products but switched to Ivanti Endpoint Manager due to its cost-effectiveness.

For manual tasks, PowerShell scripting can cover bulk requirements such as deploying or removing software from endpoint devices that are vulnerable.

I suggest trying it for a few management tasks to observe how it performs. If it proves beneficial, organizations can expand its use.

On a scale of 1-10, I rate Ivanti Endpoint Manager a 6 out of 10.

Our use cases leverage Ivanti Endpoint Manager for patch management, asset management, software deployment, and script execution across systems. We operate in diverse and segmented environments, utilizing asset control mechanisms to organize and manage assets effectively while capturing all relevant data. By deploying the Ivanti agent, we enable automated group segmentation, allowing systems to be dynamically assigned to appropriate groups based on predefined criteria. This agent-based approach facilitates seamless discovery and classification, enhancing operational efficiency. Additionally, we implement IP range-based segregation, particularly in environments with multiple VLANs. This allows us to configure deployments and asset grouping in alignment with VLAN structures, ensuring precise control and visibility across the network landscape.We primarily leverage Ivanti Endpoint Manager in agentless mode, which significantly reduces the need for deploying agents across endpoints, streamlining management and minimizing overhead.

It helps us keep everything up to date with patches, track our devices, push out software, and run scripts—all from one place.Once we install the agent, it automatically figures out which group a device belongs to, which saves us a lot of time

One of the best things about Ivanti Endpoint Manager is that the agents it uses are very lightweight, so they don’t slow down our systems. It also gives us great visibility during deployments—we can see exactly what’s happening and collect all the necessary data. The system shows us codes that help us understand what’s going on in each environment.

For example, every month we roll out patches, and monitoring is a big part of that. We can check the status of each machine without having to log into them individually. It also helps us troubleshoot issues by showing the exact error codes, which makes fixing problems much easier. Ivanti also lets us organize our servers and devices in a way that makes sense for us—by operating system, group, or IP address. This helps us manage everything more efficiently. Patching is one of our main tasks, and Ivanti gives us detailed information about each patch. Another great part is the training and support Ivanti offers. The training helps us learn how to use all the features, and the support team is always there when we need help. Since we work in a large environment, Ivanti is a great fit—it’s built to handle big setups and makes it easy to group and manage everything. We even use it to deploy our own in-house apps, not just third-party software.

I believe Ivanti Endpoint Manager has room for improvement in a few areas. One key area is reporting—both the executive-level reports and deployment reports could be more refined and user-friendly. Better customization and clarity in these reports would make it easier,but we’ve noticed that the frequent release of new versions. While updates are important, they can sometimes disrupt workflows or require additional effort to stay current, especially in large environments.

I have been using Ivanti Endpoint Manager for more than nine years.

The solution is definitely stable. Based on my experience at our company, which has been using Ivanti Endpoint Manager for over 10 years, I’ve never felt the need to change it due to performance issues or any major problems. It has consistently worked well for us without causing trouble.

Ivanti Endpoint Manager deserves a perfect score for scalability.

Ivanti’s support plays a key role in our operations. Whenever we encounter an issue, we coordinate directly with their team, and they consistently provide a resolution within 24 hours.

Positive

There are many patch management tools available in the market today. I’ve had hands-on experience with tools like BigFix and Qualys, both of which also offer strong patch management capabilities. When comparing these tools, I would rate Ivanti Endpoint Manager 9 out of 10. It performs well overall, especially in large environments, and offers a good balance of features; however, there’s still room for improvement in areas such as reporting and version management.

The initial setup and deployment of Ivanti Endpoint Manager can be a bit complex, especially in large-scale environments. However, for mid-sized and small organizations, the setup process is much more straightforward. We’ve deployed Ivanti across multiple global locations, and while pushing patches, we use separate consoles for different regions. This setup works, but it could be improved—especially when planning and coordinating patch deployments across multiple sites.

We implemented Ivanti Endpoint Manager using our in-house team, with support from Ivanti’s technical team when needed. Our internal team handled the majority of the setup and deployment, and Ivanti provided guidance and assistance during more complex stages. The collaboration worked well overall. Ivanti’s support team was knowledgeable and responsive, helping us address specific challenges during the rollout.

While we haven’t calculated a precise ROI in numbers, the return on investment from using Ivanti Endpoint Manager is clear in terms of time saved, improved efficiency, and reduced risk

I’m not directly involved in the pricing or licensing side of things, so I can’t speak to the exact costs. However, from a technical and operational perspective, Ivanti Endpoint Manager has proven to be a valuable tool in our environment.

Yes, before choosing Ivanti Endpoint Manager, we did evaluate BigFix, Qualys Microsoft SCCM and ManageEngine Patch Manager Plus

The reason I would rate Ivanti Endpoint Manager an eight out of ten is that, in some cases, we’ve experienced delays in getting issues resolved. While we do coordinate with their support agents, the resolution process can take time, and the training provided could be more precise to help speed things up.

That said, I would recommend this product to others.

One feature I appreciate in Ivanti is called bundling. In other tools, such as BigFix or Qualys, this is referred to as a baseline. What sets Ivanti apart is how easy it is to customize these bundles. For deploying in-house applications, Ivanti is one of the best solutions we’ve used. Other tools often make it difficult to handle on-premise deployments, but with Ivanti, the process is smooth and straightforward.

If you need to customize deployments, Ivanti makes it easy with minimal complexity, which is a big advantage in large or dynamic environments.

We are using Ivanti Endpoint Manager primarily for endpoint management and remote control. However, we need to deploy a new solution by the end of this year due to its limitations. We are also aiming to replace all functionalities provided by Ivanti Endpoint Manager, such as software deployment and endpoint management, with other platforms.

Ivanti Endpoint Manager has served us well over the years, supporting operating systems from Windows XP to Windows 10. It provided essential features needed for our operations, including endpoint management and remote control. The licensing was quite affordable when it was an on-premises model. Despite being an older tool, it met our requirements until recent advancements.

Ivanti Endpoint Manager is not user-friendly and feels outdated, which affects usability. It lacks features like easy connection to remote computers and has a complicated software deployment process. Communication with their technical support team can be challenging due to language barriers.

We have been using Ivanti Endpoint Manager for approximately 15 years, as it was implemented before my time with the company.

Our experience with Ivanti Endpoint Manager's technical support has been mostly fine. Although they manage to resolve our issues, communication can be difficult due to language differences, particularly when support is provided by teams based in India.

Positive

The pricing for Ivanti Endpoint Manager was economical with the on-premises licensing model. However, the transition to a Software-as-a-Service model led to significant price increases without corresponding enhancements in the platform.

We have been evaluating other solutions like Microsoft Intune, which we have already used for other functionalities like software deployment and endpoint management. However, Microsoft's Intune remote control cost is prohibitive, and it lacks certain features we require, such as unattended access.

I would not recommend Ivanti Endpoint Manager to others, especially if they are migrating from an older setup. It is more beneficial to start with a different platform due to the complexities and outdated nature of the current Ivanti Endpoint Manager system. I rate the overall solution as 7 and a half.

My main use case for Ivanti Endpoint Manager is not day-to-day, but we do patch management and asset management for laptops and PCs.

When I say asset management, I mean tracking hardware inventory and software deployment, depending on the software.

The best feature that Ivanti Endpoint Manager offers is remote desktop management, which allows viewing a user's screen. This feature stands out because we use it most often to do IT support.

Earlier versions of the on-prem server had HTML remote control that was phenomenal because I could type in the IP address of the device and connect without going through the management console, which helped our non-admin help desk people significantly.

It is disappointing that Ivanti has removed these features from the on-prem version to encourage migration to the cloud feature.

Ivanti Endpoint Manager has had a positive impact on my organization, but I cannot think of specific outcomes or improvements because everything Ivanti has done has been to reduce applications and features to force us to the cloud.

The changes have affected my team's workflow negatively. The newest update, 2024 SU3, removes the feature for a regular IT help desk role to have access to remote control a person's desktop.

I think Ivanti Endpoint Manager could be improved. If I could change or bring back anything, I would restore all the features they had in 2017 that they slowly reduced to force us to the cloud because all those features are available on their cloud product.

Restoring those features is the main priority, and it would be beneficial not to have the LANDESK admin role be the requirement for remote control desktop.

I have been using Ivanti Endpoint Manager for about 10 years.

Ivanti Endpoint Manager is stable in my experience, with no notable issues regarding downtime or reliability.

Ivanti Endpoint Manager's scalability is good, though this is because we have been steadily reducing the number of PCs in our domain.

The customer support with Ivanti Endpoint Manager is not something I experience directly because we reference a third-party vendor, NCSI, for our support before reaching out to Ivanti.

Neutral

I did not use a previous application before Ivanti Endpoint Manager.

I do not have any experience with pricing, setup cost, and licensing for Ivanti Endpoint Manager as that is managed at a level above mine.

I do not know if my organization evaluated other options before choosing Ivanti Endpoint Manager because they purchased it before I joined. It was actually called LANDESK when I started, and Ivanti later purchased LANDESK.

My advice to others considering Ivanti Endpoint Manager is that it is a great tool for asset management, but there are probably other tools that do the same thing with additional features, especially if you want to use the on-prem version.

My company has no business relationship with this vendor other than being a customer. I have not been offered any incentive or gift card for this review.

Sometimes the customer experience is more important than the company's bottom line, so I would encourage bringing back all the features that are being slowly removed for profit.

We use Mosyle for Mac management, Google Admin console for Chromebook management, and various software licensing applications for Adobe and Microsoft.

I am not interested in analyst insights about other solutions.

On a scale of 1-10, I rate Ivanti Endpoint Manager a 7.