Internet Information Services (IIS) is Microsoft's web server for Windows. This guide installs IIS, verifies the default website, and creates a separate website with its own content directory and hostname binding.

These steps were tested on a BinaryLane Windows Server 2025 instance with Desktop Experience and IIS 10 on 20 August 2026. The Server Manager workflow also applies to Windows Server 2019 and 2022, although some labels may differ slightly.


Before you begin

You need:

  • a BinaryLane Windows Server instance;
  • an Administrator account and Remote Desktop or console access;
  • the files you want the website to serve; and
  • a domain name with an A record pointing to the server's public IPv4 address if you want to use a hostname binding.

Install current Windows updates before configuring a production website. Updates can require a restart, so use a suitable maintenance window. See Modifying Windows Update settings.


Important: For public access, allow inbound TCP port 80 in the BinaryLane External Firewall, if one is attached, and in Windows Firewall. HTTP traffic is not encrypted. Configure HTTPS after the HTTP website works.


Your Windows Server operating system and IIS configuration are customer-managed. BinaryLane can provide general guidance, but does not manage the website or its operating system configuration.


TABLE OF CONTENTS

1. Install IIS

  1. Sign in to the server as an Administrator.
  2. Open Server Manager.
  3. Select Manage, then Add Roles and Features.

Server Manager Manage menu showing Add Roles and Features

  1. On Before you begin, select Next.
  2. Select Role-based or feature-based installation, then select Next.
  3. Select the local server from the server pool, then select Next.
  4. Under Server Roles, select Web Server (IIS).
  5. When prompted, leave Include management tools (if applicable) selected and choose Add Features.

Add features required for Web Server IIS

  1. Select Next on the Server Roles and Features pages. A basic static website does not require additional features.
  2. On Web Server Role (IIS), select Next.
  3. On Role Services, keep the defaults selected unless your application has documented requirements for additional modules.

Default IIS role services for a static website


Do not add Classic ASP, IIS 6 compatibility, or other optional modules unless the application specifically requires them. Unneeded modules increase the server's maintenance and security surface.

  1. Select Next, review the installation choices, then select Install.

Confirm IIS installation selections

  1. Wait for Installation succeeded, then select Close. Restart the server only if Windows requests it.

IIS installation succeeded


2. Test the default website

  1. Open a browser on the server.
  2. Go to http://localhost.
  3. Confirm that the IIS welcome page appears.

Default IIS website displayed at localhost


To test from another computer, browse to http://<server-public-IP>. If the local test works but the public test times out, check the BinaryLane External Firewall and Windows Firewall rules for inbound TCP port 80.


3. Prepare the website content

Create a separate directory for the website, such as:

C:\Sites\ExampleSite

Place the website files in that directory. For a simple test, create index.html with this content:

<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>Example Site</title>
  </head>
  <body>
    <h1>Example site is working</h1>
  </body>
</html>

The IIS application pool identity must have permission to read the directory and files. Folders created locally with normal inherited permissions usually work for static content. If IIS returns an access error, check the NTFS permissions before granting broader access.


4. Add the website in IIS Manager

  1. Open Server Manager.
  2. Select Tools, then Internet Information Services (IIS) Manager. You can also run inetmgr.
  3. In the Connections pane, expand the server, then select Sites.
  4. In the Actions pane, select Add Website.
  5. Enter the website settings:
  • Site name: a friendly name, such as Example Site.
  • Physical path: the content directory, such as C:\Sites\ExampleSite.
  • Type: http.
  • IP address: All Unassigned, unless the website must use a specific address.
  • Port: 80.
  • Host name: replace www.example.com with the website's domain.
  • Start Website immediately: selected.

Add Website settings in IIS Manager

  1. Select OK.
  2. Confirm that the new website appears with a status of Started.

Started website in IIS Manager


The combination of protocol, IP address, port and hostname is the website's binding. Two websites cannot use an identical binding. A hostname binding lets multiple HTTP websites share the same IP address and port.


5. Test the website

  1. Confirm that the domain's A record points to the server's public IPv4 address.
  2. From a different computer, browse to the HTTP URL, such as http://www.example.com.
  3. Confirm that the expected website loads rather than the default IIS page.

After the HTTP website works, configure HTTPS. See Free SSL/TLS certificates with Let's Encrypt and win-acme on Windows Server.


Troubleshooting

The website works on localhost but times out externally

Check that inbound TCP port 80 is allowed in both the BinaryLane External Firewall, if attached, and Windows Firewall. Also confirm that the domain points to the correct public IP address.

The default IIS page appears instead

Check the hostname in the browser, the DNS record, and the website's binding. The requested hostname must match the Host name configured for the website.

IIS reports a binding conflict or the website will not start

Another website is already using the same protocol, IP address, port and hostname combination. Change the binding or stop the conflicting website.

IIS returns 403.14 Forbidden

Confirm that the physical path contains a recognised default document, such as index.html, and that Default Document is enabled for the website.

IIS returns an access or permission error

Confirm that the website's application pool identity can read the content directory. Grant only the permissions required by the application.


Applies to

  • BinaryLane Windows Server 2019
  • BinaryLane Windows Server 2022
  • BinaryLane Windows Server 2025

Last verified: 20 August 2026 on BinaryLane Windows Server 2025 with IIS 10.