1. Windows Server 2016 Hyper-V
What’s new?
Mike Resseler
Technical Evangelist
Veeam Software
Thomas Maurer
Cloud Architect
itnetX

2. Mike Resseler Thomas Maurer @MikeResseler @ThomasMaurer MVP 15+ 10
MVP, Veeam Vanguard, Cisco Champion
15+ 10
Wakeboarding | Slalom waterski
Steaks, Sushi, Cheese, Chocolate

3. 10 cool items to review
Q&A

4. #1
Nano Server

5. Minimal Server Interface
Nano Server
Headless server
No UI
Everything remotely managed
Extremely low footprint
Works with packages:
Hyper-V
SOFS
DNS …
Nano Server
Server Core
Minimal Server Interface
GUI Shell
Windows Server 2016

6. #2
Shielded VMs

7. Shielded VMs
Intended to shield the VM from the fabric
Needs generation 2 VMs
Enables bitlocker inside the VMs
Works with Guarded Fabric

8. #3
Networking & Storage Enhancements

9. Networking & Storage Enhancements
Distributed Storage QoS (one or more virtual disks on SOFS)
Deduplication optimization for virtualized backup workloads
Storage Spaces Direct
VHDX improvements on ReFS
Hyper-V Virtual Switch improvements
* Programmable Hyper-V Switch
VXLAN encapsulation support (but still NVGRE)
Software load balancing interoperability (software based for virtual networks)

10. #4
PowerShell

11. PowerShell direct No network, no firewall requirements no nothing…
Enter-PSSession –VMName VMName
Invoke-Command –VMName VMName –ScriptBlock { Commands }
connected to a W10 or WS 2016 TP host with VM that run W10 or WS 2016 TP as the guest OS
You need to be logged in with Hyper-V administrator credentials on the host.
You need user credentials for the virtual machine.
The virtual machine that you want to connect to must run locally on the host and be booted.

12. #5
Virtual Machines

13. VM Configuration & format
Current at 7.1
Might need to get manually updated
Update-VmVersion vmname (or vmobject)
VM needs to be off
Format is now binary
.VMCX

14. Integration Services
No more ISO
Delivered through Windows Update
In the hands of the tenants now
Linux Integration Services (LIS) or FreeBSD Integration Services (BIS) can be built-in or require download

15. Booting with the Secure Boot option enabled Generation 2 required
Linux Secure Boot
Booting with the Secure Boot option enabled
Generation 2 required
Ubuntu (or later), SUSE Linux Enterprise Server 12 (or later), Red Hat Enterprise Linux 7.0 (or later) and CentOS 7.0 (or later)
Before booting first time:
Set-VMFirmware vmname –SecureBootTemplate MicrosoftUEFICertificateAuthority

16. Hot Add/Remove
Add vNICs to a running VM
Change memory of a running VM (add only if memory is available)

17. #6
Clustering

18. Rolling Cluster upgrade
Stay in mixed mode during an upgrade of your cluster
No more downtime
Stays at 2012 R2 functional level until: Update- ClusterFunctionalLevel
Works for Scale-Out File server failover cluster also

19. Rolling Cluster upgrade

20. Virtual Machine Resiliency Site-aware Failover Clusters
Clustering
Storage Replica
Cloud Witness
Virtual Machine Resiliency
Site-aware Failover Clusters
Workgroup & Multi-domain clusters
Storage Replica (SR) is a new feature that enables storage-agnostic, block-level, synchronous replication between servers or clusters for disaster recovery, as well as stretching of a failover cluster between sites. Synchronous replication enables mirroring of data in physical sites with crash-consistent volumes to ensure zero data loss at the file-system level. Asynchronous replication allows site extension beyond metropolitan ranges with the possibility of data loss.
Cloud Witness is a new type of Failover Cluster quorum witness in Windows Server 2016 Technical Preview that leverages Microsoft Azure as the arbitration point. The Cloud Witness, like any other quorum witness, gets a vote and can participate in the quorum calculations. You can configure cloud witness as a quorum witness using the Configure a Cluster Quorum Wizard.
Compute Resiliency Windows Server 2016 Technical Preview includes increased virtual machines compute resiliency to help reduce intra-cluster communication issues in your compute cluster as follows: .
Resiliency options available for virtual machines: You can now configure virtual machine resiliency options that define behavior of the virtual machines during transient failures:
Resiliency Level: Helps you define how the transient failures are handled.
Resiliency Period: Helps you define how long all the virtual machines are allowed to run isolated.
Quarantine of unhealthy nodes: Unhealthy nodes are quarantined and are no longer allowed to join the cluster. This prevents flapping nodes from negatively effecting other nodes and the overall cluster.
Windows Server 2016 Technical Preview includes site- aware failover clusters that enable group nodes in stretched clusters based on their physical location (site). Cluster site-awareness enhances key operations during the cluster lifecycle such as failover behavior, placement policies, heartbeat between the nodes, and quorum behavior. 
In Windows Server 2012 R2 and previous versions, a cluster can only be created between member nodes joined to the same domain. Windows Server 2016 Technical Preview breaks down these barriers and introduces the ability to create a Failover Cluster without Active Directory dependencies. You can now create failover clusters in the following configurations:
Single-domain Clusters. Clusters with all nodes joined to the same domain.
Multi-domain Clusters. Clusters with nodes which are members of different domains.
Workgroup Clusters. Clusters with nodes which are member servers / workgroup (not domain joined).

21. #7
Hyper-V Manager

22. Alternate Credentials Support Managing earlier versions
Hyper-V manager
Alternate Credentials Support
Managing earlier versions
Updated Management Protocol
Hyper-V Manager has been updated to communicate with remote Hyper-V hosts using the WS-MAN protocol, which permits CredSSP, Kerberos or NTLM authentication. When you use CredSSP to connect to a remote Hyper-V host, you can do a live migration without enabling constrained delegation in Active Directory. The WS-MAN-based infrastructure also makes it easier to enable a host for remote management. WS-MAN connects over port 80, which is open by default.

23. #8
Production Checkpoints

24. Production Checkpoints
Allows you to create “point-in-time” images of a VM
Full support for application workloads
VSS on windows (application-consistent)
File system buffer flush on Linux (file-consistent)
Still can switch to the standard method
New VMs use production checkpoints as default
Fixes the “wrong usage of checkpoints”
NOT a backup solution
Native CBT will be implemented for backup vendors

25. #9
Nested Virtualization

26. Nested Virtualization
Possible in Windows 10 build (with restrictions)
Possible in TP5
Only Intel at this point in time
Dynamic Memory needs to be off
Enabling requires specific scripts: indows/user_guide/nesting

27. #10
Much more

28. Windows-as-a-Service Containers
Much more
Windows-as-a-Service
Containers
Improvement to Windows Server won’t stop
More frequent releases
Zero downtime upgrades – rolling cluster upgrades

29. And Then …

31. Picture References
Slide 3:
Pen Pointer: