yeah, I read that before posting this... and it was right under something about "assuming" the DC not reaching tombstone end of life... since I suspect it has reached end of life I wasn't sure. Also, it's not very clear on what "reconnecting" the DC means. Is there a command? do I just plug it back into the network? Since I am working remotely and can't afford to have it get FUBARd and lock me out ,I am not willing to try things randomly without knowing what it means exactly. i.e. I'm trying to be extremely cautious.
Main Topics
Browse All Topics





by: Patrick49erPosted on 2008-10-20 at 11:07:02ID: 22760468
The disconnected domain controller is running Windows Server 2003, and an authoritative domain controller running Windows Server 2003 is available in this site or a neighboring site: Reconnect the domain controller, and immediately follow the instructions in Use Repadmin to remove lingering objects.
om/en-us/l ibrary/cc7 86630.aspx
om/en-us/l ibrary/cc7 85298.aspx
The about is from the following article titled "Reconnecting a Domain Controller After a Long-Term Disconnection":
http://technet.microsoft.c
Use Repadmin to remove lingering objects:
http://technet.microsoft.c
This should work for you. Since you stated the DC was taken down before your time, I doubt if you kinow whether it was done via the recommended method MS discusses in the article. If it was, then you are even better off. :) In either case, this should get you set without the dcpromo issue, which I wouldn't have suggested anyway.