This article describes two updates that are available for Microsoft System Center 2012 R2 Virtual Machine Manager (VMM). One update is for servers, and the other update is for the administrator console.
These updates are previews and are supported in production only if you are part of the System Center TAP program. Microsoft will support upgrading from the Update Rollup 5 Preview to the final release of Update Rollup 5. Please contact your Microsoft representative for more information about the TAP program.
This article also contains the installation instructions for Update Rollup 5 Preview for System Center 2012 R2 Virtual Machine Manager.
Features that are added in this update rollup
This update adds support for the following operations:
Creating and managing replication groups on supported storage area network (SAN) devices
Enabling the protection of a storage volume or a group of storage volumes in a replication group
Deploying new virtual machines (VMs) into protected storage by using placement
Migrating existing VMs into protected storage by using placement
Coordinating planned, unplanned, and test failover of VMs and storage volumes between sites by using Microsoft Azure Site Recovery (ASR)
Known issues with this update rollup
Migration of a replica VM by using live storage migration or live migration causes the replica VM to lose its protection status. Please contact the System Center team for a hotfix that you can apply if you experience this issue.
How to obtain and install Update Rollup 5 Preview for System Center 2012 R2 for Virtual Machine Manager
Update packages are available by manual download from Microsoft Download Center.
The following files are available for manual download from the Microsoft Update Catalog.
VMM server (KB3011473)
Download the VMM server update package now.
Administrator console x64 (KB3014875)
Download the administrator console update package for x64 now.
Administrator console x86 (KB3014875)
Download the administrator console update package for x86 now.
To manually install the update packages, run the following command from an elevated command prompt:
msiexec.exe /update <package_name>
Note In this command, the placeholder <package_name> represents the actual package name.
For example, to install the Update Rollup 5 Preview package for a System Center 2012 R2 Virtual Machine Manager server (KB3011473), run the following command:
msiexec.exe /update kb3011473_vmmserver_amd64.msp
Important As of Update Rollup 5 Preview, this step is no longer required.
Important The System Center Virtual Machine Manager DHCP Server (x64) component must be manually updated on all VMM Hyper-V hosts. If this component is not updated, virtual machines may not be assigned an IP address for several minutes after the restart of the VM. (Eventually, the VM receives the IP address and otherwise functions as usual.) To check the version of the VMM DHCP agent, run the following command from an elevated PowerShell Command Prompt window on the host:
Get-WmiObject -Class win32_product -Filter 'Name = "Microsoft System Center Virtual Machine Manager DHCP Server (x64)"'
If the version is earlier than 3.2.7828.0, you must update the agent. To update the agent, follow these steps:
Uninstall the old version by running the following command from an elevated PowerShell Command Prompt window:
MsiExec.exe /X <IdentifyingNumber>
Note You can retrieve the value of the <IdentifyingNumber> placeholder from the output of the Get-WmiObject PowerShell command that you ran earlier.
Copy the Dhcpextn.msi file from the VMM server after you apply Update Rollup 5 Preview for System Center 2012 R2 Virtual Machine Manager to your Hyper-V hosts. By default, the file is located in the following folder on the VMM server:
Note The placeholder VMM_installation_folder represents the location where VMM is installed. By default, this is the following folder:
C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\SwExtn\DHCPExtn.msi
Double-click the file to start the installation, and then follow the steps in the wizard.
Note If you also have the administrator console installed on the VMM server, you should install the updates in the following order:
Update Rollup 5 Preview for the administrator console
Update Rollup 5 Preview for the VMM Server
Between these two installations, the VMM server might create one critical error log under the VMMLogs directory. This occurs because the administrator console shares some DLLs with the VMM server, and version conflict could lead to the logging of the critical failure. To resolve this issue, install both of the updates on the VMM server that you use to start the VMM service.
Files that are updated
VMM server update (KB3011473)
File that changed
Administrator console update (KB3014875)