We help IT Professionals succeed at work.

How to integrate the new AD domain controller + DNS with the current AD domain controller with no downtime ?

258 Views
Last Modified: 2017-03-28
Hi all,

I'm about to commission 2x new Windows Server 2012 R2 and promote it as AD integrated DNS with Domain Controller (GC) role to replace the existing 2008 R2 DC/GC & DNS role.

What are the steps to implement it without outage or downtime to the existing environment ?

How can I decommission the old 2008 R2 Domain controller without impacting the Exchange email and DNS resolution ?

Thanks.
Comment
Watch Question

Are the new DC going to have the same name/IP?
s_sykesIT Director
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Principal Support Engineer
CERTIFIED EXPERT
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Senior IT System EngineerSenior Systems Engineer
CERTIFIED EXPERT

Author

Commented:
Hi Luis,

No, I plan to have different name and IP address since keeping the same name is going to be harder to cutover.
Senior IT System EngineerSenior Systems Engineer
CERTIFIED EXPERT

Author

Commented:
Dave and Sykes,

Thanks for the reply. No, it is just running as Domain Controller / Global Catalog + DNS and DHCP only for the remote office (different AD site but same AD domain).

The old 2008 R2 server does not have any FSMO role since the FSMO roles are held by the main DC/GC in the Data Center.

I guess it is just simple Next-Next-Finish deployment :-)
Senior IT System EngineerSenior Systems Engineer
CERTIFIED EXPERT

Author

Commented:
I've also checked in the AD domain, any server with static DNS is not using the DNS in these two servers that I'm about to decommission.
DHCP scope can be changed the day before the demotion I guess.
CERTIFIED EXPERT
Distinguished Expert 2018
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Senior IT System EngineerSenior Systems Engineer
CERTIFIED EXPERT

Author

Commented:
Cliff,

OK, so in this case how do I plan this properly ?

Can I reduce the DHCP IP lease to just 1 hour few days before the decommission process ?

so that on the decommission day, I can just wait one hour for the new IP to be assigned by the DHCP server ?
DrDave242Principal Support Engineer
CERTIFIED EXPERT
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Senior IT System EngineerSenior Systems Engineer
CERTIFIED EXPERT

Author

Commented:
OK so the high-level steps will be:

1. Install & Configure the 2x new 2012 R2 VMs newDC1 & newDC2 as AD/DC&GC
2. Configure as DNS+DHCP server role
3. In the existing DHCP server oldDC1, add the new DNS server as newDC1 & newDC2
4. Reduce the IP lease from 8 days into 1 hour to make it in effect
5. After all workstation clients get the new lease, decommission / demote oldDC1 and oldDC2

Can anyone clarify if that is correct ?
CERTIFIED EXPERT
Distinguished Expert 2018
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Senior IT System EngineerSenior Systems Engineer
CERTIFIED EXPERT

Author

Commented:
Cliff,

I'm decommissioning the old 2008 R2 servers and introducing the new 2012 R2.

Hopefully the steps above I mentioned is correct apart from the DHCP scope lease modification that I'm modifying and importing with another steps (Powershell script).
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Senior IT System EngineerSenior Systems Engineer
CERTIFIED EXPERT

Author

Commented:
Thanks All !