This document provides an overview and lessons on installing and configuring the Hyper-V role in Microsoft Virtual Academy. It discusses installing the Hyper-V server role, managing Hyper-V, configuring Hyper-V settings, and Hyper-V host storage and networking. The lessons cover topics like Hyper-V architecture, storage and networking considerations, using Hyper-V Manager and PowerShell, resource pools, Storage Spaces, SMB 3.0, and network teaming.

1. Microsoft Virtual Academy
Module 2
Installing and Configuring the Hyper-V Role

2. Module Overview
• Installing the Hyper-V Role
• Managing Hyper-V
• Configuring Hyper-V Settings
• Hyper-V Host Storage and Networking

3. Lesson 1: Installing the Hyper-V Server Role
• Server Platforms That Provide Hyper-V
• Hyper-V and Virtual Machine Scalability
• Hyper-V Architecture
• Considerations for Disk and Storage
• Considerations for Networking
• Considerations for High Availability
• Changes on the Host after Installing the Hyper-V Role

4. Server Platforms That Provide Hyper-V
• Windows Server 2012 and newer Windows Server operating systems:
• Include Hyper-V and other roles
• GUI and command-line management
• Licensed per processor, includes virtualization rights
• Standard edition: two virtual machines with each Windows Server operating
system
• Enterprise edition: unlimited virtual machines with each Windows Server
operating system
• Hyper-V Server 2012 and newer:
• Includes only the Hyper-V role
• Command-line management only (if managed locally)
• Free, virtual machines must be licensed separately
• Windows 8 and newer Windows client 64-bit operating systems:
• Client Hyper-V, does not include server-level features such as high
availability or live migration

5. Hyper-V and Virtual Machine Scalability
System Resource Windows Server
2012 R2
Server
Logical processors 320
Physical memory 4 TB
Virtual processors per server 2,048
Virtual
machine
Virtual processors per virtual machine 64
Memory per virtual machine 1 TB
Running virtual machines per server 1,024
Virtual disk size 64 TB
Failover cluster
Nodes per failover cluster 64
Running virtual machines per cluster 8,000

6. Considerations for Disk and Storage
• Hyper-V hosts can use
• DAS
• SAN
• NAS (SMB 3.0)
• Network shared folders (SMB 3.0)
• Virtual Machines require storage for
• Virtual hard disk files
• Configuration
• Checkpoints
• Saved state

7. Considerations for Networking
• Hyper-V host should have multiple NICs
• Dedicated NIC for Hyper-V management
• At least one NIC for virtual machine networks
• Two NICs for shared storage
• Dedicated NIC for failover clustering (private network)
• At least one NIC for live migration
• Use fast NICs
• NIC teaming for redundancy and throughput
• Bandwidth management

8. Considerations for High Availability
• Hyper-V host-based failover clustering
• Virtual machines are highly available
• Virtual machine-based failover clustering
• Cluster roles in virtual machines are highly available
• Virtual machine-based NLB
• Highly available and scale out web-based applications
• Application-specific clustering
• Applications are highly available

9. Changes on the Host after Installing the Hyper-V Role
• Hyper-V is installed as A server role
• Server Manager, Install-WindowsFeature, dism.exe
• Restart required after installation
• Hypervisor is added and starts automatically
• Windows Server is moved into parent partition
• Hyper-V management tools
• Additional services
• Performance Monitor counters
• Applications and Services logs
• Hyper-V Administrators group
• Windows Firewall rules

10. Lesson 2: Managing Hyper-V
• Overview of the Hyper-V Manager Console
• Adding the Hyper-V Manager Console
• Using Windows PowerShell to Manage Hyper-V
• Managing Hyper-V in a Workgroup Environment
• Hyper-V Best Practices Analyzer
• Hyper-V Security Model

11. Overview of the Hyper-V Manager Console
Hyper-V servers
Listing of virtual
machines
Hyper-V
server
actions
Virtual
machine
actions

12. Adding the Hyper-V Manager Console
• Used for configuring Hyper-V
• Also on Hyper-V Server
• If adding the Hyper-V role by using Server Manager,
Hyper-V Manager console is added automatically
• Hyper-V Management Tool is a feature that you must
enable
• Windows Server - Add feature
• Windows 8 - Turn on Windows Feature
• Install RSAT and turn on Windows Feature (Windows 7)
• If Hyper-V Manager console cannot run on a device
• RDP

13. Using Windows PowerShell to Manage Hyper-V
• Hyper-V module installed with Hyper-V role
• Hyper-V can be managed entirely in Windows
PowerShell
• Get-Command -Module Hyper-V
• Get-Help <cmdlet>, Get-Command *part*
• Verb-Noun cmdlet name syntax
• Get-, Set-, Disable-, Enable-, New-, Add-, …
• Get-VMHost -ServerName LON-DC1, LON-SVR1
• Get-VM -HostName LON-HOST1 | Save-VM
• Start-VM -Name *DC* -HostName LON-HOST1
• Get-VMHost -HostName LON-HOST1 | ft
• Windows PowerShell ISE

14. Managing Hyper-V in a Workgroup Environment
• Hyper-V can be a workgroup member
• This has no effect on virtual machines running on the
Hyper-V host
• Domain membership simplifies management
• To enable remote management in a workgroup
• Enable Hyper-V firewall rules (Server Core only)
• Create a local user with the same username and
password
• Add a local user to Hyper-V Administrators group
• Grant administrative rights remotely to local users
• Connect to the Hyper-V host in Hyper-V console
• Use HVRemote to simplify configuration

15. Hyper-V Best Practices Analyzer
• Best Practices are guidelines for typical deployment
• Hyper-V BPA includes over 110 rules including:
• Hyper-V should be the only enabled role
• Server Core is recommended for Hyper-V servers
• Domain membership is recommended for Hyper-V
• BPA is available in Server Manager and Windows
PowerShell
• Can scan one or multiple roles locally or remotely
• Can filter scan results
• Compliance scan returns one of three levels:
• Error, Warning, Information

16. Hyper-V Security Model
• Authorization Manager controls Hyper-V security
• Challenging to use, not suitable for complex security rules
• Depreciated, but still available in Windows Server 2012 R2
• Many administrators use VMM
• Simple Authorization is used on Server 2012 R2
• Hyper-V Administrators local and domain groups—are
empty by default
• Members have full access to Hyper-V
• Hyper-V Administrators group is incorporated into
Authorization Manager

17. Lesson 3: Configuring Hyper-V Settings
• Overview of Hyper-V Settings
• What Is NUMA?
• What Is RemoteFX?
• What Is Enhanced Session Mode?
• What Are Resource Pools?

18. Overview of Hyper-V Settings

19. What Is NUMA?
• NUMA
• Enables host to scale up CPUs and memory
• Partitions CPUs and memory into NUMA nodes
• Allocation and latency depends on relative CPU location
• Hyper-V presents NUMA topology to virtual machines
• Guest operating system can make decisions on how to use
resources
• Can minimize cross-node memory access
• NUMA spanning enabled at host level
• Virtual NUMA topology can be configured at virtual
machine level
• By default, virtual NUMA aligns with physical NUMA

20. What Is RemoteFX?
• Provides a remote desktop experience that may be equivalent
to a physical desktop environment
• System Requirements
• GPU
• Second level address translation
• RD Virtualization Host role service
• RemoteFX 3D Video Adapter virtual machine hardware
• RemoteFX features:
• RemoteFX for WAN
• RemoteFX Adaptive Graphics
• RemoteFX Media Streaming
• RemoteFX Multi-Touch
• RemoteFX USB Redirection

21. What Is Enhanced Session Mode?
• Remote Desktop over VMBus
• Full Remote Desktop capabilities
• Shared clipboard
• Printers, smart cards, USB devices redirection
• Folder redirection
• Enabled at Hyper-V host
• Guest operating system support
required
• Windows Server 2012 R2
• Windows 8.1
• Remote Desktop users

22. What Is Enhanced Session Mode?
Hypervisor
Applications
Video / Keyboard
/ Mouse Driver
VMBusVMBus
Virtual Machine
Management
Service
Virtual Machine
Worker Process
Applications
ApplicationsVirtual
machine
connect
Basic
Experience

23. What Is Enhanced Session Mode?
Hypervisor
Applications
VMBusVMBus
Virtual Machine
Management
Service
Virtual Machine
Worker Process
Applications
ApplicationsVirtual
machine
connect
Enhanced
session
mode
Remote Desktop
Services

24. What Are Resource Pools?
• Resource pools are logical containers
• Layer of abstraction between virtual machine and hardware
• Virtual machine configured to use the pool
• Virtual machine can use any resource from the configured pool
• Helpful when moving virtual machines
• Resource pools can be used for chargeback
• Different resource pool types
• Processor, Memory, Ethernet, VHD
• Resource pools configured by Windows PowerShell
• Get-VMResourcePool
• New-VMResourcePool -Name "Contoso Network" -
ResourcePoolType Ethernet

25. Lesson 4: Hyper-V Host Storage and Networking
• Overview of Storage Spaces
• Overview of Disk Deduplication
• What Is Offloaded Data Transfer?
• What Is SMB 3.0?
• Hyper-V over SMB
• Overview of Network Teaming

26. Clustered
• What’s in a storage appliance?
• x86/x64 Processors
• Memory
• Network Adapters
• Storage HBAs
“Back”
“Front”
Multiple physical
interfaces; Pools disks,
presents LUNs,
Simple, Mirrored,
Parity etc.
Presents
interfaces:
iSCSI, FC, FCoE,
NFS, SMB
Multiple physical
interfaces; Pools disks,
presents LUNs,
Simple, Mirrored,
Parity etc.
Presents
interfaces:
iSCSI, FC, FCoE,
NFS, SMB
Deploy two or more for a Scale Out CA
Solution
Servers
Servers
Servers
Servers
Servers
Servers
Servers
Servers
SAS
Ethernet: 1Gb/10Gb
FC: 1/2/4/8/16 Gb
Demystifying Storage Appliances

27. Clustered
Windows Server 2012 Spaces 
Windows Server 2012 File
Server 
Multiple physical
interfaces; Pools
disks, presents
LUNs, Simple,
Mirrored, etc.
Presents
interfaces:
iSCSI, NFS, SMB
Multiple physical
interfaces; Pools
disks, presents
LUNs, Simple,
Mirrored, etc.
Presents
interfaces:
iSCSI, NFS, SMB
Deploy two or more for a Scale Out CA
Solution
Servers
Servers
Servers
Servers
Servers
Servers
Servers
Servers
SAS
SMB3/Ethernet: 1Gb/10Gb
40Gb/56 Gb RDMA
Windows Server 2012 R2 File Server and Spaces

28. New Designs: Cluster in a Box
Availability
• At least one node and storage always available,
despite failure or replacement of any component
• Dual power domains
Simplicity
• Pre-wired, internal interconnects between
nodes, controllers, and storage
Flexibility
• PCIe slots for flexible LAN options
• External SAS ports for JBOD expansion
• Office-level power, cooling, and acoustics to fit
under a desk
Server Enclosure
Additional JBODs …
B ports
A ports
x8 PCIe
Server BServer A
x8 PCIe
x4 SAS
External JBOD
x8 PCIe
x4 SAS
x8 PCIe
1/10G E or Infiniband 1/10G E or Infiniband
B ports
A ports
SAS
Expander
SAS
Expander
23…10
NetworkNetwork
23…10
SAS
Expander
Storage
Controller
CPU
SAS
Expander
Storage
Controller
CPU
x4 SAS (through midplane)
x4 SAS (through midplane)
1/10G Ethernet cluster connect
(through midplane)
DataOn – DNS 9220
http://www.dataonstorage.com

29. • Storage Tiering
• Data deduplication
• RAID resiliency groups
• Pooling of disks
• High availability
• Persistent write-back cache
• Copy offload
• Snapshots
• Storage Tiering (new with R2)
• Data deduplication (enhanced in R2)
• Flexible resiliency options (enhanced in R2)
• Pooling of disks
• High availability
• Persistent write-back cache (new with R2)
• SMB copy offload
• Snapshots
Traditional Storage
with FC/iSCSI Storage Array
Windows File Server Cluster
with Storage Spaces
Familiar Enterprise-Grade Capabilities

30. Storage Tiering
Can “
Hard Disk Drives
Cold data

31. Overview of Storage Spaces
• Storage pools – collection of physical disks
• Storage Spaces – virtual disks on storage spaces
• Storage Spaces features
• Resiliency and integrity on standard disks
• Continuous availability and CSV integration
• Optimal storage use and storage tiering
• Multitenancy and isolation
Windows
virtualized
storage
Physical
storage
(Shared) SAS, SATA or USB
Storage Pool
Storage
Spaces
Storage Pool
Storage
Spaces
Storage Pool
Storage
Spaces

32. Overview of Disk Deduplication
• Identifies and removes duplications within data
• Without compromising data integrity
• To store more data on less space
• After data is stored (post-process)
• Requires NTFS file system
• Failover clustering and shared storage supported
• CSV support added in R2
• Can significantly decrease space for VHD library
• R2 adds support for live VHD deduplication for VDI
• VHDs must be accessed on an SMB 3.0 network share
• Deduplication of virtual machines that use local storage not
supported

33. What Is Offloaded Data Transfer?
• Traditional data copy model
• Server issues read request to SAN
• Data is read and transferred into memory
• Data is transferred and written from memory to SAN
• Issues: CPU and memory utilization, increased traffic
• Offload-enabled data copy model
• Server issues read request and SAN returns token
• Server issues write request to SAN using token
• SAN completes data copy and confirms completion
• Benefits: Increased performance, reduced utilization
• SAN must support Offloaded Data Transfer

34. What Is Offloaded Data Transfer?
Intelligent
Storage Array
Storage
array
Storage
array
Actual data transfer
Offload
read
Token
Offload
write
Token

35. What Is SMB 3.0?
• SMB is network file sharing protocol
• SMB protocol versions are backward compatible
• SMB 3.0 features in Windows Server 2012 (R2)
• SMB Transparent Failover
• SMB Scale Out
• SMB Multichannel
• SMB Direct (SMB over RDMA)
• SMB Encryption
• VSS for SMB file shares
• Managing SMB file shares by Windows PowerShell
• SMB 3.0 is used only if both sides support it

36. Hyper-V over SMB
• Hyper-V data files stored on network shares
• Virtual machine configuration, VHD files, checkpoints
• Hyper-V supports file shares over SMB 3.0 or newer
• File Server and Hyper-V must be separate servers
• They must be members of the same Active Directory
• Running virtual machine data files can be deduplicated
(VDI)
• Reliability, availability, and performance as a SAN
• Uses SMB 3.0 features
• Benefits
• Easier provisioning and management
• Uses existing infrastructure