bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Servers/Virtualization/Hyper-V/Kerberos-Enabled VM Migration.md

Browse Source
This commit is contained in:
Nicole Rappe
2025-03-13 17:59:00 -06:00
parent 46f0494b96
commit ee0f2e4bef
1 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
Servers/Virtualization/Hyper-V/Kerberos-Enabled VM Migration.md
View File

@ -3,16 +3,7 @@ You may find that you want to be able to live-migrate guestVMs on a Hyper-V envi
This document will cover both scenarios. This document will cover both scenarios.
=== "CredSSP Authentication" === "Kerberos Authentication (*Preferred*)"
- Log into both Hyper-V Hosts as the same administrative user. Preferrably a domain administrator
- From the Hyper-V host currently running the GuestVM that needs to be migrated, open Hyper-V Manager and right-click > "**Move**" the guestVM.
- Select the destination by providing the fully-qualified domain name of the destination server (or in some cases the shorthand hostname of the destination server)
- It should begin the migration process.
**Note**: Do not perform a "Pull" from source to the destination. You want to always "Push" the VM to its destination. It will generally fail if you try to "Pull" the VM to its destination due to the way that CredSSP works in this context.
=== "Kerberos Authentication"
- Log into a domain controller that both Hyper-V hosts are capable of communicating with - Log into a domain controller that both Hyper-V hosts are capable of communicating with
- Open "**Server Manager > Tools " Active Directory Users & Computers**" - Open "**Server Manager > Tools " Active Directory Users & Computers**"
@ -31,3 +22,12 @@ This document will cover both scenarios.
- Click the "**Apply**" button, then click the "**OK**" button to finalize these changes. - Click the "**Apply**" button, then click the "**OK**" button to finalize these changes.
- Repeat the above steps for the opposite Hyper-V host. This way both hosts are delegated to eachother - Repeat the above steps for the opposite Hyper-V host. This way both hosts are delegated to eachother
- e.g. `VIRT-NODE-01 <---(delegation)---> VIRT-NODE-02` - e.g. `VIRT-NODE-01 <---(delegation)---> VIRT-NODE-02`
=== "CredSSP Authentication"
- Log into both Hyper-V Hosts as the same administrative user. Preferrably a domain administrator
- From the Hyper-V host currently running the GuestVM that needs to be migrated, open Hyper-V Manager and right-click > "**Move**" the guestVM.
- Select the destination by providing the fully-qualified domain name of the destination server (or in some cases the shorthand hostname of the destination server)
- It should begin the migration process.
**Note**: Do not perform a "Pull" from source to the destination. You want to always "Push" the VM to its destination. It will generally fail if you try to "Pull" the VM to its destination due to the way that CredSSP works in this context.