01constructionStep 1: Install the Web Server (IIS) Role

In Server Manager, choose Add Roles and Features and follow the wizard:

1. Select Role-based or feature-based installation and pick your server from the pool.
2. In the Server Roles list, check Web Server (IIS), and accept the prompt to add the required features.
3. On the Role Services page, keep the defaults for a basic site, and optionally add extras such as HTTP Redirection or Basic Authentication.
4. Complete the wizard and let the server install the role.

Prefer the command line? One PowerShell command does the same:

Install-WindowsFeature Web-Server -IncludeManagementTools

02downloadStep 2: Test the Default Website

After installation, open a browser on the server and browse to http://localhost. The default IIS page confirms the web server is running. The site’s files live in C:\inetpub\wwwroot.

03usbStep 3: Publish Your Own Content

Replace C:\inetpub\wwwroot\iisstart.htm with your own HTML files, or create a new site: in IIS Manager, right-click Sites and choose Add Website, then set the site name, the folder with your files (the physical path), and the binding: an IP address, port 80 and an optional host name such as www.example.local.

04terminalStep 4: Configure Bindings and DNS

Each site is identified by its binding: IP + port + host name. To reach the site by name from other machines, create an A record on your DNS server pointing the host name to the web server’s IP. See the DNS server setup guide to configure DNS in Windows Server for your lab.

05settings_ethernetStep 5: Open the Firewall and Test Remotely

Windows usually adds the inbound rule automatically, but if clients cannot connect, open port 80:

New-NetFirewallRule -DisplayName "HTTP" -Direction Inbound -Protocol TCP -LocalPort 80 -Action Allow

Then browse to the server from another VM using its IP or DNS name.