Monday, September 22, 2008 12:47 PMWe're setting up a 2008 geocluster for our Exchange 2007 mailbox server. We've got the active node in our corporate location, and the passive node in one of our two production datacenters (call it "production A"). These are on two different subnets connected via metro ethernet. Forming the cluster was no problem.
Now, we want to add a file share witness as the quorum. In order to minimize datacenter-specific single points of failure, we want to host the witness file share in the second of our production datacenters, Production B. Production B has only servers from our production AD domain (which will call PRODUCTION). The 2008/Exchange servers are in a resource domain (call it RESOURCE). PRODUCTION trusts RESOURCE. I've confirmed the trust is working, as if I grant permissions on the witness share to a RESOURCE account, I can navigate to and view the contents of the share when logged in a RESOURCE server.
When I ude the wizard to configure the file share witness, I enter the path to the share on the Production B server, and after a brief delay to validate the share path, I get an error message that the path I entered is not a valid share path. I've granted full control permissions on the share and underlying directory to both nodes computer objects (e.g. NODE1$) and the cluster object. I've looked in the security event logs on the cluster nodes, on the production B server, and all the domain controllers in both AD domains, and I can find no audit entries, showing either sucess or failure. When I access the share from my user account, I do see the login request.
What am I missing? Is a witness share on a trusted domain not supported? Have I misconfigured my settings? Do I need to use the command line?
Monday, September 22, 2008 2:09 PMNevermind, it would seem that creating the file share quorum resource from a command line bypasses whatever the issue is with the GUI wizard. I found a step-by-step reference and it was easy enough to follow and my file share witness is working correctly.