- Split-brain DNS deployment using Windows Server DNS policy - Wed, Nov 30 2022
- Veeam Backup for Microsoft 365—Why you need to back up your M365 data - Tue, Nov 15 2022
- Cloud-based patch management with Action1 - Tue, Nov 8 2022
Most businesses initially size their Hyper-V cluster based on the number of virtual machines they need to run, storage requirements, and compute/memory resources that fit their needs. However, resource needs can change for many reasons. This might require additional compute power.
Hyper-V cluster architecture ^
Running a Hyper-V cluster on-premises involves creating a Windows Server Failover Cluster (WSFC) of Windows Server hosts containing the Hyper-V role. Virtual machines running on each Hyper-V host can be made highly available using this approach and the built-in WSFC functionality.
Therefore, if a Hyper-V host in the failover cluster fails, it will be restarted on a healthy Hyper-V host. This also means that Hyper-V hosts can easily be added to the failover cluster to scale out the solution. For example, if more computing, memory, and storage (in the case of Storage Spaces Direct) are needed, adding a host adds its contributing resources to the cluster.
Tools to add Hyper-V hosts to a failover cluster ^
Hyper-V administrators need to use a wide range of legacy tools to manage Hyper-V and accomplish all management tasks. These tools include Failover Cluster Manager, Hyper-V Manager, and PowerShell. Microsoft has long seen the need to provide an all-inclusive tool to give administrators the capabilities they need in one tool.
Windows Admin Center is the relatively new management tool Microsoft is developing to replace many of the legacy tools found in Windows Server. It provides a web interface that can be accessed anywhere and is much more aligned with UX designs found in modern apps.
How to add a node to an existing Hyper-V cluster ^
We can easily add a node to an existing Hyper-V cluster using Windows Admin Center. But, first, we need to add the Windows Server Failover Cluster (WSFC) to Windows Admin Center. This process is straightforward. Select Add from the All connections option in the dropdown menu in Windows Admin Center.
Once you select Add, you will see the various options listed for adding or creating resources in Windows Admin Center. The option we are interested in is Server clusters. Click the Add button to Add or create clusters running Windows Server or Azure Stack HCI.
Populate the Add cluster field with the Windows Server failover cluster name. The process will validate the cluster name, and you will see the green checkmark when the validation is successful.
Once the Hyper-V cluster is added to Windows Admin Center, you will see the +Add button under the Nodes menu. It allows adding nodes to the Hyper-V cluster.
When you click the +Add button, the Add servers to the cluster blade pops out from the edge of WAC. Here, you enter the hostname of the additional Hyper-V node. Then, click Add.
When you initially click Add, it places the server in a staging position, ready to be added. You then need to click the Add button at the bottom of the blade.
Once you click the Add button, you will see the process of adding the node to the cluster begin under the notifications window.
When adding a new Hyper-V node to the cluster, I received the following error during the process: There were errors adding nodes to cluster Add Nodes Action. Error: RemoteException: The server ‘hvhost03.cloud.local’ does not have the Failover Clustering feature installed. Use Server Manager to install the feature on this server.
Unfortunately, it seems that more proactive capabilities from Windows Admin Center are not in place at this time, similar to the checks that take place when you create a failover cluster. The screenshot below shows WAC performing proactive checks of the roles and features installed when creating a cluster. During this process, it will install the missing roles and features needed.
However, when you add a node to an existing Hyper-V cluster, you must install any missing features, such as Failover Clustering, manually. I suppose it has to do with the difference between a cluster WAC creates and manages from start to finish versus an imported cluster.
Once the missing features are added, the additional Hyper-V node is successfully added to the Hyper-V cluster using Windows Admin Center.
Final notes ^
As with other features and capabilities, Windows Admin Center is still rough around the edges in a few areas. Undoubtedly, we will continue to see missing features and capabilities added to WAC as time goes on.
Subscribe to 4sysops newsletter!
However, it has come a long way since its introduction, especially in cluster management, specifically Hyper-V hosts. As shown, you can add a node to an existing Hyper-V cluster using Windows Admin Center as long as you have the required roles and features preinstalled on the node.