Your restore won’t mean anything if you do not go into ntdsutil and make that servers copy of AD the authoritative copy that will be replicated to all other servers.

 

Do all the other servers have the same issue?  If they don’t then I don’t think it is an issue with AD, it may just be an issue with the OS of the server or something else to that affect.  Remember that if you end up having to rebuild the machine, you need to clean up the metadatabase before re dcpromoing the DC with the same name.  You only need to do this if you can’t run dcpromo on the machine prior to rebuilding it.

 

Justin A. Salandra, MCSE

Senior Network Engineer

Catholic Healthcare System

914.681.8117 office

646.483.3325 cell

[EMAIL PROTECTED]

 

 

-----Original Message-----
From: Rinehart, Ken [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 15, 2002 12:23 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] AD restore mode

 

 

Anyone familiar with using the AD restore mode?  I have an issue with a domain controller that boots up to an error stating that SAM initilization failed because AD couldn't start.  Get a hex error 0xc00002e1.  I've got a few tech articles on the MS site but don't really address the issue.  I'm guessing that I'll need to restore the AD from a backup off of another machine?  Is this correct?  And is authoratative the right way to go in this case since this isn't the 1st DC in my domain I've got 3 or 4 others.

 

Thanks


Ken

 

 

Reply via email to