Not all resources are migrated from a Windows Server 2003-based failover cluster to a Windows Server 2008 R2-based failover cluster

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When you migrate a Windows Server 2003-based failover cluster to a Windows Server 2008 R2-based failover cluster, only some file share resources that were in the pre-migration report of eligible resources for migration are migrated to the Windows Server 2008 R2-based failover cluster.

After a migration process, the final migration report indicates that all resources that were eligible for migration were successfully migrated. However, only some file share resources that were reported as migrated successfully are present if you check the Failover Cluster Management Microsoft Management Console (MMC) snap-in of Windows Server 2008 R2, or if you check the cluster registry hive under HKEY_Local_Machine\Cluster.

Note If you migrate from a Windows Server 2008-based failover cluster to a Windows Server 2008 R2-based failover clusters, or if you install the Failover Cluster feature on a computer that is running Windows Server 2008 R2, the pre-migration and final migration reports reflect the correct status of the migrated resources. Additionally, the resources that are in the final migration report are present in the Failover Cluster Management MMC snap-in and in the cluster registry hive.
WORKAROUND
To work around this issue, use one of the following methods to complete the migration.

Method 1

Migrate from a Windows Server 2003-based failover cluster to a Windows Server 2008-based failover cluster. Then, migrate from a Windows Server 2008-based failover cluster to a Windows Server 2008 R2-based failover cluster.

Method 2

Use the Microsoft File Server Migration Toolkit 1.2 to migrate the file share resources.

Method 3

Manually re-create all the missing resources by using the Failover Cluster Management MMC snap-in.

Note None of the workarounds support the migration of any third-party resource types in the cluster.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
A Windows Server 2008-based failover cluster can migrate settings from a failover cluster that is running Windows Server 2003 to a failover cluster that is running Windows Server 2008. However, a Windows Server 2008-based failover cluster cannot be used to migrate settings from a Windows 2000 Server-based failover cluster, or to import settings from another failover clusters that is running Windows Server 2008. For more information, visit the following Microsoft websites:
Properties

Article ID: 983840 - Last Review: 12/12/2015 04:48:33 - Revision: 1.1

Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 Standard, Windows Server 2008 for Itanium-Based Systems, Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems, Microsoft Windows Server 2003, Datacenter x64 Edition, Microsoft Windows Server 2003, Enterprise x64 Edition, Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows Server 2003, Standard x64 Edition, Microsoft Windows Server 2003, Standard Edition (32-bit x86)

  • kbnosurvey kbarchive kbclustering kbsurveynew kbexpertiseadvanced kbtshoot kbprb KB983840
Feedback