Hyper-V moving VM 0x8009030E: No suitable credentials

[Garacesh]

I've set up a new Hypervisor to retire out oldest one but I can't seem to shift any VMs over to it.

 

There was a n error during move operation.

Virtual machine migration operation failed at migration source.

 

Failed to establish a connection with the host 'NewHost.domain.tld': No credentials are available in the security package (0x8009030E).

 

The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source host: no suitable credentials available. Make sure the operation is initiated on the source host of the migration, or the source host is configured to use Kerberos for the authentication of migration connections and Constrained Delegation is enabled for the host in Active Directory.

 

• The recipient server is a new Server 2022 Datacenter build. The current host server is Server 2016 Datacenter Core.
  
• Both servers are members of the same domain.
  
• I have tried initiating the move from Hyper-V manager on the recipient server, and from Move-VM on the host server.
  
• Both machines have Enable incoming and outgoing live migrations enabled.
  
  • I have tried adding exact IP addresses/32 of both servers to both servers, and range address/24. They are both in the same IP range.
    
  • Failing this, I have also tried enabling Use any available network for live migration on both servers.

  [*]Both AD Computer objects have cifs and Microsoft Virtual System Migration Service delegation enabled in AD, trusting the other server, with Use Kerberos only enabled.

  • I've even tried adding Hyper-V Replica Service and Microsoft Virtual Console Service for good measure.
    
  • I've also tried both Use any authentication protocol and Trust this computer for delegation to an service (Kerberos only).

  [*]The AD User initiating the move is a member of Domain Administrators, and is not a member of Protected users.

  • It does not have Account is sensitive and cannot be delegated enabled.

  [*]If I try Move-VM with -Credential specified, I get Move-VM : CredSSP authentication is currently disabled in the client configuration. Change the client configuration and try the request again. which tells me it's not even trying to using Kerberos? But that may be intrinsic to using the -Credential switch, I'm not sure.

  [*]The current host's event log displays

  [*]The recipient's event log displays The Virtual Machine Management Service blocked a connection request for a Virtual Machine migration from client address '$CurrentHostIP': An existing connection was forcibly closed by the remote host. (0x80072746).

  [*]Adding credentials via cmdkey /add:$OtherHost /user:$DAUsername /pass:$DAPassword on both hosts appears to achieve nothing.

  [*]Enable-PSRemoting resulted in no change.

  [*]Dumping Kerberos tickets via klist -li 0x3e7 purge on both servers resulted in no change.

  [*]Restating the Hyper-V Virtual Machine Management (vmms) service on both servers resulted in no change.

 

At a loss of where to go here. Every single google result is telling me I've done it right, and I don't recall every having to do anything beyond cifs/MVSM Service in previous lives.

[Garacesh]

.......

 

Would somebody. Please. Please. Tell me in what world the error No credentials are available in the security package indicates that you can't move a VM if it's connected to a virtual switch, where a virtual switch of a matching name doesn't exist on the recipient host?

 

Because why wouldn't you not want to fail with a completely irrelevant error message instead of just flagging up a "Hey, look, the switch doesn't exist, so we'll move it but not connect its network adapter, you cool with that?" warning.

 

 

Dinkelbeeerg Microsoooooft!

 

Solution: Disconnect its network adapter, the initiate the move via Move-VM on the current host.

Edited September 26, 2023 by Garacesh

[supportman]

.......

 

Would somebody. Please. Please. Tell me in what world the error No credentials are available in the security package indicates that you can't move a VM if it's connected to a virtual switch, where a virtual switch of a matching name doesn't exist on the recipient host?

 

Because why wouldn't you not want to fail with a completely irrelevant error message instead of just flagging up a "Hey, look, the switch doesn't exist, so we'll move it but not connect its network adapter, you cool with that?" warning.

 

 

Dinkelbeeerg Microsoooooft!

 

Solution: Disconnect its network adapter, the initiate the move via Move-VM on the current host.

Just run into this myself, I had tried everything beforehand as well refusing the be defeated by simply exporting and importing

 

What do you mean disconnect the network adapter though?

 

EDIT: Fixed mine by changing both hosts to kerbos authentication under live migration advanced settings. No idea! but it works...

Edited January 23, 2025 by supportman

[DrCheese]

Just run into this myself, I had tried everything beforehand as well refusing the be defeated by simply exporting and importing

 

What do you mean disconnect the network adapter though?

 

Remove the network adapter on the back of Hyper-V (Or name the switch the same on both hosts)

 

Stuff like this is why I miss VMware

[Koldov]

Pretty sure when I started messing around with Hyper-V and ran into problems like this, it was usually the network adapter...

[Garacesh]

And this is why I update my threads with answers where I can.

Nobody wants to be that guy

[supportman]

And this is why I update my threads with answers where I can.

Nobody wants to be that guy

 

I actually got linked to this thread from the Microsoft official forums 😂