Microsoft released a KB article for when the Hyper-V Virtual Machine Management Service (VMMS) fails and event ID 14050 is logged after dynamicportrange is changed in Windows Server 2012. Note that the VMMS is a service that runs in the Management OS of a Hyper-V host and provides the WMI API to manage Hyper-V and the VMs running on that host.
Assume that you have a computer that is running Windows Server 2012 with Hyper-V installed. If you try to manage the Hyper-V hosts either by using System Center Virtual Machine Manager 2012 Service Pack 1 (SP1) or remotely by using Hyper-V Manager, the attempt fails. Additionally, an event may be logged in the event log that resembles the following:Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin Source: Microsoft-Windows-Hyper-V-VMMS Date: <Date> <Time> Event ID: 14050 Level: Error Description: Failed to register service principal name. Event Xml: … <Parameter0>Hyper-V Replica Service</Parameter0>
This problem may occur if the TCP dynamic port range is out of the default range. The Virtual Management Service (Vmms.exe) of Hyper-V uses Windows Service Hardening, and it limits itself to the dynamic port range.
To determine the TCP dynamic port range, run the following command at an elevated command prompt:C:>netsh int ipv4 show dynamicportrange tcp Protocol tcp Dynamic Port Range --------------------------------- Start Port : 49152 Number of Ports : 16384
This problem may also occur if the NTDS port has been restricted to a specific port on your domain controllers. If this selected NTDS port is not within the default ranges, you must add this port by running the script in the "Resolution" section on every Hyper-V host.
For more information, click the following article number to go to the article in the Microsoft Knowledge Base:
Run the script from the original KB article on each affected host. This script adds a custom port range to enable Vmms.exe to communicate over an additional port range of 9000 to 9999