How do I remove an unoperational DC from AD?

  • Thread starter Thread starter Dean Rachwitz
  • Start date Start date
D

Dean Rachwitz

The first AD domain controller on my small Win2K network
is sick. I can log in to it, but I have a blank desktop,
either locally or via RDP. I can access data via shares
and it's running DHCP and DNS fine, though. If you can
help me fix it great, if not, I need to rebuild it, I
suppose.

Since it was the first, I imagine it is the operations
master. How do I transfer its AD roles to another DC,
remove it and reintroduce it into AD after I fix it?

Any help greatly appreciated.
 
I would try to delete the administrators profile on the Dc and then log in
and see if this helps any. you can do this be maping a drive to \\server\c$
go to the doc and settings dir and delete the administrator.domain or what
ever the profile name is. Then go back to the server and try logging on
again. if this works good if not while at the blank screen press ctrl +
shift + esc for task manager and end any processes that don't seem to be
normal services.
IF all else fails then you will need to promote another server to Dc and
then transfer all 5 fsmo roles to the new server. You make have to
decomishion the DHCP server. Rebuild server and then Use ntdsutil to do a
metabase cleanup to get rid of the other server in ad .
Promote to dc and then let it replicate. Here are some KB articles
HOW TO: Remove Data in Active Directory After an Unsuccessful Domain
Controller Demotion.
http://support.microsoft.com/?kbid=216498

HOW TO: View and Transfer FSMO Roles in the Graphical User Interface
http://support.microsoft.com/?kbid=255690
..

Let us know if you have anymore questions

HTH

Paul McGuire
 
Back
Top