DRAG DROP
Your network contains an Active Directory domain named contoso.com. The domain contains four
member servers named Server1, Server2, Server3, and Server4. Server1 and Server2 run Windows
Server 2008 R2.
Server1 and Server2 have the Hyper-V server role and the Failover Clustering feature installed.
Failover
Clustering is configured to provide highly available virtual machines by using a cluster named
Cluster1.
Cluster1 hosts 10 virtual machines.
Server3 and Server4 run Windows Server 2012 R2.
You install the Hyper-V server role and the Failover Clustering feature on Server3 and Server4. You
create a cluster named Cluster2.
You need to migrate cluster resources from Cluster1 to Cluster2. The solution must minimize
downtime on the virtual machines.
Which five actions should you perform?
To answer, move the appropriate five actions from the list of actions to the answer area and arrange
them in the correct order.
Answer: 
Explanation:
1. Move Highly Available (Clustered) VMs to Windows Server 2012 with the Cluster Migration Wizard
On the Windows Server 2012 cluster – the target cluster – from the Failover Cluster Manger, select a
cluster and then use the More Actions | Migrate Roles… menu to launch the Cluster Migration
Wizard:
2. Shutdown all VMs on the source Windows Server 2008 R2 cluster that have been migrated.
3. Unmask the common shared storage (LUNs) so that they are not presented to the Windows
Server 2008 R2source cluster
4. Mask the common shared storage (LUNs) to the Windows Server 2012 target cluster.5. Start all VMs on the target Windows Server 2012 cluster.
Best practices for migration of cluster windows 2008 R2 / 2012
http://blogs.technet.com/b/hugofe/archive/2012/12/06/best-practices-for-migration-of-clusterwindows-2008-r2-2012-as-melhores-praticas-para-migrar-um-cluster-de-windows-2008-parawindows-2012.aspx
1. From the failover cluster manager on CLUSTER2! run the migrate cluster wizard.
2. Shutdown VMs on Cluster1.
3. Mask storage so Cluster1 can’t see it.
4. Unmask storage for Cluster2.
5. Startup VMs on Cluster2.
The reason for this is because you launch the migration wizard on the DESTINATION server. Then you select the SOURCE (cluster1) to migrate the settings over.
Excerpt from the TN articles above:
“Launch the Cluster Migration Wizard from the Failover Cluster Manager, select the source cluster, and then select the cluster roles on the source cluster that you’d like to migrate to the new cluster.”
1
0
Weird because Cluster 2 has nodes with Server 2012 R2. Server 2012 R2 does not have an option called “Migrate Roles…”, so this option could be run only cluster 1 that has 2008 R2 servers.
0
0