Migrate AD and DHCP services from Windows Server 2012 to Windows Server 2016

Zeeshan Opel 1 Reputation point
2020-10-19T06:59:01.05+00:00

I have two domain controllers with Active Directory and DHCP services running on them with Windows Server 2012. I want to migrate both servers from Windows Server 2012 to Windows Server 2016 keeping name and ip address same as the old ones. Please guide me step by step procedure for the migration. Highly appreciated.

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,370 questions
Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,529 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,850 questions
Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,021 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Thameur-BOURBITA 32,501 Reputation points
    2020-10-20T08:54:20.057+00:00

    Hi,

    Before performing the DHCP migration, you should increase the release duration for client , to let them keep their IP during the DHCP migration:

    word-image-1.png

    Before start the active directory migration , you should check replication and if there is any issue in order to fix it before start the active directory migration. You can use the following command: 

    repadmin /showrepl  
  
dcdiag

    To migrate DHCP and AD server to new one with same name ,IP and settings you can the following steps:

    • Build new server on Windows 2016
    • Export DHCP settings , you can use powsershell or netsh dhcp command : export-import-dhcp-server-2016-settings
    • Install DHCP service on new server and import old DHCP settings , you should keep the DHCP disabled once you complete the setting importation
    • Remove DHCP service on old server and enable it on new server
    • If the FSMO roles are in old domain controller , you have to move it to another DC : move-addirectoryserveroperationmasterrole
    • Demote active directory on old server , once completed change its IP and name
    • On new server , rename the server with same name as old DC and change its IP with same as old server
    • Promote new server as domain controller, once completed , you can move back fsmo role to this server.
    • Do the same for the second server

    Please don't forget to mark this reply as answer if it help you to fix your issue

    1 person found this answer helpful.
    0 comments
  2. Sunny Qi 10,896 Reputation points Microsoft Vendor
    2020-10-19T07:52:51.683+00:00

    Hi @Zeeshan Opel ,

    Regarding of migrating AD and DHCP services from Windows Server 2012 to Windows Server 2016, please kindly refer to the following links.

    Step By Step Migrate Active Directory Server 2012 R2 to Server 2016

    How to migrate DHCP from Windows Server 2012 R2 to Server 2016
    Please Note: Since the websites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.

    Best Regards,
    Sunny

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  3. Dave Patrick 426.1K Reputation points MVP
    2020-10-19T12:49:46.863+00:00

    The prerequisite before introducing the first 2016 domain controller: domain functional level needs to be 2003 or higher. Since you want the name and ip address to be the same you can transfer roles off then decommission / demote one as first step.

    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2016, 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 again verify health, when all is good you can move on to next one.

    Also at some point either before or after I'd recommend migrating sysvol replication from older FRS technology to DFSR
    https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments