IIS Reviews

We use the product for our web applications.

The product is easy to configure. It has a lot of good features.

The solution must improve the integration between its databases. It should also improve the definition of IP addresses and ports for connection.

I have been using the solution for more than ten years.

I rate the tool’s stability more than eight out of ten.

Compared to other web application services, IIS has better scalability. We have many different programs. A part of our customers use the solution.

The initial setup is a little complex. Even if we make a little mistake, the configuration still works well.

We need three networking personnel to maintain the product.

We pay a yearly licensing fee for the solution.

I look for network administration aspects in the product. A software person might have a different perspective. I did not configure the solution. My friends configured it. When my friends have a problem, I help them to solve it. IIS is related to software engineers and programmers. IIS is the best solution. Its services are better than other products. Overall, I rate the tool more than eight out of ten.

We primarily use the solution for application infrastructure.

The solution is easy to use.

The solution integrates well with most Microsoft products.

The solution doesn't integrate well with all Microsoft products. There are a few that actually don't integrate well with IIS.

If Microsoft IIS could work well with AppOptics or things like PHP, Python, and other custom languages that run on the webserver, it would be ideal. I think there are cases where people need to use Apache instead of IIS when IIS doesn't work well with other web languages.

I've been using the solution for ten years.

The solution is stable.

It's a good solution, but we don't use it on a large scale, so I'm not sure how well it scales. Currently, we have 250 users on it. Most are end-users, but we do have five admins on the solution as well.

We've never reached out to technical support. Mostly if we have issues, we look to community support for answers.

We also use Apache Web Server side by side with IIS.

The initial setup is very straightforward.

We handled the implementation ourselves.

We use the on-premises deployment model.

I'd recommend IIS for almost everything. I would suggest using use case scenarios.

I'd rate the solution eight out of ten.

IIS is useful for the deployment of web applications.

There aren't any particular features I found valuable since it is just used for deployment purposes.

Performance-wise, certain improvements in IIS are needed.

I have been using IIS for not more than a year now. I also sell IIS.

Its stability is good. People use it widely to host their on-premises applications, like, internal applications on IIS.

It is scalable if we include the application stack. IIS is not scalable. Its scalability is less. If we talk about its scalability with respect to the cloud, as we are seeing as of now, it's not that much scalable. We need to put some extra effort into making it scalable. Almost everyone who has a Windows server uses the solution for hosting their internal applications.

The solution's initial setup is a little complex, especially compared to what others provide. It is better than Apache.

If there are no issues, the solution's deployment can be done in an hour or two maximum. Two people are required for the deployment and maintenance of the solution. Also, it depends on the size of the infrastructure and the servers and everything. The requirement for the infrastructure is not that big. So two people are more than enough. One is the administrator, and the other one is the developer. But if there is a lot of development, then the people required for deployment and maintenance would depend on the size of the application.

The cost for IIS is already included in Windows services. We don't have to pay anything extra. We only pay for the Windows server.

I would tell those planning to use the solution depending on their requirement. If the requirement is for on-premises and in an isolated environment, then people install it on the server and start using it. But if the requirement is to go on the cloud and make the website public, then it is preferable to opt for the cloud.

I rate the overall solution an eight out of ten.

We use IIS to deploy some of Opentext applications that we need to deploy.

The most valuable feature of IIS is it does not consume a lot of resources. It does not consume a lot of resources, such as memory.

IIS could improve by having some features related to URL rewrite, ARR (Application Request Routing) and HTTPS certificate generation.

I have been using IIS for approximately five years.

IIS is highly stable.

The scalability of IIS is good. It can be scaled easily using Cluster.

We have less than five people using the solution in my company.

I did not use the support from IIS.

We purchased a Microsoft Windows license and the license for IIS came in the package.

We are using this solution because it was recommended for us to use. It is a stable solution.

