If you’ve found yourself here then chances are you messed up one of your domain controllers or at least one of your DHCP Servers. I admit I did. More than once. And I’m tired of querying for the elusive “Remove-DhcpServerv4Failover” PowerShell script to force delete the Windows Server DHCP failover relationship. The way content makes its way onto this site is usually split into two categories: Repetition, and one time specialized content not found on the internet (at least difficult).
# Command syntax: Remove-DhcpServerv4Failover -ComputerName <ServerName> -Name <DHCPFailoverRelationshipName> -Force # Real world example: Remove-DhcpServerv4Failover -ComputerName Win2016core-1 -Name "win2016core-1.ad.sysinfo.io-win2016core-2.ad.sysinfo.io" -Force
And that should do the trick. If you wanted you could form again the relationship in case the issue was a problem with the server names or you could form a new relationship with a new server. Either way just make sure you don’t have 2 DHCP servers assigned to the same IP scope that are not in a failover relationship.
In the event you have network communication with the partner in the relationship you can use the GUI instead:
Step 1. Open DHCP console. From server manager dashboard, click Tools -> DHCP.
Step 2. In DHCP console, expand IPv4 node. Right-click the scope you want to de-configure failover and then click Deconfigure Failover.
Step 3. Ignore the warning and click OK.
Step 4. Click OK.
Step 5. Click Close when you are done. You won’t be able to see a scope on partner server.
When you're a little too careless about virtualizing your domain controllers, cloning, migrating, backing up and restoring, returning from vacation… Read More
Systemd is new service manager for Linux. It's a replacement for all previous init systems (SysV/SysVinit & Ubuntu's Upstart) and… Read More