IIS Review

A stable solution for our customer's websites or internal applications

What is our primary use case?

We are a system integrator and this is one of the solutions that we assist our customers with. Our customers are primarily government departments, agencies, and ministries. These organizations are not very comfortable with using the cloud, so the majority of deployments are on-premises.

This solution is used for the customer's website or internal applications.

What needs improvement?

The areas of this solution that need improvement are monitoring, debugging, and troubleshooting. Having the monitoring as standard on the user interface would be nice.

There needs to be an easy way to escalate technical support issues beyond level one, quickly.

For how long have I used the solution?

I have been using this solution for more than fifteen years.

What do I think about the stability of the solution?

This is definitely a stable solution.

What do I think about the scalability of the solution?

Scalability is neither here nor there. You can say it's scalable, but it's an open-ended question because you have to consider whether you can host an application or product for country-wide use. I'd like to say no, but it can be used as part of a scalable infrastructure.

How are customer service and technical support?

We have contacted technical support, albeit rarely. I would rate them a six out of ten. It is not that they are slow to reply, but rather they are slow when it comes to understanding the problem. They often repeat the diagnostic steps that we have already performed.

The first level of support is not very good because by the time we speak with them, we are already past that point. This is because we do have experience and we can often solve the problems that are easy, or of medium-level difficulty. Consequently, if we have to open a support request then the problem is already difficult or complicated. We need to be able to escalate quickly. This is true in most cases, and the delay comes about because of the entry-level support people.

Which solution did I use previously and why did I switch?

In addition to this solution, we have worked with Apache Tomcat for Linux.

The choice of solution is dictated by the customer's requirements. If it is a Java application then we need to use Tomcat or Apache. If it's a .NET application in use then you need to use the IIS. It isn't a personal choice, or whether one is better than the other. Rather, it is about the application.

How was the initial setup?

The initial setup of this solution is very easy. The deployment takes between thirty minutes and two hours, maximum.

Usually, it will take one or two people to maintain this solution, including the website, if the whole infrastructure is Microsoft.

What about the implementation team?

We implement and deploy this solution for our customers. We have an internal technical team for this.

What other advice do I have?

This is a solution that I can recommend.

I would rate this solution an eight out of ten.

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More IIS reviews from users
...who work at a Comms Service Provider
...who compared it with Apache Web Server
Learn what your peers think about IIS. Get advice and tips from experienced pros sharing their opinions. Updated: April 2021.
475,291 professionals have used our research since 2012.
Add a Comment