Questions about failover cluster file share witness

Question

We're running a 4-node 2-site/subnet failover cluster. Early on we discovered a misconfiguration where the witness was placed on a DFS share. As expected this caused a split-brain when maintenance took down connectivity between sites.

Using failover cluster manager a new, non DFS share was designated as witness and the old one taken offline. But, FCM still listed the offline DFS share as the "Witness" at the top of the FCM; under Cluster Resources it shows the new witness Online and the old one Offline.

IN THE ABSENCE OF ANY OTHER CHANGE OR NETWORK OUTAGE, would this change take down an otherwise healthy cluster?

Thank you for your time.

Answer 1

@Hardesty, Joshua , You can safely remove the older the resource till the time your nodes are up and running.
You could also follow the below the step however it is highly recommended that you do it in downtime windows(Although nothing would be impacted)

Go to Quorum Configuration from FCM and do not configure any witness. This will result in a mode where in node majority will be in action.
Now, your cluster will continue to run and ideally, there should not be any resource pointing to a file share witness.
Go back to Quorum Configuration again and this time, select the new file share witness.
You should now see the new file share witness being online.