Update Rollup 8 for System Center 2016 Virtual Machine Manager

• Service deployment through VMM fails if the domain name provided is greater than 15 characters.
• ‘Get-SCServicingWindow’ PowerShell commandlet fails to return active servicing windows if ‘-ServicingWindowFilter’ parameter is passed with the value ‘now’.
• When importing a Vmware template for Windows Server 2016, ‘OS Configuration’ option is missing. 
• Note:
• Once the VMM 2016 UR8 patch is applied, VMware templates needs to be removed and re-imported after a VM refresher job is run for ‘OS configuration’ option to show-up. VM refresher job runs every 30 minutes by default.
• Virtual Machine performance counters in VMM fails to refresh.
• Bare Metal Deployment fails with the error ‘There was an error communicating with the endpoint. The server name or address could not be resolved’.
• When a host in untrusted domain is managed by VMM, events with ID ‘15030’ and ‘17140’ is logged in ‘Microsoft-Windows-Hyper-V-VMMS/Admin’ event channel every 30 minutes.
• Cross Cluster Migration fails for highly available VMware VMs managed in VMM.
• VMM does not detect the OS version of Windows client if the version is 1709 or greater.
• QOS settings set out of band is overwritten by VMM
• Operations performed on a VM may fail in an environment which uses DHCP for IP address assignment while having VMM manage the same IP address range. 
• Concurrent operations on Network Controller managed VMs may fail.
• Network Interface Card properties set OOB may get overwritten by a VMM VM refresher job in SDN v2 environment.
• The VLAN/subnet pairs under ‘Logical network connectivity’ sub-menu of Host Network adapter properties are unselected. 
• VMM console crashes when a self-service user enumerates properties of a VM with shared disk.
• Updates to memory and processor of a VM fails when an update is performed on VM disk at the same time.
• SCVMM service may crash when multiple VMs are created concurrently.
• Deprecated VMM MP classes are instantiated when VMM is integrated with Operations Manager 2016 and above.
• Multiple VMs can be deployed concurrently from a VM stored in VMM Library Server.
• Performance improvements in time taken for Static IP pool creation.

VMM 2016 UR8 has the following new functionalities added:

• Ability to Deploy Gen-2 VMs with memory up to 12TB and processor up to 240 cores.

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

Virus-scan claim

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 8 package for a System Center 2016 Virtual Machine Manager server (kb4518885), run the following command:

msiexec.exe /update kb4518885_vmmserver_amd64.msp

References

Learn about the terminology Microsoft uses to describe software updates.