Re: Domain Controller Rebuild question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

You know, that's a good point. I guess I'm thinking that I don't want to
change any of the hooks into any applications that are installed on the DC,
Symantec AV server, SMS Management point, etc.

Another reason is that we're trying to keep some consistency in server
naming, which is probably a poor excuse. Thinking it over, it would probably
much easier to just rename it and fix the App stuff afterwards. Getting the
DC up and going would make the most sense regardless of it's name. AD, DNS
and DHCP would work for users regardless of servername.
--
Sandy Wood
Orange County District Attorney


"Al Mulnick" wrote:

Sandy, I know you have what you need, but I'm curious why you're emotionally
attached to the name of a DC?
Al



"Sandy Wood" <sandy.wood@xxxxxxxxxx> wrote in message
news:6B45CCBB-45A0-46F3-8CA6-AC2A386CAC02@xxxxxxxxxxxxxxxx
OK. So say I want to name the server the same name as before it blew up on
me. If I just remove it from the domain and let replication occur, will
that
be enough?
--
Sandy Wood
Orange County District Attorney


"Al Mulnick" wrote:

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






.

Relevant Pages

  • Re: Hidden services/processes in Win2k server
    ... You have no idea what backdoors may be running on it, ... tell you "your system is clean" next to a format and re-install. ... We have recently had some problems with people running telnet server, ... We're also about to install SecureIIS, ...
    (microsoft.public.inetserver.iis.security)
  • Re: rename servers to upgrade?
    ... If you have only two DC and you decide to clean install one after another ... run DCPromo on it to remove the active directory from the server ... preferred DNS server under TCP/IP configuration. ...
    (microsoft.public.windows.server.setup)
  • Corrupt 2003 Services
    ... I'm having the strangest problem with a clean built SBS2003 server, ... I now attempt to install the IIS g-zip compression fix in ...
    (microsoft.public.windows.server.sbs)
  • Re: Corrupt 2003 Services
    ... > I'm having the strangest problem with a clean built SBS2003 server, ... > I now attempt to install the IIS g-zip compression fix in ...
    (microsoft.public.windows.server.sbs)
  • Re: New Event Log Errors!
    ... Somehow along those lines I'd also installed the Certificate Authority ... Did you apply the last Server Pack for SBS Server? ... Please install Windows Support Tools on the win2k3 sp1 problematic ... Microsoft is providing this information only as a convenience to you: ...
    (microsoft.public.windows.server.sbs)