How to Configure DHCP Failover in Load Balance Mode
Applies to: Windows Server 2019, 2022 and 2025.
DHCP failover shares lease state between two Windows DHCP servers. Load Balance mode distributes client requests while preserving service if one partner fails.
DNS and DHCP changes can interrupt authentication and remote access. Preserve console access, export current settings and test from representative clients. Managed Windows VPS services are available at networkmanager.info.
Prerequisites
- Install and authorize both DHCP servers.
- Ensure matching time, DNS and network reachability.
- Create the scope on the primary server.
- Choose a strong shared secret and secure channel.
Procedure
Step 1: Check servers
Confirm authorization and scope health.
Get-DhcpServerInDC
Get-DhcpServerv4Scope -ComputerName dhcp01.corp.exampleStep 2: Create failover relationship
Protect the shared secret and replace example names.
Add-DhcpServerv4Failover -ComputerName 'dhcp01.corp.example' -Name 'Office-Failover' -PartnerServer 'dhcp02.corp.example' -ScopeId 192.0.2.0 -LoadBalancePercent 50 -SharedSecret (Read-Host 'Shared secret' -AsSecureString)Step 3: Review relationship
Check state and partner.
Get-DhcpServerv4Failover -ComputerName dhcp01.corp.exampleStep 4: Test controlled interruption
Stop one DHCP service in a maintenance test and confirm renewed leases through the partner.
Step 5: Restore and resynchronize
Return both servers and monitor relationship state.
Verification
Both partners should report normal state and matching scope lease data.
Get-DhcpServerv4Failover -ComputerName dhcp01.corp.example
Get-DhcpServerv4Failover -ComputerName dhcp02.corp.exampleRollback
Remove-DhcpServerv4Failover only after choosing which server retains the scope and confirming clients remain served.
Operational notes
Failover does not replace backups and supports only two partners per relationship.
