replacing a dc

  • Thread starter Thread starter kb
  • Start date Start date
K

kb

Need confirmation this are the correct steps for replacing
a dc(want to keep same name)in our ads single domain
native mode forest which contains 5 dc's, 4 of which are
gcs.
This one dc holds no fsmo roles and is a global catalog
server, however we have 3 other gcs.
Get new server ready, fully patched, etc. Do not join
domain. Give it a temp name.
Remove global catalog role from server I will demote.
Run dcpromo to demote the server.
Remove the server from adsu&c.
Shut server off.
Wait for replication.
Rename new server.
Join domain.
run dcpromo.
Sound right?
Thanks
 
I would add the step of removing the CNAME record for the old DC in DNS
under _msdcs after the demotion of the old DC. This way everything is clean
in DNS. I would also verify replication does occur successfully with other
DC's and the other DC's are healthy.
Besides that, steps look correct.


Steve Dodson [MSFT]
Directory Services
--------------------
Content-Class: urn:content-classes:message
From: "kb" <[email protected]>
Sender: "kb" <[email protected]>
Subject: replacing a dc
Date: Thu, 23 Oct 2003 11:46:21 -0700
Lines: 19
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Thread-Index: AcOZlfOK0a8p9uvAQ8C1n//HvD72Ng==
Newsgroups: microsoft.public.win2000.active_directory
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.active_directory:53010
NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
X-Tomcat-NG: microsoft.public.win2000.active_directory

Need confirmation this are the correct steps for replacing
a dc(want to keep same name)in our ads single domain
native mode forest which contains 5 dc's, 4 of which are
gcs.
This one dc holds no fsmo roles and is a global catalog
server, however we have 3 other gcs.
Get new server ready, fully patched, etc. Do not join
domain. Give it a temp name.
Remove global catalog role from server I will demote.
Run dcpromo to demote the server.
Remove the server from adsu&c.
Shut server off.
Wait for replication.
Rename new server.
Join domain.
run dcpromo.
Sound right?
Thanks
Click to expand...


--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
It sounds right to me. I don't believe there are any
additional steps required, but I'm not certain.

Good luck with it.

Chad
MCSE, MCP
 
you do not need to join the domain before dcpromo'ing, just go dcpromo after rename
and make sure you are using one of the DNS server managing the domain name
I would add the step of removing the CNAME record for the old DC in DNS
under _msdcs after the demotion of the old DC. This way everything is clean
in DNS. I would also verify replication does occur successfully with other
DC's and the other DC's are healthy.
Besides that, steps look correct.


Steve Dodson [MSFT]
Directory Services
--------------------
Content-Class: urn:content-classes:message
From: "kb" <[email protected]>
Sender: "kb" <[email protected]>
Subject: replacing a dc
Date: Thu, 23 Oct 2003 11:46:21 -0700
Lines: 19
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Thread-Index: AcOZlfOK0a8p9uvAQ8C1n//HvD72Ng==
Newsgroups: microsoft.public.win2000.active_directory
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.active_directory:53010
NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
X-Tomcat-NG: microsoft.public.win2000.active_directory

Need confirmation this are the correct steps for replacing
a dc(want to keep same name)in our ads single domain
native mode forest which contains 5 dc's, 4 of which are
gcs.
This one dc holds no fsmo roles and is a global catalog
server, however we have 3 other gcs.
Get new server ready, fully patched, etc. Do not join
domain. Give it a temp name.
Remove global catalog role from server I will demote.
Run dcpromo to demote the server.
Remove the server from adsu&c.
Shut server off.
Wait for replication.
Rename new server.
Join domain.
run dcpromo.
Sound right?
Thanks
Click to expand...
Click to expand...
 
Back
Top