Configuring and Troubleshooting Internet Information Services in Windows Server 2008 Highlights

Posted on July 19, 2011


IIS does not come installed, as it did in Windows 2003 Server.

So… install IIS Webserver role in one of three ways:

  1. Server Manager > Add Web Server Role
  2. Unattended (e.g when installing web farms) > PkgMgr using .xml file for config
  3. Command Line (if using Core Server) > PkgMgr using command line

(If installing an (e.g. ASP.NET 2.0) app, add  ASP.NET as a service of the Web Server role. An app must be running in an application pool with the version of ASP.NET it needs.)

Running ASP.NET 2.0 Intergrated Mode  ASP.NET 1.0 apps need to run in ‘Classic’ mode, I think.

IIS 7 uses Microsoft Management Console (MMC) v3. New feature: Action Pane on the right, where you can start/recyle app pools, etc.

Application Pools

  • Basic Properties
    • Pool Name
  • Advanced Properties
    • Health Management
    • Recycling


Modules, such as FormsAuthentication or DefaultDocument are added/removed in the Detail Page > Server Components > Modules (sort by category) for the application in question.

Or they can be added/removed by editing c:\windows\system32\inetsrv\config\applicationHost.config. Before editing be sure to backup using “appcmd add backup original”. Restore by using “appcmd restore backup original”.


In Details pane under “Security” category for app or website:

  • Server certificates
  • Blocking IP addresses
  • ISAPI and CGI restrictions:
    • Allow ASP.NET 1.1 to run after you’ve installed it with dotnetfix.exe, for instance
  • Set rights for Active Directory users
  • Authorization, Authentication and Access
  • Set up Loggin’

Remote Admin

Remote admin uses HTTPS (port 443), so it can be used through a firewall.

Management Service (WMSVC) must be restarted after configuration changes.

Allow grant access to folders & features with IIS (under Management > Feature Delegation in Detail pane)


Check out:

Microft is touting PowerShell. It can make calls to .Net Framework, WMI, and the registry… pretty much everything.

Performance Tuning

Site and app changes are immediate, global changes recycle worker processes.

Windows System Resource Manager (WSRM). Install it with Server Manager, and use to manage amount of resources IIS uses.

Put all sites in one application pool? It’s a trade off of security vs. performance. Separate pools = more secure. If they’re all stable and use same ASP.NET version, they can be in same pool. Using one pool uses less memory.

Reliability and Performance Monitor is a more friendly version of Performance Monitor. It basically replaces Task Manager.

Deploy apps and updates with XCOPY.

Some notes:

Application Warm-Up for IIS 7.5

Application Warm-Up Beta Removed

Run 32 bit app on IIS 7.5

Web Farms

Ensure availability. How?

Backup Website > Simply, copy website files to another folder using “copy” cmd.

Cluster servers (through IIS Manager GUI > Management):

  • protects against hardware failure for one server
  • can add resources to the cluster if they are needed

Session variables must be taken care of, probably by putting them into a database.


  • Logging
    • Failed/Succeeded Request Tracing
  • Authentication
  • Authorization
  • Communication
    • e.g. physical path
  • Configuration
Posted in: Technology