Install the IIS 6.0 Migration Tool by completing the following steps:
Download the IIS 6.0 Migration Tool and user guide from the Microsoft Download Center (or see the Microsoft Download Center link on the Web Resources page at http://www.microsoft.com/ windows /reskits/webresources).
Verify that the migration tool operates correctly by typing iismt at the command prompt.
This command starts the migration tool and displays Help for the tool only. The migration process does not actually begin.
Verify that clients are no longer accessing the Web site on the source server by completing the following steps:
Prevent new clients from accessing the site by pausing the site.
To ensure that service to clients is not interrupted , pause the Web site on the source server before taking the server offline. Pausing a site prevents the site from accepting new connections, but does not affect requests that are already being processed .
Monitor the active Web connections to determine when clients are no longer accessing the source server.
To ensure that service to clients is not interrupted, monitor the Web server for any active Web connections before taking the Web server offline. Both IIS 4.0 and IIS 6.0 include performance monitor counters that can be used to monitor the active Web connections. Monitor the active Web connections to ensure that one of the following is true:
The number of active Web connections is zero.
All active Web sessions can be accounted for and can be terminated .
When the number of active Web counters is zero, stop the WWW service. Ensure that the IIS Admin service is running because the migration tool requires the IIS Admin service.
The following procedures explain how to verify that clients are not accessing the Web site.
To pause a Web site by using Internet Service Manager in IIS 4.0
From the Start menu, point to Programs , click Windows NT 4.0 Option Pack , click Microsoft Internet Information Server , and then click Internet Service Manager .
In Internet Service Manager, right-click the Web site that you want to pause, and then click Pause .
If a Web site stops unexpectedly, Internet Service Manager might not correctly indicate the state of the site. In IIS, right-click the Web Sites folder and then click Refresh to see the current state of the Web site.
To monitor active Web connections in IIS 4.0
Open Administrative Tools, and then click Performance Monitor .
Click Edit , and then click Add to Chart .
The local computer is listed in the Computers dialog box. To monitor any other computer on which the monitoring console is run, click the Browse button, select a computer from the Select Computer list, and then click OK .
In Performance object , click Web Service to monitor active Web connections.
In Counters , click Current Connections .
The performance counters are not installed when IIS 4.0 is installed on Windows NT Server 4.0. In this case, if the performance counters have not been manually enabled, they do not appear in the Counters list. For more information about enabling the performance counters, see article 226512, How To: Reinstall IIS 4.0 Performance Monitor Counters, in the Microsoft Knowledge Base. To find this article, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources.
In Instances , click _Total .
Click Add , and then click Done .
To stop the Web Service in IIS 4.0
Open Control Panel, and then double-click Services .
On the Services page, click World Wide Web Publishing Service, click the Stop button, and then click Close .
Up to this stage in the migration process, you have completed the initial preparation, deployed the target server, and installed the IIS 6.0 Migration Tool. You should now be ready to run the tool.
The scenario described in this chapter assumes that the following conditions apply:
You are logged on with an account that is a member of the Administrators group on both the source server and the target server.
You know the name of the source server.
You know the friendly name of the Web site on the source server.
You want to reapply FrontPage Server Extensions to the migrated site on the target server.
You want to display the progress of the migration tool on the screen.
If your situation is different, you might need to run the migration tool with different parameters. For more information about each of the parameters of the IIS 6.0 Migration Tool, see the IIS 6.0 Migration Tool User Guide that accompanies the tool.
The following example shows the format of the IIS 6.0 Migration Tool command for the scenario and assumptions described in this chapter:
iismt SourceServer WebSite / fpse / verbose
Using the sample server name and the friendly name of the Web site in this scenario, the command looks like this:
iismt SEA-FAB-MS01 "Fabrikam Sales Site" / fpse / verbose
To run the IIS 6.0 Migration tool, replace the sample server name and friendly name with the IP address of your source server and the friendly name of your Web site.
Table 6.4 describes the IIS 6.0 Migration Tool parameters used in this scenario.
Required or Optional
Identifies the source server by providing the server name.
Identifies the site to be migrated by providing the Web site description (friendly name), for example, Default Web Site.
Re-applies FrontPage Server Extensions to the migrated site on the target server.
Displays metabase path copy and file copy operations to the screen during the migration process.
Before continuing with the Web site migration, verify that the IIS 6.0 Migration Tool migrated the Web site content and configuration information successfully. Because you specified the / verbose parameter, the migration tool displays output that indicates the success or failure of the migration. If the output indicates that errors occurred, you can use the IIS 6.0 Migration Tool log file to resolve any errors.
Verify that the IIS 6.0 Migration Tool ran successfully by completing the following steps:
Open systemroot \System32\LogFiles\IISMT\iismt_ date _ time .log in a text editor and determine whether any errors occurred (where date is the date when the tool ran and time is the time the tool started running).
Review the log file and resolve any problems that occurred during migration before proceeding to the next step in the process.
The IIS metabase stores most IIS configuration values, which are known as metabase properties . For example, the IIS metabase stores a metabase property that references the location of the systemroot, which is the path and folder name where the Windows system files are installed.
The IIS 6.0 Migration Tool migrates metabase properties that reference the systemroot folder on the source server, but does not update the references to point to the systemroot folder on the target server. If the location of the systemroot folder on the target server does not match the location of the systemroot folder on the source server, you will not be able to view your Web site on the target server. You must modify the metabase settings on the migrated Web site to reference the correct systemroot folder on the target server. Because the default systemroot folder name changed from WINNT to Windows in Windows2000 Server and later versions, you might need to manually modify the metabase properties that reference the systemroot folder on the target server. To implement changes to some metabase properties, you might need to restart the server.
Metabase properties that reference the location of the systemroot folder can include the following:
HttpErrors. The HttpErrors metabase property specifies the custom error string sent to clients in response to HTTP 1.1 errors. If you migrate the Default Web Site on Windows NT 4.0, you must reset the HttpErrors metabase property to contain the systemroot folder for Windows Server2003, even if the systemroot folder exists on the same drive on both the source and target computer.
ScriptMaps. The ScriptMaps metabase property specifies the file name extensions of applications that are used for script processor mappings. This property contains references to paths with default ISAPIs, such as C:\Windows\system32\inetsrv\asp.dll.
Compensate for the differences in the location of the systemroot folder on the target server by completing the following steps:
Enable the IIS 6.0 metabase edit-while-running feature.
Open the MetaBase.xml file in Microsoft Notepad.
Search for any references to the path of the systemroot folder on the source server and replace these references with the path of the systemroot folder on the target server.
For example, if the source server was installed in C:\WINNT and the target server is installed to C:\Windows, you should replace any occurrences of C:\WINNT with C:\Windows .
Save the MetaBase.xml file.
Disable the metabase edit-while-running feature.
For more information about the edit-while-running feature, see Metabase Edit-While-Running Feature in IIS 6.0 Help, which is accessible from IIS Manager.
The following procedures explain how to modify IIS 6.0 metabase properties.
To enable the edit-while running feature of the metabase by using IIS Manager
In IIS Manager, right-click the local computer, and then click Properties .
Select the Enable Direct Metabase Edit check box, and then click OK .
To modify the IIS metabase
Open the Metabase.xml file in a text editor. The default path to this file is systemroot \system32\inetserv\metabase.xml.
Modify the metabase properties that you want to change in the Metabase.xml file.
Save the changes to the file, and close the text editor.
Most changes to metabase properties are automatically recognized by IIS; in some cases, you must restart IIS for the metabase property changes to go into effect.
To disable the Edit-while running feature of the metabase by using IIS Manager
In IIS Manager, right-click the local computer, and then click Properties .
Clear the Enable Direct Metabase Edit check box, and then click OK .