windows 2000 server crashed. Please help

[ericwi]

Hi all,

Recently, I have a windows 2003 server std and I ran a dcpromo to join the domain controlled by windows 2000.The process was successfuly Hence, this windows 2000 is the FSMO, DNS and all the software required by AD to this domain controller. Now, my windows 2000 crashed due to some hardware problems which forced me no choice but to reinstall windows 2000.
I would like to know how to get this window 2000 back as a domian controller once more., hopefully can get all the users settings to its original state before it crashed.

Please advice.

Thanks

 

[smsg]

after reinstalling win 2000, did you run a restore of a full backup including system state? That should bring back your server to the state before it crashed.

the 2003DC controller would contain a sync copy of ADS and should resync back the restored ADS.


If that is not possible, you can always install dns and other services on win2003 DC. Stopping and restarting "netlogon" services on 2003 DC would rebuild the necessary entries in the dns. Enable global cataloge services etc.

SMSG

 

[ericwi]

smsg,

Thanks for your reply. I do not have a backup on it .

-Is it safe to install w2k again with the same name and network properties before it crashed?

-Do I need to install sp 4 before I do a dcpromo on my new w2k server?

-Any changes I should be aware of on my windows 2003 prior to my w2k dcpormo process?

Thanks

 

[Jpoandl]

Your originaL question was a little confusing...

Did you have two DC's? or just one? (before everything crashed)

I'm going to assume that you had two. And now one of them is crashed. And that you don't have a backup.

The absolute first this I would do, is ............guess.......... come on, you can do it.....ok I'll give it to you....is BACKUP the working DC.

No, you can't simply just rebuild a new DC and expect that your domain will function 100%. Although, it probably will function. If you know that the failed DC is dead and will never come back online, I would clean up you AD database first. You will need to get rid of the DC in AD because AD will keep on trying to communicate with it. This will generate a ton of event viewer errors in your domain. Heres how:

http://support.microsoft.com/default.aspx?scid=kb;

[LN];q216498

After the old dead DC is cleaned up, just install the new server and run DCPROMO on it.




If the dead DC is your only DC...and now its dead....and you don't have a backup on it....you need to reinstall and recreate everything from scratch.

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[mlichstein]

Don't restore the system state of your 2000 DC when you have a working domain controller (the 2003 box).

Do the metadata cleanup, seize the FSMO roles to the 2003 server, install all critical updates on the 2000 server and then run dcpromo.

A system state restore of a DC is only for two situations: 1) you only have one DC, and it just died, or 2) you need to do an authoritative restore (like if an OU was deleted).