My advice to others is this is a simple-to-use solution and you can find items with ease. Microsoft has good support for its solutions. You can find the information you need from around the world because Microsoft solutions are widely used. If there are problems you can fix them easily from the support online, such as in forums.

I rate IIS a nine out of ten.

I use Windows Server IIS to publish our site for my Citrix applications.

I am using an older version of Windows Server IIS and the general management and navigation to get something done is not as straightforward as I hope it to be. The interface could be improved.

I have used Windows Server IIS for approximately three years.

Windows Server IIS is stable.

We have over 100 people using this solution in my organization.

I have contacted the support from Microsoft a few times. Depending on the issue we are having, the support in some cases takes a bit longer to get our point across for them to understand and then to receive a resolution that day.

I rate the support from Microsoft a four out of five.

I have not used another solution previously.

The initial setup of Windows Server IIS is complex. If you already have some experience it can be simple.

We have an external service provider that helps with the maintenance and monitoring of Windows Server IIS. We have internal personnel, but for anything that we can't figure out by ourselves, then we contact the service provider and external help desk.

The price of Windows Server IIS is expensive. They have a large user base, and they charge a little bit too much.

I rate Windows Server IIS an eight out of ten.

If I was using the newer version of Windows Server IIS I would rate it higher.

We use the solution for our customer's web applications. 

IIS needs to improve its security. Its support needs to be faster and clear. The tool's licensing could be cheaper as well. 

I have been using the IIS for 15-20 years. 

My company has 200 users for IIS. 

The tool's setup is simple. 

We did not use a consultant for the product's setup. 

IIS is expensive. 

I would rate IIS a seven out of ten. 

I am working as a Software Project Manager for a software company in their Pharma Services Division and using IIS on Microsoft Windows Server for local deployment of our pharma related .NET application. It is built in C# and used for uploading and validation of pharma-related information in a locally deployed application by a team of data associates and data analysts.

The information is then transported after validation to the web database on Azure from the local database using an internally-developed desktop application.

IIS is the best option on Microsoft Windows Server for hosting and deployment of .NET applications, either in a local environment or on the web.

The graphical user-interface of IIS is very easy to use and helpful in the effective management of applications.

It comes with Microsoft Windows Server by default, which makes it easier to get started for hosting .NET applications immediately, with no hassles of installation and setup of any other web server.

The integration is the best, being a Microsoft .NET application hosted on Microsoft IIS running on Microsoft Windows Server with Microsoft Database Connectors and Drivers.

IIS has a very simple and user-friendly interface, which helps a lot in effective and efficient management. The simplicity of the interface helps the newbies to learn to manage it fast.

IIS needs immediate improvements, especially in the area of security management.

Having no support for other than a Microsoft environment and programming languages limits the usage of IIS in many cases.

The capability to host and deploy open-source applications would definitely add more value to it. There should be plugins to enable it to support open-source programming languages.

It also limits us in the choice of operating systems.

IIS should be enhanced in terms of its capabilities for monitoring and debugging.

I have been using IIS on Microsoft Windows Server for more than five years.

It is very stable in its operations, hence requires minimum efforts in performance management. It is easy to keep it alive and maintain server uptime.

We have found that customer support has always been good for cases that we have raised. It has a huge user community.

I have experience with Apache Web Server, WAMP, and XAMPP.

Being a part of Microsoft Windows Server, it is very easy to set up and manage IIS.

I tried Apache Web Server before implementing IIS.

We use IIS for hosting service, user authentication, and Active Directory integration.

The product could be more compatible with Linux and macOS, particularly when applying user configuration policies. We have to download and configure other player controllers for the same.

The product is stable. We do not encounter any issues from IIS after configuration.

We have 80-90 IIS users in our organization. We might increase the usage in the future.

The product is straightforward to configure. However, there could be a component to add a feature for third-party system integration.

I recommend IIS to others and rate it a ten out of ten. I cannot apply any policies from Windows server to Linux and Mac machines.