When using System Center 2012 R2 Virtual Machine Manager (VMM 2012 R2), you may discover that some virtual machines that are deployed on Hyper-V Network Virtualization networks with dynamic IP address allocation may not get an IP address for a few minutes after a reboot of the VM. Eventually the VM gets the IP address and otherwise functions normally.
The behavior can occur if the host has an older version of the VMM DHCP server extension. In order to verify this, find the version of “Microsoft System Center Virtual Machine Manager DHCP Server (x64)” installed on the host by running the following PowerShell command:
Get-WmiObject -Class win32_product -Filter 'Name = "Microsoft System Center Virtual Machine Manager DHCP Server (x64)"'
If the version is less than 3.2.7649.0 then VMs may not get IP addresses for a few minutes after a reboot.
To resolve this issue, you first need to manually uninstall the old version of the VMM DHCP server extension, otherwise you’ll end up with two entries in Control Panel\Programs. To uninstall the old version, run the following from a Command Prompt:
Once UR3 is installed, the last thing to do is install the new version of DHCP extension. The installer for this can be found on the VMM server in the following location:
The default path is
C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\SwExtn\DHCPExtn.msi
to the Hyper-V hosts experiencing the problem and run it to install the updated DHCP server extension. Once this is done, the VMs should no longer experience a delay in acquiring an IP address after a reboot.