NT4.0 到 Windows 2003: IIS 迁移

偷瓜的贼

IIS 6.0 MIGRATION TOOL
The IIS 6.0 Migration Tool is a command-line utility for migrating Web site content and configuration settings from Internet Information Services (IIS) 4.0, IIS 5.0, and IIS 6.0 to IIS 6.0 running on members of the Microsoft Windows Server 2003 operating system family.  Using the migration tool saves time and reduces the chance of introducing errors by automating many of the repetitive processes involved in moving sites manually.  In addition, the migration tool maps some application-related IIS settings to their equivalent settings in IIS 6.0.
Note: The IIS 6.0 Migration Tool is not an end-to-end migration solution.  You cannot use it to migrate Web application-related components, such as database tables, stored procedures, or software, or applications, such as Microsoft Office, custom-built applications, or third-party applications.
1.1        Overview
Use the IIS 6.0 Migration Tool when you have performed a clean installation of Windows Server 2003 and you need to move a Web site or applications to new server.  The migration tool is especially useful when you do not have a setup program or deployment script for the Web site that you are migrating or when the setup program or deployment script cannot be used with IIS 6.0.
For example, an administrator who manages 100 Active Server Pages (ASP) sites on a server running Windows 2000 Server wants to move these Web sites to a server running IIS 6.0, but does not have a deployment script for the sites.  The administrator can use the migration tool as an alternative to manually re-creating the Web sites and moving the content.
Note: If you have a setup program or script for deploying the Web site that you want to migrate and you have modified it to run on Windows Server 2003, use the modified program or script, not the IIS 6.0 Migration Tool.
You can migrate Web content to target servers running Windows Server 2003 and IIS 6.0 from source servers that are running the following:
·         IIS 4.0 running on the Microsoft® Windows NT® Server operating system
·         IIS 5.0 running on the Microsoft® Windows® 2000 Server operating system
·         IIS 6.0 running on Windows Server 2003
Important: The IIS 6.0 Migration Tool cannot be used on source or target servers that are running IIS 6.0 in IIS 5.0 isolation mode.  Your source and target servers must be running IIS 6.0 in worker process isolation mode.
The migration tool does the following:
·         Backs up the IIS metabase configuration on the target server.
·         Migrates Web site content from the source server to the target server.  
·         You can change the path for migrated content so that it will reside in a new location on the target server.  You also can choose to migrate only the metabase configuration, not the content.
·         Copies file system access control lists (ACLs) for migrated content.
·         Copies the Web site’s IIS metabase configuration from the source server to the target server.
·         Maps IIS 4.0 and IIS 5.0 application isolation settings to IIS 6.0 application pool settings.  
·         An application pool is a grouping of URLs that are routed to one or more worker processes.
·         Writes operations to a log file.  
In addition, you can specify that the migration tool should do the following:
·         Change the Web root directory path from the source server to the target server.
·         Re-extend Microsoft® FrontPage® Server-extended sites.
·         Change the IP address, port, and host-header information of the migrated site to new values that you specify.
·         Change the site ID.
If you need to migrate multiple Web sites from the source server, you must run the migration tool once for each web site that you need to migrate.
The migration tool does not support migrating metabase nodes that are located below the site level.  Therefore, you cannot use it to migrate an individual virtual directory or a Web directory.
Note: You cannot use the IIS Migration Tool to migrate IIS 6.0-based sites to and from the same server.
1.2        Installing IIS 6.0
Install the IIS 6.0 Migration Tool only on the target server — the server that is running Windows Server 2003 operating system and IIS 6.0 and to which you want to migrate Web sites.  You can run the migration tool executable program from any location on the target server.  You do not need to install the tool on the source server—the server from which you want to migrate Web sites.  
Before you begin using the migration tool, ensure that the following conditions are met:
·         There is an established a network connection between the source and target servers.  
·         The IISAdmin service is running on both the source and target servers.
·         Administrative file sharing is enabled on the source server; for example, the server allows drive mapping of drives C$ and D$.
·         You have administrator privileges and are the administrator on both the source and the target servers.  
·         There is adequate hard disk space on the target server to accommodate the Web site content that will be migrated.
1.2.1           IIS 6.0 Migration Tool Syntax and Parameters
The IIS 6.0 Migration Tool uses the following syntax:
iismt.exe Server Website [/user Username] [/password Password] [/path path] [/serverbindings ServerBindings String] [/siteid SiteID | Replace] [/configonly] [/fpse] [/verbose] [/overwrite] [/noninteractive]
The following table lists the migration tool command-line parameters that you can use to specify required and optional information about the sites that you want to migrate and the target server environment.  

