Hyper-V Live Migration Fails Due to Authentication Errors Between Hosts

Manon David 60 Reputation points
2026-11-18T06:11:48.6+00:00

In a Windows Server environment, administrators are experiencing authentication errors when attempting to perform Hyper-V Live Migration between two domain-joined Hyper-V hosts. Both hosts are online, network connectivity is working, and the virtual machines are running normally. However, migration attempts fail with authentication-related errors, preventing virtual machines from moving between hosts without downtime. What could cause these authentication failures, and how can I systematically troubleshoot Kerberos authentication, constrained delegation, CredSSP configuration, Active Directory permissions, SPN registration, and Live Migration settings to identify the root cause and restore successful migrations?

Windows for business | Windows Server | Storage high availability | Virtualization and Hyper-V
0 comments No comments

2 answers

Sort by: Most helpful
  1. Marcin Policht 113.6K Reputation points MVP Volunteer Moderator
    2026-11-18T06:43:34.5833333+00:00

    This can be caused by a broad range of issues, including incorrect Kerberos delegation, mismatched authentication settings, missing or duplicate Service Principal Names, insufficient Active Directory permissions, or improperly configured CredSSP. Although both Hyper-V hosts may be online and network connectivity may be working, Live Migration requires the source host to authenticate to the destination host on behalf of the administrator or service initiating the migration. This introduces an authentication delegation requirement that does not necessarily exist when managing a server directly.

    The first step is to establish which authentication protocol is being used. Hyper-V supports CredSSP and Kerberos for Live Migration. CredSSP is generally simpler to configure but requires the migration to be initiated from the source Hyper-V host, because the administrator's credentials are delegated to that host. Kerberos supports remote initiation, including migrations initiated through Hyper-V Manager on a separate management workstation, but requires correctly configured constrained delegation in Active Directory. For production environments, Kerberos with constrained delegation is generally the preferred configuration.

    Next, check the Hyper-V Live Migration configuration on both hosts. Open Hyper-V Manager, select the Hyper-V host, open Hyper-V Settings, and examine the Live Migrations section. Verify that incoming Live Migrations are enabled on both servers and that the appropriate network configuration is selected. Under Advanced Features, check the authentication protocol. Both hosts should use a compatible authentication configuration. If Kerberos is selected, verify that the corresponding Active Directory delegation configuration exists. If CredSSP is selected, verify that the migration is initiated from the source host and that CredSSP is enabled. You can inspect the configuration using PowerShell:

    Get-VMHost | Select-Object `
        ComputerName,
        VirtualMachineMigrationEnabled,
        VirtualMachineMigrationAuthenticationType,
        VirtualMachineMigrationPerformanceOption,
        MaximumVirtualMachineMigrations
    

    You can also inspect the relevant settings through the Hyper-V management interface. Do not assume that successful network connectivity establishes that Live Migration is configured correctly. The migration authentication protocol, permitted migration networks, and incoming migration settings must all be checked independently.

    Next, investigate Kerberos constrained delegation. This is one of the most common causes of authentication failures when Kerberos is selected. Kerberos delegation allows the source Hyper-V host to use the administrator's security context when accessing services on the destination host. Without the appropriate delegation configuration, the initial authentication might succeed, but the subsequent authentication to the destination service can fail.

    Open Active Directory Users and Computers, locate the computer account for the source Hyper-V host, and examine its Properties, Delegation tab. Select Trust this computer for delegation to specified services only and Use Kerberos only. Add the relevant services running on the destination Hyper-V host. For Hyper-V Live Migration, these are normally CIFS and Microsoft Virtual System Migration Service. Select the corresponding service instances associated with the destination computer account. If migrations must work in both directions, configure the equivalent delegation on both computer accounts, pointing each source host to the services on the other destination host.

    For example, if the hosts are HV01 and HV02, the delegation configuration should allow HV01 to delegate to the required services on HV02 and HV02 to delegate to the required services on HV01. Make sure you configure delegation on the source computer account, not the destination computer account alone. Also verify that the delegation settings have replicated to the domain controllers used by the two hosts.

    If CredSSP is being used, investigate credential delegation separately. Unlike Kerberos constrained delegation, CredSSP requires the administrator's credentials to be delegated to the source Hyper-V host. This means that initiating a migration remotely from a management workstation can result in authentication failures because the credentials are not available for the second authentication hop. A practical test is to log on directly to HV01, open Hyper-V Manager there, and attempt to migrate a VM to HV02. If this works while initiating the same migration remotely fails, the problem may be related to credential delegation rather than Hyper-V connectivity or permissions.

    You can inspect and configure CredSSP using PowerShell. On the source host, configure the client role, specifying the destination host. On the destination host, enable the server role:

    # Source host
    Enable-WSManCredSSP -Role Client `
        -DelegateComputer "HV02.domain.local" -Force
    
    # Destination host
    Enable-WSManCredSSP -Role Server -Force
    

    Check the configuration with:

    Get-WSManCredSSP
    

    Also verify the corresponding CredSSP settings in Hyper-V Settings on the hosts. Be aware that CredSSP delegation should be restricted to the necessary destination hosts. Avoid enabling broad credential delegation through Group Policy simply to make a migration work.

    SPN registration should be the next area of investigation. Kerberos relies on Service Principal Names to associate a service with the Active Directory computer account that runs it. Missing, incorrectly registered, or duplicate SPNs can prevent Kerberos from identifying the correct service account. Hyper-V Live Migration particularly depends on the SPNs associated with the Microsoft Virtual System Migration Service and CIFS.

    From a domain administration workstation, examine the SPNs registered for both computer accounts:

    setspn -L HV01
    setspn -L HV02
    

    Look for entries associated with the Hyper-V migration service and CIFS. You can also query specific SPNs:

    setspn -Q "Microsoft Virtual System Migration Service/HV01"
    setspn -Q "Microsoft Virtual System Migration Service/HV02"
    
    setspn -Q "cifs/HV01"
    setspn -Q "cifs/HV02"
    

    Check for duplicate SPNs throughout Active Directory:

    setspn -X
    

    A duplicate SPN can cause Kerberos authentication to fail because Active Directory cannot uniquely identify the account responsible for the service. If an SPN is missing, first establish whether it should be registered automatically by the service and whether the computer account has the required permissions. Correct missing or misplaced registrations only after confirming the intended service account. Use setspn -S rather than setspn -A when adding an SPN because -S checks for duplicates before registering it. Do not blindly add SPNs that are already present or register them against user accounts.

    Active Directory permissions and computer account health must also be verified. Both Hyper-V hosts should have valid computer accounts in the same trusted domain environment, and their secure channels with Active Directory should be functioning. Check whether the computer accounts are enabled, whether their passwords and secure channels are healthy, and whether the hosts can locate and authenticate against their domain controllers. You can run the following commands on each host:

    Test-ComputerSecureChannel -Verbose
    
    nltest /dsgetdc:domain.local
    
    nltest /sc_verify:domain.local
    
    w32tm /query /status
    

    Pay particular attention to time synchronization. Kerberos is sensitive to clock differences between clients, servers, and domain controllers. The default Kerberos maximum clock skew is five minutes unless modified through domain policy. Also verify DNS resolution for both hosts, preferably using their fully qualified domain names, and confirm that the records point to the correct IP addresses.

    The account initiating the migration must also have sufficient administrative privileges. Verify that it belongs to the local Administrators or Hyper-V Administrators group on the relevant hosts and that applicable domain security policies are not preventing the required logon or service access. If the migration uses SMB-based storage or shared storage, examine the associated share permissions and NTFS permissions as well. These are separate authorization requirements and should not be confused with Kerberos authentication itself.

    Examine the Windows event logs to identify the actual authentication failure. Rather than repeatedly changing delegation settings, correlate the timestamp of a failed migration with events on both Hyper-V hosts and the domain controllers. On the Hyper-V hosts, inspect the System and Security logs, as well as the Hyper-V VMMS and Hyper-V Worker operational logs under Applications and Services Logs. On the domain controllers, examine the Security log for Kerberos authentication and service-ticket failures. Relevant events include 4768 (Kerberos authentication ticket requested), 4769 (Kerberos service ticket requested), 4771 (Kerberos pre-authentication failed), and 4776 (NTLM authentication validation). Event 4769 is particularly useful when investigating service-ticket requests and identifying the service principal involved in a failure.

    You can also inspect the Kerberos ticket cache on the source host:

    klist
    

    After correcting SPNs or delegation settings, purge the existing tickets for the affected logon session and retry authentication:

    klist purge
    

    This removes cached Kerberos tickets for the current logon session, so use it with care on administrative systems where other authenticated sessions may be affected. A fresh authentication attempt can help determine whether the corrected configuration is working.

    Finally, verify that the Live Migration network and performance settings are not introducing a separate problem. Check that the hosts can communicate over the configured migration networks and that Windows Firewall permits the required Hyper-V Live Migration traffic. If SMB is being used as the migration transport, also investigate SMB connectivity, authentication, and signing or encryption requirements. Test the relevant ports and name resolution between the hosts. For example:

    Test-NetConnection HV02.domain.local -Port 445
    
    Resolve-DnsName HV02.domain.local
    

    For TCP-based Live Migration, check the configured migration network and the applicable firewall rules rather than assuming that an open SMB port is sufficient. Also verify that the migration networks configured on both hosts are compatible and that the selected performance option is supported by the network infrastructure.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-18T06:12:17.1066667+00:00

    Common causes are Kerberos or delegation misconfiguration, missing SPNs, using CredSSP in the wrong session context, insufficient permissions for the migration account, or incorrect Live Migration authentication settings on one or both hosts.

    A systematic troubleshooting path:

    1. Verify the authentication mode configured on both Hyper-V hosts.
      • Open Hyper-V Settings on each host.
      • Go to Live Migrations > Advanced or Advanced Features.
      • Confirm the authentication protocol is set correctly:
        • Kerberos if remote-initiated migrations are required without signing in to the source host.
        • CredSSP only if the migration is started while signed in to the source host.
    2. Check whether the failure matches a CredSSP limitation.
      • If the error is 0x8009030E (“No credentials are available in the security package”), CredSSP may be in use without an interactive sign-in to the source host.
      • With CredSSP, a sign-in to the source server is required through local console, Remote Desktop, or remote Windows PowerShell session.
      • If avoiding source-host sign-in is required, switch to Kerberos and configure constrained delegation.
    3. Validate Kerberos configuration for Live Migration.
      • In Hyper-V Settings > Live Migrations > Advanced/Advanced Features, set Authentication protocol: Kerberos on both hosts.
      • Kerberos is the required path when migrations are initiated remotely without logging on to the source host.
    4. Configure constrained delegation in Active Directory for both Hyper-V hosts.
      • Open Active Directory Users and Computers.
      • Open the computer account for each Hyper-V host.
      • On the Delegation tab, select:
        • Trust this computer for delegation to specified services only
        • Use any authentication protocol
      • Add the partner Hyper-V host and include these services:
        • cifs
        • Microsoft Virtual System Migration Service
      • If storage is moved during migration, cifs is required.
    5. Check SPN registration.
      • Missing SPNs can cause 0x80070005, 0x8009030E, or 0x8009030D.
      • Register the migration SPN if missing:
         setspn -s Microsoft Virtual System Migration Service/<FQDN> <ComputerName>
      
    6. Purge stale Kerberos tickets after delegation or SPN changes.
      • Old tickets can keep the failure active even after configuration is corrected.
      • Run:
         KLIST PURGE -li 0x3e7
      
      • Or wait up to 15 minutes for Kerberos tickets to time out.
    7. Interpret the common authentication errors.
      • 0x80070005: general access denied; commonly tied to Kerberos, SPN, or delegation problems.
      • 0x8009030E: no credentials available; commonly caused by CredSSP being used without signing in to the source host, or Kerberos/delegation not being configured.
      • 0x8009030D: supplied credentials not recognized; commonly caused by Kerberos authentication not enabled on both hosts or constrained delegation not configured correctly.
    8. Confirm Active Directory permissions and host account configuration.
      • Ensure the required delegation entries are configured on the computer accounts of both Hyper-V hosts.
      • Confirm the migration accounts have the required permission levels for live migration.
    9. Re-test from the correct context.
      • If using CredSSP, sign in to the source host and retry.
      • If using Kerberos, retry after delegation, SPN, and ticket updates are complete on both hosts.
    10. If migration still fails, verify adjacent configuration that can look like authentication failure.
    • Confirm all hosts are online and healthy.
    • Verify firewall rules and port accessibility, including UDP 3343 for WSFC where applicable.
    • Ensure required VM switches exist and are identically configured across hosts.
    • Confirm the destination host can access the VM storage.

    A practical root-cause checklist for this scenario:

    • CredSSP selected, but migration started remotely instead of from the source host
    • Kerberos not enabled in Hyper-V Live Migration settings on one or both hosts
    • Constrained delegation missing or incomplete in AD
    • cifs or Microsoft Virtual System Migration Service not added in delegation settings
    • Missing SPN for Microsoft Virtual System Migration Service
    • Stale Kerberos tickets after configuration changes
    • Incorrect permissions on the host computer accounts or migration account

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.