IIS 6.0 Migration Tool V1.1
Microsoft just released an updated version of IIS 6.0 Migration tool - version 1.1. Previous version 1.0 was released at 24th April, Version 1.0 was bundled with IIS 6.0 Reskit Tool as well. Here's the KB content installed together with this version. Note the KB 839721 is NOT online at support.microsoft.com yet.
----
Title: IIS6 Migration Tool version 1.1
The information in this article applies to:
- IIS6 Migration Tool 1.0
SYMPTOMS
==========
A new Version of the IIS6 Migration Tool is released to corrects the following problems.
1- Cannot spawn new worker processes during the migration.
If the Migration is performed to a live poduction IIS6 server, existing sites may not serve properly until the migration completes. This behavior was because the migration tool locks the metabase during the migration. In the new version the migration tool does not lock the metabase and hence existing sites on the destination server will continue to serve during the migration.
2- Permissions of the AdminACL for the W3SVC/ in the IIS 6.0 metabase are incorrect after migration.
The migration tool did not migrate the AdminACL correctly for the W3SVC/. This resulted to web applications not funtioning on the target IIS 6 server. Users may get "500 Internal Server Error" when browsing the migrated ASP web application or "Server Application is Unavailable" when browsing the migrated ASP.NET application.
3- Migration Tool does not migrate nested applications correctly.
The migration tool did not migrate nested application properly. The AppRoot metabase key is migrated as (/LM/W3SVC//Root/....) instead of (/LM/W3SVC//Root/....) which resulted to web application not bering served. Users may get "500 Internal Server Error" when browsing the migrated ASP web application or "Server Application is Unavailable" when browsing the migrated ASP.NET application.
RESOLUTION
===========
A new version of the IIS6 Migration Tool (version 1.1) has been released to address the above issues.
More Information:
=============
- If you are migrating from NT4 with FPSE 98, and you choose to migrate with /fpse switch, it is possible that the Server Extensions will not function properly on IIS6 as they were on IIS4. The only recommended workaround is to upgrade to FPSE 2000 or FPSE 2002 on the source (NT4) before you migrate.
- The migration can be performed for only one individual site at a time, if you want to migrate the entire IIS server, you may want to put all the migration commands in a batch or script file.
- Files that are located in a directory structure that exceeds MAX_PATH are not migrated. The migration tool will error out with "Access Denied" and stops the migration.
- If you migrate the same site twice and the administrators group does not have full control permission on the source content, the migration tool will error out the second time with an "Access Denied" error. To workaround this, you can either give the administrators group full control on the source content or delete the content on the destination server before you run the migration the second time.
Please refer to the IIS 6.0 Migration Tool User Guide for usage and documentation.
--------