Virtual Desktop Infrastructure: A deployment guide for education

Virtual Desktop
Infrastructure
A deployment guide
for education
January 2014
Table of
contents
3 Choosing a VDI deployment scenario
6 Virtual machine–based desktop deployment
10 Session-based desktop deployment
13 Windows MultiPoint Server 2012
15 Preparing the infrastructure for VDI
17 Placing VDI servers
18 Building virtual desktop templates
20 Client licensing for VDI
22 Using Volume Activation
25 Connecting users to VDI sessions
27 Storing user and application settings
30 Running Windows Store and sideloaded apps
31 Managing VDI
33 Group Policy
34 Windows PowerShell
34 SystemCenter2012R2CongurationManager
35 Windows Intune
1VIRTUAL DESKTOP INFRASTRUCTURE
Virtual Desktop
Infrastructure
A deployment guide for education
One of the challenges for educational institutions is
managing the wide diversity of devices and user types.
Given such diversity, establishing and maintaining a

standardized technology learning platform can be difcult.
Although it may be possible to purchase new devices
running the Windows 8.1 operating system or upgrade
existing devices to Windows 8.1, other institution-owned
devices may be unable to run Windows 8.1 (such as
older hardware or devices running Apple iOS or Google
Android).
Inaddition,BringYourOwnDevice(BYOD)initiativesareincreasingly
popular in institutions because they allow faculty to use their devices
toperformadministrativerolesaidwithcurriculum.BYODinitiatives
alsoallowstudentstousetheirdevices(inandoutoftheclassroom)
asapartoftheeducationalprocess.BYODinitiativeshelpinstitutions
byreducingtheup-frontcostofdeviceswhileallowingfacultyand
studentstotakeadvantageoftechnologyforeducation.
However,BYODinitiativescancreateproblemsforITproswho
support the faculty and students. It is almost certain that the
deviceswillhavebroaddiversity.Althoughitmaybepossiblethat
thefacultyorstudentsmayhavedevicesrunningtheWindows8.1
operatingsystem,otherpersonallyowneddevicesmaybeunableto
runWindows8.1(suchasolderhardwareordevicesrunningiOSor
Android).
YoucanaddressthesechallengesbyusingVirtualDesktop
Infrastructure(VDI)poweredbytheWindowsServer2012R2or
WindowsMultiPointServer2012operatingsystem.WithVDIin
NOTE
Althoughmanyofthe
topics discussed in this
guideareapplicable
toVDIinWindows
Server 2012 R2, Windows

Server 2012, or Windows
MultiPoint Server 2012,
thisguidefocusesonVDI
in Windows Server 2012
R2. For more information
about Windows MultiPoint
Server2012planningand
deployment, see the topic
“Windows MultiPoint
Server 2012” at http://
technet.microsoft.com/
library/jj916259.aspx and
other Windows MultiPoint
Server 2012 resources
listedinthisguide.
2VIRTUAL DESKTOP INFRASTRUCTURE
Windows Server 2012 R2 or Windows MultiPoint Server 2012, users can remotely run Windows 8.1
appsasthoughtheywererunningontheirlocaldevice,includingvideoclips,movies,streaming
video,andothergraphicallyintensiveapplications.UserscanalsodirectlyaccessUSBdevices
connectedtotheirdevice(suchassmartcardreaders,USBashdrives,orscanners)fromwithin
VDI.
Thefollowingisalistofassumptionsabouttheinstitutionally-owneddevicesdescribedinthis
guide:
• Thedevicesmayormaynotbedomain-joined.
• Userslogontotheirdevicebyusinganinstitution-issuedaccount(andpossiblehavean
associatedMicrosoftaccount)insteadofusingtheirownWindowsaccount.
• Windows8.1Enterprisecanbedeployedonthedevices(ifdesired).
• Windows-baseddevicesthatneedtosupportMicrosoftRemoteFXwillberunningWindows
Vistaorlateroperatingsystems.
• DevicesrunningoperatingsystemsotherthanWindows(suchasiOSorAndroid)willrequire

anappthatsupportstheRemoteDesktopProtocol(RDP)andRemoteFX.
Thefollowingisalistofassumptionsaboutthepersonallyowneddevicesdescribedinthisguide:
• Thedevicesarenotdomainjoined.
• UserslogontotheirdevicebyusingtheirownWindowsaccount(andpossibleMicrosoft
account)insteadofaninstitution-issuedaccount.
• NoneofthedeviceswillberunningWindows8.1Enterprise.
• Windows-baseddevicesthatneedtosupportRemoteFXwillberunningWindowsVistaor
later.
• DevicesrunningoperatingsystemsotherthanWindows(suchasiOSorAndroid)willrequire
anappthatsupportstheRDPorRemoteFX.
3VIRTUAL DESKTOP INFRASTRUCTURE
Choosing a VDI
deployment scenario
WindowsServer2012R2offersthefollowingdeploymentscenarios:
• Virtual machine (VM)–based In this scenario, Windows 8.1
VMsruninaHyperVinfrastructure.YouuseRemoteDesktop
Services to provide users remote connectivity to the VMs.
YoucanusetheVM-baseddeploymentscenariowithpooled
or personal VM collections. For more information about the
VM-based deployment scenario and pooled and personal VM
collections, see the section “Virtual machine–based desktop
deployment”onpage6.
• Session-based In this scenario, remote users connect to
RemoteDesktopServicesinWindowsServer2012R2andrun
theirapplicationinWindowsServer2012R2sessions.Only
RemoteDesktopServicesisrequiredforthisscenario.Formore
information about the session-based deployment scenario, see
the section “Session-baseddesktopdeployment”onpage10.
Figure1providesahigh-levelcomparisonoftheVDIdeployment
scenariosinWindowsServer2012R2.UsetheinformationinFigure1

toidentifythehigh-leveldifferencesbetweentheVMandsession-
based desktop deployment scenarios.
FIGURE 1 High-level
comparisonofVDI
desktop deployment
scenarios
Personalization
GOOD BETTER BEST
Application
compatibility
User density
Image count
Cost
Sessions
Pooled VMs
Personal VMs
4VIRTUAL DESKTOP INFRASTRUCTURE
Table1provideamoredetailedcomparisonoftheVDIdesktopdeploymentscenariosand
WindowsMultiPointServer2012.Usetheinformationinthistabletochoosetherightcombination
ofVDIdeploymentsolutionsforyourinstitution.Youcanuseanycombinationofthesescenarios
tocreateacomprehensiveVDIdeploymentsolution.
TABLE 1 DetailedComparisonofVDIDesktopDeployment
Scenarios and Windows MultiPoint Server 2012
SeSSion-baSed deSktop
deployment
WindoWS multipoint
Server 2012
vm-baSed deSktop
deployment
User operating system

experience
Windows Server 2012 R2 Windows 8.1 Windows 8.1
Support for full-delity
video, with coverage for
all media types and highly
synchronized audio, rich
media support, Microsoft
Silverlight, 3D graphics,
and Windows Aero
Microsoft RemoteFX Requiresdirectvideo–
connectedstations,USB
zero client–connected
stations,USB-over-
Ethernet zero clients,
orRDP–over-LANwith
RemoteFX
RequiresRemoteFX
Directly connect the VDI
session to client USB
devices
• StandardRDP
connection provides
limited support of
USBdevice
• RemoteFXrequired
for broader support
ofUSBdevices
• StandardRDP
connection provides
limited support of

USBdevice
• Directvideo–
connected stations,
USBzeroclient–
connected stations,
USB-over-Ethernet
zero clients, or
RDP-over-LANwith
RemoteFXrequired
for broader support
ofUSBdevices
• StandardRDP
connection provides
limited support of
USBdevice
• RemoteFXrequired
for broader support
ofUSBdevices
5VIRTUAL DESKTOP INFRASTRUCTURE
SeSSion-baSed deSktop
deployment
WindoWS multipoint
Server 2012
vm-baSed deSktop
deployment
Supported client devices Any device that
supportsRDPor
RemoteFX(including
WindowsThinPC)
Supportsthefollowing:

• Directvideo–
connected stations
• USBzeroclient–
connected stations
• USB-over-Ethernet
zero clients
• Any device that
supportsRDPor
RemoteFX
Any device that
supportsRDPor
RemoteFX(including
WindowsThinPC)
Scaling As many as hundreds
of users for each server,
but multiple servers can
be added to scale to
highernumbers
As many as 20 users Uptohundredsofusers
for each server, but
multiple servers can be
addedtoscaletohigher
numbers
High availability Supportsloadbalancing
andclusteringof
resources
Unavailable Supportsloadbalancing
andclusteringof
resources
Additional resources:

• “HP Client Virtualization SMB Reference Architecture for Windows Server 2012” at http://
h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA4-3901ENW&cc=us&lc=en
6VIRTUAL DESKTOP INFRASTRUCTURE
Virtual machine–based desktop deployment
Figure2illustratesthehigh-levelcomponentsinaVM-baseddesktop
deployment.Youcanrunthesecomponentsallononeserveroron
evenmoreserverstoprovideadditionalscalingandhighavailability.
ThefollowingisadescriptionofthecomponentsinatypicalVM-
based desktop deployment:
• Remote Desktop Connection Broker Thisroleservice
managesconnectionsbetweentheclientsandtheVMsrunning
ontheRemoteDesktopVirtualizationHost.
• Remote Desktop Virtualization Host Thisroleservice
integrateswithHyperVtoprovideVMs.ItusestheRemote
DesktopConnectionBrokerroleservicetodeterminetheVMto
which the user is redirected.
• Remote Desktop Web Access Thisroleserviceenablesusersto
accessVMsthroughawebbrowser.
• Client Theclientprovidesaccesstotheremotedesktop.it
canbeatraditionaldevicerunningtheRemoteDesktopClient
inWindows,anappthatsupportsRDPandRemoteFX,athin
orzeroclientthatsupportsRDP(suchasWindowsThinPC),
or a RemoteFX-enabled device. For institution-owned devices,
the client device may or may not be a member of an Active
FIGURE 2 Components
in a VM-based desktop
deployment
CLIENT
REMOTE DESKTOP
VIRTUALIZATION HOST

REMOTE DESKTOP
CONNECTION BROKER
REMOTE DESKTOP
WEB ACCESS
DOMAIN
CONTROLLER
7VIRTUAL DESKTOP INFRASTRUCTURE
Directorydomain.Forpersonallyowneddevices,theclientwillnotbeamemberoftheActive
DirectoryDomainServices(ADDS)domain.
• Domain controller and other network infrastructure services Theseservicesinclude
ADDS,DynamicHostCongurationProtocol(DHCP),DomainNameSystem(DNS),and
routing.
Windows Server 2012 R2 introduces the concept of virtual desktop collections. A virtual desktop
collectionconsistsofoneormorevirtualdesktopsusedinaVDIdeploymentscenario.Youcan
choosetodeploypooledorpersonalcollectionswiththemethodyouselect,dependingonyour
environment and preferences, as described in Table2.
TABLE 2 ComparisonofPooledandPersonalVirtualDesktopCollections
pooled perSonal
Changes are made to Transientvirtualharddisk VM virtual hard disk
Changes saved after
session ends
No(exceptforuserprolechanges) Yes
VM instances SingleVMmasterimagethatallusers
in the collection share
Separate VM instances created from a
mater VM for each user
Number of images to
manage
Onemasterimage Animageforeachuser(aftertheVM
instanceiscreated)

Infrastructure services • Managednetwork
• RemoteDesktopServices
• HyperV
• Managednetwork
• RemoteDesktopServices
• HyperV
Network connectivity • SupportstandardRemoteDesktop
Servicesbyusinglow-bandwidth
connections
• RemoteFXconnectionrequires
medium-tohigh-bandwidth
connections(dependingon
contentbeingdisplayed)
• SupportstandardRemoteDesktop
Servicesbyusinglow-bandwidth
connections
• RemoteFXconnectionrequires
medium-tohigh-bandwidth
connections(dependingon
contentbeingdisplayed)
Storage requirements • Storageformasterimageand
transient virtual hard disks
• StorageforeachUserProleDisk
(ifused)
RequiresseparateVMstoragefor
eachuser;iftheaveragestoragefor
the master VM is 100 GB and there
are100users,10TBofstoragewillbe
required
8VIRTUAL DESKTOP INFRASTRUCTURE

pooled perSonal
Manageability Onlyoneimagetomanage,souse
stand-aloneimage-management
tools;changestothemasterimage
arereectedthenexttimeasessionis
initiated
Managebyusingtechnologies
and products such as Group Policy,
WindowsServerUpdateServices,
or Microsoft System Center 2012 R2
CongurationManager
User exibility • Userscannotinstallapps
• Userscannotbeanadministrator
on their VM
• Userscaninstallapps
• Userscanbeanadministratoron
their VM
User prole storage • Transientvirtualharddisk(VHD;
userprolechangesarelost)
• UserProleDisk(userprole
changesareretained)
StoredandretainedintheVMVHDs
User, operating system,
and app conguration
management
• RoamingProles
• Folder Redirection
• MicrosoftUserExperience
Virtualization(UE-V)
• Microsoft Application

Virtualization(App-V)
• UserProleDisk
• RoamingProles
• Folder Redirection
• UE-V
• App-V
• LocallystoredonVM
Youcandeploybothpooledandpersonalcollectionsas:
• Managed ThisdeploymentoptionletsRemoteDesktopServicesautomaticallymanagethe
virtual desktops within the collection.
• Unmanaged Thisdeploymentoptionletsyoumanuallymanagethevirtualdesktopswithin
the collection.
Thehigh-levelstepsfordeployingVM-baseddesktopdeploymentare:
1. DeployWindowsServer2012R2ontheRemoteDesktopConnectionBrokerserver.
2. DeployWindowsServer2012R2ontheRemoteDesktopWebAccessserver.
3. DeployWindowsServer2012R2ontheRemoteDesktopVirtualizationHostserver.
4. EnsurethatallserversaremembersofthesameADDSdomain.
9VIRTUAL DESKTOP INFRASTRUCTURE
5. OntheRemoteDesktopConnectionBrokerserver,useServer
Managertoaddalltheserverstotheserverpool.
6. OntheRemoteDesktopConnectionBrokerserver,useServer
ManagertoinstallthefollowingroleservicesfortheRemote
DesktopServicesInstallationserverrole:
• RemoteDesktopConnectionBroker
• RemoteDesktopWebAccess
• RemoteDesktopVirtualizationHost
7. AddthevirtualdesktoptemplatetotheRemoteDesktop
Virtualization Host server.
8. Ifdeployingapooledcollection,createanetworksharedfolder
inwhichtostoretheUserProleDisk(typicallyontheRemote

DesktopConnectionBrokerserver).
9. Createthecollection(pooledforapooledcollectionor
personalforapersonalcollection).
10. Verify that the virtual desktop collection works correctly.
Additional resources:
• “TestLabGuide:VirtualDesktopInfrastructureStandard
Deployment”at />hh831541.aspx
• “TestLabGuide:ManagedPooledVirtualDesktopCollections”
at />• “TestLabGuide:UnmanagedPooledVirtualDesktop
Collections” at />hh831618.aspx
• “Windows8/WindowsServer2012:PooledVirtualDesktop
Infrastructure” at />archive/2012/10/31/windows-8-windows-server-2012-pooled-
virtual-desktop-infrastructure.aspx
NOTE
Althoughyouarerunning
ServerManageron
theRemoteDesktop
Connection Broker server,
ServerManagerprompts
you for the names of the
serversrunningtheother
RemoteDesktopServices
role services.
10VIRTUAL DESKTOP INFRASTRUCTURE
Session-based desktop deployment
Figure3illustratesthehigh-levelcomponentsinasession-based
desktopdeployment.Youcanrunallofthesecomponentsonone
serveroronevenmoreserverstoprovideadditionalscalingandhigh
availability.
Thefollowinglistprovidesadescriptionofthecomponentsina

typical session-based desktop deployment:
• Remote Desktop Connection Broker Thisroleservice
managesconnectionsbetweentheclientsandtheremote
desktopsessionsrunningontheRemoteDesktopSessionHost.
• Remote Desktop Session Host Thisroleserviceruns
RemoteAppprogramsorsession-basedvirtualdesktops.
Thisroleserversisultimatelywheretheusersconnecttorun
programs,saveles,anduseotherresources.ItusestheRemote
DesktopConnectionBrokerroleservicetodeterminethe
remote desktop session to which the user is redirected.
• Remote Desktop Web Access Thisroleserviceenablesusersto
accesstheremotedesktopsessionsthroughawebbrowser.
• Client Theclientprovidesaccesstotheremotedesktop.itcan
beatraditionaldevicerunningtheRemoteDesktopClientin
Windows,anappthatsupportsRDPandRemoteFX,athinor
zeroclientthatsupportsRDP(suchasWindowsThinPC),ora
RemoteFX-enabled device. For institution-owned devices, the
FIGURE 3 Components in
a session-based desktop
deployment
CLIENT
REMOTE DESKTOP
SESSION HOST
REMOTE DESKTOP
CONNECTION BROKER
REMOTE DESKTOP
WEB ACCESS
DOMAIN
CONTROLLER
11VIRTUAL DESKTOP INFRASTRUCTURE

clientdevicemayormaynotbeamemberofanADDSdomain.
For personally owned devices, the client will not be a member of
anADDSdomain.
• Domain controller and other network infrastructure
services TheseservicesincludeADDS,DHCP,DNS,and
routing.
Thehigh-levelstepsfordeployingsession-
based desktop deployment are:
1. DeployWindowsServer2012R2ontheRemoteDesktop
Connection Broker server.
2. DeployWindowsServer2012R2ontheRemoteDesktopWeb
Access server.
3. DeployWindowsServer2012R2ontheRemoteDesktop
Session Host server.
4. EnsurethatallserversaremembersofthesameADDSdomain.
5. OntheRemoteDesktopConnectionBrokerserver,useServer
Managertoaddalloftheserverstotheserverpool.
6. OntheRemoteDesktopConnectionBrokerserver,useServer
ManagertoinstallthefollowingroleservicesfortheRemote
DesktopServicesInstallationserverrole:
• RemoteDesktopConnectionBroker
• RemoteDesktopWebAccess
• RemoteDesktopSessionHost
7. CreateanetworksharedfolderinwhichtostoretheUser
ProleDisk(typicallyontheRemoteDesktopConnection
Brokerserver).
8. Create the session collection.
9. Verify that the session collection works correctly.
NOTE
Althoughyouarerunning

ServerManageron
theRemoteDesktop
Connection Broker server,
ServerManagerprompts
you for the names of the
serversrunningtheother
RemoteDesktopServices
role services.
12VIRTUAL DESKTOP INFRASTRUCTURE
Additional resources:
• “TestLabGuide:RemoteDesktopServicesSessionVirtualizationStandardDeployment”at
/>• “TestLabGuide:RemoteDesktopServicesSessionVirtualizationQuickStart”athttp://
technet.microsoft.com/en-us/library/hh831754.aspx
• “Windows8/WindowsServer2012:RemoteDesktopManagementServer”athttp://blogs.
technet.com/b/askperf/archive/2012/10/30/windows-8-windows-server-2012-remote-
desktop-management-server.aspx
• “Virtualization:VDImadeeasy”at />aspx
13VIRTUAL DESKTOP INFRASTRUCTURE
Windows MultiPoint Server 2012
Windows MultiPoint Server 2012 enables multiple users to share
one computer and provides a low-cost alternative to traditional
computingscenariosinwhicheachuserhastheirowncomputer.
WindowsMultiPointServer2012alsoprovidesaneasymanagement
solution for Windows MultiPoint Server 2012 system administration
called MultiPoint Managerandaneasymanagementsolutionfor
day-to-day administration called MultiPoint Dashboard.
Windows MultiPoint Server 2012 is available in Standard and
Premiumversions.UsetheinformationinTable3 to select the
appropriate versions for your educational institution.
Standard premium

Number of
simultaneously connected
stations
10 20
Can be joined to a
domain?
No Yes
Virtualization support as
a host or guest operating
system?
No Yes
WindowsMultiPointServer2012canonlybedeployonasingle
computer.YoucanscaleWindowsMultiPointServer2012only
throughtheadditionofWindowsMultiPointServer2012instances:It
hasnoinherenthighavailability.However,youcouldrunvirtualized
instancesofWindowsMultiPointServer2012onhighlyavailable
HyperV clusters.
TheuserendpointsthatconnecttothecomputerrunningWindows
MultiPoint Server 2012 are called stations. Windows MultiPoint
Server2012supportsthefollowingstationtypes:
• Direct video–connected stations Thecomputerrunning
Windows MultiPoint Server 2012 can contain multiple video
cards,eachofwhichcanhaveoneormorevideoports.This
allowsyoutoplugmonitorsformultiplestationsdirectlyinto
TABLE 3 Comparison
of Windows MultiPoint
Server 2012 Standard and
Premium
14VIRTUAL DESKTOP INFRASTRUCTURE
the computer. Keyboards and mouse devices are connected

throughUSBhubsassociatedwitheachmonitor.Usea
combinationofallofthesetechnologiestocreateadirect
video–connected station.
• USB zero client–connected stations USBzeroclient–
connectedstationsusetheUSBzeroclientasastationUSBhub
(alsoreferredtoasamultifunction USB hub with video).These
stations connect to the Windows MultiPoint Server 2012 instance
throughaUSBcableandtypicallysupportavideomonitor,a
mouse,akeyboard(PS/2orUSB),audio,andadditionalUSB
devices.
• USB-over-Ethernet zero client–connected stations USB-
over-EthernetzeroclientsareavariationofUSBzeroclient–
connectedstationsthatsendUSBoverLANtotheWindows
MultiPointServer2012instance.Theseclientsfunctionsimilarly
toUSBzeroclient–connectedstationsbutarenotlimitedbyUSB
cablelengthmaximums.USB-over-Ethernetzeroclientsarenot
traditionalthinclients,andtheyappearasvirtualUSBdeviceson
the Windows MultiPoint Server 2012 system.
• RDP-over-LAN–connected stations Thesestationsinclude
traditionalthinclientsorotherdevicesrunningafulloperating
systemthatsupportRDP.
Additional resources:
• “DeployingWindowsMultiPointServer2012”athttp://technet.
microsoft.com/en-us/library/jj916399.aspx
• “PlanningaWindowsMultiPointServer2012Deployment”at
/>• “DifferencesbetweenProductVersions:Standardversus
Premium” at />jj916405.aspx
• “MultiPoint Server Stations” at />us/library/jj916411.aspx
NOTE
Personally owned devices

canonlyuseRDP-over-
LANconnectedstation
types. Institution-
owned devices can use
any stationed type as
applicable.
15VIRTUAL DESKTOP INFRASTRUCTURE
Preparing the infrastructure for VDI
BeforeyoudeployVDIinyourinstitution,youmustpreparetheappropriateinfrastructure.Table4
liststheVDIinfrastructurecomponentsandprovidesanoverviewofthepreparationthatmaybe
necessary for each component. In some instances, no infrastructure remediation may be necessary.
TABLE 4 VDIInfrastructureComponentsandPreparationSteps
Component preparation StepS
Network Thefollowingfactorsaffectwhetherthenetworkinfrastructureisableto
supporttheVDIsessiontrafcbetweenVDIclientsandtheVDIservers:
• PlacementoftheVDIserverscandirectlyaffecttheavailablenetwork
requirements(asdescribedinthesection“PlacingVDIservers”onpage
17).
• ThelargerthenumberofVDIclientssimultaneouslyaccessingtheVDI
infrastructure,thegreaterthenetworkbandwidththatisrequired.
• Typeofclienttrafc—forexample,graphicallyintensiveVDIsessionsrequire
morenetworkbandwidththanlessgraphicallyintensivesessions.
Storage Theprimaryconsiderationforplanningstorageare:
• Pooledcollectionsrequiresufcientstorageforthetransitionalharddisks
andtheUserProleDiskforeachVDIsession.
• PersonalcollectionsrequiresufcientstorageforeachVHDforeachVDI
session.
16VIRTUAL DESKTOP INFRASTRUCTURE
Component preparation StepS
Client devices EachuserwhoaccessestheVDIinfrastructurerequiresadevicethatsupports

theappropriateclients.Userswhowillaccess:
• VM-orsession-baseddesktopdeploymentscenariosrequiredevicesthat
supportRDPorRemoteFX
• WindowsMultiPointServer2012requireoneofthesupportedWindows
MultiPoint Server 2012 stations
Someofthesedevicescanbesoftware-basedclients(suchastheRemote
DesktopClientinWindowsoperatingsystemsorappsforotheroperating
systems)orhardware-basedclients(suchasRemoteFXdevices,thinclients,or
zeroclients).
FormoreinformationabouttheclientdevicesthatcanbeusedintheseVDI
solutions,seethefollowingsectionsinthisguide:
• “WindowsMultiPointServer2012”onpage13
• “ConnectinguserstoVDIsessions”onpage25
YoucanapproximatetheactualrequirementsforeachcomponentinTable4onpage15 by
verifyingtheresourcerequirementsinalabenvironment.Forexample,youcouldapproximatethe
networkbandwidthrequirementbyconguringatestenvironmentandmeasuringthenetwork
trafcalimitednumberofVDIsessionsperformingtypicaltasksgenerate.Then,youcould
extrapolatetheactualrequirementbymultiplyingthemeasurednetworktrafcinthelabbythe
numberofsimultaneousVDIsessions.
17VIRTUAL DESKTOP INFRASTRUCTURE
Placing VDI servers
Table5comparesthecentralizedanddecentralizedplacementstrategiesforVDIservers.Youcan
useanycombinationofthesestrategiestoplaceyourVDIservers.
TABLE 5 ComparisonofCentralizedandDecentralizedPlacementofVDIServers
Centralized deCentralized
Scenario CentralizedITdatacenter. Placement in classrooms, labs, or near
VDIclientlocations.
Management Requireslesseffortbecausethereare
fewerserverstomanage.
Requiresmoreeffortbecausethere

aremoreserverstomanage.
High availability HigherconcentrationofuserVDI
sessionsmakesimplementinghigh-
availabilitytechnologies(suchas
loadbalancingorWindowsfailover
clustering)morecost-effective.
LowerconcentrationofuserVDI
sessionsmakesimplementinghigh-
availabilitytechnologieslesseffective.
Scaling HigherconcentrationofuserVDI
sessionscanoffsetthecostsrequired
forscaling.Youcanaddserversor
systemresourcestoincreasescaling
capability.
LowerconcentrationofuserVDI
sessions may not be able to offset
costsrequiredforscaling.For
example,addingaservertoa
classroomwithanexistingserver
would effectively double the costs.
Efcient use of system
resources
UserVDIsessionscanbedistributed
(loadbalanced)acrossmultiple
servers, which results in the servers
beingmoreequallyutilized.
SomeVDIserversmaybe
underutilized, while others are
overutilized, with no way to share
resourcesamongservers.

Network trafc Higheravailablenetworkbandwidth
isrequiredontheinstitution’s
networkbackbonetosupportVDI
sessions.
Trafcismorelocalizedandhasless
impactontheinstitution’snetwork
backbone.
18VIRTUAL DESKTOP INFRASTRUCTURE
Building virtual desktop templates
VDIVM-baseddesktopdeploymentscenariosrequireavirtual desktop template. A virtual desktop
templatehasallthenormalsettingsofaVM(suchasmemory,networking,andVHDsettings).
WhenanewuserconnectstotheVDI,theVDIcreatesavirtualdesktopVMbasedonthevirtual
desktop template.
Tocreateyourvirtualdesktoptemplate,useHyperVManagerwiththerecommendationslistedin
Table6.
TABLE 6 VirtualDesktopTemplateCongurationSettingRecommendations
Set ting deSCription
Memory Dependingontheappsyouruserswillberunning,youmayneedtoincrease
thisvalue.Measurethememoryusersrequirebydeterminingthememory
consumedonaphysicaldevicewhilerunningtheapps.Youcancongure
the virtual desktop template to use static or dynamic memory. Microsoft
recommendsthatyoucongurethevirtualdesktoptemplatetouseatleast
1,024 MB.
Network Congurethevirtualnetworkadaptertoconnectto:
• AvirtualswitchinHyperVontheRemoteDesktopVirtualizationHost.The
HyperVvirtualswitchmustconnecttoyourinstitution’sintranetsothatthe
VDIsessionscanconnecttoresourcesonyourintranetandtheInternet.
• Thedomainspeciedduringthecongurationprocess.Thisisrequired
because the instances of the VM template are automatically joined to the
domain when they are created.

VHDs OnlyoneVHDissupported.TheVHD:
• MustcontainaWindows8.1imagethatyouhaveconguredtoa
generalizedstatebyusingtheWindowsSystemPreparationTool(Sysprep)
• Canbeconguredasadifferencingdisk
• CancontainmorethanonepartitionbutonlyoneWindowsoperating
systemimage
Snapshots Thevirtualdesktoptemplatecanhaveoneormoresnapshotsbutthecurrent
(Now)stateofthevirtualdesktoptemplate.Thisallowsyoutomanagethe
templatemoreefciently.Youcantakesnapshotofthetemplatejustpriorto
runningSysprepsothatitiseasytorestorethetemplatetoabeginningstate,
changetheconguration,takeanothersnapshot,andthenrunSysprepagain
on the updated version of the template.
19VIRTUAL DESKTOP INFRASTRUCTURE
RemoteDesktopServicesexportsthevirtualdesktoptemplateduring
thevirtualdesktopcollectioncreationprocess.Theexportprocess
createsacopyofthevirtualdesktoptemplate,includingallofthe
congurationsettingsmadeinTable6onpage18.Thisallowsyou
managethevirtualdesktoptemplatewhileusersareconnectedto
theirVDIsessions.
Additional resources:
• “SingleImageManagementforVirtualDesktopCollections
in Windows Server 2012” at />archive/2012/10/29/single-image-management-for-virtual-
desktop-collections-in-windows-server-2012.aspx
• “TestLabGuide:ManagedPooledVirtualDesktopCollections”
at />• “TestLabGuide:UnmanagedPooledVirtualDesktop
Collections” at />hh831618.aspx
• “SettingupanewRemoteDesktopServicesdeployment
usingWindowsPowerShell”at />archive/2012/07/18/setting-up-a-new-remote-desktop-services-
deployment-using-windows-powershell.aspx
NOTE

Twoormorevirtual
desktop collections can
share the same virtual
desktop template.
20VIRTUAL DESKTOP INFRASTRUCTURE
Client licensing for VDI
MicrosoftlicensesclientaccesstoVDIsessionsthroughWindows
VirtualDesktopAccess(VDA).WindowsVDAisadevice-based
subscription that licenses Windows 8.1 for virtual desktops by access
device:
• Devices covered by Microsoft Software Assurance Virtual
desktopaccessrightsareabenetofSoftwareAssurance.
DevicescoveredunderSoftwareAssurancehaveaccesstoaVDI
desktopatnoadditionalcharge.
Table7listtheWindows8.1VDIlicensingoptionsbasedonthe
operatingsystemrunningonthedeviceusedasaVDIclient.
• Devices not covered by Software Assurance Thesedevices
(suchasthinclients)mustpurchaseaWindowsVDAlicensefor
eachdevicetoaccessaVDIdesktop,regardlessoftheoperating
systemrunningonthedevice.Thisincludespersonallyowned
devices.
Client oS vda liCenSe optionS
Windows 8.1 Pro WindowsVDAlicenseandfreeupgradeto
Windows 8.1 Enterprise included
Windows RT WindowsVDAlicenseincludedwhenthedevice
is associated with a primary device covered by
SoftwareAssurance(forexample,theprimarydevice
isrunningWindows8.1Enterpriseandiscoveredby
SoftwareAssurance)
Windows 7 WindowsVDAlicenseandfreeupgradeto

Windows 8.1 Enterprise
Windows Vista WindowsVDAlicenseincluded;licensedtouse
WindowsThinPCasanRDPandRemoteFXclienton
these devices
Windows XP WindowsVDAlicenseincluded;licensedtouse
WindowsThinPCasanRDPandRemoteFXclienton
these devices
Android MustpurchaseaWindowsVDAlicenseforeach
device
INFO
Thelicensinglistedin
this table applies only to
institution-owned devices.
All personally owned
devicesrequireaWindows
VDAsubscription.
TABLE 7 WindowsVDA
LicensingOptions
21VIRTUAL DESKTOP INFRASTRUCTURE
Client oS vda liCenSe optionS
iOS MustpurchaseaWindowsVDAlicenseforeach
device
Additional resources:
• “MicrosoftVDIandWindowsVDAFrequentlyAskedQuestions”atrosoft.
com/download/1/1/4/114A45DD-A1F7-4910-81FD-6CAF401077D0/Microsoft%20VDI%20
and%20VDA%20FAQ%20v3%200.pdf
• “VolumeLicensing—MicrosoftSoftwareAssurance“at />software-assurance/default.aspx
• “MicrosoftLicensingfortheConsumerizationofIT”at />about-licensing/briefs/consumerization-it.aspx
• “MicrosoftLicensingfortheConsumerizationofIT—AcademicLicensingScenarios”athttp://
www.microsoft.com/licensing/about-licensing/briefs/consumerization-it-academic.aspx

• “LicensingWindowsdesktopoperatingsystemforusewithvirtualmachines”athttp://
download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/
Licensing_Windows_Desktop_OS_for_Virtual_Machines.pdf
22VIRTUAL DESKTOP INFRASTRUCTURE
Using Volume Activation
YoumustprovideWindows8.1licenseactivationfortheVMsused
inVDIscenarios.ThefollowingisalistoftheMicrosoftVolume
ActivationtechnologiesavailableforWindows8.1andabrief
description of each:
• Active Directory-Based Activation (ADBA) ADBAisarole
servicethatallowsyoutouseADDStostoreactivationobjects,
whichcanfurthersimplifythetaskofmaintainingVolume
Activationservicesforanetwork.WithADBA,noadditionalhost
serverisneeded,andactivationrequestsareprocessedduring
computerstartup.ADBAworksonlyfordomain-joineddevices
runningWindows8.1.
• Key Management Service (KMS) TheKMSroleserviceallows
organizationstoactivatesystemswithintheirnetworkfroma
server on which a KMS host has been installed. With KMS, you
cancompleteactivationsonyourlocalnetwork,eliminating
the need for individual computers to connect to Microsoft for
productactivation.KMSdoesnotrequireadedicatedsystem,
and it can be cohosted on a system that provides other services.
By default, volume editions of Windows 8.1 connect to a system
thathoststheKMSservicetorequestactivation.Noactionis
requiredfromtheuser.
Table8liststheVolumeActivationtechnologiesandtheinformation
necessaryforselectingtheappropriatetechnologiesforyour
institution.Youcanuseanycombinationofthesetechnologiesto
designacompleteVolumeActivationsolution.

TABLE 8 VolumeActivationTechnologySelection
adba kmS
Domain joined Yes Yes
Devices must connect to the
network at least once every
180 days
Yes Yes
INFO
For information about
licensingtheclientsused
toaccessyourVDI,seethe
section “Clientlicensing
forVDI”onpage20.
NOTE
Althoughyoucanperform
Volume Activation by
usingMultipleActivation
Keys(MAKs),Microsoft
does not recommend
MAKsforVDIbecausethey
cannot be dynamically
applied to VMs based on
VDIdemands.UseADBA
or KMS, instead.
23VIRTUAL DESKTOP INFRASTRUCTURE
adba kmS
Supports Volume Activation
of Microsoft Ofce
Yes(Microsoft
Ofce2013only,

not Microsoft
Ofce365or
previous versions of
Ofce)
Yes
Requires Volume Activation
services in Windows
Server 2012 R2
Yes No
Microsoft Volume Licensing
information is stored in
AD DS
Yes No
Infrastructure ADDS
ADDS
KMS server
ADBAandKMSarebothroleservicesintheVolumeActivation
Services server role in Windows Server 2012 R2. KMS is also available
inpriorversionsofWindowsServer.YoucanuseServerManager
orWindowsPowerShellcmdletstoinstallandconguretheserole
services.
YoucancentrallymanageWindows,Ofce,andotherMicrosoft
products’volumeandretailactivationprocessesbyusingtheVolume
ActivationManagementTool(VAMT),whichisincludedinthe
WindowsAssessmentandDeploymentKit.
NOTE
Youcanusethesame
Volume Activation
infrastructuretomanage
VDIactivationand

activation for your other
Windows 8.1, Windows 7,
Windows Server 2012
R2, and Windows
Server2008R2operating
systems.