Website under construction

More info See the following link 
https://msdn.microsoft.com/virtualization/ 
hyperv_on_windows/user_guide/nesting
. 
Linux secure boot 
Linux VMs that are created as Generation 2 VMs can now utilize secure boot. To do this, you must 
turn on the VM to use the Microsoft UEFI Cert Authority by running the following Windows 
PowerShell command: 
Set-VMFirmware vmname -SecureBootTemplate MicrosoftUEFICertificateAuthority 
You also can turn on secure boot via the Hyper-V manager or Virtual Machine Manager. 
Currently, only certain distributions support secure boot: 

Ubuntu 14.04 and later 

SUSE Linux Enterprise Server 12 and later 

Red Hat Enterprise Linux 7.0 and later 

CentOS 7.0 and later 
Integration services 
Updates to integration services for Windows guests are distributed through Windows Update. For 
service providers and private cloud hosters, this puts the control of applying updates into the hands 
of the tenants who own the VMs. Tenants can now update their Windows VMs with all updates, 
including the integration services, using a single method.
Hyper-V Manager improvements 
There are some new improvements to the Hyper-V Manager. Let’s take a look at them: 

Alternate credentials support You can now use a different set of credentials in Hyper-V 
Manager when you connect to another Windows Server 2016 or Windows 10 remote host. You 
also can save these credentials to make it easier to sign in again. 

Manage earlier versions With Hyper-V Manager in Windows Server 2016 and Windows 10, you 
can manage computers running Hyper-V on Windows Server 2012, Windows 8, Windows Server 
2012 R2, and Windows 8.1. 

Updated management protocol Hyper-V Manager has been updated to communicate with 
remote Hyper-V hosts using the Web Services Management (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 turning on constrained delegation in Active 
Directory. The WS-MAN–based infrastructure also makes it easier to set up a host for remote 
management. WS-MAN connects over port 80, which is open by default.