recovering a DC

J

James

Hello,

I have a window 2000 DC with corrupt registry (it is not the pdc). Is there
a way to recover the server and active directory by a parallel install? if
yes, how? thank you in advance.
 
G

Guest

Hi,
I have a window 2000 DC with corrupt registry (it is not the pdc). Is there
a way to recover the server and active directory by a parallel install? if
yes, how?

have you got a System State Backup from _this_ Server ?
If the Server is only a DC, then you can demote your DC from the domain with
DCPROMO, install the server new and then promote your server in the domain
again with DCPROMO.
 
J

James

Thanks for the reply,

The server is only a DC and is not bootable at this time. Also, there is no
good backup for the system.
 
H

Hank Arnold

I would:

1) Verify that all FSMOs are on the other DC's
2) Verify that all other functions like DNS, DHCP, etc. are on the other
DC's
3) Shut the bad DC down and verify that the network functions normally
4) DCPROMO to a member server
5) Remove from the domain
6) Verify whether a meta data cleanup is necessary
7) rebuild the server
8) DCPROMO it back

Regards,
Hank Arnold
Thanks for the reply,

The server is only a DC and is not bootable at this time. Also, there is no
good backup for the system.
 
J

Jorge Silva

Hi



- Transfer any fsmo roles olded by the servers to be removed

How to view and transfer FSMO roles in Windows Server 2003

http://support.microsoft.com/kb/324801/en-us

-Make sure that you have at least one GC on your forest.

- Transfer any other services that you might have on the old DC (like;
DNS, DHCP, Wins, DFS, etc).
- Take the old server offline; confirm that everything works with the old
server offline.
- If everything OK, use Dcpromo to remove the old DC from network, (Ps:
don't
forget to remove it manually from Active Directory Sites and Services)
Check:
Decommissioning a Domain Controller
http://technet2.microsoft.com/Windo...bf98-4a80-8718-dd80dc1071fd1033.mspx?mfr=true



If you have EFS take a look at:

http://support.microsoft.com/?scid=kb;en-us;241201&x=5&y=13


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

Hank Arnold said:
I would:

1) Verify that all FSMOs are on the other DC's
2) Verify that all other functions like DNS, DHCP, etc. are on the other
DC's
3) Shut the bad DC down and verify that the network functions normally
4) DCPROMO to a member server
5) Remove from the domain
6) Verify whether a meta data cleanup is necessary
7) rebuild the server
8) DCPROMO it back

Regards,
Hank Arnold
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top