In this guide, we will walk through creating a 2-node or 4-node Hyper-V failover cluster where the nodes are not domain-joined, using mutual certificate-based authentication instead of NTLM or shared...
There's a bit of mucking about - I wrote it up here: https://techcommunity.microsoft.com/blog/itopstalkblog/enable-certificate-based-authentication-for-windows-admin-center-gateway-servers/4455790
Based on your article, I successfully built a Hyper-V failover cluster on Windows Server 2025 using a workgroup and certificate-based configuration.
At present, both the Failover Cluster and Hyper-V are functioning correctly. However, I am seeing Event ID 20501 every minute in the Microsoft-Windows-Hyper-V-High-Availability/Admin event log:
"Failed to register the cluster name in the local user group: Incorrect function. (0x80070001). Hyper-V will retry the operation."
Despite this recurring event, the cluster appears to be operating normally. Do you know what could be causing this issue or how it can be resolved?
Event ID: 20501
Failed to register the cluster name in the local user group: