General discussion


Recovering Domain from non-booting PDC

By BraveLittleToaster ·
Durring and update to my Primary Domain Controller (win 2000 advanced server) something has it cought in a blue screen reboot loop. This I may not concerned about, however is there a way to recover my domain information and usernames/passwords so I can simply format over the boot partition and rebuild the server? I can get the server to boot into directory restore mode, but restoring system state (ntbackup) simply puts it back into the same loop. The last thing I want to do is have to rejoin 30 computers to a new domain when I rebuild the server. Definite steps would be much appreciated.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by wtkool In reply to Recovering Domain from no ...

Firstly you are passed the point of no return on the w2k server. Since your system state is pouched it would be easier to start over.Unplug that problem box and promote one of your existing BDC to PDC status. Make sure you pick the BDC that is not running wins or DHCP server.This will bring you back to where you started from. Format and install NT4 back on the problem box. Run a check of the hardware compatability on the new PDC. Make sure you have "Client for Microsoft Networks and File and print sharing for Microsoft Networks" tcp/ip protocols installed first and bound to your nic. Install dns on the new PDC and synchronize them up. Make sure you are pointing the nic to it's self for DNS. Now with no hardware issues and the right protocols installed run the upgrade to w2k. I'm assuming that you were upgrading an NT4 PDC to w2k. If you simply updated your w2k PDC emulator than and ran into problems and have a second DC, then use ntdsutil to seize the roles to another DC. Do a Meta data cleanup in AD of the decommisioned box. **** away the the system partion format and reinstall w2k server. Run DC promo and promote it back up into the domain as a DC. If none of the above solutions describe your situation then boot into DS restore mode on the W2K box and check the event logs to see what is causing the reboot. You may find that you have been infected.

Related Discussions

Related Forums