Hyper-V

HOTLINE
09251222279
 Install and configure Hyper-V
• Determine hardware and compatibility requirements for installing Hyper-V

• Install Hyper-V

• Install management tools

• Upgrade from existing versions of Hyper-V

• Delegate virtual machine management

• Perform remote management of Hyper-V hosts

• Configure virtual machines using Windows PowerShell Direct

• Implement nested virtualization

 What's New in Windows Server 2016

Functionality Description

TPM Trusted Platform Module (TPM) is a standard for a secure

crypto-processor to store cryptographic keys. In Windows
Server 2016, VMs have a virtual TPM so they can use
BitLocker. The virtual TPM does not require a physical TPM to
be present.
Nested Virtualization With Nested Virtualization, you can install the Hyper-V role
in the virtual machine and then run virtual machines in
Hyper-V inside a virtual machine.
Shielded Virtual Machines Shielded VMs in Hyper-V in Windows Server 2016 enables
you to protect the VM and its virtual hard disks, and only let
it run on trusted Hyper-V hosts.
Containers Where Hyper-V provides hardware virtualization to run
multiple servers on one physical server, containers provide
OS virtualization. Containers allow you to run applications
isolated from other applications on the same server, either
physical or virtual.
Server Virtualization

Q. What is Server Virtualization?

• With server virtualization, you can create separate virtual machines and run them
concurrently on a single server that is running Hyper-V. These virtual machines
are guests, while the computer that is running Hyper-V is the virtualization server or
the management operating system. It may also be referenced as a virtualization host.
Client Virtualization

Software developers and IT administrators often need to run multiple operating

systems for testing purposes, usually on many different computers. However,
providing access to a full test environment is not possible for many organizations,
and so virtualization can be a solution that saves space and time.
• Client Hyper-V
✓ You can install the Hyper-V role on computers that are running the Windows 8,
Windows 8.1 and Windows 10 operating systems on all editions but the Home
editions. This allows you to run virtual machine guests on client computers. This
allows users to access older apps that are incompatible with more modern
Windows operating systems.
• Enabling Client Hyper-V on Windows Client Computers
✓ To run Client Hyper-V, hardware virtualization support must be enabled in the
computer’s BIOS first and the operating system must be 64-bit. But Client Hyper-
V supports both 32-bit and 64-bit guest operating systems.
How to enable Client Hyper-V

• To enable Client Hyper-V on Windows 10, go to Control Panel > Programs > Turn
Windows Features on or off, check Hyper-V, making sure all components are selected,
and click OK. Once enabled, you can now launch the Hyper-V Manager console from the
Start menu.
Tips for Hyper-V
Requirements for Client Hyper-V
• Client Hyper-V, the Hyper-V feature in Windows 8, Windows 8.1, and Windows 10 operating systems, has slightly
different processor requirements than Hyper-V on Windows Server 2012, Windows Server 2012 R2 and Windows
Server 2016. Specifically, with Windows 8, Windows 8.1, and Windows 10 client operating systems, the computer:
• Must have an x64 platform that supports Second Level Address Translation (SLAT).
• Have a minimum of 4 gigabytes (GB) of random access memory (RAM).

Features Not Supported by Client Hyper-V

• The Client Hyper-V role supports many of the features that are available with the server version of Hyper-V.
However, it does not support advanced Hyper-V features such as:
• Virtual machine migration
• Hyper-V Replica
• Shared .vhdx

• For more information, you can see:

• Client Hyper-V (TechNet) - https://technet.microsoft.com/en-us/library/hh857623(v=ws.11).aspx

• Download Client Hyper-V - https://aka.ms/dxlex-edx_inf215_hvclient

 Desktop Virtualization

• In Virtual Desktop Infrastructure (VDI), client operating systems are hosted centrally as virtual machines, and
clients connect to these virtual machines by using client software, such as Remote Desktop Client (RDC). You can
configure a server to support VDI by selecting a Remote Desktop Services installation in the Add Roles and
Features Wizard. When you configure a virtualization server to function as a VDI server, you install the Remote
Desktop Virtualization Host role feature in addition to the Hyper-V role.
Desktop Virtualization Continued :

• Benefits of a VDI Solution

• VDI can simplify the management of client operating systems by:
• Ensuring regular backups occur for all client computers that are hosted in a data center.
• Hosting the client virtual machines on a highly available virtualization server.
• Ensuring that users can still access their virtual machine by using other RDC methods when
a client computer fails.

• RemoteFX
• RemoteFX is a technology that benefits VDI deployments by providing a set of
enhancements to remote desktop connections. RemoteFX enables virtual
machines to display rich graphics and video capabilities, including media
streaming. It also provides support for multi-touch. RemoteFX requires:
• A graphics processing unit (GPU) that supports DirectX® 9.0c or newer
• A central processing unit (CPU) that supports SLAT.
 Microsoft Azure Virtualization

Microsoft Azure is a cloud-based platform on which you

can purchase capacity for virtual machines, for applications,
or for services such as SQL Server databases on SQL Azure.
One advantage of using Microsoft Azure is that you pay
only for the capacity that you use, rather than paying a
fixed rate. Cloud-based capacity is elastic, meaning it can
grow or shrink quickly as required. By using a hosting
provider, capacity is scaled automatically and you do not
have to spend the time or money that it takes to switch from
one server to another. The Microsoft Azure Marketplace
offers a many virtual machines with different operating
systems.
 Benefits of Azure Cloud

Hosting Websites or Production Apps

• On cloud-based platforms, such as Microsoft Azure, you can deploy apps without
having to deploy the underlying server infrastructure. For example, say you require a
database. Rather than deploying Windows Server 2016 and SQL Server 2016, and then
deploying the specific database, you can rent the cloud-based database server, and
then host the database there. You can also use Microsoft Azure to host websites.
Deploying Cloud-based Virtual Machines for Proof of Concept Solutions
• Cloud-based virtual machines, apps, and services can be useful when you need to
provide proof-of-concept solutions for proposed projects. Rather than purchase test
hardware and deploy a proof-of-concept solution to it, you can deploy a cloud-based
virtual machine quickly, and then deploy the proof-of-concept solution to that virtual
machine. Then, once you validate the proof-of-concept solution, you can discard the
virtual machine, or keep it, depending on operational concerns. This solution is faster
and less expensive than buying the hardware for the proof-of-concept solution.
For more information, you can see:
• Microsoft Azure (30 day free trial) - https://azure.microsoft.com/en-us/free/
 Presentation Virtualization

• Presentation virtualization is another virtualization solution that enables IT to provide an

organization with a centralized desktop environment. In this solution, user apps run on the
shared centralized server.

Presentation virtualization differs from desktop virtualization in the following ways:

Desktop virtualization Presentation virtualization
Each user is assigned their own virtual machine Users sign in and run separate sessions on a
that runs a client OS. server OS.
Apps run within virtual machines. Desktop and apps run on the virtualization
server.
 How Clients Access Presentation Virtualization

On networks that use Windows Server 2016, the Remote Desktop Services server role provides presentation
virtualization. Clients can access presentation virtualization in the following ways:
• Full Desktop. Clients can use a remote desktop client, such as RDC, to access a full desktop session and run
programs on the Windows Server 2016 virtualization server
• RemoteApp programs. Rather than use a full desktop client, such as RDC, the Windows Server feature RemoteApp
makes it possible for programs that run on the Windows Server 2016 server to display on the client computer.
• Remote Desktop Web Access. Using Remote Desktop Web Access (RD Web Access), clients can access a website
on a specially configured server, and then launch RemoteApp programs and Remote Desktop sessions from their
browser.

Remote Desktop Gateway

• Remote Desktop Gateway (RD Gateway) makes it possible for external clients to access Remote Desktop
and RemoteApp without using a virtual private network (VPN) or DirectAccess connection. RD Gateway
is a role service that you can install on a computer that is running Windows Server 2016. You deploy RD
Gateway servers on perimeter networks, and then configure the RDC client with the address of RD
Gateway servers. This ensures that the client checks to see if the target remote desktop server is on the
organizational network. If it is, the client makes a direct connection to it. If the remote desktop server is
not on the network, the client routes the connection through the RD Gateway server.
Self Study:

For more information, you can see:

• RemoteApp - https://technet.microsoft.com/en-
us/library/cc755055(v=ws.11).aspx
• Remote Desktop Web Access - https://technet.microsoft.com/en-
us/library/cc772452(v=ws.11).aspx
• Deploying Remote Desktop Gateway Step-by-Step Guide -
https://technet.microsoft.com/en-us/library/dd983941(v=ws.10).aspx
 Basic Hyper-V Concepts

• Hyper-V is the hardware virtualization role that is available in Windows Server 2016. Hardware
virtualization provides a hypervisor layer that has direct access to the host server’s hardware. The host
operating system and all virtual machines that are running on the host access the hardware through
the hypervisor layer.

You can install the Hyper-V role on the Server Core installation of Windows Server 2016 and there also is a
free Microsoft Hyper-V Server 2016 edition, which includes only the components necessary to host virtual
machines.
 Hyper-V requirements
Hardware
• 64-bit CPU with SLAT
• VM Monitor mode extensions • GUI mode
• Virtualization support on in BIOS/UEFI • Server Core
• Nano server
Intel-VT/AMD-V DEP enabled
• Enough RAM for workloads
• Windows Vista – Windows 10
Other features require other hardware such as • Windows Server 2008 – WS2016
TPM for shielded VMs, and UEFI 2.3.1c for • Linux
secure boot & measured boot • FreeBSD

Tip: Run Systeminfo.exe to validate hardware

 Virtual Machine Management
Tools
• Hyper-V Manager
• PowerShell
• RSAT tools

PowerShell Direct
• Uses PowerShell
remoting to a VM
where you would not
have network access to
normally
 Nested virtualization
New feature in WS2016
Requires:
• Host running WS2016 Hyper-V
• VM running WS2016 or Windows 10 anniversary update
• A Hyper-V VM with configuration version 8.0 or greater
• An Intel processor with VT-x and EPT technology

To configure:
1. Create a virtual machine
2. While the virtual machine is in the OFF state, run the following on the Hyper-V host to enable nested
virtualization

Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true

3. Start the virtual machine

4. Install Hyper-V within the virtual machine, just like you would for a physical server
 Configure virtual machine (VM) settings
• Add or remove memory in running a VM
• Configure dynamic memory
• Configure Non-Uniform Memory Access (NUMA) support
• Configure smart paging
• Configure Resource Metering, manage Integration Services
• Create and configure Generation 1 and 2 VMs and determine appropriate usage scenarios
• Implement enhanced session mode, create Linux and FreeBSD VMs, install and configure Linux Integration
Services (LIS)
• Install and configure FreeBSD Integration Services (BIS)
• Implement Secure Boot for Windows and Linux environments, move and convert VMs from previous versions
of Hyper-V to Windows Server 2016 Hyper-V, export and import VMs, implement Discrete Device
Assignment (DDA)
 VM Settings

What can be changed (and live)

Gen1 and Gen2 differences

• NUMA spanning
• Dynamic memory
• CPU(s)
• Integration services (and when to configure
them)
• Smart paging and other paths

Tip: Be sure to explore all options

 Gen1 & Gen2 Support
Hardware differences
• Secure boot
• Disks - must boot from IDE disk in Gen1
• No IDE disks in Gen2
• Legacy NIC Gen1 only (allows PXE)
• BIOS vs Firmware
• Gen2 is for WS2012+ guest OS
• TPM in Gen2
• Shielded VMs possible with new hardware presented
 Configure Hyper-V storage
• Create VHDs and VHDX files using Hyper-V Manager

• Create shared VHDX files

• Configure differencing disks

• Modify virtual hard disks

• Configure pass-through disks

• Resize a virtual hard disk, manage checkpoints

• Implement production checkpoints

• Implement a virtual Fibre Channel adapter

• Configure storage Quality of Service (QoS)

 Types of disk
Formats
VHD
• Classic format. Backward compatible
VHDX
• Larger disk size beyond 2TB (64TB)
Pass-through
• Uses physical disks from host exclusively

Types
Fixed
• Uses physical space from day 1 equal to disk size
Dynamically expanding
• Space is consumed on demand up to max disk size
Differencing
• Disk chains allow parent-child disk relationships
for speed of deployment
Shared VHDX files

• Allows for sharing of a VHDX file to >1

VM
• Example: data disk that multiple VMs can
simultaneously access to read/write to
• Allows data for services/applications to
exist once in inexpensive storage
• Requires hosting on shared storage
• Primary use case: Guest-based VM
clusters
• Host-level backups can leverage access to
the VHDX file
• Configure access through the SCSI
controller on a VM
 Configure Hyper-V networking
• Add and remove virtual network interface cards (vNICs)
• Configure Hyper-V virtual switches, optimize network performance
• Configure MAC addresses, configure network isolation, configure synthetic and legacy virtual network
adapters
• Configure NIC teaming in VMs
• Configure virtual machine queue (VMQ)
• Enable Remote Direct Memory Access (RDMA) on network adapters bound to a Hyper-V virtual switch using
Switch Embedded Teaming (SET)
• Configure Bandwidth Management
 Add and remove virtual network interface
cards (vNICs)

Legacy Network adapter

• Used in Gen1 VMs
• Limited bandwidth 100Mbps
Network adapter
• Gen1 and Gen2 support
• 10 Mbps connections

PXE Support for VMs

• Legacy network adapter only in Gen1 VMs
• Native support in Gen2 Network adapters
Configure Hyper-V virtual switches, optimize network performance

External
• Uses physical NIC in host to allow LAN/Internet
connectivity.
• VM NIC must use IP address relevant to physical
subnet
Internal
• Connectivity between VMs and host only on the
same switch
Private
• Connectivity between VMs only on the same switch
Bandwidth Management
New NAT switch in WS2016 VLAN ID
New-VMSwitch -Name “NATSwitch” -SwitchType NAT - SR-IOV
NATSubnetAddress 172.16.1.0/24 VMQ
 NIC teaming

Configurable in VM or host

New 2016 host feature:

Switch-embedded teaming (SET) - a new way to implement network teaming that is compatible with RDMA and
VMQ
• Combine network adapters into a team with up to 8 network adapters
• All of the network adapters in a team must be identical with the same firmware version and driver. SET is
automatically enabled when multiple network adapters are used

To create a virtual switch with SET, use the following Windows PowerShell command:
 Configure NIC settings
MAC addresses assigned from a pool
• Configurable on host, always starts 00-15-5D
You can assign static MAC
• Know when you would – NLB, Nested VMs
When to use spoofing?
• If a VM uses NLB or similar services that use a common MAC
address

DHCP Guard
• Protects leakage of packets from a VM acting as a DHCP server
Router Guard
• Suppresses router advertisements from VMs configured as
routers
Port Mirroring and more!
 Practice Question
You plan to deploy a Hyper-V based nested virtualization solution onto a number of servers. The nested servers
need access to the Internet. You have the following virtual machines (VMs) available.
You need to identify which servers from the following table can be used for this purpose.
VM Name Installation VM Configuration Network configuration
type version
Server1 Server with 7.0 Internal network switch
GUI
Server2 Server Core 8.0 External network switch
Server3 Nano Server 8.0 NAT switch
Server4 Server Core 8.0 MAC address spoofing configured
Which servers should you identify?
A. Server1 and Server2
B. Server2 and Server3
C. Server1 and Server3
D. Server3 and Server4
https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/user_guide/nesting
Hyper-V Networking

SR-IOV
VMQ
NIC Teaming