Migration Tasks That Must Be Completed Manually

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

The following steps in the Web site migration process must be completed after running the IIS 6.0 Migration Tool.

Migrating Additional Web Site and Application Content

The IIS 6.0 Migration Tool migrates all of the content that is located in the home directory of the Web site and in any subdirectories contained in that home directory. You can migrate any Web site and application content that is not located in these directories by completing the following steps:

• Migrate content located outside the home directory and subdirectories of the Web site. When the Web sites and applications reference content that is located in folders outside of the home directory of the Web site or the virtual directories beneath the home directory, you must migrate this content manually.

• Migrate content located in a virtual directory. When the virtual directory content on the source server is stored on a disk volume, such as F:, that does not exist on the target server, you must migrate this content manually.

Configuring Additional Web Site and Application Properties

After running the IIS 6.0 Migration Tool, the Web sites are configured comparably to how they were configured on the source server. However, depending on the configuration of the Web sites and applications on the source server, you might need to configure additional Web site and application properties, by completing the following steps:

• Change the IIS metabase settings to reflect where Windows is installed. If the Windows Server 2003 systemroot path does not match the Windows systemroot path on the source server, you must modify the metabase settings on the migrated Web sites to reference the correct folder on the target server. For example, if Windows was installed on C:\WINNT on the source server, the IIS metabase entries for ScriptMaps, and HTTPErrors properties might still reference these paths, and therefore need to be updated on the target server.

• Configure IIS properties that reference local user accounts. There are a number of Web site configuration properties on the source server that you can configure to utilize user accounts that are local to the source server. Local user and group accounts are not migrated from the source server to the target server by the IIS 6.0 Migration Tool. As a result, the migrated Web sites reference user accounts that do not exist on the target server. In these cases, you must configure the Web sites to utilize user accounts that are domain-based or local to the target server, and then re-create the file system permissions on migrated content by completing the following steps:

  • Configure local user NTFS permissions on content. If NTFS permissions are granted to local user accounts on the source server, you must create new user accounts, or designate existing user accounts, for use on the target server and then grant the corresponding NTFS permissions to the user accounts on the target server.

  • Configure anonymous account properties for Web sites and virtual directories. If a Web site or virtual directory is configured to use a user account on the source server for anonymous access (other than the default IUSR_computername account), you must create a new user account, or designate an existing user account, for use on the target server.

  • Configure IIS 4.0 and IIS 5.0 application isolation identities. If the Web sites or applications are isolated and are configured to use a local user account on the source server as the application isolation identity, you must create a new user account, or designate an existing user account, for use on the target server. Then you must configure the corresponding application pool, on the target server, to use the newly created account as the identity of the application pool.

  • Add Web service extensions for dynamic content used by the Web sites. Any dynamic content types, including ISAPI extensions, ISAPI filters, or CGI applications, which are not automatically migrated by the IIS 6.0 Migration Tool need to be added to the Web service extensions list.

  • Add MIME types for static content used by the Web sites. MIME types define the types of static files that are served by the Web server. You must identify the MIME types defined on the source Web server and then create the same associations of MIME types to file name extensions on the target Web server.

  • Configure SSL certificates. You must export server certificates for Secure Sockets Layer (SSL)-enabled Web sites from the source server, and then install the certificates on the target server after the migration process is complete.

  • Configure FrontPage Server Extensions users and roles. If FrontPage Server Extensions is configured to use a local user account on the source server as the FrontPage administrator, you must create a new user account, or designate an existing user account, for use on the target server. In addition, you must assign the user the same FrontPage role as the corresponding user had on the source server.

  • Configure IIS for ASP.NET applications. If you migrate ASP.NET applications from the source server, you might need to migrate the attribute settings in the Machine.config file that are used to set process-model behavior. When the target server is configured for worker process isolation mode, the attribute settings in the Machine.config file need to be converted to corresponding application pool settings. This is because ASP.NET uses the IIS process model when IIS is running in worker process isolation mode. For more information, see Migrating Machine.config Attributes to IIS 6.0 Metabase Property Settings later in this section.

Performing Application-Specific Migration Tasks

In addition to the IIS 6.0 configuration changes that are required, you might need to complete any migration tasks that are specific to the applications running on the source server. The application-specific steps that you might need to perform include the following:

• Modifying application code for compatibility with Windows Server 2003 and IIS 6.0. When the applications on the source server are not compatible with Windows Server 2003 and IIS 6.0, you need to modify the applications. Most of these modifications are required when applications use application programming interfaces (APIs) no longer supported by Windows Server 2003 and IIS 6.0.

• Installing additional software required by the applications. When applications on the source server require additional software that was developed by your organization, by Microsoft, or by other organizations, you need to install that software on the target server. This software can include filters and ISAPI extensions. You must obtain a version of the software that is compatible with Windows Server 2003 and IIS 6.0.

• Migrating MTS packages, COM objects, and COM+ applications. When your applications include MTS packages, COM objects, or COM+ applications, you must migrate them to the target server. For MTS packages, you need to rewrite the MTS as a COM+ application.

• Creating IP addresses that are used to uniquely identify the applications. Web sites and applications are uniquely identified by a unique IP address, a unique combination of an IP address and a TCP port, or host headers. When Web sites and applications on the source server are uniquely identified by IP addresses, you must create corresponding IP addresses on the target server and then configure the migrated Web sites and applications to use the new IP addresses.

• Creating users and groups that are used by the applications. When users that access the applications on the source server have accounts that are local to the source server, you need to create new accounts on the source server and then assign the appropriate NTFS permissions on the target server to the new accounts. When the user accounts are in Active Directory, you only need to assign the appropriate NTFS permissions on the target server to the accounts in Active Directory.

• Creating registry entries for the applications. When your applications store configuration information in the registry, you might need to create the same registry entries for the applications on the target server.

For information about using the IIS 6.0 Migration Tool to perform your migration, see Migrating Web Sites with the IIS 6.0 Migration Tool later in this section.