Migrating Machine.config Attributes to Metabase Property Settings

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

When IIS 6.0 is configured to run in IIS 5.0 isolation mode, the .NET Framework uses the <processModel> section of the Machine.config file (in the %systemroot%\Microsoft.NET\Framework\versionNumber\Config folder) for its runtime configuration. When the target server is running in IIS 5.0 isolation mode, you do not need to convert the attribute configuration settings on the source server to their equivalent IIS 6.0 metabase property settings on the target server so you can proceed to the next step in the migration process. To proceed to the next step in the migration process, see Determining Whether to Run the IIS Lockdown Tool and UrlScan.

However, if you configured IIS 6.0 to run in worker process isolation mode, the .NET Framework ignores the <processModel> section of the Machine.config file, and instead gets its process configuration from the IIS 6.0 metabase. Because the migration process does not migrate the existing settings in the Machine.config file, you must manually migrate any settings that are required by your ASP.NET applications.

For information about how to migrate the Machine.config settings to IIS 6.0 metabase settings, see Migrating Machine.config Attributes to IIS 6.0 Metabase Property Settings.