|
Yes that is the best way, but in order to dcpromo it again, you will
first have to remove it from the metabase of AD from another DC. There should be MS Technet Docs on how
to do this. Does anyone know? Justin A. Salandra, MCSE Senior Network Engineer Catholic Healthcare System 914.681.8117 office 646.483.3325 cell -----Original
Message----- The machine has been
rebooting itself in an edless loop for at least a month. I just stumbled
upon it because it's located in an area that isn't visited much. I
haven't seen anything weird in AD other than a mention of not being able to
replicate to all DCs in the site which may explain why I was getting that
error. Looks like it's back to doing the same thing again. What is
the best way to rebuild this guy? Wipe it clean, reinstall W2K server
then DCPROMO using the same name it had?
-----Original Message----- You may have to cease the roll of that operation
master to a different role for the time being. It sounds like the machine is just not liking you right
now. What were you doing before
this happened on the machine? Justin A.
Salandra, MCSE Senior
Network Engineer Catholic
Healthcare System 914.681.8117
office 646.483.3325
cell -----Original
Message----- Interesting.
Well after playing around I figured out a way to "fix" the database
on that machine using eseututl This infact cleared up the
inconsistancies in the DB and now the machine will boot up but I can't
login! Administrator passwords don't work. It doesn't help that we
don't know much about this machine. I believe it is the forest and
infrastructure controller for our root domain. Ken -----Original Message----- 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 -----Original
Message----- 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
|
- [ActiveDir] AD restore mode Rinehart, Ken
- RE: [ActiveDir] AD restore mode SALANDRA, JUSTIN
- RE: [ActiveDir] AD restore mode Rinehart, Ken
- RE: [ActiveDir] AD restore mode SALANDRA, JUSTIN
- RE: [ActiveDir] AD restore mode Rinehart, Ken
- RE: [ActiveDir] AD restore mode Fugleberg, David A
- RE: [ActiveDir] AD restore mode SALANDRA, JUSTIN
- RE: [ActiveDir] AD restore mode Sadie, John (DIS)
- Re: [ActiveDir] AD restore mode Tony Murray
