From 952b162911d131847fbe654fc553e2d8a1c09851 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Thu, 13 Mar 2025 17:53:13 -0600 Subject: [PATCH] Update Servers/Virtualization/Hyper-V/Kerberos-Enabled VM Migration.md --- .../Hyper-V/Kerberos-Enabled VM Migration.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/Servers/Virtualization/Hyper-V/Kerberos-Enabled VM Migration.md b/Servers/Virtualization/Hyper-V/Kerberos-Enabled VM Migration.md index 24499a8..e7154dd 100644 --- a/Servers/Virtualization/Hyper-V/Kerberos-Enabled VM Migration.md +++ b/Servers/Virtualization/Hyper-V/Kerberos-Enabled VM Migration.md @@ -24,4 +24,10 @@ This document will cover both scenarios. - Click on the "**Add**" button - Click the "**Users or Computers...**" button - Within the object search field, type in the name of the Hyper-V server you want to delegate access to (this will be the opposite host. e.g. VIRT-NODE-02, then repeat these steps later to delegate access for VIRT-NODE-01, etc) - - You will see a list of services \ No newline at end of file + - You will see a list of services that you can allow delegation to, add the following services: + - `cisvc` + - `mcsvc` + - `Virtual Machine Migration Service` + - 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 + - e.g. `VIRT-NODE-01 <---> VIRT-NODE-02` \ No newline at end of file