Converting to Worker Process Isolation Mode

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

When the upgrade process is complete, IIS 6.0 is configured to run in IIS 5.0 isolation mode. Although IIS 5.0 isolation mode provides compatibility with existing applications, it is unable to provide all the security, availability, and performance improvements in worker process isolation mode. To take full advantage of these improvements, you must configure IIS 6.0 to run in worker process isolation mode.

After upgrade, most Web sites and applications function in worker process isolation mode without modification. IIS can run in only one application isolation mode at a time — either IIS 5.0 isolation mode or worker process isolation mode. As a result, configuring IIS to run in worker process isolation mode affects all of the Web sites and applications hosted by IIS. Therefore, before configuring IIS to run in worker process isolation mode, you must determine whether your applications are compatible with this isolation mode. If the existing Web sites and applications are not compatible with worker process isolation mode, you can continue to Configuring IIS 6.0 to Host ASP.NET Applications.

Figure 5.4 illustrates the process for converting the Web server to worker process isolation mode.

Figure 5.4   Converting to Worker Process Isolation Mode

For more information about worker process isolation mode and IIS 5.0 isolation mode, see Determining Application Compatibility with Worker Process Isolation Mode.