We have been waiting for this to come up and here it is:
Improvements and issues that are fixed
Virtual Machine Manager now lets you not claim certain storage devices by Multipath I/O
(MPIO) when you add a host. This list of storage devices is controlled through
a registry key on the Virtual Machine Manager server.
When hosts are added to a cluster with Storage Spaces Direct (S2D) enabled,
you receive the following warning:
Multipath I/O is not enabled for known storage arrays on host hostname.
- Multipath I/O (MPIO) is not disabled for the hosts in a BMC Storage Spaces Direct cluster.
- Provides a consistent experience across Hyper-V and S2D clusters for changing classification on Cluster Shared Volume (CSV).
- The Virtual Machine Manager cloud cannot calculate the storage classification capacity (it is displayed as 0) with an S2D cluster.
- After onboarding an out-of-band Hyper Converged or S2D Scale Out FileServer (SOFS) into Virtual Machine Manager, the Storage Provider is not added, and SOFS properties such as volume, physical disk, and tiers are not available in Virtual Machine Manager.
- Migrating a virtual machine (VM) from a VMware ESXi host to a Nano server host fails with error 2903.
- SAN migration of virtual machines fail between two stand-alone Nano Server hosts.
- As part of the V2V conversion for a VMWare Highly Available virtual machine, Virtual Machine Manager calculates the host ratings without considering CSV.
- Migration of and/or cloning the virtual machine fails because the version of the virtualization software on the host does not match the version of the virtual machine’s virtualization software on the source.
- Files are left in the following scenarios:
- In the virtual machine library directory, even after the virtual machine is deleted from the Library
- When a service instance fails and then is deleted
- You can’t delete NAT Connection from the UI for Network Controller (NC) Managed Networks.
- The Cloud Summary is missing capacity data for Tenant Administration.
- Deletion of Logical Switch triggers a Virtual Machine Manager UI crash.
- Program Menu reverts to System Center 2012 after installation of System Center Virtual Machine Manager 2016 Update Rollup 1.
- Shielding an existing virtual machine fails intermittently with Error (1730).
- Virtual machine start job reports fail with error 12711 when a virtual machine has the Set Order Priority option set.
- Provides a simplified Create Volume wizard for S2D cluster creation.
- Guest Agent is not upgraded on servicing a service after you upgrade Virtual Machine Manager from System Center 2012 R2 Virtual Machine Manager to System Center 2016 Virtual Machine Manager.
- Service operations fail when there is a shared VHDX on a CSV volume and more than one Service virtual machine hosted on a single host.
- Provides reliability improvements in the Virtual Machine Manager service.
- Removal of Hyper-V Host fails in the following scenarios:
- If any virtual machine on the host exists with checkpoints
- If hosts have a VHD that’s referenced by a disk on another host
- Slow performance when you perform a refresh on virtual machines that have many checkpoints.
- Nano virtual machine deployment through a virtual machine template does not join the domain.
- VDI virtual machines deployed through RDS do not appear in the Virtual Machine Manager console.
- With Network Controller (NC) onboarded, virtual machine operations fail when there is a Port SACL applied on the virtual machine network.
- NAT improvements including the following:
- The release of the IP address reserved for a NAT connection when the connection throws an exception
- The display of junk entries if the virtual machine network has a NAT connection
- The removal of incoming NAT rules applied on a network adapter after the network adapter is disconnected and reconnected.
- Creating a Host Cluster with Static IP address fails.
- Network Controller (NC)–related improvements including the following:
- The scale-out and scale-in of NC virtual machines.
- The blocking of IPV6-based virtual machine network creation from the UI.
- Network Controller-managed network adapter is not displayed as noncompliant after a PortACL rule is removed.
- Load balancer improvements including the following scenarios:
- Virtual Machine Manager goes into an inconsistent state after a SLB MUX deployment failure.
- Load Balancing rules don’t work after disconnecting and reconnecting Network Controller-managed network adapters.
- Gateways do not require certificates. They use user name and password for authentication. But, Gateway Templates starts the MUX service, which requires certificates for controller certificates and MUX certificates based on CA self-signed scenarios. This forces gateways to mandate certificates even through it is not required.
- Virtual Machine Manager mandates all the gateway front-end pools to be available for the Network Controller host group scope.
- Virtual Machine Manager lets users create a network adapter with dynamic option for Network Controller-managed connected networks. This should be blocked with an appropriate error message as the Network Controller does not support dynamic IP configuration for the network adapter.
- Changing a virtual machine network between Network Controller-managed connected networks is successful in Virtual Machine Manager. However, the Network Controller still has old information in its network adapter JSON when it uses the DHCP option.
- UI improvements include the following:
- Noncompliant warning (26909) displayed for a Virtual Machine and its network adapter when you deploy a virtual machine that is connected to a network by using a Dynamic IP address.
- Hyper-V Nano host is displayed as not compliant for SET team Logical Switch.
- By default, Remote Access Gateway connections are disabled when configured through Virtual Machine Manager.
- Improved SDN manageability includes the following:
- When you use the Force option to remove a Virtual Network Gateway even when the Network Controller is down.
- Setting Port Profiles of Network Controller-managed virtual machines after migration.
- Virtual Machine Manager does not delete the routes from the Network Controller. However, removing the VPN Connection deletes the routes and the VPN connection. Creating the same routes from Virtual Machine Manager will also work as it would find the routes in the Network Controller.
- When a self-service user deploys a virtual machine to the cloud and changes the hardware profile, Virtual Machine Manager does not let you use the IP pool available in the selected VLAN.
- Unable to create VLAN-based logical networks through Virtual Machine Manager when the subnet is not specified.
For more details about other features that are available in Virtual Machine Manager 2016, see What’s New in VMM 2016.
- You cannot update VM hardware profile properties for VMs with dynamic memory after you install Update Rollup 2. The error that you see is because of the startup memory in the Console being reset to 1 every time that you start the VM Properties dialog box from the Console for a VM where Dynamic Memory is enabled. This issue is only a display issue and actual memory of the VM is not affected.
Because this is just a Console issue, you can continue to use VMM PowerShell to manage hardware properties without performing any additional steps. Or, the properties can be updated from the Console after stopping the VM and updating the startup memory within the original acceptable range.
- When you create a VM with dynamic memory through the Console or by updating the memory of a VM from static to dynamic through the Console after you deploy Update Rollup 2, the default maximum memory is set to a value greater than 1 TB. This causes VM creation/update to fail.
To work around this issue, update the maximum memory value to 1TB or less in the Console to avoid errors. Additionally, you can use PowerShell to create VMs with 1TB maximum memory without performing any additional steps.
- After you apply Update Rollup 2, if you try to change the value for ‘Number of Processors’ of a deployed VM through the Administrator Console or VMM PowerShell to a number greater than 64, you encounter an error. This issue applies to even new VMs you create after you install Update Rollup 2.
To work around this issue, continue to provision VMs with the number of processors not greater than 64.