Skip to content

Commit 724b0ce

Browse files
v-liannav-lianna
committed
Create hyper-v-cluster-connectivity-management-configuration.md
1 parent 01a0c60 commit 724b0ce

1 file changed

Lines changed: 162 additions & 0 deletions

File tree

‎support/windows-server/virtualization/hyper-v-cluster-connectivity-management-configuration.md‎

Lines changed: 162 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,162 @@
1+
---
2+
title: Troubleshooting Hyper-V Cluster Connectivity, Management, and Configuration Failures
3+
description: Provides a comprehensive guide to troubleshooting various issues related to Hyper-V clusters and management environments on Windows Server 2019 and Windows Server 2022.
4+
ms.date: 08/20/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, jeffhugh, v-lianna
9+
ms.custom:
10+
- sap:virtualization and hyper-v\integration components
11+
- pcy:WinComm Storage High Avail
12+
---
13+
# Troubleshooting Hyper-V Cluster Connectivity, Management, and Configuration Failures
14+
15+
This article provides a comprehensive guide to troubleshooting various issues related to Hyper-V clusters and management environments on Windows Server 2019 and Windows Server 2022. These issues can manifest as failures in cluster management consoles, virtual machine (VM) migration, remote administration, authentication, storage configuration, and network connectivity. The guide identifies symptoms and root causes, offering actionable resolution steps to address the problems. Effective troubleshooting of these issues is critical to maintaining high availability, business continuity, and compliance in enterprise virtualization environments.
16+
17+
## Symptoms
18+
19+
### End-user symptoms
20+
21+
- Inability to connect to Hyper-V Manager or Failover Cluster Manager consoles.
22+
- Failures in remote VM management operations (e.g., start, stop, or migrate) from certain hosts or accounts.
23+
- Virtual machines fail to migrate between cluster nodes or become inaccessible after migration or upgrade.
24+
- Hyper-V Manager displays "Loading virtual machines…" or "Connecting to Virtual Machine Management service…".
25+
- Certain user accounts cannot perform administrative actions, while built-in administrators succeed.
26+
- Backup or cluster operations hang, fail, or report errors.
27+
- VMs report duplicate universally unique identifiers (UUIDs) detected by third-party tools.
28+
29+
### Technical/system symptoms
30+
31+
- Error: "Cannot connect to the virtual machine. Try to connect again. If the problem persists, contact your system administrator."
32+
- Error: "You do not have the required permission to complete this task. Contact the administrator of the authorization policy for the computer."
33+
- Error: "The operation on computer failed: WinRM process the request. The error code 0x80090311 occurred while using Kerberos authentication."
34+
- Error: "SEC_E_NO_AUTHENTICATING_AUTHORITY: No authority could be contacted for authentication."
35+
- Error: "Start-VM: Hyper-V encountered an error trying to access an object on computer [host] because the object was not found."
36+
- Error: "get-vm: The paging file is too small for this operation to complete."
37+
- Hyper-V Manager becomes unresponsive or does not display any VMs.
38+
- VMConnect fails from certain remote hosts but succeeds from others.
39+
- Netlogon and DNS logs show failed domain controller discovery.
40+
- Windows Management Instrumentation (WMI) errors, including WMIPrvSE.exe crashes.
41+
- Virtual Machine Management Service (VMMS) hangs or enters a deadlock state.
42+
- Duplicate UUIDs detected for VMs (e.g., by vendor extraction tools).
43+
- No error messages, but failures in adding storage, configuring quorum disks, or managing updates.
44+
- Network traces show blocked ports between hosts and domain controllers.
45+
- Event logs and analytic logs may be missing or not generated for affected actions.
46+
47+
## Cause
48+
49+
### Network and authentication issues
50+
51+
- **Firewall blocking**: Required ports (e.g., UDP/TCP 389 for LDAP, port 2179 for VMConnect) are blocked, disrupting authentication, domain controller discovery, or management traffic.
52+
- **DNS/Netlogon failures**: UDP pings or DNS queries to domain controllers fail, which breaks Kerberos authentication and remote management.
53+
54+
### Permission and group membership misconfiguration
55+
56+
- **Insufficient privileges**: Users lack membership in necessary administrative groups (e.g., Hyper-V Administrators, Storage Replica Administrators, or Remote Management Users).
57+
- **Group Policy restrictions**: Policies block credential delegation or Windows Remote Management (WinRM) operations in workgroup or multi-domain environments.
58+
59+
### Configuration and state file corruption
60+
61+
- **Corrupt VM files**: Corrupted .VMRS, .VMCX, or configuration files caused by improper shutdowns or service crashes.
62+
- **Deadlocks in VMMS**: Service deadlocks triggered by pending network operations or driver issues.
63+
64+
### Software/code defects
65+
66+
- **High availability (HA) VM settings bugs**: Known defects in Hyper-V HA settings, especially in Windows Server 2019 and 2022, that affect storage management or cluster operations.
67+
68+
### Environmental and update problems
69+
70+
- **Outdated OS**: Missing Windows updates cause instability in Hyper-V role installation or operation.
71+
- **Backup or third-party software impact**: Backup operations or third-party tools cause services (e.g., WMI) to crash or malfunction.
72+
73+
### Storage and hardware identifier issues
74+
75+
- **Duplicate UUIDs**: Duplicate VM UUIDs due to manufacturer settings or cloning.
76+
- **Storage configuration gaps**: Misconfigured or unrecognized shared storage and storage pools.
77+
78+
### Console/management tool failures
79+
80+
- **Failover Cluster GUI/console issues**: Misconfigurations or duplicate case scenarios prevent the management interface from operating properly.
81+
82+
## Resolution
83+
84+
### Scenario 1: Cluster or Hyper-V Manager console fails to connect/authenticate
85+
86+
1. **Verify network connectivity and firewall rules**: - Ensure UDP/TCP port 389 is open between Hyper-V hosts and domain controllers.
87+
- Open port 2179 for VMConnect/console access.
88+
- Use network trace tools to identify blocked traffic.
89+
2. **Check DNS and Netlogon settings**: - Review Netlogon logs for failed domain controller discovery.
90+
- Verify DNS settings and confirm domain controller reachability.
91+
3. **Confirm group memberships and permissions**: - Ensure users are members of: - Hyper-V Administrators
92+
- Remote Management Users
93+
- Storage Replica Administrators (if applicable).
94+
- Remove affected users from the default Users group if necessary.
95+
4. **Update Group Policy and WinRM settings**: - Enable PowerShell Remoting:Enable-PSRemoting
96+
- Configure CredSSP for authentication:Enable-WSManCredSSP -Role serverEnable-WSManCredSSP -Role client -DelegateComputer "<Hyper-V host>"
97+
5. **Adjust trusted hosts and firewall rules**: - Set trusted hosts for WinRM:Set-Item wsman:localhost\client\trustedhosts <Hyper-V host IP>
98+
- Enable relevant firewall rules: - Remote Administration
99+
- Remote Desktop
100+
- Remote Volume Management
101+
- Windows Management Instrumentation (WMI).
102+
103+
### Scenario 2: Virtual machine fails to migrate, start, or is inaccessible after upgrade
104+
105+
1. **Check storage and network configuration**: - Verify shared storage and storage pools are configured and accessible from all cluster nodes.
106+
- Ensure consistent network settings across all nodes.
107+
2. **Validate OS updates**: - Run Windows Update on all Hyper-V hosts before installing or migrating the Hyper-V role.
108+
3. **Investigate VM state and configuration files**: - If a VM is unresponsive: - Shut down all healthy VMs.
109+
- Reboot the Hyper-V host.
110+
- Delete the problematic VM from Hyper-V Manager (retain the VHDX file).
111+
- Backup and, if needed, delete/rename the .vmcx and .vmrs files.
112+
- Recreate the VM using the existing VHDX disk.
113+
4. **Repair corrupted files**: - Collect a process dump and analyze for VMMS deadlocks.
114+
- Use tools like Process Explorer or TSS scripts (from [aka.ms/getTSS](https://aka.ms/getTSS)) to collect logs and terminate stuck processes.
115+
116+
### Scenario 3: Permission/access denied errors when managing VMs
117+
118+
1. **Update user group memberships**: - Add the user to the appropriate administrative groups on the Hyper-V host.
119+
2. **Recompile WMI classes**: - Run:MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof
120+
3. **Reconfigure credential delegation in Group Policy**: - Allow delegation of fresh credentials with NTLM-only server authentication.
121+
122+
### Scenario 4: Duplicate VM UUIDs detected by vendor tools
123+
124+
1. **For VMware**: - Edit the VM’s .vmx file: - Locate uuid.bios = and assign a unique value.
125+
2. **For Hyper-V**: - Use a third-party tool to randomize/update the BIOS GUID.
126+
- If not feasible, create a new VM from scratch to ensure a unique UUID.
127+
128+
### Scenario 5: Cluster or Hyper-V role installation fails
129+
130+
1. **Install the latest Windows updates**: - Fully patch the server before attempting the Hyper-V feature installation.
131+
2. **Retry role installation**: - Use Server Manager, PowerShell, or Deployment Image Servicing and Management (DISM) tools:Install-WindowsFeature -Name Hyper-V -IncludeManagementTools
132+
133+
### Scenario 6: Backup or WMI-related cluster node failures
134+
135+
1. **Check WMI service status**: - If WMIPrvSE.exe crashes, restart the service or reboot the node.
136+
2. **Collect logs during the incident**: - Gather SDP, TSS, and cluster logs for root cause analysis.
137+
138+
### Scenario 7: Failover Cluster console/GUI not working
139+
140+
1. **Check for duplicate cases**: - Verify the issue is not already tracked in an open support case.
141+
2. **Verify cluster configuration**: - Review cluster logs and configurations for inconsistencies.
142+
143+
### Scenario 8: Hardening and best practices
144+
145+
1. **Run Best Practices Analyzer (BPA)**: - Use Server Manager or PowerShell:Invoke-BpaModel -ModelId Microsoft/Windows/Hyper-V
146+
2. **Implement hardening recommendations**: - Apply security recommendations from Microsoft documentation and BPA output.
147+
148+
## Data collection
149+
150+
### Logs and commands
151+
152+
- **TSS script for Hyper-V diagnostics**:Download and run: [aka.ms/getTSS](https://aka.ms/getTSS)Example:Set-ExecutionPolicy -scope Process -ExecutionPolicy RemoteSigned.\TSS.ps1 -SDP HyperV
153+
- **Event log collection**:%SystemRoot%\System32\winevt – Copy and zip event log folders.
154+
- **WMI and VM UUID queries**:Get-CimInstance -ClassName Win32_ComputerSystemProduct | Select UUIDGet-WmiObject Win32_ComputerSystemProduct | Select-Object -ExpandProperty UUID
155+
- **WinRM and PowerShell Remoting setup**:Enable-PSRemotingEnable-WSManCredSSP -Role server/clientSet-Item wsman:localhost\client\trustedhosts <host IP>
156+
- **VM operations via remote PowerShell**:$cred = Get-CredentialInvoke-Command -Credential $cred -ComputerName <Hyper-V host IP> -ScriptBlock { Start-VM <VM Name> }
157+
158+
## References
159+
160+
- [Microsoft Lifecycle Documentation](https://learn.microsoft.com/en-us/lifecycle/overview/product-end-of-support-overview)
161+
- [Microsoft Style Guide](https://learn.microsoft.com/en-us/style-guide)
162+
- [Accessibility Checklist](https://learn.microsoft.com/en-us/writing-style-guide-msft-internal/checklists/accessibility-checklist)

0 commit comments

Comments
 (0)