IIS Migration Wizard Topics | Previous | Next
This topic provides the following information:
Supported Source Platforms
Note
In this documentation, "source" refers to the computer from which you are migrating, and "target" refers to the computer to which you are migrating.
The IIS Migration Wizard can migrate Web sites from the following source platforms to Windows 2000 Server and IIS 5.0:
- UNIX with Apache HTTP Server 1.3
- Windows NT Server 4.0 with Netscape Enterprise Server 3.5.1
- Windows NT Server 4.0 with IIS 4.0
- Windows 2000 Server with IIS 5.0 (you can use this feature to replicate an IIS Web server to another computer)
Note
Microsoft Peer Web Services is not supported as a migration target or source.
The following conditions must be met in order for the IIS Migration Wizard to run correctly:
- The target computer must have Web access to the source computer.
- The person running the wizard must have local computer administrator rights on both the source and the target computers.
- The target computer must be running Windows 2000 Server and IIS 5.0. It should also have a default configuration.
- The source platform must be supported, as described previously in this topic.
- A source computer running Apache HTTP Server or Netscape Enterprise Server must have Perl 5.x installed.
- During a migration, the IIS 5.0 Default Web Site must be running on the target computer.
- For migrations from IIS, the IIS Default Web site must be running on the source computer. If the Default Web Site has been deleted or renamed, then the first Web site that appears under the Administration Web Site in the IIS snap-in must be running.
- For migrations from Apache HTTP Server and Netscape Enterprise Server, the Web server must be running on the source computer.
- Total content involved in a single migration cannot exceed 4 gigabytes (GB). If content exceeds this limit, you can perform separate migrations for virtual Web sites. If you have only one Web site, you can decrease the content in a single migration by creating virtual Web sites that each refer to a portion of the content. You can then conduct separate migrations for the virtual Web sites.
- As described later in Migrating UNIX Files and Applications, before starting a migration from Apache HTTP Server, you must make sure that file names and directory names adhere to Windows conventions. Otherwise, some files and directories could be overwritten.
- It is strongly recommended that you uninstall IIS Migration Wizard source and target components after completing the migration process. Leaving these components installed could pose a security risk. On a Windows-based computer, you uninstall the components by using the Add/Remove Programs utility in Control Panel. On a UNIX-based computer, you uninstall the components by deleting the [webroot]/iismu directory and the [cgibin]/iismu directory.
- For Apache HTTP Server and Netscape Enterprise Server migrations, you must specify a password when installing the source component. You then enter this password during the migration process when connecting to the source computer from the target computer.
- You must have local computer administrator rights on both the source and target computers in order to use the migration wizard. Being a domain administrator satisfies this condition.
Once you have installed the IIS Migration Wizard source component, you are ready to run the wizard and conduct a migration. For more information, see Installing the IIS Migration Wizard.
To run the IIS Migration Wizard
- Make sure you have satisfied the conditions for using the wizard as described in Requirements for Running the Wizard. If you have not done so, the wizard will not run correctly.
- If you have installed the target component, log on to the target computer as Administrator, and then select IIS Migration Wizard from Programs on the Start menu. This starts the wizard.
Or:
If you have not installed the target component, log on to the target computer as Administrator, and then connect to http://[source]/iismu/welcome.htm, where [source] is either the computer name or the IP address of the source computer. This starts the wizard. When prompted, choose the option to install the target component. When the installation is complete, continue with the wizard.
- When prompted, select the server content, settings, and MIME information to migrate for each virtual server. When migrating from Netscape Enterprise Server or Apache HTTP Server, you can also choose the option to migrate users, as described later in Migrating Netscape and Apache Users. The IIS Administration Web Site is not migrated by default, but you can select an option to migrate it.
- To get help while using the wizard, click Help at the bottom of the dialog box.
- When satisfied with your selections, click Next. The wizard then starts the migration, which can take from several minutes to over an hour. When the migration is complete, the wizard displays a list of warnings, as well as additional steps required to complete the migration.
- To save the activity log or the migration archive file, which contains migrated content and settings, click the appropriate link at the bottom of the wizard screen. For more information, see Saving Archive Files.
- To close the wizard, click Finish.
Important It is strongly recommended that you uninstall both the source and target components after completing the migration process. Leaving these components installed could pose a security risk. For more information, see Important Security Information.
For More Information
For more information about migrated configuration settings, see IIS Migration Wizard Migrated Settings. For more information about how content is migrated, including applications, see Completing the Migration of Content.
After you have taken all the steps to complete the migration, you can start the new Web site in the IIS snap-in. To do this, select the new Web site, and then click the Start button on the toolbar. Be aware that the Default Web Site serves IIS 5.0 documentation and samples, and that it runs on port 80 by default. If you try to run your new Web site on the same port, you will create a conflict. If you change the port number of the Default Web Site, you will no longer be able to access your documentation. Therefore, if you are running a single Web site, it is best to run it under the Default Web Site. For information about running more than one Web site at a time on IIS 5.0, see the "Adding Sites" topic in the IIS 5.0 online product documentation.
You can run the IIS Migration Wizard again on the same target computer and use either the same source Web sites or different source Web sites. The following are the results for each scenario:
- Using the same source Web site, and giving it the same name during a migration, results in a duplicate virtual Web site in the IIS 5.0 snap-in. The new Web site is given the same name as the original Web site, with an appended serial number. All Web site content contained in Inetpub\[Web Site], where [Web Site] is the name of the original Web site, is overwritten by content from the source Web site, and both sites refer to the new content.
- Using the same source Web site, and giving it a new name during a migration, results in a new virtual Web site, with the new name, in the IIS 5.0 snap-in. Source Web site content is written to Inetpub\[New Web Site], where [New Web Site] is the name you gave the new Web site.
- Using a different source Web site creates a new virtual Web site in the IIS 5.0 snap-in and a new directory of source content in Inetpub\[New Web Site], where [New Web Site] is the name you gave the new Web site.
To run the wizard again
- If necessary, install the source component on the source computer, as described in Installing the IIS Migration Wizard.
- Follow the procedure given in Running the IIS Migration Wizard.
During a migration from Netscape Enterprise Server or Apache HTTP Server, you can select the option to migrate a user database. If you choose this option, the wizard creates a user file and stores it in a location you specify. Once the migration is finished, you can use Addusers.exe, a Windows 2000 Resource Kit tool, to import the users to Windows 2000 Server. For instructions on using Addusers.exe, click Help on the final wizard screen.
The IIS Migration Wizard copies all source Web site content to the target computer. It also performs much of the necessary configuration in order for IIS 5.0 to serve the content. However, for certain types of content you might need to take additional steps to complete the migration. This topic describes the directory structure the wizard creates for content and the additional steps you might need to complete the migration.
The IIS Migration Wizard places content in the following directory structure that it creates in Windows Explorer on the target computer: Inetpub\[source]\[drive]\[directory structure], where [source] is the computer name or IP address of the source computer, [drive] is the drive on which the content was stored on the source computer, and [directory structure] is the directory structure as it exists on the source computer.
The wizard configures IIS 5.0 properties for migrated content, with the following results:
- Web pages are configured to be served correctly. You might need to change UNIX-style file names might to reflect Windows conventions. For more information, see Migrating UNIX Files and Applications.
- CGI applications are placed in a directory with execute permissions enabled. You might need to take additional steps in order for your CGI applications to run on IIS 5.0, particularly UNIX CGI applications. For more information, see "Migrating a Web Server to IIS 5.0" in the Microsoft® Windows® 2000 Resource Kit Internet Information Services Resource Guide.
- ASP applications with relative paths are configured to run correctly. You might need to correct absolute paths in .asp files to reflect the new directory hierarchy.
- ISAPI extensions are configured to run correctly.
- NSAPI extensions are migrated, but are not converted to a format that runs on IIS 5.0.
- DLLs that are stored in Web content directories on the source computer are configured to run correctly. DLLs stored outside Web content directories are not migrated.
- COM objects that are stored in Web content directories on the source computer are copied to the appropriate directory. However, to complete the migration of COM objects, you must manually run Regsvr32.exe. COM objects stored outside Web content directories are not migrated.
- ODBC sources are not migrated.
- Security certificates are not migrated.
For more information
For more information about additional steps you might need to take to migrate Web site content, especially from the UNIX environment, see Migrating UNIX Files and Applications, next.
Because of operating system differences between UNIX and Windows 2000 Server, you might need to make a few changes to content files and directories that you migrate from Apache HTTP Server.
Before migrating from Apache HTTP Server, it is important to make sure that your file and directory names adhere to Windows conventions. The IIS Migration Wizard overwrites any files that have duplicate names according to Windows conventions, when they exist in the same directory on the source computer. If the wizard encounters a file with the same name as another file in a directory, even if the letters have different cases, it overwrites the file that it encountered first with the "duplicate" file. The wizard overwrites directories in the same manner, at the directory level.
Besides correcting duplicate file names, you might need to remove "illegal characters" from file names. The wizard retains the UNIX-style names of migrated files and directories, and IIS 5.0 will serve these files correctly. However, you might encounter some problems when working with your files and directories in the Windows file system if their names contain any the following characters:
/ \ : * ? " < > |
In addition, you might need to change file names and path names within application files so that they reflect Windows conventions. For more information on migrating applications, see "Migrating a Web Server to IIS 5.0" in the Internet Information Services Resource Guide.
The IIS Migration Wizard provides the option to save two archive files: a .cab file containing migrated content and settings, and a .log file containing a list of events that occurred during the migration. From the .cab file, you can restore the settings and content of a particular migration, as described in the next topic. By reviewing the events recorded in the .log file, you can troubleshoot any problems with the migration.
At the end of a migration, the wizard provides the option to save the two archive files to a location that you specify. If you do not choose the option to save these files, and then later discover that you need them, you can find them in the %SystemRoot%\System32\inetsrv\iismu directory on the target computer. By default the files are named [source].cab and [source].log, where [source] is either the computer name or the IP address of the source computer. For example, if the source computer has the computer name "SomeName," the wizard would name the files SomeName.cab, and SomeName.log. However, be aware that the next time you run a migration, these files will be overwritten, so it is highly recommended that you save them to a different location when the wizard provides this option.
For each migration, the IIS Migration Wizard provides the option to save a .cab file that archives migrated settings and content, as described previously. If you make changes to a migrated Web site that you later want to "undo," or if your data becomes corrupted, you can restore the original settings and content. You do this by running the wizard again and referencing the .cab archive file rather than a source Web server. You can also use this method to replicate migrated settings and content to another computer running Windows 2000 Server and IIS 5.0.
The wizard restores or replicates migrated settings and content as follows:
- If, in the IIS 5.0 snap-in, the wizard encounters a Web site with the same name as the Web site for which the archive .cab file was created, it restores the Web site settings to the state recorded in the .cab file. The wizard also overwrites any content contained in Inetpub\[Web Site Name]\ folder with corresponding content from the archive .cab file. [Web Site Name] is a folder with the same name as the migrated Web site. If the wizard does not find a folder with this name, it creates a folder with this name and copies the content into it.
- If, in the IIS 5.0 snap-in, the wizard does not encounter a Web site with a name that corresponds to the name of the archived Web site, it creates and new Web site with this name. It also copies all of the archived content to Inetpub\[Web Site Name]\, where [Web Site Name] is a folder the wizard creates with the same name as the migrated Web site.
To restore or replicate migrated settings and content
- Log on to the target computer (the one onto which you want to replicate or restore settings and content) as Administrator.
- If necessary, install the target component, as described in Installing the IIS Migration Wizard.
- Select IIS Migration Wizard from Programs on the Start menu. This starts the wizard.
- On the Welcome page, click Next.
- In Step 2: connect to the source server, select the option to use the archive file.
- In the box, type the path and file name of the archive .cab file, and then click Next.
- Click Next on each subsequent screen until the migration begins. Once started, the process takes from a few minutes to over an hour, depending on the amount of content being restored or replicated. When it is complete, the wizard displays a list of warnings, as well as additional steps required.