Techie BabajiLearn to Code. Build Real Skills.
IIS (Internet Information Services) · Getting Started

IIS Manager

IIS Manager (inetmgr) is the graphical console for IIS. Knowing where each setting lives — and which file it writes to — makes everything else easier.

Beginner 5 min Lesson 3 of 33Covers IIS 10 on Windows Server 2019/2022/2025 and Windows 10/11.
Before you start:Installing IIS
0/33 in IIS
On this page · 5 min · Beginner

On this page

  1. In simple words
  2. Learning objectives
  3. Explanation
  4. Code example
  5. Step by step
  6. Real-world use
  7. Common mistakes
  8. Best practices
  9. Remember this
  10. Practice exercise
  11. Mini quiz
  12. Related topics
  13. My notes
Reading time
5 min
Difficulty
Beginner
Updated
Oct 30, 2026

Related tutorials

Interview questions

In simple words#

IIS Manager is the control room of the building. The left panel is the floor plan (server → sites → apps), the middle shows the switches for the selected floor, and the right panel holds the action buttons.

Connections pane
Tree of server, app pools, sites and apps.
Features View
Icons for each setting (Bindings, SSL, Authentication…).
Actions pane
Buttons like Start, Stop, Browse, Edit.

Learning objectives#

  • Open and navigate IIS Manager
  • Understand server vs site vs application levels
  • Use Features View and Content View
  • Know which file each setting changes

Explanation#

Open it with Win+R → inetmgr. The Connections pane shows the server, Application Pools and Sites.

Settings at the server level apply to all sites (stored in applicationHost.config). Settings at a site or application level usually go into that folder’s web.config.

Features View shows setting icons; Content View shows files. The Actions pane changes with what you select.

Configuration Editor (at any level) shows the raw configuration sections and can generate scripts for any change.

Code example: Where settings are stored#

TextWhere settings are stored Illustrative
Level selected in IIS Manager        Typical file written
Server (MACHINE-NAME)                C:\Windows\System32\inetsrv\config\applicationHost.config
Application Pools                    applicationHost.config  (<applicationPools>)
Site "Shop" → Bindings               applicationHost.config  (<sites>)
Site "Shop" → Default Document       C:\inetpub\shop\web.config
Site "Shop" → URL Rewrite            C:\inetpub\shop\web.config
Application "/api" → Authentication  applicationHost.config (locked sections) or /api/web.config


Configuration Editor → Generate Script → shows C#, JavaScript, AppCmd and PowerShell for the change
Expected output
You know exactly which file to back up, review or put in source control for every setting.

This example is illustrative. Copy or download it and run it in your own environment; the expected output is shown above.

Step-by-step explanation#

  1. Server-wide and binding settings live in applicationHost.config.
  2. Most per-site settings live in the site’s web.config.
  3. Some sections (like authentication) are locked to applicationHost.config by default.
  4. Configuration Editor generates scripts for automation.

Real-world use case#

A developer configures compression in IIS Manager once, copies the generated PowerShell from Configuration Editor, and adds it to the deployment script.

Common mistakes#

Editing applicationHost.config with a text editor while IIS Manager is open

One can overwrite the other. Back up first and prefer IIS Manager or PowerShell.

Not knowing settings were saved to web.config

Redeploying the app can overwrite them. Keep web.config in source control.

Best practices#

  • Back up applicationHost.config before big changes
  • Keep web.config in source control
  • Use Configuration Editor’s Generate Script
  • Prefer scripts over manual clicks in production

Remember this#

inetmgr opens IIS Manager.

Server/pools/bindings → applicationHost.config.

Site features → web.config.

Practice exercise#

Your task: Back up the IIS configuration from the command line.

Show solution
PowerShell Illustrative
& "$env:windir\System32\inetsrv\appcmd.exe" add backup "before-changes"

Mini quiz#

IIS Manager quizMultiple choice Question 1 of 1

Where are site bindings stored?

Score so far: 0/0

Want more? Practise all IIS MCQs · IIS interview questions

My notes#

Saved in this browser.

Progress is saved in this browser. Sign in to sync.