IIS Reviews

We commonly use IIS to deploy most of the applications or network services internally or externally. We have to deploy different kinds of applications on IIS to access them externally. IIS makes these applications available to the internal or external end users.

The solution is very simple to use and easy to deploy. Once you deploy your application, it can reach the desired users. Since the solution already came together with the Windows servers, the deployment of our applications is clear and straightforward.

Most of the time, we procure perpetual licenses, and getting support is not easy for us. We didn't face many issues with IIS because of our expertise and the extensive experience we have using the Microsoft Windows service. In most cases, we figured out solutions by ourselves. Sometimes, we encounter difficult issues, and getting support from Microsoft to resolve those issues is not easy.

It would be good if IIS could add monitoring features.

I have been using IIS for a long time.

Once it's up and running, IIS is a stable solution.

I rate the solution a nine out of ten for stability.

IIS is a scalable solution. You can add different kinds of services or applications within IIS by separating or using different kinds of ports. More than 2,050 users might be using the solution in our organization.

I rate the solution a nine out of ten for scalability.

The solution’s initial setup is straightforward.

We implemented the solution through an in-house team. It takes around 15 minutes to deploy the solution.

Users can get a subscription-based license or a perpetual license for IIS.

We are hosting web-based applications using IIS. I would recommend IIS to people planning to deploy any kind of application. The solution requires additional protection or security because IIS can't be protected by itself. In terms of performance, the solution stands up perfectly to traffic spikes if your network backbone is good.

It's an operating system. If you have a machine to be used as a Microsoft Windows server, you have to deploy it directly. From the security aspect, Microsoft provides patches every three years. Then, you have to patch on the Windows server machine you have. The side effect of Microsoft is that it can be easily penetrated by any kind of cyber attack. So, it easily breaks down compared to other products.

Overall, I rate the solution a nine out of ten.

We use the platform for hosting Dynamics from our Microsoft Server.

The product is essential for hosting our ERP and managing our database, making it very important for the company.

The product's most valuable features are performance and security. 

The solution's pricing and stability need improvement. 

I have been using IIS for seven months. 

We have 57 IIS users in our organization. We use it regularly. I rate the platform's scalability a nine. 

Microsoft's support is responsive enough to our requirements.

The initial setup process is straightforward. The deployment of the Microsoft server was precise. We were able to install Windows efficiently.

We take help from a third-party vendor for product implementation. 

They offer a one-time payment model for the product license, and we pay annually for support.

I rate the pricing an eight out of ten. 

I would recommend the platform to others because of the integrated security features and the reliability of the server OS. 

Overall, I rate IIS a nine out of ten. 

We started using the solution for running web applications. We have custom applications that we develop for different customers. They are for case management, government statistics, and records. It depends on what we are running. We have run it for payment integrations in different types of platforms.

The product is easy to use. It might be easy because we've used it for long. When we use a product for a long time, it becomes second nature. We have never had any security breaches.

The user interface could be improved. We do not like it when the UI is changed often. Every time there is a change, we need to restart the server.

I have been using the solution for 15 to 20 years.

The product is completely stable.

We have not seen any issue with the scalability. We don't have very complex web services or web applications.

The setup is straightforward. We know how it works. The deployment can be done within hours. Many things depend on the applications. The solution can be deployed on the cloud and on-premise. We use the control panel of the console to deploy the product. The deployment process is similar for the cloud and on-premise versions. On the cloud, the only difference is that the server is not with us.

We deploy the tool in-house.

The return on investment is almost instantaneous on the cloud version. We use it when we need it. We do not pay anything upfront. There is no CapEx.

The product is cost-effective. We do not have to buy it. The tool is included with Windows. We license the Windows environment on a monthly basis. It is expensive. Sometimes, it is cheaper to run Linux than Windows.

I will recommend the tool to others. Whenever people ask us about web servers, we suggest that they use IIS. It is easy to use. We did not have many issues except when we occasionally had to restart the server. I encourage everyone to use the product. Our traffic is not as big. We have no issues with performance. Overall, I rate the tool a nine out of ten.

My company is a reseller of cloud-based products, and we are using IIS for this.

It is an easy-to-use and secure program.

The solution can be made more compatible. IIS also has some stability issues and needs restarting.

I have been using the solution for two years.

