TL;DR – How to Fix!

If your Health service is in a Failed state, you most likely cannot get your SDDC Management service to start up. You also probably cannot manage the cluster via Windows Admin Center (WAC).

It also means you cannot run the Stop-ClusterPerformanceHistory command, as that relies on these services to be running.

If you do not care about the historical data of your cluster’s stats, you can purge it all and recreate everything by running the following commands on a S2D cluster node directly:

Before running any code you find on a random website, please read through it and run it at your own risk.

A Little more about SDDC Management

Since Windows Server 2019, when you deploy a Storage Spaces Direct (S2D) cluster, you get a few out-of-the-box resources for managing the S2D components via WAC:

This slightly changed in Windows Server 2022 (and Azure Stack HCI), where Microsoft moved these resources from the Core Cluster Group to its own SDDC Group:

Failover Cluster Manager sometimes does not show the SDDC Group in the GUI due to a display bug. Microsoft has made it clear that they have no interest in fixing this since you should be using PowerShell or Windows Admin Center… 🤷‍♂️

The SDDC Management resource is a grouping of “microservices” responsible for relaying information about the cluster, its member nodes, networking, and storage to whatever is querying the API. This is the main way that Windows Admin Center (WAC) and other tooling gets information about the cluster.

Leave a Reply

Your email address will not be published.