Hi:
I'm looking at an Exchange 2010 install with a root domain, user child domain, resource child domain (where servers are located), and few other child domains operated by other company entities. Single forest, one exchange organization. All DCs
are 2008r2. Exchange is also installed on 2008 r2.
The resource child domain contains a multi-node DAG with multiple copies of databases. I've been testing the same configuration in a test lab to determine the dependency list of exchange components in various scenarios. I've noted two so far,
and wonder how to best prepare for the "day" when things break.
One is the restart sequence for active directory. While you may have multiple DNS servers specified, it seems that Windows has problems using the second or third DNS entry (at least quickly ) to get a DC up and running. Is there a recommended
way to configure DNS settings for DCs in a child domain. Should they point to themselves first, root domain second...all point at root domain, etc.
One of the tests I performed was to replicate the user account child domain DNS to all DCs in the forest. Even in the absence of the root domain controllers being up, machines seemed sluggish to resolve names or servers in the user account child domain,
despite having a copy of the zone. This seemed to be resolved once the Root DCs/DNS were started.
Along the same lines of a test, trying to get Exchange up fully without the root DCs seems to be problematic. Scenario...root DCs are down, but both the child user account domain and resource domains DCs are all functional. Even with the child domain user
acct zone replicated to all DCs. Unless the root zone DC was up..System attendant service on the Exchange DAG nodes would not start. So despite knowing where the child user domain was, it seemed unable to resolve things properly until the root was configured. Any suggestions for Exchange configuration tweaks in a resource child domain and User child domain??
What is the MS Exchange System Attendant service looking for on startup?
thanks