Hello:
I am trying to resolve a problem with my AD DS infrastructure.
Our domain has three 2008R2 DC's. All are GC's and each host the DNS service and have an AD Integrated copy of the forward lookup zone for the AD DS domain. All are up to date patch wise - in fact it appears that it was one of the patches installed yesterday that has caused the problem.
The problem started sometime overnight when patches were installed on the DC's. One of the DC's did not reboot successfully after the patches were installed and, because of that, it would seem that our entire AD infrastructure is broken - The notable issue being that we cannot on logon to our exchange servers.
The problematic DC was getting a blue screen on boot and the Stop error is "C00002E2 Directory Services Could Not Start", and the error status was 0xC0000001.
My first recovery efforts involved trying to get the problem DC back on line. I tried rebooting in safe mode but that failed so I booted from the installation DVD and did a "repair". From the command prompt I ran startrep.exe. It went through all it's steps and reported that it could not fix the problem. In the startrep log it indicated that all but one of the tests passed - the test that failed reported the following error "A patch is preventing the system from starting."
Further recovery steps I found required me to boot up in DSRM so I tried that. As the DSRM password I have recorded does not seem to be correct :-( I decided to move on trying to figure out why the other DC's were not just taking over.
The first step there was to try to determine why the Exchange 2010 server was not just using a different DC. Trouble is that I cannot successfully launch either EMC or EMS - the error I am getting is "No logon Servers can be found". Quite purposefully I did NOT specify a DC or GC for Exchange to use but, apparently, Exchange has decided to use the DC that's down and that's that. Of course, since I can't get the Exchange tools to start, I can't change that setting.
Next step was to look at the remain DC's - my thought was that, as I believe Exchange is pointing to the FQDN of the failed server, perhaps I could just punt that server out of the environment and add a new one with the same name.
So, at this point, I have logged on to both of the other two DC's and, in both cases then I try to launch AD DS tools like ADUC or ADDT I get: "Naming information cannot be located because: The specified domain either does not exist or could not be contacted" WTF?
As mentioned earlier, all three DC's are GC's, all three are DNS's and have the DNS information for the domain. While the DC that's down was entered as the 'primary' DNS on our DHCP server, the other two addresses are also set up as DHCP options and, except for name resolution of AD DS systems, the DNS infrastructure is working fine. When I look in the DNS consoles of the remaining DC's the appropriate AD DS info is present.
While it is true that the failed DC holds all the FSMO role, I don't understand why the other DC's are not accessible - isn't this the point of having multiple DC's in an AD domain??
Any thoughts of what I can try would be much appreciated!
Mike