Thursday, January 2, 2014

This post relates to the new Windows Server 2012 Failover technology. I was diagnosing DHCP Issues at a customer when I was required to remove my DHCP scopes from failover configuration then re-add them. After attempting to re-add the scopes I received the following error.

Despite removing the scopes from DHCP failover the partner server still believes the DHCP failover relationship was in existence.

After messing around a little longer I found out a work around. The error was occurring because I was using the same Relationship Name as before. Changing the Relationship Name to something else resolves the issue.