Hyper-V Shared Nothing Migration between 2 Clusters in different AD Domains

Lanky Doodle 226 Reputation points


We are in the process of migrating to a new AD Domain. One of the last pieces of work is to move all the VMs off of the existing Cluster which is connected to the old AD domain to the new Cluster which is connected to the new AD Domain.

If I try, this is the error I get:


Everything works "locally", e.g. moving VMs between hosts in the same Cluster, where from Hyper-V Manager or Live Migration from Failover Cluster Manager. The 2 AD Domains are trusted.

A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,600 questions
Windows Server Migration
Windows Server Migration
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Migration: The process of making existing applications and data work on a different computer or operating system.
413 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 44,071 Reputation points

    Hi. Thank you for your question and reaching out.

    Configure restricted delegation using the Users and Computers snap-in.

    1. Launch the Snap-in for Active Directory Users and Computers. (From Server Manager, click Tools >> Active Directory Users and Computers and pick the server if it is not already chosen.)
    2. Select the domain from the Active Directory Users and Computers navigation pane, then click twice on the Computers folder.
    3. Right-click the source server's computer account in the Computers folder, and then select Properties.
    4. Select the Delegation tab from the Properties menu.
    5. Choose Use any authentication mechanism after selecting Trust this machine for delegation to the listed services only on the delegation tab.
    6. Select Add.
    7. Users or Computers can be selected from Add Services.
    8. Type the name of the destination server into the box labeled Select Users or Computers. To confirm, click Check Names, after which click OK.
    9. Do the following, then click OK, after selecting Add Services from the list of accessible services:
      9.1 Choose cifs to relocate the virtual machine storage. This is necessary whether you wish to move the storage alongside the virtual machine or just the storage for a particular virtual machine. This need to be the default option if SMB storage for Hyper-V is enabled on the server.
      9.2 Choose Microsoft Virtual System Migration Service to move virtual machines.
    10. Make sure the services you chose in the previous step are listed as the services to which the destination computer can present delegated credentials on the Delegation tab of the Properties dialog box. Select OK.
    11. Repeat the process by selecting the destination server's computer account from the Computers folder. Make careful to enter the name of the source server when prompted in the Select Users or Computers dialog box.

    The configuration modifications take effect following the occurrence of both of the following:
    -The modifications are replicated to the domain controllers that host the Hyper-V servers.
    -A fresh Kerberos ticket is generated by the domain controller.

    For more information, please see https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/use-live-migration-without-failover-clustering-to-move-a-virtual-machine

    If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.