Support Tip: VMs deployed to Hyper-V networks experience delays acquiring an IP address after reboot

[System-Center-Team]

First published on TECHNET on Jul 31, 2014

~ Prad Senniappan

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.

Cause

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.

Resolution

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:

MsiExec.exe /X{3834A905-5CC1-454D-8CA4-AC449F12775D}

Next you need to upgrade the VMM 2012 R2 server to Update Rollup 3 (UR3) or later. For information on UR3 as well as a download link, please see the following:

2965414 - Update rollup 3 for System Center 2012 R2 Virtual Machine Manager ( http://support.microsoft.com/kb/2965414 )

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:

\<VMM_Installation_Folder>\SwExtn\DHCPExtn.msi

NOTE The default path is C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\SwExtn\DHCPExtn.msi

Copy 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.

Prad Senniappan | Senior SDE | Microsoft

Get the latest System Center news on Facebook and Twitter :

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

SCVMM 2012 R2