How to Install and Configure IIS on Windows Server

Quick answer: Install IIS via Server Manager, Add Roles and Features, Web Server (IIS), adding ASP.NET if you host .NET sites. Confirm with http://localhost, then in IIS Manager add a website with a physical path and host-name binding. Run each site in its own application pool.

Internet Information Services (IIS) is the built-in Windows web server. It is not installed by default; you add it as a role. This guide installs IIS, confirms it works, and creates your first site.

1. Install the IIS role

Open Server Manager > Add Roles and Features. Step through to Server Roles and tick Web Server (IIS). On the Role Services screen, keep the defaults and add what your applications need - for example ASP.NET under Application Development if you host .NET sites. Complete the wizard to install.

2. Confirm IIS is running

Open a browser on the server and go to http://localhost. The IIS default welcome page confirms the web server is live. Make sure Windows Firewall allows ports 80 and 443 so visitors can reach it from outside.

3. Create a new site

Open IIS Manager (inetmgr). Right-click Sites > Add Website and set:

Site name:      yourdomain
Physical path:  C:\inetpub\yourdomain
Binding:        http, port 80, host name yourdomain.com

Place your site files in the physical path. The host name binding lets one server host multiple sites on the same IP by matching the domain in the request.

4. Understand application pools

Each site runs in an application pool, which isolates it from others. For a .NET site, set the pool's .NET CLR version appropriately; for a site that does not use .NET (for example a static or PHP site), set it to No Managed Code. Isolating sites in separate pools means one crashing site does not take down the others.

5. Set permissions

Ensure the application pool identity can read the site folder. If pages return a 500 or access-denied error, folder permissions for the pool identity are the usual cause.

Frequently asked questions

A site returns 500 or access denied - why?
Usually the application pool identity lacks read permission on the site folder.

What CLR version should the app pool use?
Set the .NET version for .NET sites, or No Managed Code for static or PHP sites.

Managed Windows hosting saves you this setup: a SoftSys managed Windows VPS can be delivered with IIS and ASP.NET pre-configured, or with Plesk if you prefer to manage sites, databases, and SSL through a control panel.