Update Rollup 3 for System Center 2012 R2 Virtual Machine Manager

Applies to: Microsoft System Center 2012 R2 Virtual Machine Manager


This article describes the issues that are fixed in Update Rollup 3 for Microsoft System Center 2012 R2 Virtual Machine Manager. Two updates are available for System Center 2012 R2 Virtual Machine Manager. One update is for servers and the other is for the administration console. This article also contains the installation instructions for Update Rollup 3 for System Center 2012 R2 Virtual Machine Manager.

Issues that are fixed and the features that are added in Virtual Machine Manager

Issues that are fixed in this update rollup

  • Total storage for a User role is reported incorrectly. For example, the User role can use only half of the allowed quota.
  • A host cluster update fails intermittently because of a locked job.
  • Virtual machine (VM) refreshers do not update highly available virtual machines (HAVMs) after failover to another node.
  • A cluster IP address for a guest cluster configuration in a Hyper-V Network Virtualization (HNV) environment is not updated correctly by using HNV policies during failover. For more information about this issue, see the following article in the Microsoft Knowledge Base:

    2981736 The cluster IP address in an HNV environment is updated incorrectly during failover
  • Server Message Block (SMB) shares may not be usable by high availability (HA) workloads if they are also connected to stand-alone hosts.
  • Storage objects discovery does not occur on a Virtual Machine Manager server if the discovery item is too big.
  • A Virtual Machine Manager job that assigns network service back-end connectivity fails.
  • Enable maintenance mode fails when you evacuate failed-state VMs.
  • The Virtual Machine Manager service cannot be restarted because of database corruption.
  • The ZH-TW language incorrectly appears in the tooltip of the VM Network icon.
  • Library refresher rewrites the alternative data stream on every file during every update.
  • For iSCSI hardware storage-based array, when the MaskingPortsPerView property option is set to "multi-port per view," the target endpoint is not obtained as the port address.
  • The virtual hard disk (VHD) is left in the source folder after storage migration is complete.
  • The addition of a bandwidth limitation to an existing virtual private network (VPN) connection is not added to the generated script.
  • A VM that is attached to an HNV VM network loses connectivity when it is live migrated to another node in the failover cluster that is not currently hosting other VMs that belong to the same VM network.
  • VM network shared access is lost after a service restart or an update interval.
  • The Remove-SCFileShare command fails for a network-attached storage SMI-S provider.
  • Setting the template time zone to UTC (GMT +0:00) is incorrectly displayed as "Magadan Standard Time."
  • The System Center 2012 R2 Virtual Machine Manager crashes when you add groups that contain the at sign (@) character in User roles.
  • VM deployment fails in a VMWare environment when you have virtual hard disk (.vmdk) files of the same size in your template.
  • Deployment of an application host on HAVMM fails and generates a 22570 error.
  • Live migration of an HAVM cross cluster creates a duplicate VM role in the target cluster.
  • An error occurs when you apply physical adapter network settings to a teamed adapter.
  • A VMM agent crashes continuously when the HvStats_HyperVHypervisorLogicalProcessor query returns a null value.
  • A host refresh does not update the VMHostGroup value of a VMWARE cluster after the cluster is moved from VCENTER.
  • VMM reports an incorrect Disk Allocation size for dynamic VHDs that are mapped to a virtual machine.
  • A VMM service template script application does not work for a self-service role.
  • VM creation fails if Virtual Machine Manager undergoes failover during the creation process.
  • The Access Status value of a file share is incorrect in the user interface.
  • The Virtual Machine Manager service crashes because of an invalid ClusterFlags value.
  • VMs cannot be deployed from a service template to a cloud across multiple host clusters (multiple datacenters).
  • Running processes are not sent a termination signal before shutdowns occur during VM specialization.
  • RunOnce commands that run during Linux OS specialization have a time-out setting that is not configurable in the UI. To control the time-out setting for Linux RunOnce commands:
  • Create a file, and name it /opt/microsoft/scvmmguestagent/etc/commandtimeout. Put the number of seconds to use as the time-out on the first line.

    This file can be created or modified on the VHD before it's imported to the library, or by using the first RunOnce command in the OS profile. For example, the following command sets the RunOnce command time-out to 900 seconds:

    echo 900 > /opt/microsoft/scvmmguestagent/etc/commandtimeout

Features that are added in this update rollup

  • This update includes a Linux guest agent upgrade to support the following new operating systems:
    • Ubuntu Linux 14.04 LTS (32-bit)
    • Ubuntu Linux 14.04 LTS (64-bit)
    • Note Ubuntu 14.04 x64 is supported as either a generation 1 or generation 2 virtual machine. To create a generation 2 VM template for Ubuntu x64, the following configuration must be applied to the VHDX before the VMM Library import:
      1. Make sure that you have root access, and then change the directory to /boot/efi/EFI:

        cd /boot/efi/EFI
      2. Recursively copy the Ubuntu directory to a new directory that's named boot:

        cp -r ubuntu/boot
      3. In the newly created boot directory, rename shimx64.efi as bootx64.efi:

        mv /boot/efi/EFI/shimx64.efi /boot/efi/EFI/bootx64.efi
  • This update also includes the following:
    • Host DHCP extension driver upgrade
    • Several performance improvements
    • Several management pack package improvements

How to obtain and install Update Rollup N for System Center 2012

Download information

Update packages for Virtual Machine Manager are available from Microsoft Update or by manual download.
Microsoft Update
To obtain and install an update package from Microsoft Update, follow these steps on a computer that has an applicable System Center 2012 R2 component installed:
  1. Click Start, and then click Control Panel.
  2. In Control Panel, double-click Windows Update.
  3. In the Windows Update window, click Check Online for updates from Microsoft Update.
  4. Click Important updates are available.
  5. Select the update rollup packages that you want to install, and then click OK.
  6. To install the selected update packages, click Install updates.

Manual download of the update packages
Go to the following website to manually download the update packages from the Microsoft Update Catalog:

Installation instructions

This update rollup includes a Management Pack package upgrade. If you use System Center Operations Manager and System Center Virtual Machine Manager integration, we recommend that you upgrade your Management Pack installation to the latest version after you apply this update. The default installation path for this package is "C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\ManagementPacks."

To manually install the update packages, run the following command at an elevated command prompt:

msiexec.exe /update <packagename> 
Note In this command, <packagename> represents the actual package name. For example, to install the Update Rollup 3 package for a System Center 2012 R2 Virtual Machine Manager server, run the following command:

msiexec.exe /update kb2965414_vmmserver.msp 
Important After you install the update package, you must run the following SQL script on your Virtual Machine Manager Microsoft SQL Server database so that Update Rollup 3 functions correctly.

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 will receive the IP address and otherwise function normally.) 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.7672.0, you will have to update the agent. To update the agent, first uninstall the old version by running the following command from an elevated PowerShell command prompt window:

MsiExec.exe /X{3834A905-5CC1-454D-8CA4-AC449F12775D}
Copy the Dhcpextn.msi file from your VMM server after you apply Update Rollup 3 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:

After you have copied the Dhcpextn.msi file to the host, double-click the file to start the installation process, and then follow the steps in the wizard.