Ivanti Endpoint Manager Reviews

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.

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.

I am implementing the tool at the moment. In my company, we recently had the first onboarding training for the tool. In the upcoming week, we start with the first ten machines.

The software associated with Ivanti Endpoint Manager is running in our company right now, but it is not productive because we have not onboarded its machines. In our company, we have the machines ready for the PoC phase, and I see that they work well enough. We are planning to move the Machines used in the PoC phase once we onboard the real productive machines.

The tool is for managing the clients, patching them, and for remote access control in case there is a need. We also block USB devices and everything else that is related to movable storage, like CD drives or DVD drives, and can only be opened if you have permission in an Active Directory group. Additionally, we also need images from machines because we sometimes have machine computers related to operating machines in our production, and those machines are the ones we cannot change or set up from scratch. We need some machines for the backup, and it is an area that can be managed by Ivanti Endpoint Manager.

I used Ivanti Endpoint Manager because I had one of their other tools in my old company, which is a DSM. DSM was used for my old environment, which I was responsible for, and I was really satisfied with Ivanti. Ivanti later on decided not to sell DSM anymore and stopped supporting it. Ivanti then offered people a tool named LANDESK. Ivanti Endpoint Manager is a tool we are bringing in place in our current company, and it has a similar functionality to DSM, a reason why my company decided to go for it. We also install machines from scratch with the tool. We can also patch third-party products, and it does not even have to be Microsoft always. Actually, we get a lot of freeing up resources because we can now manage Ivanti Endpoint Manager from a central point, which was not possible earlier, and we had to run to each machine.

The product's implementation process is in areas of concern where improvements are required.

Ivanti Endpoint Manager should create a list that users can use. There are some inclusions in the product which are not helpful for the person working with. Compared to Ivanti Endpoint Manager, there are areas in DSM where we have done way better since it offers something like a traffic light system where red means you have to do something. Yellow means you have to watch out. And green means you don't have to do anything.

I have experience with Ivanti Endpoint Manager.

There was no need to contact the product's technical support since we had a consultant who was very familiar with that software and who was the implementation person. We had a really good opportunity to contact him all the time, and he used to reach out to Ivanti's team if he didn't know something.

There are a lot of other tools in the market that are similar to Ivanti Endpoint Manager, but I believe that Ivanti is enough to cater to all use cases. What we can do with that system is everything we need, and this is what we can do with the system that includes everything we need, and it is all available in one tool. If we had used some other system, we would have needed more systems to fulfill our needs, which may include areas like USB blocking. With Ivanti in place, everything is included in one package.

The product's implementation phase was done remotely, and it is not working so well for me. I would like to have the people on-site, and it would work much better for me. We already could see when people from Ivanti, who are part of the implementing team from Ivanti, were on-site. We really had to move a lot as Ivanti's implementation team worked remotely and moved slowly. When people are on-site, the product's implementation phase goes fast. And this is one of my takeaways. Next time, I would just ask for on-site implementation since it would shorten the process a little bit.

My company smartly carried doubt about a PoC phase in the previous year, and by taking that into consideration, we created our environment, which turned out to be actually good. We could prove the use cases we were looking for from Ivanti, so we got the approval to buy the software from my company. The approval came in the month of February, and then right away, we bought the stuff. I think the tool's implementation phase started in June by creating relevant images and functionalities for the solution. Actually, we started last Tuesday by really looking into the use cases, and we have not had the chance to utilize everything. We will start onboarding this upcoming week.

The product saves time and money. I cannot provide you with an exact number associated with the savings that stem from the use of the solution since it can vary from person to person. It is impossible to describe how long it takes for people to patch their devices.

In terms of the tool's patch management capabilities, the product is used by my company to manage around 250 clients in a production environment with around two people in each.

Speaking about the use of AI in data analytics or device maintenance, I would say that my company's headquarters is in Sweden, and it is named Sandvik. Though it is not done yet and not completely decided, we plan to utilize Rapid7's system, which they have in place. Additionally, we would like to analyze the data in Splunk in the same way we used to do for the official office environment. For the OT environment, it's not really decided yet, but the idea is that we can do the same thing. Unfortunately, on some devices, it is not possible because Rapid7's system destroys data traffic, which is sometimes necessary for some machines. In the end, there is an idea to do it, but we don't do it with Ivanti's tools, so we will do it with some other IT tools.

I don't know how the product is in the production environment.

I would recommend the product to others.

I rate the tool an eight out of ten.

The solution is being used for Venture Rate. 

The GoSoft SIP and App SIP features are valuable. They protect our documents, especially financial documents. Ivanti is a great product from a security perspective.

Setting up the solution on-premises is difficult and needs improvement. 

I have been using Ivanti Endpoint Manager since 2018. 

Overall, I would rate the product an eight out of ten.