cdshreve
asked on
DAG and FSW issues
I have a 2 (AD)site exchange 2010 DAG set up. I moved the FSW to a third site on a Domain controller (I know not optimal). I recently shut down one site and thought that the high availability would keep the second site on line as the FSW and the one Server(hub/mailbox) would accomplish having the 2 votes needed to have quorum and stay on line and take over.
I look at the cluster properties and it shows that the FSW is still the old one I initially set up. It also shows that the Quorum type is nodeandfilesharemajority.
Any help would be much appreciated!
Thanks
I look at the cluster properties and it shows that the FSW is still the old one I initially set up. It also shows that the Quorum type is nodeandfilesharemajority.
Any help would be much appreciated!
Thanks
ASKER
Should have let you all know we have Win 2008 R2 boxes for the Exchange servers and the DC.
Since it is a DC you can't add the Exchange Trusted Subsystem universal security group to the local Administrators group on it but it let exchange create the folders and files.
Other than that I think I covered everything in that article....
Since it is a DC you can't add the Exchange Trusted Subsystem universal security group to the local Administrators group on it but it let exchange create the folders and files.
Other than that I think I covered everything in that article....
Sorry, I copied a wrong article.
http://blogs.technet.com/b/timmcmic/archive/2010/07/13/exchange-2010-file-share-witness-oddities.aspx
http://blogs.technet.com/b/timmcmic/archive/2010/07/13/exchange-2010-file-share-witness-oddities.aspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That is the command I used to move it to the third site and I added the actual directory.
So I tried moving it to a CAS server on the 2nd site, and it works like a charm. soooo, it looks to be an issue with the DC in the third site. Could it be a FW issue? What ports does it use to communicate to the FSW?
So I tried moving it to a CAS server on the 2nd site, and it works like a charm. soooo, it looks to be an issue with the DC in the third site. Could it be a FW issue? What ports does it use to communicate to the FSW?
http://technet.microsoft.com/en-us/library/dd351172.aspx