RE: Provide feedback to DC promotion/replacement

To rename a domain controller using the Netdom.exe tool, the domain
functional level must be set to Windows Server 2003. Take care if you have
certificate authority on a dc, because domain controllers running Certificate
Authority services (CA) can never be renamed.

Good luck!

"agt" wrote:

You might run into few problem there.
1. Once promote DC3 into DC. You can not rename.
2. Make sure DC3 has GC enable.

"tnt" wrote:

Guys,

I posted this question a while back, but never had time to run through the
test. Anyways, here is the info:

We have DC1 & DC2 (domain controller & DNS). My goal is to replace DC1 in
the near future since the raid 1 controller failed on us (no more raid). On
DC1, we also have the TS Licensing Server.

Part of the goal is to add DC3 (domain controller) into the domain and then
in the long run demote DC1 (retire for good) and rename DC3 to DC1. Right
now DC1 has all the master operation roles.

Here is what I like to do in different timeframe (the week sequence is just
an example that I like to do in different time):

Week 1

1) Join DC3 to domain.
2) Install DNS and do nothing since it will replicate from AD
3) Promote to DC
4) Netdiag/dcdiag tests

Week 2

1) Transfer FSMO roles from DC1 to DC2
2) Netdiag/dcdiag tests


Week 3

1) Demote DC1 and bring it offline.
2) Rename DC3 to DC1 and reuse old IP address of DC1 (using
netdomcomputername).
3) Reinstall TS Licensing Server on the new DC1 (Call MS to reactivate
licenses)
4) Netdiag/dcdiag tests
5) Pray (joke).


Questions:

1) What else do I have to do besides the FSMO roles transfer? Also, during
this procedure, would it affect live production-meaning any users/clients?

2) On week 1, client workstation still use DC1 & DC2 as their DNS, so
nothing will change with them.

Please provide feedback. I will post more questions as I go.

Thanks,
TNT



.

Relevant Pages

  • Re: Domain controller name -rename issue
    ... Make sure you have at least a system state backup before starting the rename of the production one. ... The DNS host names of domain controllers in a renamed domain are not ... Windows NT 4.0 primary domain controller to Windows 2000 ... it with dcpromo /forceremoval to member server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Second domain controller does not take over in case the first fail
    ... Recently I did a test shutting down first our primary domain controller, ... which is both GC server and holds all the FSMO roles. ... local service credentials. ... DC1 was running perfectly at ...
    (microsoft.public.windows.server.active_directory)
  • Re: Demoting a DC in W2003
    ... forrest / single domain with three DCs. ... It's only role is being a DC and our primary internal DNS server. ... transfered the FSMO roles from DC1 to DC2 using the MS KB article 324801. ... The local domain controller has attempted to replicate the following object from the following source domain controller. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Mess - Problem promoting second server to DC
    ... > I was able to bring up a second domain controller on an old PC ... but DC1 died before I was able ... > the AD that was now running on DC2. ... > I installed DNS on DC2, and configured DC2 to use itself for DNS. ...
    (microsoft.public.windows.server.dns)
  • Re: Domain controller name -rename issue
    ... Because you did not know what your predecessor have done with the DC1 renaming, i would make sure that the correct existing DC2 have all 5 FSMO roles and is GC server and DNS with AD integrated zones only for the correct old named "domain" domain. ... AD users and computers and AD sites and services is cleaned up you can now promote the old DC1 again to domain controller. ...
    (microsoft.public.windows.server.active_directory)