The Bottom Line
Identify the ways to deploy Hyper-V. Windows Server 2016 Hyper-V can be
deployed using numerous methods. The traditional approach is to install a server from
setup media, which could be a DVD, USB device, or even files obtained over the
network. Enterprise systems management solutions such as System Center
Configuration Manager and Windows Deployment Services can be used to customize
deployments. System Center Virtual Machine Manager can also be used to deploy
Hyper-V hosts using Boot to VHD technology, providing a single management
solution for deployment of hosts and virtual machines. Nano Server deployments are
deployed in a different manner, as custom images are created and leveraged.
Master It What other types of servers can SCVMM 2016 deploy?
Explain why using Server Core is beneficial to deployments. Windows Server
and Windows client operating systems share a lot of common code, and a typical
Windows Server deployment has a graphical interface, Internet browser, and many
graphical tools. These components all take up space, require patching, and may have
vulnerabilities. For many types of server roles, these graphical elements are not
required. Server Core provides a minimal server footprint that is managed remotely,
which means less patching and therefore fewer reboots in addition to a smaller attack
surface. Because a host reboot requires all virtual machines also to be rebooted, using
Server Core is a big benefit for Hyper-V environments in order to remove as many
reboots as possible. Nano Server is a completely refactored deployment of Windows
Server, which is also a good choice for Hyper-V Servers but may not be compatible
with an organization’s management toolset.
Master It What was the big change to configuration levels between Windows Server
2012 R 2 and Windows Server 2016?
Explain how to create and use virtual machine templates. While it is possible
to create the virtual machine environment manually and install the operating system
for each new virtual machine, it’s inefficient, considering the virtual machine uses a
file for its virtual storage. A far more efficient and expedient approach is to create a
generalized operating system template VHDX file, which can then be quickly deployed
to new virtual machines. A virtual machine template allows the virtual hardware
configuration of a virtual machine to be configured, including OS properties such as
domain join instructions, local administrator password, and more. The configuration
is then linked to a template VHDX file. When the template is deployed, minimal
interaction is required by the requesting user, typically just an optional name, and
within minutes, the new virtual environment with a configured guest operating
system is available.