Fix it now
The source host tried to authenticate to the destination and had no credentials to present. That is the standard result of selecting Kerberos as the live migration authentication protocol without configuring constrained delegation in Active Directory. The virtual machine keeps running on the source host, so nothing is lost until you fix it.
Get-VMHost | Select-Object Name, VirtualMachineMigrationEnabled, VirtualMachineMigrationAuthenticationType
- If the authentication type is Kerberos, open Active Directory Users and Computers, find each host’s computer object and open the Delegation tab.
- Select trust for delegation to specified services only, using Kerberos only, and add two services for every partner host: the cifs service and the Microsoft Virtual System Migration Service.
- Do this on every host, in both directions. Delegation is not reciprocal, so configuring one side achieves nothing on its own.
- Restart the hosts, or purge their computer tickets, so new Kerberos tickets reflect the change, then retry the migration and read the Hyper-V-VMMS log on both ends.
If you would rather not configure delegation, the alternative is CredSSP, which works only when you are signed in to the source server itself. That is a deliberate limitation of CredSSP, not a fault.
If a migration started from a remote session completes, stop here. If delegation is configured and it still fails, the next section covers what else Kerberos needs between two hosts.
Why it happens
Live migration is a conversation between two hosts that you usually start from somewhere else: your workstation, Failover Cluster Manager, or a script. The source host has to open connections to the destination, and to the storage, as you rather than as itself. Handing your identity onwards like that is delegation, and Windows will not do it unless it has been told to, by name, for specific services.
Microsoft documents two supported ways to authorise it, and which you pick depends on how you manage the hosts. CredSSP passes your credentials from your interactive session to the source host, which works only when you are signed in to that source host. Moving a machine back then means signing in to the other host first. Kerberos constrained delegation removes the restriction by letting the source host’s computer account request tickets to specific services on the destination on your behalf, which is what makes remote and scripted migrations possible.
The two services to add are exactly those Microsoft names: cifs, which is needed for moving virtual machine storage with the machine, for storage-only migrations, and wherever the host uses SMB storage; and Microsoft Virtual System Migration Service, which is needed to move machines between hosts. Both go on each host’s computer object, naming every host it may migrate to. In a cluster that means every node to every other node.
Read the event text rather than the numbers here. The one Hyper-V management service number Microsoft publishes an example for is used against a virtual machine that failed to start because a network adapter’s switch port connection was invalid, which is not a migration at all. These are general operation-failure entries whose accompanying text names the operation, so the text is the diagnosis and the number is only a label.
Kerberos is selected and no delegation exists
You have this one if It fails on the first attempt, and the Delegation tab on the host’s computer object still says do not trust this computer for delegation.
- In Active Directory Users and Computers, open the source host’s computer object, go to Delegation, and choose trust for delegation to specified services only, with Kerberos only.
- Add the cifs service for every host it may migrate to, so it can reach the storage.
- Add the Microsoft Virtual System Migration Service for the same set of hosts.
- Repeat on every host, then restart them so fresh tickets are issued.
Configure delegation for every pair that may ever migrate in either direction. Half a matrix produces migrations that work one way and fail the other, which is a confusing thing to inherit.
Delegation is incomplete after a host was added or rebuilt
You have this one if Migrations between the original hosts work and anything involving the newest host fails.
- Add the new host’s two services to every existing host’s delegation list.
- Configure the new host’s own delegation list to include all the others.
- Treat a rebuilt host as new even when the name is unchanged: it has a new computer object and its delegation has to be configured from scratch.
- Restart the affected hosts and retry.
CredSSP is in use and the migration was started remotely
You have this one if The authentication type is CredSSP, and migrations succeed only when you are signed in at the source host itself.
- Either sign in to the source host and run the migration there, which is what CredSSP supports and is a reasonable choice for two hosts.
- Or switch to Kerberos on both hosts with
Set-VMHost -VirtualMachineMigrationAuthenticationType Kerberosand configure delegation. - Confirm the setting took on both ends with
Get-VMHostbefore retrying.
The account lacks rights on the destination host
You have this one if The failure names the logon type rather than missing credentials, and it happens at the destination rather than at the source.
- Confirm the account performing the migration is an administrator on both hosts, or a member of Hyper-V Administrators on both.
- Check for a policy restricting logon rights on the destination host that excludes the account or the source host.
- Retry with an account you know holds the rights, to separate a policy problem from a delegation one.
Win32 error 1385 is published as ‘Logon failure: the user has not been granted the requested logon type at this computer’, which is a rights problem rather than a credentials one. If you see 0x80070569, you are in this cause and not the one above.
Kerberos itself is unhealthy between the hosts
You have this one if Delegation is configured correctly and tickets still fail, or the failure changed shape after delegation was added.
- Check clock skew. Compare
w32tm /query /statuson both hosts and resync withw32tm /resyncif they disagree. - Confirm forward and reverse name resolution matches between the hosts.
- Look for duplicate service principal names, which produce intermittent and confusing authentication failures.
- Purge stale tickets or reboot, then retry.
Full reference
Which authentication protocol to choose
| CredSSP | Kerberos | |
|---|---|---|
| Where you must be signed in | The source host itself | Anywhere |
| Configuration needed | None | Constrained delegation on every host’s computer object |
| Suits | Two hosts, managed at the console | Remote management, scripts, clusters |
| Moving a machine back | Sign in to the other host first | No change; delegation is configured both ways |
The delegation entries, exactly
- Open Active Directory Users and Computers and find the host’s computer object.
- On the Delegation tab, choose trust this computer for delegation to specified services only, and Use Kerberos only.
- Add the cifs service on every host this one may migrate to. This is what lets it reach the storage, and it is required where the host uses SMB storage for Hyper-V.
- Add the Microsoft Virtual System Migration Service on the same set of hosts. This is what lets it move machines.
- Repeat for every host, in both directions.
- Restart the hosts so new tickets are issued. Waiting for replication and a ticket lifetime works too, and takes longer than anyone expects.
Where the migration is failing
| What you observe | Most likely area |
|---|---|
| Fails from your workstation, works from the source host console | Delegation missing; CredSSP is carrying the console case |
| Fails in one direction only | Delegation configured on one computer object and not the other |
| One new host fails and the established ones are fine | The new host was never added to the delegation lists |
| All migrations fail after a directory change | Ticket lifetime, duplicate service principal names, or clock skew |
| The migration starts and fails part-way | Networking or storage access, not authentication |
Reading the failure rather than the number
The Hyper-V management service logs operation failures with a small set of numbers whose text varies enormously. Microsoft’s own published example of the main one is a virtual machine that failed to start because the switch port connection for a network adapter was invalid, which has nothing to do with migration. So take the operation from the entry’s text and the machine name from its body, and treat the number as a label rather than as a diagnosis. The one code on this page with a published meaning is the logon-type refusal, Win32 error 1385, and that one tells you plainly that you are looking at rights on the destination rather than at delegation.
Checking it took
Get-VMHost | Select-Object Name, VirtualMachineMigrationEnabled, VirtualMachineMigrationAuthenticationType, VirtualMachineMigrationPerformanceOption
klist purge -li 0x3e7
When a licence is the actual fix
Getting delegation right costs nothing and you should do it before anything else. What live migration does raise is a licensing question, because Windows Server is licensed per host and virtual machine entitlements travel with the host rather than with the guest. Microsoft publishes the limits plainly: Windows Server 2025 Standard allows two virtual operating system environments per licensed host, and Datacenter allows an unlimited number. On a cluster where machines move freely, every host has to be entitled to run whatever might land on it, which is why clustered hosts are usually licensed with Windows Server 2025 Datacenter rather than stacking Standard licences. Datacenter also carries the automatic virtual machine activation host requirement, which matters if you activate guests that way. Arco can work out which edition is cheaper for your machine density and supply either.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
Event ID 21502 |
A general Hyper-V management service operation failure. Microsoft’s published example of it is a virtual machine that failed to start because the switch port connection for a network adapter was invalid, so read the operation from the entry text rather than assuming a migration | Microsoft Learn |
Event ID 21500 |
Not published by Microsoft. It appears where the connection the operation needed could not be established | not published by the vendor |
0x8009030E |
Not published by Microsoft as a numeric code. The nearest published wording is the SSPI status SEC_E_NO_CREDENTIALS, ‘No credentials are available’, which is the shape of Kerberos selected without constrained delegation | not published by the vendor |
0x80070569 |
Win32 error 1385: logon failure, the user has not been granted the requested logon type at this computer. A rights problem on the destination, not a delegation one | Microsoft Learn |
Event ID 21111 |
Not published by Microsoft. It appears against a failed live migration of a named machine | not published by the vendor |
Event ID 21024 |
Not published by Microsoft. It appears from the source host side of a failed migration | not published by the vendor |
Event ID 22038 |
Not published by Microsoft. It appears from the destination host side of the same failure | not published by the vendor |
Confirm the fix worked
- A live migration started from a remote management session, not from the source host console, completes.
- Migrating back in the opposite direction also completes, which proves both computer objects are configured.
Get-VMHoston both hosts shows the same authentication type.- Every host’s Delegation tab lists cifs and Microsoft Virtual System Migration Service for every partner host.
- No new migration failures appear in the Hyper-V-VMMS logs on either host.
Questions people ask about this
Can I avoid delegation by always working at the console?
Yes, with CredSSP, and it is a reasonable choice for a two-host environment. It stops being practical the moment you manage hosts remotely, script migrations, or let a cluster move machines on its own schedule.
Do I need Datacenter edition to use live migration?
No. Live migration is a feature of the Hyper-V role and works on Standard. The edition decides how many virtual machines you may run on a host: two virtual operating system environments on Standard, unlimited on Datacenter.
Why does it work for one administrator and not another?
Usually because one of them is signed in at the source host and the other is not, so one path uses CredSSP and the other needs delegation. Test both deliberately rather than assuming an account problem.
How long after configuring delegation before it works?
Once Active Directory has replicated and the hosts hold fresh Kerberos tickets. Restarting both hosts is the reliable way to get there, and is worth doing before you conclude the change did not help.
Which of the two errors am I actually looking at?
If the security layer reports no credentials available, you are missing delegation. If you get 0x80070569, Microsoft publishes that as the logon type not being granted, which is a rights problem on the destination host and delegation will not fix it.
