I've given up on TechNet forums as no one there can ever answer a question...back to EE!
We have a customer with an odd problem in the setup of their Exchange 2010 SP1 DAG. They have 2 AD Sites and each site is physically different. One HQ and one dedicated DR site. Each site has a combined CAS/HUB server and a Mailbox server for a total of 4 servers (all virtual). The DAG is therefore a 2 member DAG, with each node in a separate physical site. It is in DAC mode. Although the File Share Witnesses are listed correctly in the DAG properties, when you look at the Failover Cluster Manager, there are 3 FSWs listed. Someone clearly added a 3rd one in an attempt to "fix" something and the FSW in the primary Site that is listed is an old one no longer used. Hence, in the Summary at the top of the Failover Cluster Manager, there is a warning that the FSW is down. The net effect of all this is that the Failover Cluster manager does not "see" the real FSW in the primary site (it actually lists the original one and marks it as "Offline") and therefore the 2nd Mailbox server is the 2nd vote in the DAG. So, when the 2nd Mailbox server is rebooted, the databases dismount in the primary Site.
How can I clean this up? I assume there are some Cluster commands that can add/delete the FSWs listed and essentially re-do them? What effect will that have on the DAG? Need answers quickly. Thanks.