Update Rollup 4 for System Center 2016 Virtual Machine Manager

This article describes the issues that are fixed in Update Rollup 4 for Microsoft System Center 2016 Virtual Machine Manager. There are three updates that are available for Virtual Machine Manager, one for the Virtual Machine Manager server, one for the Administrator Console, and one for the Guest Agent. This article also contains the installation instructions for this update.

• Installation of VMMAgent or upgrade through an Update Rollup overrides the winrm/config/MaxTimeoutms value.
• The AvailabilitySet property is lost when you migrate a Highly-Available (HA) or Non-HA VM on a cluster as a HA VM on the same or a different cluster.
• Storage Migration of the VM fails when multiple snapshots exist at the same level.
• Deletion of a VM that has multiple snapshots does not delete the VHD/VHDX if there is a parent snapshot deletion.
• VM deployment is stuck at 97% when you create the VM from a template that has an OS disk that consists of a SetupComplete.cmd that does not end in a new line.
• The PowerShell cmdlet New-SCVMHost causes a critical exception when it is run as delegated administrator.
• The Virtual Machine Manager UI when .NET Framework 4.7 is installed crashes when you try to give user/group access to a VM.
• When cross-cluster VM migration fails for reasons other than cancelation of the Virtual Machine Manager job, ghost resources are left on the source cluster.
• The PowerShell cmdlet Get-SCVirtualMachine throws an exception when the cmdlet is executed while deletion of a disk/volume on the VM is in progress.
• The Management Pack - CPU Utilization monitor does not alert when winrm is configured to use https.
• When NC Host Agent is refreshed, the vmqWeight setting might be changed if it is set through Virtual Machine Manager.
• Earlier Virtual Machine Manager versions enabled the conversion of HVN-type logical networks to other kinds of logical networks even if there were associated VM networks. This functionality was incorrect and has been removed.
• In the Japanese language version, when you create an IP Pool, the Automatic option in the list of Default Gateway metric is not translated from English. Selecting the Automatic option results in an error.
• Disabling Network Virtualization on a logical network that has no associated VM networks fails.
• In the German language version, the Port Profile settings wizard does not show the scroll bar, as the complete list of options is not displayed.
• When NC deployment on cloud fails, the error message displayed is generic and unclear.
• Default limits, for network components such as VM networks, Gateways, Subnets, etc., cannot be changed through a Network Controller.
• Deploying a Logical Switch with SR-IOV and SET causes the following error:

  When SR-IOV is enabled on the logical switch 'Test SET SR-IOBV', there can only be one uplink port. 
  Either disable SR-IOV or set the number of uplink ports to one. 

  ID:25208

• Several VMs lose connectivity when a VMM failover process occurs when adding a VM Role resource by using WAP/SPF with HTTPS load balancing enabled fails and causes the following error:

  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]

• No administrator other than Tenant Administrators can open the SCVMM console when there are many duplicate IPv6 addresses in the database.

Note Because updates for System Center 2016 Virtual Machine Manager are cumulative, this update includes all the improvements and fixes that are included in the previous cumulative update. For more information, see Update Rollup 3 for System Center 2016 Virtual Machine Manager.

After you install this update:

• The self-signed certificate uses SHA-256 hash algorithm for authentication/encryptions between VMM and Infrastructure servers. The existing self-signed certificates, using SHA-1, are updated to SHA-256.
• System Center components support for TLS 1.2. For more information about how to set up, configure, and run your environment with TLS 1.2, see the following article in the Microsoft Knowledge Base:
  4051111 TLS 1.2 Protocol Support Deployment Guide for System Center 2016

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:

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 package and then click Ok.
6. 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 server 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 4 package for System Center 2016 Virtual Machine Manager Server (KB4041074), run the following command:

msiexec.exe /update kb4041074_vmmserver_amd64.msp

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Learn about the terminology Microsoft uses to describe software updates.