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.