What is our primary use case?
We initially used Ivanti as an IT service management tool for instant problem change and request fulfillment. Now we use the solution in a range of different workflow scenarios across various corporate teams, including HR requests, corporate comms, building orders, and customer management.
What is most valuable?
Ivanti offers us the flexibility to transform it from purely an internal IT tool to something we can use across multiple departments. There's now a queue of departments waiting to onboard and get their processes built. The flexibility within the workflow is excellent.
What needs improvement?
You have limited ability to customize how Ivanti renders. It's a fairly strict design that doesn't offer you much freedom to alter the rigid, two-column layout on the screen. You can choose between one column or two, but that's about it. The presentation is probably the biggest weakness.
For how long have I used the solution?
We've been using the current setup since 2013, but I have worked on predecessors to the Ivanti product since 2007.
What do I think about the stability of the solution?
Ivanti is stable. We've been using it for many years. Now and then, we've had issues scaling up the servers, but nothing unexpected.
What do I think about the scalability of the solution?
Ivanti has proven to be highly scalable. However, we probably underestimated the demand when we brought in extra customers. We have about 23,000 users now.
How are customer service and support?
We've never had a huge issue with Ivanti technical support, but we don't need them often. Typically, we only have issues when upgrading, and we need their assistance to get that fixed beforehand. We don't rely on them for day-to-day support, which we primarily handle in-house.
Which solution did I use previously and why did I switch?
Each company had its own solution before we merged. We were all independent up to that point. My last company was with was using the Touchpaper solution, which became LANDesk, then Ivanti. We've continued with our tool, but there had to be a corporate standard, so the other companies were told to migrate on to the Ivanti platform.
How was the initial setup?
The initial deployment took over 18 months, including migration from eight solutions to this one. We were formed through the merger of eight or nine different bodies into a single organization. They all had different solutions.
The migration was pretty complex from that point of view, but getting the system up was straightforward. It just took us 18 months to onboard all the users from the different areas.
What about the implementation team?
The deployment was mostly in-house with some vendor support. We had LANDesk consultants at the time, but now they're Ivanti. We had a few days' support from them, but it was primarily in-house.
What other advice do I have?
I rate Ivanti Service Desk eight out of 10. If you can invest the development time, you'll get a lot out of this product. We've invested a lot of resources into this, and our usage has expanded dramatically.
You get out what you put in. If you want something you can just deploy and forget about, this is probably not suitable. You could do that with some other solutions. However, we've found this to be excellent in terms of the customization options.
Which deployment model are you using for this solution?
On-premises