Export (0) Print
Expand All

Process for Migrating IIS Web Sites to IIS 6.0

Updated: August 22, 2005

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

The process for migrating Web sites hosted on IIS consists of preparing for and performing the migration. Before performing the migration, you need to evaluate the compatibility of the software installed on your existing Web server (including software that generates dynamic content, database connections, and any non-Microsoft software) with Windows Server 2003 and IIS 6.0. You can then perform the migration manually or with the IIS 6.0 Migration tool. After the migration is complete, you must further customize the configuration of IIS 6.0. Figure 6.1 illustrates the process for migrating existing IIS Web sites to IIS 6.0.

Figure 6.1   Migrating IIS Web Sites to IIS 6.0

Art Image
To migrate a Web farm, use the process described in this section to migrate Web sites from each Web server in the source Web farm. Then, use provisioning or Web site staging software to propagate the migrated content and site configuration to other Web servers in the target Web farm.

Depending on your familiarity with Windows server operating systems, IIS, and the migration process, you might require less information to complete the IIS 6.0 migration process. To facilitate the fastest possible migration, the following quick-start guide is provided. You can use this guide to help identify the steps of the IIS 6.0 migration process that you need additional information to complete, and then you can skip the information with which you are already familiar. In addition, all of the procedures that are required to complete the IIS migration process are documented in Appendix A: IIS Deployment Procedures.

Prepare for Migration

  1. Identify which Web site and application components to migrate.

  2. Determine compatibility with Windows Server 2003.

  3. Determine application compatibility with worker process isolation mode by evaluating the following:

    • The benefits of worker process isolation mode

    • The application changes that are required for worker process isolation mode

    • The management and provisioning script changes that are required for worker process isolation mode

    • The results of lab tests that were completed to verify application compatibility with worker process isolation mode

  4. Determine application compatibility with the Microsoft .NET Framework on Windows Server 2003.

  5. Select one of two methods for migration:

    • Using the IIS 6.0 Migration Tool

    • Completing the migration process manually

  6. If you are using the IIS 6.0 Migration Tool, identify the following:

    • Tasks that are automated by the migration tool

    • Subsequent tasks that must be performed manually

Deploy the Target Sever

  1. Install Windows Server 2003.

  2. Install and configure IIS 6.0.

Migrate Web Sites with the IIS 6.0 Migration Tool

  1. Install the IIS 6.0 Migration Tool.

  2. Verify that clients are not accessing Web sites.

  3. Run the migration tool.

  4. Verify that the migration tool ran successfully.

  5. Migrate additional Web site content that is in the following two locations:

    • Outside the home directory of the Web site

    • Inside virtual directories

  6. Modify IIS metabase properties that reference the systemroot folder.

Migrate Web Sites Manually

  1. Verify that clients are not accessing the Web sites.

  2. Create Web sites and virtual directories.

  3. Migrate Web site content to the target server.

  4. Configure Web site application isolation settings by completing the following tasks, if appropriate:

    • Document the current application isolation settings on the source server.

    • Configure application isolation settings in IIS 5.0 isolation mode.

    • Configure application isolation settings in worker process isolation mode.

  5. Modify IIS 6.0 metabase properties that reference the systemroot folder.

Configure IIS 6.0 Properties

  1. Configure IIS 6.0 properties that reference local user accounts.

  2. Configure Web service extensions.

  3. Configure Multipurpose Internet Mail Extensions (MIME) types.

  4. Migrate server certificates for Secure Sockets Layer (SSL).

  5. Migrate Microsoft FrontPage® users and roles.

  6. Configure IIS 6.0 to host ASP.NET applications by completing the following tasks:

    • Configure IIS to use the correct version of the .NET Framework.

    • Configure the .NET Framework.

    • Review how ASP.NET applications run in each application isolation mode.

    • Migrate Machine.config attributes to their equivalent IIS 6.0 metabase property settings.

  7. Determine whether to run the IIS Lockdown Tool and UrlScan.

Perform Application-Specific Migration Tasks

  1. Modify application code for compatibility with Windows Server 2003 and IIS 6.0 by doing the following:

    • Modify references to Windows platform components and application programming interfaces (APIs) that are no longer supported in Windows Server 2003.

    • Modify references to IIS 6.0 metabase properties that have changed or are no longer supported in IIS 6.0.

    • Modify applications to be compatible with worker process isolation mode.

  2. Install additional software required by applications.

  3. Migrate Microsoft Transaction Server (MTS) packages, Component Object Model (COM) objects, and COM+ applications that are required by applications.

  4. Modify data source names (DSNs) and Open Database Connectivity (ODBC) connections required by applications.

  5. Create IP addresses that are used by applications.

  6. Create users and groups that are used by applications.

  7. Create registry entries required by applications on the target server.

Complete the Migration

  1. Verify that the Web sites and applications migrated successfully.

  2. Back up the target server.

  3. Enable client access.

Community Additions

© 2016 Microsoft