Installation isn't simple, but it's doable. You need to read the documentation first.

Creating the template isn't simple, and you need to restart a lot of services to get the new templates ready for use. It needs to be restarted for the new changes to take effect.

My company wants to deploy and use the product on an on-premises model.

Three to four administrators are required to take care of the product.

The complexity of the initial setup depends on the hierarchy. If you define a quite complex hierarchy, then the deployment is complex. I find the initial setup straightforward. If you know what to do, the initial setup is straightforward.

It takes three days to implement the infrastructure. After that, it's a matter of operating the service.

For anybody who has the training, this is an easy solution to set up.

When I first deployed this solution, it took me about five days. The reason it took this length of time is that I was integrating with WSUS, and it is a separate server so there are a lot of patches that need to be done.

In other cases, the initial setup is more straightforward.

It is complex to deploy.

The initial setup is straightforward, and you can deploy this solution within three hours.

This solution has been difficult to deploy in some cases. The length of time required depends on the customer's requirements and needs. If there are a lot of customized workflows then it is going to take longer.

I would say that the average time to deploy is about two weeks.

The initial setup is quite complex. It requires someone with advanced knowledge to install it.

The initial setup was pretty simple. The deployment part did not take long at all.  

From the infrastructure perspective, the setup is not a big deal. It is really simple. But from the operation perspective, you need to define the SLA (Service Level Agreement) and you need to define how you use the chain management copy process. You need to define your own clauses and many things that can take six months or one year. It depends on your situation. If you need to customize it, the customizing takes time. 

Many of the things are out of the box and they do not need a lot of customization. On the other hand, too much customization is not the way it should go. It may cause problems later. It should be as straightforward as possible for deployment and not add complexity just for complexity's sake. A little development for a few things, especially for the integration, should be what you want to shoot for.

The initial setup is very nice. But after 2012 they changed the pattern of the solution because they are integrating it with the cloud. It takes more time to make a change. Because it's as if to say the change occurs every two years. I'm talking about people. People that manage it. I teach them about every two years to do it. When I started with it, I went for training, after the training, it was easy for me. So I cannot say that it's something somebody cannot easily learn from scratch from different services. Because all the material is online even video training is there. It is pretty easy to set up if you have the right training. It took me five days to set up. This included integrating WSCS with ACCM.

The initial setup was a bit complex. It wasn't that user-friendly. My team had to play around with it a bit.

The initial setup is not very complex, but it requires some basic knowledge and skills to understand how to install the SQL server. It's not straightforward, either. It's something in the middle. However, it requires some technical know-how. That said, it is easy to learn how to install it. It's not like SCCM for example. System Center Configuration Manager is much more complicated. There are others as well that are not easy to install. This solution is just much simpler to handle in comparison.

In terms of deployment, the basic installation could take one day just to install the servers without any configuration or special customization taken into account. It might take one to two days, or, more likely, one and a half days to install the basic servers and to prepare the infrastructure for the program. 

In order to configure the product and make the customizations based on the customer needs or requirements, it could take as long as three or four months. That's on average. It could also take up to six or eight months for a full deployment, but it depends on the client.

You only need one person to deploy the solution. Any ticketing system, any ITSM tool, doesn't require many human resources in order to complete the project. Products like ServiceNow might require more people. One for implementation, and one for the development, for example. In Service Manager, we might need one more person who has some SQL reporting skills who can help us create a custom report. For a normal installation, however, one consultant is enough.

You also only need one person to maintain it. Sometimes after doing the project, after completing the project via one consultant, we assign another consultant for the maintenance. However, the maintenance itself is quite minimal.

The installation was straightforward.

We followed Microsoft's advice, and it was straightforward.

The initial setup isn't too difficult. It's moderate in terms of difficulty. It takes a bit of work to personalize it for our purposes.

The product's setup is easy. I would rate the solution's setup a seven out of ten. The product's deployment took three days to complete.  

I did not install this software on the server, but my understanding is that it was straightforward. On the Help Desk side, the setup is not complex.

It took us less than one month to deploy.