Installing and Configuring IIS

  • Article

Applies To: Windows Server 2003, Windows Server 2003 with SP1

Because IIS 6.0 is not installed during the default installation of Windows Server 2003, the next step in deploying the target server is to install and configure IIS 6.0. The migration process presented here assumes that you install IIS 6.0 with the default options in Add or Remove Programs in Control Panel. If you use other methods for installing and configuring Windows Server 2003, such as Manage Your Server, the default configuration settings might be different.

Install and configure IIS 6.0 by completing the following steps:

  1. Install IIS 6.0 with only the essential components and services.

    As with installing Windows Server 2003, the primary concern when installing and configuring IIS 6.0 is to ensure that the security of the target server is maintained. Enabling unnecessary components and services increases the attack surface of the target server. You can help ensure the target server is secure by enabling only the essential components and services in IIS 6.0.

    For more information about how to install IIS 6.0, see Install IIS 6.0. For more information about the IIS 6.0 protocols and services, see Enabling Only Essential IIS Components and Services.

  2. If the source server has Web sites with FrontPage Server Extensions, install FrontPage 2002 Server Extensions from Microsoft on the target server.

    For more information about how to enable FrontPage Server Extensions, see Configure Web Service Extensions.

  3. Configure IIS 6.0 to run in IIS 5.0 isolation mode.

    If you determined that one or more of your Web sites or applications are incompatible with worker process isolation mode (the target server is currently configured to run in worker process isolation mode), configure IIS 6.0 to run in IIS 5.0 isolation mode in IIS Manager, or by setting the IIS metabase property IIs5IsolationModeEnabled to a value of True.

    Note

    If you configure IIS 6.0 to run in IIS 5.0 isolation mode and then decide to change the configuration back to worker process isolation mode, the original worker process isolation mode settings are retained. Similarly, if you configure IIS 6.0 to run in IIS 5.0 isolation mode, change to worker process isolation mode, and then change back to IIS 5.0 isolation mode, the IIS 5.0 isolation mode settings are retained.

    For more information about how to configure IIS 6.0 to run in worker process isolation mode or in IIS 5.0 isolation mode, see Configure Application Isolation Modes. For more information about determining compatibility with worker process isolation mode, see Evaluating Application Changes Required for Worker Process Isolation Mode.