Introduction
This article describes the issues that are fixed in Update Rollup 14 for Microsoft System Center 2012 R2 Virtual Machine Manager. There are two updates available for Virtual Machine Manager, one for the Virtual Machine Manager server and one for the Administrator Console. This article also contains the installation instructions for this update.
Issues that are fixed
-
When the VMM environment manages more than six Scale-Out File Server (SOFS) storage providers, the background job to update storage provider properties times out and causes a "Not responding" state for the storage provider in VMM.
-
Several virtual machines lose connectivity when a VMM failover process occurs.
-
When you add a VM Role resource by using WAP or SPF together with HTTPS load balancing enabled, the addition fails and you receive the following error message:
Error (31304) VM Role resources was not successfully deployed in the Cloud Service
Recommended Action VM Role can be repaired if the entity was created
Error (21426) Detailed Exception: Microsoft.SystemCenter.DataCenterManager.LB.LBException: Invalid Argument Value [HTTPS]
-
When the .NET Framework 4.7 is installed, the Virtual Machine Manager UI crashes when you try to give user or group access to a virtual machine.
Note Because updates for System Center 2012 R2 Virtual Machine Manager are cumulative, this update includes all the improvements and fixes that are included in the previous cumulative updates. For more information, see Update Rollup 13 for System Center 2012 R2 Virtual Machine Manager.
More information about this update
Update Rollup 14 for System Center components adds support for Transport Layer Security (TLS) protocol version 1.2. For more information about how to set up, configure, and run your environment to use TLS 1.2, see the following article in the Microsoft Knowledge Base:
4055768 TLS 1.2 Protocol Support Deployment Guide for System Center 2012 R2
How to obtain and install Update Rollup 14 for System Center 2012 R2 Virtual Machine Manager
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 a Virtual Machine Manager component installed:
-
Click Start, and then click Control Panel.
-
In Control Panel, double-click Windows Update.
-
In the Windows Update window, click Check Online for updates from Microsoft Update.
-
Click Important updates are available.
-
Select the update rollup package, and then click OK.
-
Click Install updates to install the update package.
Manual download
Go to the following websites to manually download the update packages from the Microsoft Update Catalog:
Download the Virtual Machine Manager update package now .
Download the Administrator Console update package now .
For information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Installation instructions
To manually install the update packages, run the following command from an elevated command prompt:
msiexec.exe /update packagename
For example, to install the Update Rollup 14 package for a System Center 2012 R2 Virtual Machine Manager Server (KB4041077), run the following command:
msiexec.exe /update kb4041077_vmmserver_amd64.msp
Notes
-
Performing an update to Update Rollup 14 on the VMM server requires installing the VMM Console and Server updates. For more details, see the following topic on the Microsoft TechNet website:
-
After you install the Console and Server updates, run the Agent Update on all the Hosts. For more details, see the following topic on TechNet website:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology Microsoft uses to describe software updates.
