Forum Discussion
Solved
Cluster issues with Exchange 2016
Hi, We recently rebuilt one of our Exchange servers, and have come across an issue with the Windows Failover Clustering, rather than the Exchange side of things. Once the server had been rebuilt...
- Answer was that the for whatever reason, it failed to automatically add the node back in to the Failover Cluster. When I tried to manually add it to the Failover Cluster, and it stated the node was already a part of a node, what that really meant was I had manually changed the service from Disabled to Automatic in the process of trying to find why it wasn't working.
Switching the service back to Disabled, then attempting to add the node to the cluster fixed the issue.
Now both DAG, and Failover Cluster are reporting as Healthy.
Answer was that the for whatever reason, it failed to automatically add the node back in to the Failover Cluster. When I tried to manually add it to the Failover Cluster, and it stated the node was already a part of a node, what that really meant was I had manually changed the service from Disabled to Automatic in the process of trying to find why it wasn't working.
Switching the service back to Disabled, then attempting to add the node to the cluster fixed the issue.
Now both DAG, and Failover Cluster are reporting as Healthy.
Switching the service back to Disabled, then attempting to add the node to the cluster fixed the issue.
Now both DAG, and Failover Cluster are reporting as Healthy.