A Safe Local IIS Lab: Build a Site From Scratch

Objective

Install IIS on a local Windows machine, create a custom site of your own (not just the default one), and locate its log files — building hands-on familiarity with IIS's structure before ever touching a production server. This lab is entirely local and has zero production risk; everything here happens on your own machine.

Setup

Confirm you have administrator rights on the machine you're using, and that no production or shared server is involved — this lab is designed for a personal or lab machine only.

Steps

1. Enable IIS. Open PowerShell as Administrator and run:

   Enable-WindowsOptionalFeature -Online -FeatureName IIS-WebServerRole, IIS-WebServer, IIS-CommonHttpFeatures, IIS-HttpErrors, IIS-ApplicationDevelopment
   

   This may take a few minutes and might require a restart depending on your Windows version.

2. Confirm the default site works. Open a browser and navigate to http://localhost. You should see the default IIS welcome page — this confirms IIS itself is running correctly before you build anything custom.

3. Create a folder for your own site, e.g. C:\inetpub\mysite, and add a simple index.html file with any content you like.

4. Open IIS Manager (search for "Internet Information Services (IIS) Manager" in the Start menu).

5. Add a new website, not just a virtual directory: right-click Sites → Add Website. Give it a site name, point the physical path at the folder from step 3, and set the binding to a port that isn't already in use (e.g., 8081) rather than port 80, so it doesn't conflict with the default site.

6. Confirm your new site responds by browsing to http://localhost:8081.

7. Locate the application pool your new site was assigned to. By default, IIS creates a new, dedicated application pool with the same name as your site — click Application Pools in IIS Manager and find it. This is the concrete, hands-on version of the site/pool/worker-process distinction covered in the companion guide.

8. Find and open the IIS log for your new site. By default, IIS logs live under C:\inetpub\logs\LogFiles\, in a folder named W3SVC followed by a site ID number. Open today's log file (a plain text, space-delimited file) and find the line corresponding to the request you just made in step 6 — look for the timestamp and the path you requested.

Verification checklist

• IIS is installed and the default website responds at http://localhost.
• A new, custom site (not the default) is created and bound to its own port.
• You can locate and read an entry in the IIS log for a request you just made.
• You can explain, in your own words, the difference between a site and an application pool.

Extend this lab

Deliberately stop your new site's application pool from IIS Manager, then try browsing to it again — observe the specific error IIS shows for "the pool exists but isn't running," so you recognize it immediately if you see it on a real server. This is a safe, hands-on preview of the failure mode covered in IIS Application Pools: What They Are and Why They Crash.

Verification checklist

• IIS is installed and the default website responds at http://localhost.
• A new, custom site (not the default) is created and bound to its own port.
• You can locate and read an entry in the IIS log for a request you just made.
• You can explain, in your own words, the difference between a site and an application pool.

Part of: Freshers, System Administrators

Continue learning

Mark this article as read

← Back to Labs

Next → Setting Up Your First Development Environment A from-scratch lab to get your first coding environment working — editor, a language runtime, the terminal, and Git — so setup friction never blocks your learning again.