Up against two DL380 Gen10s running 2016 that are failing to connect to their Hyper-V guests after (what was described as) a graceful shutdown.
Both hosts are exhibiting the same issue: VMs showing expected uptime, plenty of spare resources, network adapter information is correct, preview is showing the logon screen, nothing in Hyper-V event viewer indicating critical\error\warning, host is listening on the expected port and I can ping the guest. The connection window just sits at 'Connecting to hostname..' for several minutes until it throws the timeout dialogue. Guests in this case range from application servers to DC and cifs.
Unfortunately they were down for a couple months due to the owner\operator's health issues, so the domain accounts expired\locked and he cannot find a working local admin credential (i.e. remote desktop and vmconnect cannot auth). I'm essentially working with him to get things back up and running as-is if at all possible.
Primary goal at the moment is to repair Hyper-V console functionality so I can boot the DC to a PE, reset the local Admin creds via utilman trick, and hop into ADUC from there. This is my first instance of Hyper-V outside a classroom\homelab environment so there isn't much in the way of prior knowledge I can throw against this issue. It also seems like the VMs have an excessive number of checkpoints, they might be compounding the issue but don't seem to be the root cause. So far I have:
- Completed the most recent spp for both chassis
- Latest ssu and cumulative update for server 2016
- Removed Hyper-V feature via powershell, renamed ProgramData and
adjacent folders
- dism and sfc prior to reinstalling the role and registering the VMs
into the console
- Merged and mounted vhd of a smaller appliance server without issue
- Can toggle secure boot without change in behavior
At this point I might just consider an in-place to 2019 in an effort to repair whatever component is broken. Any help is much appreciated!
