In this Tutorial we are going to cover Introduction
The issue was that all VMs running on a Windows Server 2012 R2 server was showing like the image below.
Looking at the logs on the VMM Server, one of the errors was 1002 and 5004, and based on the image below some logs were generated. Some of them were showing credential problems in SQL and there are other refresh tasks failing for account issues on VMM console.
Using Hyper-V manager the VMs were fine and the connectivity was fine as well.
The issue was between the communication from the Hyper-V host, VMM and Active Directory. In my customer, the site had a single Domain Controller and it was waiting on some updates and it was unresponsive, after restarting the domain controller and making sure that either Hyper-V host(s) and VMM were able to communicate properly (DNS, UNC and event log checks), the next step was to restart the VMM services on both VMM Server and VMM Agent(Hyper-V host), as follows.
After that a refresh on VMM and we should have all servers available as shown in the image below.