Parameter	Required?	Description
Server	Yes	The source server.  You can specify the name or the IP address of the source server.
Website	Yes	The site that you want to migrate.  You can specify either a site description, such as “Default Web Site,” or the metabase key path, such as W3SVC/1.
/user UserName	No	The user name you want to use when connecting to the source server.  You can specify either a UserName or a Domain\UserName.  If you do not specify a user name, the migration tool uses the current user’s credentials to connect to the source server.
/password Password	No	The password for UserName.
/path Path	No	The location for the migrated site’s root directory on the target server; for example, D:\Inetpub\Wwwroot.  The migration tool ignores the /path parameter if the /configonly parameter is specified.
/serverbindings ServerBindings String	No	Allows you to change the IP address, the port, and the host header information for the site that will be migrated.  The /serverbindings parameter uses the following syntax: IP:Port:Hostheadername; for example: 192.168.1.1:80:www.example.com.  The format for the ServerBindings String is the same as it is for the IIS metabase property ServerBindings, and you set it in exactly the same way that you set the property using utilities such as Active Directory Services Interface (ADSI) or Windows Management Instrumentation (WMI).
/siteid [SiteID] | Replace	No	The site ID for the Web site when it is created on the target server.  If you want the migrated site to overwrite a site that has that site ID on the target computer, use the Replace parameter.
/configonly	No	Instructs the migration tool to migrate only the IIS configuration, not the content files.
/fpse	No	Re-extends a FrontPage Server-extended site if that site was extended on the source computer.  This parameter is ignored if the /configonly parameter is used.
/verbose	No	Displays the metabase path copy and file copy operations on the screen as they occur.
/overwrite	No	Suppresses a message that prompts the user to confirm overwriting an existing destination file or folder when content is copied from the source to the target server.
/noninteractive	No	Suppresses messages that prompt the user for input.  When this parameter is used, the migration tool exits when it encounters the first error condition.  This is a useful parameter for invoking the migration tool from a batch file or script program.

The following examples illustrate how to use the command line to migrate Web sites.  
To migrate a site with the ID 1 from IIS-SERVER with default options, you would enter the following on the command line:
D:\iismt.exe IIS-SERVER w3svc/1
To migrate a site with the ID 1 from IIS-SERVER and to set the server bindings and new site ID, you would enter the following on the command line:
D:\iismt.exe IIS-SERVER w3svc/1 /serverbindings 192.168.1.1:80:www.site.com /siteid 100
To migrate a site with the ID 1 from IIS-SERVER, and to specify that the migration tool should connect with the user name AdminUser and the password passw@rd to IIS-SERVER, use the existing site ID, and use F:\Wwwroot\Inetpub as the new content location, you would enter the following on the command line:
D:\iismt.exe IIS-SERVER w3svc/1 /user AdminUser /password passw@rd /siteid replace /path F:\Wwwroot\Inetpub
1.3        Running the IIS Migration Tool
The IIS 6.0 Migration Tool performs the following tasks during migration:
·         Authentication
·         Metabase backup
·         Content migration
·         Configuration migration
·         FrontPage Server Extensions re-extension
·         Migration activity logging
Important: After migrating a Web site to a server, you need to ensure that any scripts and services required by the site are enabled on IIS 6.0.  To do this, use the Web Service Extensions node in IIS Manager.
1.4        Authentication
To use the migration tool, you must have administrative credentials on both the target and source servers.  If you do not specify a user name and password using the /user and /password parameters, respectively, the tool attempts to connect to the source server using the user name and password that you used to log on to the target server.  If you specify the user name only, the migration tool prompts you to enter a password before it attempts to connect to the source server.
1.5        Metabase Backup
The migration tool backs up the metabase settings of the source IIS Web server and saves the settings to a file named systemroot\System32\Inetsrv\Metaback\IIS Migration Tool Backup.MD##, where ## is a number starting at 0 and increasing by one for every backup that is performed.  If errors occur and you need to restore the source server to the last good configuration, you can use the iisback.vbs utility and specify the name of the backup file created by the migration tool.  For more information about iisback.vbs, see Backing Up IIS Configurations in IIS 6.0 Help.  
1.6        Content Migration
The migration tool migrates the following:
·         All files, folders, and subfolders that are located in the Web root directory for the Web site being migrated, for example, C:\Inetpub\Wwwroot.
·         All files, folders, and subfolders located in all virtual directories that belong to the site being migrated.
To prevent introducing security risks or overwriting IIS 6.0 system files on the target server, the migration tool does not migrate the configuration or content from the following virtual directories, or from any child nodes of these directories, if they are present:
·         IISSamples
·         IISHelp
·         IISAdmin
·         _Vti_bin
·         Printers
·         MSADC
·         IISADMPWD
The following rules apply when the migration tool migrates site content:
·         The migration tool prompts the user to confirm whether to overwrite files and folders on the target server that have the same name as the migrated files.  
·         In order for the migration tool to copy content files, the source server must be configured to allow an administrator interprocess communication (IPC) share to be created.  If the source server has content on a local drive, for example, on C:\Inetpub\Wwwroot, the tool builds a Copy command using a UNC path containing the server name and the path, for example, \\Server1\C$\Inetpub\Wwwroot.
·         The IIS 6.0 Migration Tool does not support including a UNC path when using the /path parameter.  To migrate content to a UNC share, you must map a drive letter and include it with the /path parameter.
1.6.1           Changing the Web Root Directory Path
Use the /path parameter to change the Web root directory path for the migrated Web site.  The migration tool moves the content to the new location on the target server, and it resets the metabase on the target server to reflect the path change.  For a virtual directory, the content is moved to the same location that it was in on the source computer.  
Consider a site with the following content structure:
·         Web root = C:\Inetpub\Wwwroot
·         VDIR1 = D:\Applications\App1
·         VDIR2 = E:\Application2\App2
When the migration tool is executed with the /path parameter set to f:\Inetpub\Wwwroot, the resulting content structure on the target server is as follows:
·         Web root = F:\Inetpub\Wwwroot
·         VDIR1 = D:\Applications\App1
·         VDIR2 = E:\Application2\App2
1.7        Migrating Sites with UNC File Shares
The migration tool ensures that source content that resides on a UNC share will not be migrated unnecessarily to that same share.  If the Web site root that is designated for migration contains a UNC path, the content will be migrated only if you specify a new path that is different from the original UNC path.  If a virtual directory within the site that is being migrated references a UNC path, the content is not migrated.
1.7.1           Setting File ACLs
The migration tool preserves file system ACLs that are set with well-known security identifiers (SIDs), machine accounts, or domain accounts (if the source server is in the same domain as the target server) for migrated content.  For example, the migration tool reapplies a file system ACL set for the Administrators group; however, the migration tool does not recreate an ACL set on a file for a unique local user, and the tool does not recreate the local user account on the target computer.
Important: The IIS 6.0 Migration Tool preserves ACLs only for files that are migrated to NTFS partitions.
1.8        Configuration Migration
The IIS 6.0 Migration Tool allows you to migrate the site node (IISWebServer) from the source to the target server.  The tool copies the key and property hierarchy and offers several options for changing the IIS configuration.
1.8.1           Setting Server Bindings Properties
The /serverbindings parameter allows you to reset the server bindings properties—IP address, TCP port, and host-header string—for the migrated site on the target server.  The /serverbindings parameter uses the following syntax:
IP:Port:Hostheadername.  
The migration tool validates the server bindings as follows:
·         The IP (IP address) field can be blank, which sets the value to All Unassigned, or it can specify any valid IPv4 address.
·         The Port field must contain a number in the valid port range.  You cannot leave the port field blank.
·         The HostheaderName field can be blank, which means that no host header value is assigned, or it can contain any valid host-header string.
Note: The server bindings property is MD_SERVER_BINDINGS for /lm/w3svc/ on the target server.
1.8.2           Setting Site ID Numbers
You can use the /siteid parameter to set a specific site ID for the migrated site on the target server.  You can use the Replace parameter to specify that the migrated site be assigned the same site ID on the target server that it has on the source server.  If a site with that site ID already exists on the target server, it will be replaced by the migrated site.  If you do not specify the site ID, IIS automatically generates a site ID for the migrated site, using the next ID in the sequence.
1.8.3           Assigning Sites to Application Pools
When you migrate a site running on IIS 4.0 or IIS 5.0, the tool automatically creates new application pools and assigns the applications to the new application pools according to their existing isolation settings.  
1.9        Migrating from IIS 4.0 and IIS 5.0
In IIS 4.0 and IIS 5.0, application isolation was achieved through the use of Microsoft Transaction Server (MTS)/COM+ applications.  The migration tool maps the legacy isolation settings to the new application pool settings, so applications have the same level of isolation in IIS 6.0 as they had originally.  
The migration tool places applications in application pools based on the MD_APP_ISOLATED value, as follows:
·         In-process applications — which run on the Web server as DLLs in Inetinfo.exe and are not protected from other applications running in-process — are placed in the application pool named InProcess.
·         Pooled applications — which run as DLLs in the same single instance of DLLHost.exe and are protected from the effects of applications running in high isolation — are placed in the application pool named Pooled.  
·         Isolated applications — which run as DLLs in their own DLLHost.exe and are protected from the effects of other applications running in medium or high isolation — are placed in a unique application pool.
The following table lists the application pools created by the migration tool.  

