You can also offer some security for Generation 1 virtual machines: Key Storage Drive. Shielding, as above, required Generation 2 VMs. There are levels of shielding, so it’s not an all or nothing.

A VM is encrypted by the customer/tenant using BitLocker – a rogue admin/attacker/government agency cannot inspect the VM’s contents by mounting the disk(s).

A highly secured Host Guardian Service must authorize the hosts.

A VM can only run on a trusted & healthy host – a rogue admin/attacker cannot start the VM elsewhere.

Cloud is a big deal for customers – some are worried about industry and government regulations preventing adoption of the cloud. Microsoft wants Windows Server to be the best platform. The number of attack vectors is up, attacks are on the rise, and the sophistication of those attacks is increasing. The first area that Ben will cover is security. There’s as much new stuff in this 1 release as there were in the last 2!

A lot of this stuff still cannot be found in vSphere.Īnd we can compare that with what’s new in WS2016 Hyper-V (in blue at the bottom). Here is a summary of what was introduced in the last 2 versions of Hyper-V. The session is an overview of the features that are new, why they’re there, and what they do. This post is a collection of my notes from the Ben Armstrong’s (Principal Program Manager Lead in Hyper-V) session (original here) on the features of WS2016 Hyper-V.

Vdmx demo windows