Two DHCP leases are created for each domain controller when you use the VDC cloning feature

Article ID: 2742836 - View products that this article applies to.
Expand all | Collapse all

Symptoms

Consider the following scenario:
  • You are using the virtualized domain controller (VDC) cloning feature that was introduced in Windows Server 2012. 
  • As part of your deployments, you implement Dynamic Host Configuration Protocol (DHCP). Therefore, cloned domain controllers automatically lease IP addresses when those domain controllers are created. 
  • Cloning finishes on each domain controller. 

In this scenario, you notice that two IP addresses are leased from the DHCP server for each cloned domain controller.

Note Only the more recent lease is used by the cloned domain controllers.
Back to the top | Give Feedback

Cause

This issue occurs because the new server first takes a lease in its pre-cloned state during the cloning process. The new server then clones, becomes a new domain controller, and obtains a new lease. However, the old lease is not released during this process.
Back to the top | Give Feedback

Resolution

To resovle this issue, manually delete the unused address leases in DHCP, or let those leases expire as usual. 
Back to the top | Give Feedback

More information

This behavior is expected.

For more information about how to configure and troubleshoot VDC, go to the following Microsoft websites:

Introduction to Active Directory Domain Services (AD DS) Virtualization (Level 100)
(http://technet.microsoft.com/en-us/library/hh831734.aspx)


Virtualized Domain Controller Technical Reference (Level 300)
(http://go.microsoft.com/fwlink/p/?LinkId=236370)

Back to the top | Give Feedback

Properties

Article ID: 2742836 - Last Review: September 21, 2012 - Revision: 8.0
Applies to
  • Windows Server 2012 Datacenter
  • Windows Server 2012 Standard
Keywords: 
KB2742836
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top