Application Pool Name	Description
SourceServerName_InProcess	Application pool that holds all migrated applications marked as in-process.
SourceServerName_Pooled	Application pool that holds all migrated applications marked as pooled.
SourceServerName_AppFriendlyName	Application pool that holds the migrated source application specified by AppFriendlyName.

1.10   Migrating from IIS 6.0 to IIS 6.0
If you want to consolidate servers or move sites to new hardware running on the same version of the operating system, you can use the IIS 6.0 Migration Tool to migrate sites from IIS 6.0 to IIS 6.0.  In this case, the migration tool migrates the application pools associated with those sites according to the following rules:
·         If the application pool exists on the target server, then the application being migrated is associated with the existing application pool.  If the application pool does not exist on the target, the migration tool creates the pool.
·         If an application pool does not already exist on the target server and properties are explicitly set for the source application pool, the properties are migrated to the application pool created on the target server.  If the application pool already exists on the target server, the source properties are not migrated.
·         Inherited application pool properties are never migrated.
1.11   Re-extending FrontPage Server Extensions
The /fpse parameter re-extends and upgrades a FrontPage Server Extensions-enabled Web site to FrontPage Server Extensions 2002.  The migration tool re-extends the site only.  It does not recreate local FrontPage Server users that might have been configured previously.  The migration tool can serve as a starting point for getting the FrontPage Server Extensions-enabled site up and running, but you might have to perform some activities after the migration is complete to recreate the FrontPage Server Extensions-enabled site exactly as it was on the source server.
Important: If you use the /configonly parameter, the migration tool does not attempt to reapply FrontPage Server Extensions.
The migration tool uses the Owsadm.exe command-line tool to apply FrontPage Server Extensions to the migrated site on the target server.  Owsadm.exe is available at LocalDrive:Program Files\Common Files\Microsoft Shared\Web Server Extensions\50\bin.  For more information about this tool, search for “owsadm” on MSDN, which you can access from the MSDN Online link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources.
1.12    Logging Migration Tool Activity
The IIS 6.0 Migration Tool logs its activity and saves the logs as a text file on the target server.  A new log file is created every time you run the migration tool.  The log file name format is systemroot\System32\LogFiles\IISMT\Iismt_%u%u%u_%u%u%u.log.  For example, a log file might be named systemroot\System32\LogFiles\IISMT\iismt_ 20021119_124828.log, where 20021119 represents the date (yyyy/mm/dd) and 124828 represents the time (hh/mm/ss) that the log file was created.
The log file contains general operation information, lists of migrated properties, and file copy operations.  It also contains Win32 error messages for operations that failed.

