Avatar of Donna Johnson
Donna JohnsonFlag for United States of America

asked on 

How to migrate DHCP configuration from two DHCP servers configured for failover hot-standby?

How to migrate DHCP configuration from two DHCP servers configured for failover hot-standby?


Are there any good articles, documentation, videos on how to migrate DHCP configuration?

Existing environment:

1) Two DHCP servers running Window Server 2016 Standard where each scope is configured with DHCP failover in stand-by mode.  

2) Need to standup a third (new) DHCP server with the same scope configurations as the two current DHCP servers.

3) Need to decommission one of the original two DHCP servers that is already a member of the failover.

What is Microsoft best practices to accomplish this?

Do we need to break the failover relationship prior to starting this project?

Thank you

DHCPMicrosoft

Avatar of undefined
Last Comment
Robert
Avatar of Robert
Robert
Flag of United States of America image

When you configure failover in DHCP it should automatically send the main servers DHCP configuration to the failover server.
As far as I know you can only have 2 servers in this configuration I know you used to be able to do full DHCP failover clustering but I haven't looked into this in a few years.
So basically you would need to remove the other server from the failover configuration then add the new server in the wizard. 
Avatar of Philip Elder
Philip Elder
Flag of Canada image

Using PowerShell or CMD on the primary and destination:
# Migrate DHCP

# TODO Export
$OldDHCPServer = "MY-OldDC"
$Domain = "DOMAIN.Com"
Export-DhcpServer -File C:\DHCPdata.xml -Leases -Force -ComputerName "$($OldDHCPServer).$($Domain)" –Verbose

# TODO Import
$NewDHCPServer = "MY-TempDC"
$Domain = "DOMAIN.Com"
Import-DhcpServer -File C:\DHCPdata.xml -BackupPath C:\DHCP\ -Leases -ScopeOverwrite -Force -ComputerName  "$($OldDHCPServer).$($Domain)" –Verbose

# Using CMD
netsh DHCP server export C:\dhcp.txt

netsh DHCP server import C:\Temp\dhcp.txt

Open in new window

ASKER CERTIFIED SOLUTION
Avatar of Hello There
Hello There

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of Donna Johnson
Donna Johnson
Flag of United States of America image

ASKER

What would you do differently if you wanted to keep the same IP address on the new server? I know I would have to change the IP address on the second server to DHCP and assign the IP address to the 3rd server but would I have to do anything else?

Regards
SOLUTION
Avatar of Robert
Robert
Flag of United States of America image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of Donna Johnson
Donna Johnson
Flag of United States of America image

ASKER

Just to make sure, I would do this in the order below?

1. Break the DHCP failover
2. Change the IP's
3. Prepare a third DHCP server and install the DHCP role
4. Stop DHCP on the second DHCP server
4. Authorize DHCP on the third server
5. Configure the DHCP failover

Avatar of Robert
Robert
Flag of United States of America image

Correct (note that you could technically unauthorize / stop DHCP on the second server right after you break the failover. However the order you provided/listed would also work. 
Avatar of Donna Johnson
Donna Johnson
Flag of United States of America image

ASKER

  1. Break the DHCP failover.
  2. Stop DHCP on the second DHCP server.
  3. Change the IP's
  4. Prepare a third DHCP server and install the DHCP role
  5. Authorize DHCP on the third server
  6. Configure the DHCP failover
So is the above correct? Sorry for all the questions but we have never done this before and don't want to break DHCP.
Avatar of Robert
Robert
Flag of United States of America image

Yes the order you provided will work.

 


DHCP
DHCP

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

11K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo