Website under construction

Host resource protection 
One of the problems with virtualization has always been the struggle to prevent a VM from using 
more than its fair share of resources. This overuse could potentially affect the host system 
performance and guest VMs. By default, this monitoring and protection is turned off; to turn it on, run 
the following: 

---

12 
CHAPTER 2 | Software-defined datacenter 
Set-VMProcessor -EnableHostResourceProtection $true 
This will turn on a monitoring process that scans for excessive usage and will limit the resources of 
any VM that might be causing the issue, thereby isolating the impact. 
Connected Standby 
When the Hyper-V role is installed on a computer that uses the Always On/Always Connected (AOAC) 
power model, the Connected Standby power state is now available
.
Device assignment 
Using this feature, you can give a VM direct and exclusive access to some PCIe hardware devices. 
Using a device in this way bypasses the Hyper-V virtualization stack, which results in faster access. 
More info See the following link 
http://blogs.technet.com/b/virtualization/archive/2015/11/19/ 
discrete-device-assignment.aspx
. 
Windows PowerShell Direct 
Windows PowerShell Direct gives you a way to run Windows PowerShell commands in a VM from the 
host. Windows PowerShell Direct runs between the host and the VM. This means it doesn't require 
networking or firewall requirements, and it works regardless of your remote management 
configuration. 
Windows PowerShell Direct works much like remote Windows PowerShell except that you do not 
need network connectivity. 
To connect to the VM from a host, use the Enter-PSSession cmdlet, as follows: 
Enter-PSSession -VMName  
You will be prompted for credentials and then you can manage the VM from this PSSession. 
The Invoke-Command cmdlet has been updated to perform similar tasks; for example, you can 
execute a script from the host against the VM, as shown here: 
Invoke-Command -VMName  -FilePath C:\Scripts\MyTestScript.ps1