Article ID: 2922695 - View products that this article applies to.
Assume that you perform a migration for your Dynamic Host Configuration Protocol (DHCP) servers to servers that are running Windows Server 2012 R2 or Windows Server 2012. Then, you configure DHCP failover on the servers. After the migration, you notice that several IP addresses in each scope are marked as BAD_ADDRESS in the DHCP server address lease table and become permanently unusable. Specifically, the scope statistics on the primary and secondary server are not synced correctly.
This issue occurs because DHCP servers lease the IP addresses that are actually owned by some client after the migration. Then, these IP addresses are marked as BAD_ADDRESS.
To resolve this issue in Windows Server 2012 R2, install update 2919355.
To resolve this issue in Windows Server 2012, install update rollup 2919393.
For more information about how to obtain update 2919355, click the following article number to go to the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2919355/ )Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014
For more information about how to obtain update rollup 2919393, click the following article number to go to the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2919393/ )Windows RT, Windows 8, and Windows Server 2012 update rollup: February 2014
Note After you apply this update, IP addresses that are marked as BAD_ADDRESS will be removed when clients renew those IP Addresses.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to configure DHCP for failover, go to the following Microsoft website:
How to configure DHCP for failover in Windows Server 2012
See the terminology
(http://support.microsoft.com/kb/824684/ )Microsoft uses to describe software updates for more information.
Article ID: 2922695 - Last Review: April 8, 2014 - Revision: 2.0