IIS Reviews

We are using IIS got Active Directory and DNS.

We are using six core hardware from Dell to run the solution.

The most valuable feature of IIS is the database it provides.

IIS could improve by Microsoft Windows improving the update services. We would like to be able to update all systems that are connected. The WSA service has to be in good order to accomplish this.

I have been using IIS for approximately nine years.

The solution is highly stable.

IIS is scalable.

We have approximately 75 servers using the solution. We have plans to increase our usage.

I have not used the support from the vendor for IIS.

The initial setup of IIS is simple and can be done within one hour.

We are using the solution virtually and we did the deployment. We have two or three people who deploy the solution.

There is an annual license to use this solution and the price could be better.

I would recommend this solution to others.

I rate IIS a nine out of ten.

It allowed us to set up and use a Windows Server we had in place already to host our internal web page.

It is a lightweight web host that is easy to configure for simple webpages.

Finding different settings can be difficult if you don't know where to look.

Stability seems good.

We have not needed to scale out with it, as we use it for very lightweight things.

I have not needed to contact technical support.

I have tried other tools (such as Apache), and found that IIS is more stable and easier on the memory for low resource systems.

Initial setup is straightforward for a basic setup (e.g. one host hosting HTTP traffic), but can get more complicated the more features you want to add (e.g. Windows Authentication, HTTPs, web farm, etc.).

It is licensed with your Windows installation which makes it relatively cheap if you already have a Windows Server sitting around.

We also evaluated Apache, but found that IIS was easier to set up for what we wanted.

Give it a shot. The features are included for free with Windows, so test it out. If you are unhappy, it is easy to disable and switch to a different solution.

We use the solution to build web-based applications and platforms.

The solution is easy to use.

The solution's scalability needs improvement.

It is reasonably stable.

The solution's scalability could be better.

The solution's initial setup process is straightforward.

If you're looking for a scalable solution, look at alternatives other than IIS. But it serves the purpose if you're looking for a small to medium solution. I rate it an eight.

IIS is primarily used for hosting and managing web applications.

The performance of IIS could be improved. Occasionally, we encounter performance issues with IIS where it becomes unresponsive and requires a solution restart.

I have been using IIS for six years.

I give IIS a seven out of ten for stability.

IIS is scalable.

The initial setup is straightforward.

The licensing cost is dependent on the usage.

I give IIS an eight out of ten.

We have around 15,000 people using IIS in the organization.

We require around three people for IIS maintenance.

I recommend IIS to others.

The solution's black box is not fast. 

I would rate the solution's stability a six out of ten. 

The product is scalable. 

The tool's setup is straightforward. 

The product's price is not high. 

I would rate the solution a five out of ten. 

The tool shows us the operating systems where our servers and applications are running. 

There is an issue with the network. The tool's price is also high. 

I am using the tool for one year. 

I would rate the tool's stability a ten out of ten. 

The solution is fully scalable. We have around 10-20 users for the solution. 

The solution's setup is straightforward. The deployment took around two to three weeks to complete.  

The tool's deployment can be done in-house. 

The tool's pricing is on a yearly basis. 

I would rate the product a nine out of ten. 

I am using IIS in our organization to manage the flow of the Active Directory.

The solution can be deployed on-premise and on the cloud.

The solution is highly reliable.

The solution is slow and could have better performance.

I used IIS within the last 12 months.

I rate the stability of IIS a six out of ten.

The solution is scalable.

The initial setup of IIS is easy.

I am able to deploy the solution myself.

There is a license needed for the solution.

I do not like the solution but I have no choice but to use it. I prefer open-source solutions, such as Linux.

I rate IIS a five out of ten. 

We have a GIS solution from ESRI, ArcGIS Web Adaptor, and it is installed on top of IIS. It's part of ArcGIS Enterprise solution.

The graphical user interface makes it easy for users to configure the sites. 

This solution needs to be easier for cases where you want to have an IIS cluster. If you have several IIS solutions running, it is not clear on how to make them communicate to each other. Normally, IIS Web Server run independently on each server. To have "IIS cluster", currently you need to have a network load balancer (NLB) appliance running in front of them. We use NLB to distribute the load and have high-availability of IIS Web Server.

This solution is stable. However, because of the way IIS interacts with the application pool, it is possible that another application running in different application pool, can have an impact to other application pool. Theoretically, each application pool will have independent process and should not conflicting between each other.

This is something that we are looking into because we want to have IIS Web Server that can communicate between each other. So far, we cannot find this options inside it, anywhere on the menu.

In our office, we only have few people who use this solution and we don't have a plans to increase its usage. It is for internal publishing only.

But for our client, we implement this solution in production environment and so far, no critical issue happened to run IIS Web Server on it.

We have not been in contact with technical support. So far, we have been able to handle all issues.

The initial setup of this solution is simple. Even if you aren't familiar with it, it is not complex. If you are installing it inside Windows Server, it will take less than half an hour to deploy. In most cases, it can be done in fifteen minutes.

This solution comes included with Windows Server.

My advice for anybody who is considering this solution is to go ahead with it. This is a mature product that is suitable for production environment. It competes with the Linux-based web server, which has more features. However, Microsoft is becoming more friendly with the open-source community, so hopefully they will implement more advanced features inside IIS.

It seems to me that Microsoft has been evolving the product with one of the main goals to be ease of use. However, I think that they need to focus on handling the biggest load. 

I would rate this solution a seven out of ten.