AD Naming error

[JonR]

Hi all

Came back from holiday and found main DC (windows 2000 running ad, dns & dhcp) with error "Error Message: Windows Could Not Start Because the Following File Is Missing or Corrupt: \Winnt\System32\Config\Systemced"

Anyway fixed that by replacing system hive, so now it boots into windows and I can logon to the server, however if I try to load the ad users and computers msc it comes up with the following error

 

 

Has anyone seen this before? How do I fix this?

 

I have got 2 windows 2008 servers on the system and they are running ad, has the original win2k server lost sync with the domain? can I demote and the promote that server to recover the situation.

 

Any help gratefully recieved

[FN-GM]

You can demote and premote, does the server hold any roles?

 

Personally i would do a clean install, might as well and wont take long. Why not get rid of these 2000 server and just use the 2008 ones?

[pete]

Is there a compelling reason to keep it around, if all it's doing (that the other DCs aren't) is providing DHCP?

 

As FN-GM suggests, I'd seize the roles on another DC, demote it, shift DHCP to another server and retire it.