The In’s and Out’s of the IIS 6.0 Migration Tool The In’s and Out’s of the IIS 6.0 Migration Tool Chris Adams Web Platform Supportability Lead Microsoft Corporation

Agenda  Introduction to “Migration” Scenario’s  Platform Requirements for IIS 6.0 Migration Tool  Where can I install it? Use it?  Upside of the IIS 6.0 Migration Tool  Migration of Website and Virtual Directory  Migration of Web Content  Auto extending of FPSE-Enabled Webs  Demonstration One  Downside of the IIS 6.0 Migration Tool  Lack’s Server Paths’ intelligence  Requires use of Administrative Shares (Security)  Failure to create any custom or domain accounts used in web environments  Demonstration Two  Demonstration Three  Summary

Introduction to “Migration” Scenario’s  The term “Upgrade”  Upgrade indicates a in-place upgrade on existing hardware  The term “Migration”  Migration indicates that greater than 1 server is being used, such as the case in a simple migration – One Source Server | One Target Server

Introduction to “Migration” Scenario’s Source Server Target Server Administrator’s Workstation Terminal or Remote Desktop Access Pulls data from Source

Platform Requirements for IIS 6.0 Migration Tool  Installation  There is no installation process for the IIS 6.0 Migration Tool  It is a single executable, Iismt.exe  Running Iismt.exe  Copy iismt.exe to Windows 2003 Server (the target server)  Source Servers:  Windows NT 4.0 & IIS 4.0  Windows 2000 & IIS 5.0  Windows 2003 & IIS 6.0  Unix | Linux & Apache (requires special version of IIS 6.0 Migration Tool

IIS 6.0 Migration Tool: How it Works ParameterRequired?DescriptionServerYes The source server. You can specify the name or the IP address of the source server. WebsiteYes 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: :80: 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. /configonlyNo Instructs the migration tool to migrate only the IIS configuration, not the content files. /fpseNo 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. /verboseNo Displays the metabase path copy and file copy operations on the screen as they occur. /overwriteNo 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. /noninteractiveNo 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.

IIS 6.0 Migration Tool: How it Works Fab01 Fab2k3 Read Metabase.bin Copy Config from w3svc/223 to Fab2K3 into current Metabase For each Path (IIsWebServer, IIsWebVirtualDir), copy content from Fab01 to Fab2K3 to directory on the Target Server Extend w3svc/223 for use of FPSE Clean Up!

Upside of the IIS 6.0 Migration Tool  Very easily migrates website and virtual directories configuration information  Uses standard SMB Connections for migrating content, up to and including Dynamic Content such as ISAPI’s, CGI, and PHP.  Supports UNC paths for sites and virtual directories as long as permissions are adequate on the remote share  Automatically Extends FrontPage webs where the administrator chooses using one easy switch

Demonstration One Seeing a failure with ISAPI and the IIS 6.0 Migration Tool The purpose of this demonstration is to show how the migration tool will move dynamic content such as ISAPI or CGI, but will still not register the ISAPI\CGI hence still failing and causing clean up.

Upside of the IIS 6.0 Migration Tool  The ability to restrict the tool to only copying the configuration using the easy switch /config  Easily creates and tracks usages of the Migration Tool by creating a file in the following directory: systemroot\System32\LogFiles\IISMT\Iismt_datetime_number.log

Downside of the IIS 6.0 Migration Tool  Failure to give detail output of errors  Invalid Anonymous Account?  Because we are using custom anonymous accounts and that account doesn’t exist on the target server  Invalid Custom Error Paths?  The path isn’t valid, such as WINNT instead of Windows  Failure to migrate FTP\SMTP sites  SMTP sites are often relied on by applications on the server, but the tool has no method of moving important SMTP sites

Downside of the IIS 6.0 Migration Tool  Fails to account for new Web Service Extension if ISAPI\CGI is copied  The existence of ScriptMaps are copied by IIS 6.0 Migration Tool but the WebServiceExtensions property “WebSvcExtRestrictionList” hence they fail to work without administrator intervention  If servers have extensive FPSE usage, the migration tool fails to copy any built-in or custom roles  Only workaround is to rebuild all the roles which can be time consuming

Downside of the IIS 6.0 Migration Tool  Fails to move any pertinent database connections in the form of ODBC  Requires these to be moved manually  Requires that Administrative Shares on Source Server and Target Server  For example, on the target server, if the content is stored on d:\inetpub\wwwroot then the Administrative Share D$ must exist

Downside of the IIS 6.0 Migration Tool Conclusion: The IIS 6.0 Migration Tool is very useful in scenarios where large installations are migrated to IIS 6.0. However, if the IIS 4/5 installation is a large FPSE environment then the Post-Migration work will be large and daunting. In these situations, investigate doing a in-place upgrade or do a staggered migration.

Summary  The IIS 6.0 Migration Tool is very useful and offers administrators a very quick method of copying the IIS configuration  The IIS 6.0 Migration Tool is very useful because it moves configuration AND content  Allows a migration of many different servers to be consolidated to one single IIS 6.0 server

Demonstration Two Migrating from IIS 4.0 to IIS 6.0 using the Migration Tool Let’s just do it…

Demonstration Three Migrating from IIS 5.0 to IIS 6.0 using the Migration Tool Let’s just do it…

References and Resources  IIS 6.0 Migration Tool Documentation  spx?FamilyID=56fc92ee-a71a-4c73-b628- ade629c89499&DisplayLang=en spx?FamilyID=56fc92ee-a71a-4c73-b628- ade629c89499&DisplayLang=en spx?FamilyID=56fc92ee-a71a-4c73-b628- ade629c89499&DisplayLang=en  Resource Guide Information for IIS 6.0 Migration Tool  74fe970d-4a7d f5d e7f7/09_CHAPTER_6_Migrating_IIS_ Web_Sites_to_IIS_6.0.doc 74fe970d-4a7d f5d e7f7/09_CHAPTER_6_Migrating_IIS_ Web_Sites_to_IIS_6.0.doc 74fe970d-4a7d f5d e7f7/09_CHAPTER_6_Migrating_IIS_ Web_Sites_to_IIS_6.0.doc

Q & A