The initial setup is a mix of complex and straightforward because it depends on which modules you are implementing for ITSM. There are a lot of complex workflows and SLAs around the workflow. We have to configure much more complex things than just Patch Management and Endpoint. For example, it might not take even two weeks to roll out APM for 10,000 assets, but it will take three months to roll out ITSM for 10,000 assets and an equal number of users. That's because the modules you were implementing require much more knowledge, and there are a lot of complexities and nitty-gritties inside the tool which need to be understood. ITSM skill sets are in demand because reaching an L3 certification is not easy. We have those certified skill sets. That's why we're able to roll out at a fast pace.

With standard documentation available, it's very clear for a certified resource to understand step-wise implementation. For every step, there is a "build and test" approach. It's a continuous integration. You follow this process, so you don't suddenly realize there are many issues at the end of setup. You have to keep testing each module and process as you roll out. It's not complex, but you need to know the product.

I don't know about the product's installation process since I don't operate as a support team for Ivanti.

The solution's installation depends on its customization. It is easy. If you need additional customization, you need to hire product special services or have someone who knows the system. 

It's fairly simple, but for the most part, the critical aspect is network configuration (multi-tenancy-wise). You need to whitelist specific IP addresses and ports, and this might necessitate assistance from your network administrator. Once that's in place, the rest of the process is straightforward, and you can proceed with the configuration steps while your network admin is on hand to assist you. The solution provides three deployment architecture options, but I specifically utilize the on-premises deployment.

If I recall correctly and according to my free time, the deployment of this tool took approximately a work day (eight hours). However, it's worth noting that this includes the time needed to read and follow the provided documentation, which contains specific steps and information.

The initial setup is easy. The deployment method depends on the customers’ requirements. We mostly have on-premise solutions. We have deployed cloud versions for a few customers. To deploy the tool, we need the infrastructure from the customer. The customer purchases the license from Ivanti. We directly install the application in their environment and activate the license. 

A person who knows the installation process can easily set up the solution. We can also do some customization out of the box. The installation and basic configuration take a couple of days if the infrastructure is ready.

We prefer on-premises solutions for security reasons, especially in the banking sector.

The initial setup was very complex. I think the skills transfer from the consultants or service providers is also problematic, as they can't show you everything. They will just give you what you need, so I believe that sometimes they were rather stingy with information. That is why I ended up going online trying to get more info.

Since I was already very familiar with HEAT it was not difficult setting up version 8.

The initial setup is very easy. 

The initial setup is not overly complex. It is pretty straightforward. 

It is quick to deploy. It would likely take an hour to a couple of hours to have it up and running. It wouldn't take days. 

The deployment typically can be handled by one engineer. 

The initial setup is straightforward. The time it takes to deploy depends on the customization. Some customers need more customization than others. It could take anywhere between one and four weeks.