Changed and upgraded functionality of Hyper-v Server 2016.
- Hyper-v cluster with mixed hyper-v version
- Join a Windows Server 2016 Hyper-v with Windows Server 2012 R2 Hyper-v
- Functional level is Windows Server 2012 R2
- Manage the cluster, Hyper-V, and virtual machines from a node running Windows Server 2016 or Windows 10
- Use Hyper-V features until all of the nodes are migrated to Windows Server 2016 cluster functional level
- Virtual machine configuration version for existing virtual machines aren’t upgraded
- Upgrade the configuration version after you upgrade the cluster functional level using Update-VmConfigurationVersion vmname cmdlet
- New virtual machine created in Windows Server 2016 will be backward compatible
- Hyper-V role is enabled on a computer that uses the Always On/Always Connected (AOAC) power model, the Connected Standby power state is now available
- Production checkpoints
- Production checkpoints, the Volume Snapshot Service (VSS) is used inside Windows virtual machines
- Linux virtual machines flush their file system buffers to create a file system consistent checkpoint
- Check point no longer use saved state technology
- Hot add and remove for network adapters, virtual hard drive and memory
- add or remove a Network Adapter while the virtual machine is running for both Windows and Linux machine
- Adjust memory of a running virtual machine even if you haven’t enabled dynamic memory
- Integration Services delivered through Windows Update
- Windows update will distribute integration services
- ISO image file vmguest.iso is no longer needed to update integration components
- Storage quality of service (QoS)
- create storage QoS policies on a Scale-Out File Server and assign them to one or more virtual disks
- Hyper-v auto update storage policies according to storage policies
- Virtual machine Improvement
- Import virtual machine with older configuration version, update later and live migrate across any host
- After you upgrade the virtual machine configuration version, you can’t move the virtual machine to a server that runs Windows Server 2012 R2.
- You can’t downgrade the virtual machine configuration version back from version 6 to version 5.
- Turn off the virtual machine to upgrade the virtual machine configuration.
- Update-VmConfigurationVersion cmdlet is blocked on a Hyper-V Cluster when the cluster functional level is Windows Server 2012 R2
- After the upgrade, the virtual machine will use the new configuration file format.
- The new configuration files use the .VMCX file extension for virtual machine configuration data and the .VMRS file extension for runtime state data.
- Ubuntu 14.04 and later, and SUSE Linux Enterprise Server 12 supports secure boot using Set-VMFirmware vmname -SecureBootTemplate MicrosoftUEFICertificateAuthority cmdlet
- Hyper-V Manager improvements
- Support alternative credential
- Down-level management of Hyper-v running on Windows Server 2012, Windows 8, Windows Server 2012 R2 and Windows 8.1.
- Connect Hyper-v using WS-MAN protocol, Kerberos or NTLM authentication
- Guest OS Support
- Any server operating systems starting from Windows Server 2008 to Windows Server 2016
- Any desktop operating systems starting from Vista SP2 to Windows 10
- FreeBSD, Ubuntu, Suse Enterprise, CentOS, Debian, Fedora and Redhat
9. ReFS Accelerated VHDX
- Create a fixed size VHDX on a ReFS volume instantly.
- Gain great backup operations and checkpoints
10. Nested Virtualization
- Run Hyper-V Server as a guest OS inside Hyper-V
11. Shared VHDX format
- Host Based Backup of Shared VHDX files
- Online Resize of Shared VHDX
- Some usability change in the UI
- Shared VHDX files are now a new type of VHD called .vhds files.
12. Stretched Hyper-V Cluster
- Stretched cluster allows you to configure Hyper-v host and storage in a single stretch cluster, where two nodes share one set of storage and two nodes share another set of storage, then synchronous replication keeps both sets of storage mirrored in the cluster to allow immediate failover.
- These nodes and their storage should be located in separate physical sites, although it is not required.
- The stretch cluster will run a Hyper-V Compute workload.
Hyper-V on Windows 10 doesn’t support failover clustering