James Mahoney
asked on
Server 2012r2 hosts live migration authentication failing
I'm adding a replication host to my current environment. There are now two servers running Windows Server 2012r2. I am managing from a Windows 10 workstation. I have both a physical & virtual AD server at 2012r2, through which I've enabled delegation for both the CIFS & Windows Virtual System Migration Services. On both computers in Active Directory, I've added both hosts & their FQDN's to enable these services.
Authentication is still failing when using the 'move' feature in Hyper-V manager.
Thoughts on something I may have missed?
Authentication is still failing when using the 'move' feature in Hyper-V manager.
Thoughts on something I may have missed?
Flip both host's delegation properties to Trust this computer for delegation for any service then restart the VMMS on each host.
A reboot _may_ be required.
What AD Domain/Forest level?
A reboot _may_ be required.
What AD Domain/Forest level?
Well, I am a bit confused as to what you are trying to do...
If you added a *replication host* to your environment, you'd never "move" a VM or use live migration. Hyper-V Replica already has a full copy of the VM on the replica target. You'd instead use the "failover" set of commands.
If you are *not* configuring a replication host, we'd need to know more about your setup. Is there shared storage involved? Are you trying to perform a shared-nothing live migration? Is there a cluster?
If you added a *replication host* to your environment, you'd never "move" a VM or use live migration. Hyper-V Replica already has a full copy of the VM on the replica target. You'd instead use the "failover" set of commands.
If you are *not* configuring a replication host, we'd need to know more about your setup. Is there shared storage involved? Are you trying to perform a shared-nothing live migration? Is there a cluster?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Configuration of Authentication on host did not apply...double checked & was successful.
As a domain admin?