Migrate DHCP from server 2012 R2 to Server 2019

Ed Dias 26 Reputation points
2020-11-30T11:51:32.803+00:00

I need to migrate DHCP from a server running 2012 R2 to Server 2019. I see there is a new migration tool however I wish the new server to have the same IP address as the old server. Does anyone have the steps or a guide for this?

Thanks.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,458 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
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
Windows Server Migration
Windows Server Migration
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Migration: The process of making existing applications and data work on a different computer or operating system.
408 questions
0 comments
Accepted answer
  1. Gloria Gu 3,891 Reputation points
    2020-12-01T07:11:42.57+00:00

    @Ed Dias Hi,

    Thank you for posting in Q&A!

    I've done tests in my own environment with server 2012R2 and server2019, it can be done by PowerShell command, please follow these steps:

    1.Log in with an administrator account to the Windows Server 2012 R2 system.

    2.Open Powershell and then type in the following command:

    Export-DhcpServer -File C:\DHCPdata.xml -Leases -Force -ComputerName old.network.local –Verbose

    43870-15.png

    3.Copy the file C:\DHCPdata.xml the Windows Server 2019 system.

    4.Install and configure the DHCP role on Server 2019

    5.Start the DHCP service.

    6.Type in the following command on Powershell to import the DHCP Data.

    Import-DhcpServer -File C:\DHCPdata.xml -BackupPath C:\DHCP\ -Leases -ScopeOverwrite -Force -ComputerName new.network.local –Verbose

    43789-16.png

    7.Restart the DHCP service.
    Verify your DHCP scope, IP leases, reservations etc and they should match with DHCP Server 2012 R2.

    43883-17.png

    Hope you have a nice day : )
    Gloria

    ============================================

    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.
    https://learn.microsoft.com/en-us/answers/articles/67444/email-notifications.html

    8 people found this answer helpful.

7 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ed Dias 26 Reputation points
    2020-12-16T11:35:42.993+00:00

    Thanks, for changing the IP address after migration , is it just a simple case of changing it in the normal via the connection properties?

  2. Ed Dias 26 Reputation points
    2020-12-16T13:09:48.753+00:00

    So steps would be.

    • run export powershell on old server. Deauthorize it in DHCP
    • Change IP of old server
    • Install DHCP server role on new server.
    • CHange ip to old server ip
    • Run import powershell
    • Auth new server with new ip (of old server)
    • Test!
    • Relax
  3. Bracy Poppell 1 Reputation point
    2022-10-12T17:45:11.087+00:00

    I know this is a little late, but I just wanted to add one step that is often overlooked, but may not affect most people. Also, if, as a few comments have noted, you are changing the IP address of the new server to the old server's IP then this last step is not needed.

    But here it is, please check with ALL your routers, firewalls, etc. that might be acting as a DHCP forwarder and make sure to change those to point to the new IP address of the DHCP server. Otherwise, network devices that rely on DHCP on other subnets will not be redirected to the correct/new server to get it's an IP address.

    0 comments