DC crash damage control
Posted on 2010-09-24
Came in in the middle of aproject and inherited all of this.
We have three DC servers. py the original priamry server crashed this week after being demoted to a member server. PY and AST both are backup DCs with Global Catalog enabled on both. We are having some minor issues, now that the demoted server has actually crashed.
1: one of the DCs, in a separate location and on a separate subnet, is now complaining that it can't find a logon server.
2: On the PDC, on the same subnet as the old PDC, I am now getting the error message that the DNS record for PY (on PY) cannot be deleted automatically and must be deleted manually.
This probably has a good deal of bearing on the issue: I demoted the original PDC PY, not knowing that it was an SBS installation. I realize that SBS cannot be demoted and must server as a DC, but having worked almost entirely with the iserver remotely, I missed the fact that it was a SBS DC.
How bad is this long and short term?
What is the immediate impact on log ons, etc.
What are the 3 highest priority steps I need to take to resolve this issue and stabilize the network?