Our use case with Ivanti is not very radically different from Matrix42. The two are comparable and similar in nature, where we separate private and personal profiles from the corporate profile while focusing on aspects like data leak prevention, security measures, access control, and data wipeout in case of loss.
The best part about Ivanti and Matrix 42 is that they are low-code solution builders with drag-and-drop capabilities regarding service management. They help where you need to build a lot of workflows and processes aligned to all IT processes or businesses.
Ivanti users are comfortable with the solution because its UI is appealing.
One of the features that Ivanti could improve is patching for non-Windows settings, such as Linux and Ubuntu. We manage the patching through workarounds because it is not straightforward. I have seen that the world is primarily on Windows and less on other operating systems, but large organizations with about 30,000 employees and multiple kinds of business will have core applications on these other operating systems as well, and that's where we find Ivanti faces limitations.
I have been using the solution for over a decade.
The solution is very stable.
The solution is highly scalable. We have implemented it for one of the largest banks in India, with approximately 150,000 to 160,000 endpoints, and the system is working fine for them.
Whether there are 10,000 or 150,000 endpoints, the solution remains stable. By following the product guidelines and details provided by the OEM, one is unlikely to deliver an unstable solution.
Technical support has a support portal where we log the case, and there is a response and resolution time frame. The support is good.
It's not complex, but you need certified skills for setup to be easy. It is different for an L1 resource, who has a basic understanding of things and may not be a developer who deeply understands how to build up the solution, where that understanding is present with an L3 or L2 resource.
For maintenance, you need at least one skill set for each module. You would need one for UEM and one more for MDM, which is the ideal way to do it unless you have people who know the modules in and out. We have a larger team for IT service management because the demand for IT service management is high, but we can see that for other modules as well now.
The timeline for the ROI differs based on the organization's size, whether it is small, medium, or large, but you will see an ROI after about 18 to 24 months.
The licensing is based on assets for MDM or EM, where you need one license per asset. The license is annual, and it is not very expensive.
You have to understand whether it is with or without an agent, regardless of managed devices, unmanaged devices, and endpoint management. Ivanti operates with agent and agentless, which sometimes becomes challenging because some organizations don't want to install an agent on an endpoint because it might interfere with other applications inside the end device. That becomes a challenge at times, but most of the time, organizations understand that having the agent is much safer because the agent is a repository of all the security and any elements that go through the agent. We push patches and upgrades and control the device through the agent, which makes more sense.
Working with Ivanti will be difficult if you have a layman trying to learn and understand Ivanti. We have multiple projects with people exchanging or rotating skills across projects of different kinds. All of this is important. It's not a one-way situation where you do certain things in a certain way. You need a global experience to happen, so what we do is different. Depending on the customer, we keep rotating skills, so there is more exposure to complexities, with more environments of different types, and then they can manage them. When configuring and building workflow processes or certain other things, you need to understand the outcome and impact. You need a system integrator or partner with those skills and experience implementing solutions for different customers in similar environments. You can gradually pick up the skills.
You have to keep integrating people and getting them skilled and certified, which is also a requirement for OEM and partnerships. You graduate to a high level of partnership based on the number of qualified skill sets, including pre-sales, delivery, and QA. So when you have a larger team size to show to the OEM, your partnership is two notches higher than the others. You could then be a platinum or a super partner. You will remain in a lower category because you don't have the skill set, and then you will not be able to implement the solution for many customers whose requirements might be bigger and more complex.
If you have drag-and-drop capabilities, you have a platform that helps you easily configure and build work processes while aligning them to the business, which makes the tool more powerful and flexible. However, that does not always work in the market because each environment, customer, and business is different. You need to understand what aligns best and what you need to configure out of the box to align it with the system.
In India, the SAARC region, the presence of Ivanti is limited in this part of the world. So Ivanti needs to reach out more often where the solution's marketing could be improved. This part of the world is adopting many solutions now, and the market has many value trends. Unless they look at the region in a more focused way, they will chase the competition and not get ahead of it. There are, however, more adopters of Ivant compared to Matrix42.