Example: Converting to Worker Process Isolation Mode

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

A fictitious organization, Contoso, has an existing IIS 5.0 Web server that hosts four Web applications. The administrator plans to upgrade the Web server to IIS 6.0, and has tested the applications for compatibility with IIS 6.0 worker process isolation mode and Windows Server 2003. Table 5.4 lists the existing configuration of the Web applications before upgrading to IIS 6.0.

Table 5.4 Configuration Before Upgrade

After the upgrade, the administrator verified that the Web applications continued to run properly in IIS 5.0 isolation mode. Then the administrator configured IIS 6.0 to run in worker process isolation mode. Table 5.5 lists the configuration of the Web applications immediately after configuring IIS to run in worker process isolation mode.

Table 5.5 Configuration After Converting to Worker Process Isolation Mode

To approximate the original configuration of the Web applications in worker process isolation mode, the administrator does the following:

1. Creates a new application pool for each application that was configured for isolation.

2. Configures each application pool with the identity assigned previously to the application configured for isolation.

3. Ensures that the identity assigned to each newly created application pool is added to the IIS_WPG local user group.

4. Assigns each application to the corresponding application pool.

5. Continues hosting all other applications in the default application pool.

6. Verifies that the applications in the default application pool properly run under the NetworkService account identity.

Table 5.6 Final Configuration of Web Sites and Applications