Re: Domain Controller Rebuild question
- From: "Al Mulnick" <amulnick_No_SPAM@xxxxxxxxxxx>
- Date: Wed, 14 Jun 2006 19:13:22 -0400
When you go to add in the new server, I hope you plan to have a valid backup
stored safely somewhere.
If you have more than one DC, I would honestly say that you're biggest
concern is that your schema upgrades properly and quickly. To ensure that
goes smoothly, make sure that your DC's are healthy and replication is
operating correctly before starting.
If you should run into an issue during the procedure, that DC can be remade
with a new name and IP address and then promoted to DC. You'd have to clean
up the old information from the directory. You *could* also dcpromo the
existing down to a member server, bare metal install 2003 and then dcrpomo
it back up (after adprep etc.) which would give you a clean start on the OS.
That assumes you have more than one DC of course.
Al
"Sandy Wood" <sandy.wood@xxxxxxxxxx> wrote in message
news:2AFC0576-2CB3-4EFC-B74E-92DEA8E293FC@xxxxxxxxxxxxxxxx
I'm getting ready to upgrade on of my DCs from Windows 2000 to Windows
2003
and I'm trying to image and be ready for any scenarios. Assuming the worst
happens and I need to rebuild the DC from bare metal, what AD cleanup
tasks
do I need to consider when adding the DC back into my Win2003 domain? Do I
need to clean the schema before adding the new server?
--
Sandy Wood
Orange County District Attorney
.
- Prev by Date: Re: target principle name is incorrect
- Next by Date: Re: New accounts replicate disabled.
- Previous by thread: AD connect method fails when IIS anonymous logon is disabled
- Next by thread: Re: Domain Controller Rebuild question
- Index(es):
Relevant Pages
|
