Update Rollup 3 for System Center 2016 Virtual Machine Manager

This article describes the issues that are fixed in Update Rollup 3 for Microsoft System Center 2016 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.

• A Tenant Administrator cannot create a virtual machine (VM) network by using the UI.

• When an HNV VM is migrated to a host that is in legacy mode, HNV policies are not updated, which causes the VM to lose connectivity.

• Fabric Administrators (Delegated Administrators) cannot delete VMs in a tier if they share a common VHDX file on a host.
• Shared VHDX files are incorrectly used with multiple VMs.
• The deletion of a VM by using a shared disk causes the deletion of the shared disk when other VMs that use that same disk are in a Stopped state.
• Loading the properties page for a VM or Hardware Profile crashes the console when the memory value is set to a number higher than the acceptable range.
• Internal Garbage Collection Refresher fails with the exception "Unable to connect to database."
• For VMware device controllers other than SCSI and IDE, Virtual Machine Manager displays a "Bad controller type" exception message instead of skipping the device controller and displaying a warning message.
• A template that is imported by a tenant administrator is not visible in the administrator console.
• The attestation monitor gives false alarms if it's enabled for hosts other than Host Guardian Service (HGS) hosts.
• The VMM Cloud disappears from the Create Wizard if a user selects another cloud before the previous operation of creation/display of VMM cloud is complete.
• An update agent on a network controller-managed host changes the host certificate, and the network controller is not updated with new certificates.
• An unexpected host restart warning occurs while updating the networking properties of a guarded host, even though the HGS settings are not changed.
• The Get-SCGuestOSPofile cmdlet does not return the expected results.
• The AddCluster cmdlet hangs while adding a cluster to Virtual Machine Manager when the communication to the Virtual Machine Manager server is lost.
• Virtual Machine Manager does not recognize the SET switch and displays the external standard switch (SET) as internal.

• HNV policies are not updated on VMs that are moved through Failover Cluster Manager (FCM).

• The F5 load balancer is not working and displays an exception when the static IP address is used together with service templates.
• Software Defined Networking (SDN) service template deployment completes even though it failed during script execution.
• Importing of service templates fails with an XSD validation failure error.
• Tenant users are not able to View or Update properties for VMs having a disk attached to SCSI ID7.
• NAT rules are not applied, which causes issues on VMs that are part of a similar tenant network.
• Cannot set the inbound and outbound bandwidth for VPN connections.
• When removing a host vNic from a Network Controller (NC), the corresponding Network Interface JSON in the Network Controller is not removed.
• The maximum limit of the attribute VMNetworkSubnets per Gateway is incorrectly set for a Network Controller.
• The Network Controller service template fails when a password contains reserved characters, such as the ampersand (&), comma (,) and double quotation mark (") characters.
• When Gateway settings are configured through the Virtual Machine Manager UI (where traffic selector settings are not visible), Virtual Machine Manager sets VpnTrafficSelector values as Empty.
• The FQDN of REST endpoint is treated as case-sensitive, which is not true, as FQDN is not a case-sensitive entity.
• SDN VMs created (such as NC, Mux, and GW VMs) are not being added to the cluster.
• When a Network controller is updated, the Host vNic policies are not set correctly in Windows Management Instrumentation (WMI).
• The creation of NAT connections by using a public IP address displays an exception.
• The deletion of Network Controller nodes is restricted if the remaining instance count goes below 3.
• When a volume is created on the platform, it does not appear in Virtual Machine Manager until the refresher executes.
• Storage utilization is displayed incorrectly in Overview. It should display the (total-committed) value.
• The creation of a file share in Storage Space Direct (S2D) SOFS backed by using SAN displays an exception message.
• In Storage Space Direct (S2D) SOFS, the Add Volume command opens the Create Logical Unit wizard instead of the Create Volume wizard.
• Cannot assign a classification to a host disk when the HC Cluster and CSV are not created by using Virtual Machine Manager.
• A user cannot set IOPS Maximum on a VHD from Virtual Machine Manager.
• Removing a CSV removes its corresponding LUN when in hyper-converge.
• In the UI, the remove CSV button is disabled for hyper-converge.
• System Center Operations Manager returns no value for the IsClustered property for a Host Volume.
• This update adds an alert for warning state change for HBA port monitors.
• Virtual Machine Manager Management Pack creates an Alert when a VM is put into paused state.
• The System Center Operations Manager dashboard displays incorrect performance data for vPort.

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 2.1 for System Center 2016 Virtual Machine Manager

After you install this update, backing up and restoring the software-defined networking (SDN) infrastructure is possible. For more information, see the following topic on the Microsoft Docs website:

Back up and restore the SDN infrastructure

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 Download Center:

 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 NN package for a System Center 2012 R2 Virtual Machine Manager 2016 Server (KB4014528), run the following command:

msiexec.exe /update kb4014528_vmmserver_amd64.msp

Notes

• Performing an update to Update Rollup 3 on the VMM server requires that you install the VMM Console and Server updates. For more details, see the following topic on the Microsoft Docs website:
   
  How to install, remove, or verify update rollups for System Center 2016 VMM
• 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:
   
  How to Update the VMM Agent

After the installation

To fix the "Another machine with the same SMBIOS GUID is found" error on your existing Storage Spaces Direct (S2D) clusters, remove the providers, and then add them again. After the providers are restored, update those providers.

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.