var kba = new KBAlertz { "(RE)Launch Date" : "January 1st, 2015" }

Article ID: 976160 - View products that this article applies to.


You connect to a computer that is running Windows Server 2008 and that is acting as a Dynamic Host Configuration Protocol (DHCP) server. You use the Microsoft Management Console (MMC) DHCP snap-in on a computer that is running Windows Server 2008 R2 to make this connection. Then, you use the DHCP snap-in to convert the DHCP server's existing lease to a reservation. When you do this, the lease on the Windows Server 2008-based computer is marked as inactive. It is no longer displayed in the DHCP snap-in.

Note The same behavior occurs on a client computer that is running Remote Server Administration Tools (RSAT) and Windows 7 and on a DHCP server that is running Windows Server 2003. Converting a lease to a reservation on the client computer or on the DHCP server marks the lease as inactive.


To resolve this behavior, you must renew the lease on the Windows Server 2008-based computer's DHCP client. DHCP clients that are configured to renew leases automatically also resolve this issue if the automatic renewal takes place before the DHCP server clears out inactive leases.


Article ID: 976160 - Last Review: October 22, 2009 - Revision: 1.0
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Standard
kbtshoot kbdhcp kbexpertiseinter kbsurveynew kbprb KB976160