Microsoft-windows-hyper-v-vmms failed to register service principal name

Now i have installed additonal Hyper-V host, which generates every 2 min. Failed to register the service principal name 'Microsoft Virtual Console Service'.

No problem, take google and fix the problem.. The beavior is very strange, the errors also come up if the SPN's where manually added to the computer account. Only one google hit after hours of searching says one guy has disabled the firewall and it works.

Now this is what i have done.. So i stop the firewall service and it works!! The SPN's are successfuly registered! After the service is restarted, no more event coming up. After reboot same shit, events coming up again until the firewall servive is fully stopped and after successfully registering restarted. But why?? Firewall rules are correctly implemented. Any help will be appreciate!! Friday, May 16, AM. Absolutely the same behavior.

If the service start starts you will see the message "The Hyper-V Networking Management service was start successfully. Click the computer node. If the basic troubleshooting above, fails, this may be due to Service Hardening when dynamicportrange is changed. This applies to Windows Server systems.

As a workaround, manually configure the SPN for the service specified in the event description. If this error frequently occurs, contact Microsoft Product Support. If you happen to see this issue I would start looking at my connection to the my DCs. If the service is already configured to start automatically and you just need to restart the service, you can do that from Hyper-V Manager, or from the sc start vmms command shown above. Open Hyper-V Manager. Skip to main content.

This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? In this article.