This article describes the issues that are fixed in Cumulative Update 1 (CU1) for Microsoft System Center 2016 Virtual Machine Manager (VMM) Technical Preview 5. There are two updates available for CU1 for System Center 2016 VMM Technical Preview 5. One update for VMM Server and one update for the Administrator Console. Additionally, this article contains the installation instructions for this cumulative update.
Issues that are fixed in this cumulative update
Issue 1: When you deploy a Network Controller on a Nano Server-based host by using service templates in VMM, you may receive the following error message:
Error (22743) The host agent on the host host_name for virtual machine VM_name is not up to date and cannot provision the physical resources required for the servicing operation.
Recommended Action Ensure the virtual machine has network connectivity to the library servers, or that the host agent is up to date, and then retry the operation.
Issue 2: The onboarding process of the Software Load Balancer (SLB) to a Network Controller may fail.
The fix in this cumulative update enables you to onboard the SLB by configuring the IP address manually on the virtual machine. Additionally, you receive the following warning message:
Warning (50267) Could not assign static IP IP_Address from HNV Logical network to backend nic for the VM VM_Name.
Recommended Action Manually configure the static ip on the backend Nic for the VM VM_Name.
Issue 3: When you install the Host Guardian Hyper-V Support feature in your environment, the installation may fail and return a critical exception. This issue may occur when the Diagnostic and Usage Data option is enabled on the VMM server.
Issue 4: After you shield an existing VM, the conversion job may fail and return the following exception:
Exception: System.ArgumentException: An item with the same key has already been added.
Additionally, the Temporary Shielding Helper VM that's used for shielding the VM continues to be displayed in the VMM Console, although that VM was deleted.
Note The VM is converted but the conversion job fails.
Issue 5: You connect an unconnected virtual network adapter of a VM to a network controller-managed Hyper-V Network Virtualization (HNV) VM network by specifying the type of MAC address (MacAddressType). If you use the Self Service User (SSU) user role to do this, the connection may fail and you receive the following error message:
Set-SCVirtualNetworkAdapter : You do not have permission to access one or more of the objects required by this operation. (Error ID: 11418)
This issue is fixed in this cumulative update. However, to temporarily work around this issue, do not pass the MacAddressType parameter when the network adapter is attached by using Windows PowerShell. Or, do not attach the network adapter to the VM when you create the VM by using Windows Azure Pack (WAP) or PowerShell.
Issue 6: When you enable the Host Guardian Hyper-V Support feature on a Nano Server-based host, the service fails. After you apply this cumulative update, you must enable the Host Guardian Hyper-V Support feature out of band. To do this, follow these steps:
Copy the Packages folder from the installation media of Windows Server 2016 Technical Preview locally to the running Nano Server-based host (for example, to C:\packages).
Use PowerShell Remoting to log on to the Nano Server-based host and add the Host Guardian packages by running the following commands: