I have a Windows Server 2016 virtual host which is hosting a virtual domain controller, and a few additional servers. When the physical host needs to reboot for scheduled patching, upon startup the server receives the following errors:
"Failed to register the service principal name 'Hyper-V Replica Service'.
Failed to register the service principal name 'Microsoft Virtual System Migration Service'.
Failed to register the service principal name 'Microsoft Virtual Console Service'."
Service principal names are properly set in the attributes of AD of the host for each of the respective SPN's, and I'm unsure how to trace this out any further. Does anyone have any first hand experience or recommendations in regards to this? There are also no NTDS port restrictions in place.
Best Answer
Go to Active Directory, select view Advanced Features. On the Hyper-V host computer Security Tab/Advanced select the SELF principal/EDIT and allow permission for "Validated write to service principal name".