1.13   Post-Migration Tasks
The IIS 6.0 Migration Tool automates many of the processes related to migrating Web sites, but it does not perform all steps that might be required during the migration process.  
Note: When Migrating Web Servers, you will also have to test the new web servers to validate that each web site from the source environment exists, works, and is configured properly for all the client operating system versions identified during the assessment.
Depending on your environment and the type of Web sites, applications, and content on your servers, you might need to perform some tasks after the migration is complete to ensure that your sites and applications perform as expected.  Post-migration tasks may be required for:
·         Applications
·         Content
·         FrontPage Server Extensions
·         IIS configuration
This section describes the tasks that are required for each of these categories.
1.14   Application-Related Post-Migration Tasks
The following table lists the post-migration tasks associated with applications.  

Task	Description
Register components	You must use Regsvr32.exe to manually register any DLLs that require registration.  Additionally, you must recreate the components’ COM+/MTS packages if they are required.
Copy content or binaries not stored in the Web site root directory	You must manually copy files that are stored outside the Web site root directory to the target server.  For example, you must copy DLLs that are stored in a directory named bin on the hard drive.
Set Open Database Connectivity (ODBC) or data source name (DSN) settings	If the application requires an ODBC connection, you must recreate it manually.   Note A file-system DSN can be reused if it exists in the Web content that is copied to the target server.
Create application-specific registry settings	You must create application-specific registry settings manually.
Reinstall dependent software	You must reinstall dependent third-party software, such as Perl, manually.
Convert code	If code needs to be changed or recompiled to run on Windows Server 2003, you must make those changes manually.  For example, you need to replace CDONTS in ASP scripts with CDOSYS.
When migrating from IIS 5.0 to IIS 6.0, recreate ASP.NET process model settings	If you have ASP.NET applications that use process model configuration in machine.config, such as recycling, Web gardens, and health detection, you must manually reset that configuration in IIS 6.0 application pools.  As part of a platform migration, these ASP.NET settings are natively part of IIS 6.0 and, therefore, will be disregarded if you do not set them manually in IIS 6.0.

1.15   Content-Related Post-Migration Tasks
The following table lists the post-migration tasks associated with Web content.

Task	Description
Reset local user accounts, groups, and ACLs	If you have set file ACLs with local users or groups on the source server, you must recreate the users or groups and reset the ACLs on the target server.
Copy content stored outside of the Web root or virtual directories	If you have content on the source server that is used by the application that will be migrated but that is not stored in the Web root or virtual directories, you must migrate it manually. For example, ASP code that uses Server Side Include files that point to some location outside the Web root must be migrated manually.

1.16   FrontPage Server Extensions-Related Post-Migration Tasks
The following table lists the post-migration tasks associated with FrontPage Server Extensions.

Task	Description
Migrate the FrontPage Server Extensions Administrator user account	The migration tool does not migrate the site administrator account.  If this is a local account, you must also recreate it on the target server.
Migrate Custom FrontPage Server Extensions security settings	If the site you migrated uses FrontPage Server Extensions, and the original site had custom FrontPage Server Extensions security settings, the migration tool might not transfer those settings correctly to the new site.  Open the FrontPage Server Extensions Administration tool and check to see whether you need to reset the FrontPage security settings.

1.17   IIS Configuration-Related Post-Migration Tasks
The following table lists the post-migration tasks associated with IIS configuration.  

	Replated Post-Migration Tasks
