Steps to migrate domain controller from 2008 to 2016 with DHCP and DNS...

All replies

• 

  

  0

  Sign in to vote

  adprep is a part of domain controller promotion. DNS is also an integrated part of active directory domain services. (my steps included below) You can follow along here to migrate DHCP role to a new server.

  http://www.rebeladmin.com/2014/11/step-by-step-guide-to-migrate-dhcp-from-windows-server-2003-to-windows-server-2012-r2/

  I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting. Then I'd stand up the new guest, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to verify health, when all is good you can decommission / demote old one.

   

   

  ---

  
  Regards, Dave Patrick ....
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management
  
  Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
  

  • Proposed as answer by David_Ding2018Microsoft contingent staff Tuesday, January 15, 2019 1:45 PM

  Thursday, January 10, 2019 10:30 PM
• 

  

  0

  Sign in to vote

  I've seen documents for upgrading from Windows Server 2012 to Windows Server 2016.

  The Overview:

  1. Add New Domain Controller with Windows 2016.  This will automatically ADPREP forest and Domain
  2. Promote Windows 2016 Domain Controller
     
  3. Transfer FSMO role if needed (there can only be ONE FSMO)
  4. Demote Domain Controllers
  5. Raise the Forest and Domain Functional level to 2016

  My question is, what about the DHCP and DNS?  There are no guides for DC that has DHCP and DNS.

  Do you migrate the DHCP from the old Windows Server 2008 to the new Windows 2016 Before, During (and which step), or After demoting the old AD server?

  ---

  SysAdmin

  
  

  Hi,

  concrening adprep /forestprep, will be launched automatically when you promote your first domain controller on Windows 2016 using a account member of enterprise and schema admins group.

  Concerning DNS, as explained by Dave, the domain DNS zone will be  replicated will you promote your domain controller 2016. There is no additional action required to migrate DNS.

  Concerning DHCP server , you have to migrate manually after or before demotion of old DC because it don't depend of the AD migration, you have  export data from old DC/DHCP and import it on new DC/DCHP  2016, you can follow the procedure described on the following link : Migrate DHCP from Windows Server 2012 R2 to Window Server 2016 in Just Two Steps.

  ---

  Please don't forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/

  Thursday, January 10, 2019 11:12 PM
• 

  

  0

  Sign in to vote

  You are right about the upgrade steps for your AD DS. For the FSMO transfer, you can either do it manually or it will be automatically done by the FSMO holders when they are getting demoted as long as they can communicate with the other domain controllers and this is not a forced demotion.

  For the DNS servers, assuming that your DNS zones are all AD-integrated, they will be automatically replicated to your new domain controllers as long as the new domain controllers are also DNS servers. It may be easier to re-use the IP addresses of your old servers to avoid updating the configurations on the clients (through DHCP for dynamic IPs or manually for static ones). If you have a different setup other than the one I have described then you may have a different path to take.

  For the DHCP, you can simply export the database and import it on the new server and then shutdown the service on the old server. If you re-use the same IPs then you won't have to change your DHCP relay agents configuration.

  ---

  This posting is provided AS IS with no warranties or guarantees , and confers no rights.

  Ahmed MALEK

  My Website Link

  My Linkedin Profile

  My MVP Profile

  • Proposed as answer by David_Ding2018Microsoft contingent staff Tuesday, January 15, 2019 1:45 PM

  Saturday, January 12, 2019 3:46 AM
• 

  

  0

  Sign in to vote

  how can I find out what all hosts are using the domain controller that is being replaced for DNS resolution?  Is there a command or a tool I can use?  I do not want to miss changing the DNS entry of any hosts NIC.  We have Windows, Linux and Appliances in our environment.

  Thanks,

  Emil

  Thursday, June 25, 2020 5:05 PM