Windows Server / DNS, DHCP & Server Networking
Inspect a Windows DHCP failover relationship before changing partners
A failover pair can continue serving some clients while its relationship is degraded. Read the actual state and partner details.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-DhcpServerv4Failover -ComputerName DHCP01Read the result
The result describes configured IPv4 failover relationships on the selected server. State must be compared with the partner and recent communication events.
Resolve and verify
Check partner reachability, clock alignment and scope consistency. Repair the verified fault and follow the documented state-transition procedure when intervention is necessary.
Before changing production
Do not delete and recreate a failover relationship or force both servers into conflicting ownership states.