The solution is mostly stable, but sometimes there are issues and needs a restart. I rate it eight out of ten.

It is a scalable solution. Around 50 users are using it presently in our organization.

The initial setup was easy, and it took one week to be deployed. For deployment, first, we are planning, second, we are implementing on-premise, and third we are publishing the cloud. For maintenance, we need managers, admins, and engineers.

The solution is simple, and you can find the deployments everywhere. I rate it nine out of ten.

It is used for the REST service.

The tool is very easy and efficient.

In the next release, the tool should be more easily integrated and configured with other provisions. The pricing should also be made cheaper since it's very expensive now.

I have been using it for twenty years.

The tool is stable. 

The solution is a scalable product. My company has 1000 users for the tool. I have plans to increase the number of users.

Previously, we used Apache, Orache and Webinar Technologies.

The initial setup was easy.

The product was deployed through an in-house team.

The yearly licensing cost is very high. The solution is very expensive.

IIS is a very efficient and stable solution.

I would rate it a ten out of ten.

The solution is simple and very easy to manage compared to Linux.

Compared to Linux, the solution’s Windows patching is slower. I would like to improve it.

I have been using the product for ten years. I use the tool’s latest version.

I would rate the solution’s stability a seven.

I would rate the tool’s scalability around six to seven out of ten. There are around 4000 users for the solution in our company.

The tool’s tech support is not excellent but good. They take too much time to solve an issue.

The tool’s initial setup is straightforward. The deployment can be completed within a day. I will hardly take seven to eight hours. However, the time will depend on how you are deploying it.

The tool’s deployment was done in-house.

The solution’s pricing is yearly. The pricing is affordable and not high.

I would rate the overall solution a six out of ten. We have around five to six developers and engineers for the solution’s deployment and maintenance. You can use the solution if your website is not too big or complicated. However, if it is big and complicated, then you need to use Apache or Red Hat. This tool can be used for internal purposes. But if you plan to host a public app, then I wouldn’t recommend the tool.

I use IIS to deploy applications for customers and end users who want to publish their application or domain and access the same globally. They have to deploy their application over IIS so that some, like Binding, MDIS, and other application security services, can be configured. 

The most valuable feature of the solution is that it is easy to use and easy to understand.

Some developing aspects like coding have to be improved in the solution. Presently, some developers do not have technical knowledge of managing IIS, so that needs to be improved in the next release.

I definitely want the core part to be differentiated from the technical part.

I have been using IIS for approximately four to five years.

It is a Microsoft feature so it is definitely a good and stable product.

It is a scalable product. Every product has scale-based technologies so if you are good at understanding new technologies and new features, and if you have an interest in the same, then you are definitely going to like it.

I have not been in a situation to contact the support team yet as the solution’s features are very reliable and expressive.

Positive

The initial setup was very easy. It took approximately 15-20 minutes.

There is no license required for the product as it is role-based. Whenever you go for a Windows platform server, the role has to be installed directly from the server manager.

There is no additional cost that has to be paid for that. It is free to use.

I give this solution an eight out of ten.

The primary use case is mainly using the IIS service to host web applications so that these applications can be accessed from outside through a web server. 

I think that the IIS includes most features that are required by web applications so that they can run smoothly on Windows operating system. And since it is a native service from Microsoft that is part of the Windows Server ecosystem, so performance is good, and compatibility with the operating system also is excellent. The integration also is great with the operating system, and the integration with other Windows Server roles and applications.

When you are working with Microsoft solutions, you will see that the integration with the operating system, and implementing some security features, are easier in IIS than when using another solution. For example, if you want to use single authentication, SSO, or single sign-on, by authenticating yourself with your Windows username and password, when you are logging in to your computer, the IIS can use these credentials to automatically authenticate you in the application without the need to write or to type again your username or password. This is the SSO, the single sign-on, you can implement it quickly and easily in IIS since it is natively developed to work with Windows operating system. You only need to implement the SSO in your application. And once you develop this module and integrate it into your application, you can easily use it with the IIS within Windows.

Sometimes if you are using IIS in large-scale scenarios, meaning that if you are deploying an application within IIS service and you are expecting a large number of users to use this application, you can sometimes find some problems, meaning that the service can shut down by itself unexpectedly if you don't configure your IIS with the correct configuration that can handle this number of users.

Some configurations are not that easy to configure, there are a lot of details that you need to specify to tweak your applications. Sometimes, you can find problems, especially with applications that are not developed with .NET languages. If you want your application to perform well and can handle a large number of users, you need to use .NET languages like ASP.NET or other .NET technology. But if you are using for example PHP application, sometimes you can find some performance issues.

I encountered that type of problem, especially when you are using, for example, applications that are not developed in the Windows environment and you want to deploy this application with the IIS, sometimes you will find problems, especially performance-related problems.

Frankly, I have been using the solution since 2010. And am still using it when we want to deploy web applications and you want to use a web server. So the IIS is a role within the Windows Server operating system that you can activate to use the web service in the operating system.

It's not about stability, but it's more about compatibility. Meaning that, if you are using Microsoft technology, you won't find better than IIS. But if you are using other programming language technologies that aren't Microsoft technologies, you can find yourself facing these kinds of issues. Especially if your application wasn't developed to fully work with IIS. So sometimes you can find this problem, this problem can be caused by the development process of this application. But sometimes even though you will take into consideration the compatibility problem, the IIS won't perform well with other technologies that are not Microsoft.

The solution is scalable. You can have as many servers that host IIS so that they can handle the connections from users. And this is where the Failover Cluster service is used, it is used to create a cluster of services so that you can make your service scalable and available.

For Microsoft, if you subscribe for example, to the premium subscription plan, and it depends on the level or the urgency of the ticket or the incident, they will contact you sometimes within the hour if it's a critical problem. But if it's just a simple support ticket, sometimes within 24. It's less than 48 hours before they will call you. It depends on if you want them to assist you by phone or by email. And their support is really great, sometimes they can find the problem within minutes. Yeah, I think it's great.

Frankly, we are using other web server applications like the Apache web server. It depends on the application, and how or what web service application it was developed. If it was developed to be used with the IIS, then we use IIS for that application. If this application was developed for Apache or another web service, then we will install this webserver to run the application. Most of the time when it is a PHP web application, then we will use the Apache web server rather than the IIS. But if it's ASP.NET or another .NET technology, then we will use IIS. Or if we are using, for example, another solution from Microsoft, such as SharePoint or Microsoft Exchange mail servers, et cetera, then we will be forced to use the IIS service. Sometimes, you don't have a choice to choose. If it's a Microsoft solution you want to deploy, you will be forced to use IIS. If it's in-house developed application or you buy a product that needs a web server, then you can choose, but it depends also on the compatibility list of the application.

The initial setup is straightforward. It doesn't take much time. It's Windows, it's Microsoft stuff, and with Microsoft, it's about making the installation process easier, you cannot find an easier installation than Microsoft products. It's a role within the Windows Server, so with a number of clicks, you will find yourself ready to use the IIS service.

The implementation was completed in-house. 

Sometimes, I deploy it by myself, and sometimes when another department needs visual machines with Windows Server and the IIS service, I can either install everything by myself or provide them with the virtual machines and the access information credential, et cetera. And the company that will deploy the application for them, it'll be the one that will install the role and configure it.

I think it's part of the Windows Server, so you won't have any other costs to add in order to use the IIS service. Meaning that, if you have a license for Windows Server, then automatically you will have also the IIS service available.

I give the solution eight out of ten.

The IIS service version also depends on the version of the Windows Server. So for example, if you are using the Windows Server 2012, it may have an old version compared to the 2022 Windows Server version. It is the last one since we are also using the 2022 Windows Server operating system, so we are using the latest version 6.0.

Most of the time, if it's me who deployed or installed IIS in the first place, I am the one who will maintain it. But if it's another person or another company or its part of the maintenance program, then we will call the other company to do their maintenance tasks.

In my experience, I think that if you want to use IIS, you need to develop your application to be fully compatible with IIS. Meaning that, you need to use Microsoft technologies rather than other languages, for example, Java or PHP or other, Python or anything else. Rather than that them, you need to choose .NET technologies so that you will take advantage of the performance and compatibility of the system with your application. This is what I can recommend people to do in order to use IIS. Because when for example, you acquire an application or a solution that wasn't developed initially for IIS, you need to do many tweaks in the applications and the IIS in order to make it run. And sometimes these types of tweaks can cause you problems in the production environment.