We have setup Exchange 2010 recently with 2 DAG on 2 AD sites, each DAG has 3 nodes, Site A has 2 and Site B has the 3rd for DR. Site B has 2 also and the 3rd in Site A for DR, everything is working well so far but somehow Cluster Manager shows that Site B Quorum Configuration is in "Node Majority" and Site A Quorum Configuration is in "Node and File Share Majority". Also below, the alternate witness server is located in remote site, is that OK or NOT? From what I've read we do not need FSW because we have a 3 Node DAG, just curious why the quorum configuration differs. SITE A DAG01 Properties: AMB001 (mailbox server) AMB002 (mailbox server) AMB003 (mailbox server located in Site B for DR) Witness Server = AHUB001 (hub/cas server) Witness Directory = C:\FSW_DAG01 Alternate Witness Server = BHUB0001 (hub/cas server in Site B) Alternante Witness Directory = C:\FSW2_DAG01 SITE B DAG02 Properties: BMB001 (mailbox server) BMB002 (mailbox server) BMB003 (mailbox server located in Site A for DR) Witness Server = BHUB001 (hub/cas server) Witness Directory = C:\FSW_DAG02 Alternate Witness Server = AHUB0001 (hub/cas server in Site A) Alternante Witness Directory = C:\FSW2_DAG02 Thanks, Jonathan

The way it's designed, the DAG doesn't use the FSW when it has an odd number of members. I'm not sure what the indication you're seeing means. Where do you see "Node Majority" or "Node and File Share Majority"? The purpose of the alternate FSW is in case you need it in a remote site, so, yes, it's appropriate that it's located there. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I see it in Failover Cluster Manager in the Summary view of the DAG.

What do you show in "Nodes"?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I see the 3 mailbox servers (BMB001, BMB002, BMB003 ) and their network connetions.

You may need to re-run the set-databaseavailability command. Note: The quorum model change should happen automatically. However, if the quorum model doesn't automatically change to the proper model, you can run the Set-DatabaseAvailabilityGroup cmdlet with only the Identity parameter to correct the quorum settings for the DAG. src: http://technet.microsoft.com/en-us/library/dd298065.aspx Mike Crowley Check out My Blog!

Mike, What exact command should I run? After the command, should it be in Node Majority or Node and File Share Majority. Thanks Jonathan

The quote I provided above answers this question. "run the Set-DatabaseAvailabilityGroup cmdlet with only the Identity parameter " such as: set-databaseavailabilitygroup -identity dag1 Mike Crowley Check out My Blog!

Thanks, I'll try it later tonight.

Thanks, both shows as Node Majority now. JonathanF-

Great! Mike Crowley Check out My Blog!