Microsoft Windows Server 2003 Deployment Kit—Deploying Microsoft Internet Information Services (IIS) 6.0 [Electronic resources] نسخه متنی

Overview of Migrating IIS Web Sites to IIS 6.0

You begin the migration process by determining the compatibility of your existing Web sites and applications with IIS 6.0 and the Microsoft Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; or Windows Server 2003, Web Edition operating system. Next, you install Windows Server 2003 and IIS 6.0 on the target server, which is the server that will host your Web sites after migration. Then, you migrate the Web site content and configuration settings from the source server, which is a server running the Microsoft Windows NT Server 4.0 operating system and IIS 4.0 or the Windows 2000 Server operating system and IIS 5.0, to the target server.

After the migration of your Web site content, you customize the configuration of IIS 6.0, based on your Web sites and applications. Finally, after you have completed the customization of IIS 6.0, you back up the target server, enable client access to the Web sites and applications on the target server, and decommission the source server.

The process in this chapter focuses on transferring the Web site content and configuration settings, and not on the details of how to make application code changes in dynamic content. If your Web sites contain only static content, you can most likely complete the migration process in a few simple steps. However, if your IIS Web sites contain dynamic content, such as Active Server Pages (ASP), ASP.NET, or Common Gateway Interface (CGI) scripts, you might need to modify the code in the dynamic content separately. In addition, any provisioning scripts or setup programs for your existing Web sites and applications might need to be modified after the migration process is complete. Ensure that you test any modifications after the migration process is complete. For more information about potential modifications, see "Preparing for Migration" later in this chapter.

Also, if the existing Web sites and applications depend on software other than the Windows operating system and IIS, the complexity of the migration process increases. For example, the process for migrating a Web server that hosts Web sites and applications that were designed to run on Windows 2000 Server and IIS 5.0 is relatively simple. On the other hand, the process for migrating a Web server that hosts Web sites, applications, and other software — such as Microsoft Commerce Server, Microsoft BizTalk Server, monitoring software, custom applications, or other non-Microsoft software — is more difficult because all of the software must be compatible with Windows Server 2003 and IIS 6.0.

In some cases, you can simplify the Web site migration process by using the IIS 6.0 Migration Tool. For more information about using the IIS 6.0 Migration Tool, see "Preparing for Migration" later in this chapter.

Process for Migrating IIS Web Sites to IIS 6.0

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

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 "IIS Deployment Procedures" in this book.

Prepare for Migration

Identify which Web site and application components to migrate.

Determine compatibility with Windows Server 2003.

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

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

Select one of two methods for migration:

Using the IIS 6.0 Migration Tool

Completing the migration process manually

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

Install Windows Server 2003.

Install and configure IIS 6.0.

Migrate Web Sites with the IIS 6.0 Migration Tool

Install the IIS 6.0 Migration Tool.

Verify that clients are not accessing Web sites.

Run the migration tool.

Verify that the migration tool ran successfully.

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

Outside the home directory of the Web site

Inside virtual directories

Modify IIS metabase properties that reference the systemroot folder.

Migrate Web Sites Manually

Verify that clients are not accessing the Web sites.

Create Web sites and virtual directories.

Migrate Web site content to the target server.

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.

Modify IIS 6.0 metabase properties that reference the systemroot folder.

Configure IIS 6.0 Properties

Configure IIS 6.0 properties that reference local user accounts.

Configure Web service extensions.

Configure Multipurpose Internet Mail Extensions (MIME) types.

Migrate server certificates for Secure Sockets Layer (SSL).

Migrate Microsoft FrontPage users and roles.

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.

Determine whether to run the IIS Lockdown Tool and UrlScan.

Perform Application-Specific Migration Tasks

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.

Install additional software required by applications.

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

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

Create IP addresses that are used by applications.

Create users and groups that are used by applications.

Create registry entries required by applications on the target server.

Complete the Migration

Verify that the Web sites and applications migrated successfully.

Back up the target server.

Enable client access.