Task	Description
Reset the anonymous user name and password for local accounts	If the AnonymousUserName and AnonymousUserPass properties are set to a local account and to a password for a site or virtual directory that has been migrated, these properties must be reset on the target server to specify a user that exists and a password.  Alternatively, you could create a new user and reset the metabase. The IIS 6.0 Migration Tool does not recreate anonymous user accounts if they don’t exist on the target server.
Reset the user name and password for the application identity	If the WAMUserName and WAMUserPass properties are set to a local account and to a password, respectively, for a site or virtual directory that has been migrated, these properties must be reset on the target server to specify a user that exists and a password.  Alternatively, you could create a new user and reset the metabase.
Reset the %windir% location	If you migrate a Web site to a target server that has a different Windows directory (%windir%) location than the source server did, you must manually change the properties in the metabase that reference the %windir% location on the source server. These properties can include: ·         HTTPErrors   The HttpErrors property specifies the custom error string sent to clients in response to HTTP version 1.1 errors. ·         ScriptMaps   ScriptMaps contain references to paths with default Internet Server Application Programming Interfaces (ISAPIs), such as C:\Windows\System32\Inetsrv\Asp.dll. Note If you migrate the Default Web Site on Windows NT 4.0 or Windows 2000, you must reset the HTTPErrors property to contain the new path for Windows Server 2003, even if the Web sites exist on the same drive, because this property is set explicitly in a default IIS 6.0 installation. To reset the HTTPErrors property, open the text metabase in Notepad, and then replace WINNT with %WINDIR%. Alternatively, you can remove the HTTPErrors or ScriptMaps property to allow the value to be inherited from the parent property.
Change the physical location of a virtual directory	The migration tool allows you to change only the site root directory.  It does not allow you to change paths of virtual directories under the site root virtual directory.  If the target server does not have a drive for the virtual directory, then you must copy content manually and create a new virtual directory path.   In addition, the migration tool can override content if it migrates multiple virtual directories that have the same path.  For example, if you migrate a virtual directory with the path F:\Dir, and F: does not exist on the target server, you must create a new location for the content and reset it in the metabase, or create a new F: drive.
Migrate certificates	You must reinstall or manually migrate certificates that are installed on the source server.
Migrate ISAPI filters and extensions DLLs	The migration tool migrates ISAPI extensions or filters that exist in the migrated content. You must manually install ISAPI extensions or filters that do not reside within the migrated content.
Migrate IIS registry settings	The migration tool does not migrate and save in the IIS 6.0 metabase those IIS 5.0 settings that were stored in the registry. Note: Most of these settings have been deprecated for IIS 6.0.
Reset MIME-type properties	The IIS Migration Tool does not migrate MIME-type properties.  You must reset MIME types manually on the target server.
Update WebServiceExtRestrictionList	·         You might need to enable ISAPI applications on the target server after you have migrated the Web site.  You will have to do this in the following situations: ·       If you migrated an ASP site to a target server on which ASP is not enabled.   ·         Note: IIS 6.0 does not enable ASP by default. ·       You migrated an application with a custom ISAPI extension that is not enabled by default and which you have not added to the Web Services Extensions list on the target server.  In this case, you must manually create and enable the application on IIS 6.0.
Copy log files	If you want IIS log files to be moved to the target server, you must copy them manually.

1.18   ChkLnks UI
1.18.1        Link Check Wizard
　　From the introductory screen, click Next.
　　If ChkLnks does not find any dead links, an informational diologue box appears, which contains the text: No Dead Link Files were found.
　　Click OK to terminate the wizard.
1.18.2      Select links to remove
　　The "Select the links to remove" page provides an interface to remove dead links found by the ChkLnks tool.  This page has the following options:

	Selecting Links to be Removed
Option	Description
Links to remove window	Inside the Links to remove window is a list of dead links.  Click a link to mark it for deletion.  Right-click a file name to view the details of that dead link.  The details included are File name, Location of the shortcut file on the hard disk, Resolves to physical location, and Error Status.
Select/Deselect all button	The Select/Deselect all button selects or deselects all dead links.   To select all the links, click the Select all button.  The button toggles to read "Deselect all." To deselect all the links, click the Deselect all button.  The button toggles to read "Select all."
Next button	Deletes the selected dead links and exits the Link Check Wizard
Back button	Returns to the previous wizard page
Cancel Button	Cancels the wizard.

2.0    IIS 6.0 Resource Guide tools download site
http://www.microsoft.com/downloads/details.aspx?FamilyID=80a1b6e6-829e-49b7-8c02-333d9c148e69&displaylang=en