Let's reminisce about what we discussed in the initial chapters of this title. At the onset, we looked at installing and configuring a Windows Server 2012 R2 host in various installation modes. Thereafter, we looked at how the Hyper-V role was installed, allowing for effective abstraction of physical hardware and enabling the pooling of resources comprising of compute, memory, network, and storage. The latter action moves the original Windows installation into a parent partition hosted on the type 1 hypervisor (Hyper-V) and it is referred to as Management OS and sits at ring 3. The Management OS is responsible for setting up communication via VM hypercalls in between VMs and the Hyper-V, as well as performing management tasks. These two entities, Hyper-V and Management OS, must be protected under various subsections. We may switch between three Windows installation modes, ensure the Hyper-V host is patched per both security and cumulative updates, and...