planning, deploying and managing a microsoft vdi infrastructure (slides translated to english)
DESCRIPTION
Planning, deploying and managing a microsoft vdi infrastructure english slides English translation of my session at the italian community days 2011TRANSCRIPT
Planning, Deploying and Managing a Microsoft
VDI Infrastructure
Fabrizio VolpeMVP Directory Services
@Fabriziovlp
http://www.linkedin.com/in/fabriziov
Agenda
Virtual Desktop – Five ways to the virtual desktop
Microsoft VDI – Architecture
Microsoft VDI – Personal Vs Pooled Desktops
Windows Licensing for VDI
Microsoft VDI – Microsoft RemoteFX
Virtual Desktop – Five ways to the virtual desktop
Desktop Virtualization
Client - Local
1 Bare Metal 2 Hosted
Server Hosted - Remote
Execution
3 ‘Shared’
(RDS)Personal
4 Stateless (Pooled)
5 Steteful (Assigned
)
Virtual Desktop – Preliminary Evaluation
Applicazions
1) What applications are we using and how much they are important ?
2) Are they feasible to be used remotelly in the datacenter ? 3) Applicazione is compatible with a Terminal Server
environment ?
Other considerations
1) Will we use non-Windows clients ? 2) Applications will need data from the back-end ?
3) Should I start the application in a fast way from new devices ?
4) The application needs locally saved data ?
Virtual Desktop – Vendors
Virtual Desktop – Features Comparison
http://www.virtuall.eu/view-document-details/vdi-smackdown
Microsoft VDI – Architecture
Microsoft VDI – Architecture in Deep
Remote Desktop Web Access (RDWA) is the unified starting point
Remote Desktop Gateway (RDG) is an optional feature and we’ll use it on the network edge using Network Policy Server (NPS) and certificates to improve our security.
Microsoft VDI – Architecture in Deep
Remote Desktop Session Host (RDSH) holds applications and redirects to RDVH
Remote Desktop Virtualization Host (RDVH) is an Hyper-V server dedicated to virtual desktops
Remote Desktop Connection Broker (RDCB) gives informations about the right host to use for connection
Microsoft VDI – User Experience
Using Remote Desktop Connection Broker (RDCB) and Web Access (RDWA) we have a logon screen with the same look as the one for RemoteApp but with access to the two different kinds of virtual desktop
Pooled
Dedicated
Microsoft VDI – Personal Vs Pooled Desktops
Golden Image
User 1
User n
Day 2 Day n
Day 2 Day n
Day 1 Day 2 Day n
Clone
Personal Virtual Desktop:
Golden Image
1
n
User 1
Pool Day 1 Day 2 Day 3
Clone
User 1
User 1
Pooled Virtual Desktop: User Profiles
etc
Microsoft VDI – Personal Virtual Desktop
A single Virtual Machine VM hosted on a RD Virtualization Host server may be assigned to an Active Directory account to be used as a personal virtual desktop
The personal virtual desktop is used through RemoteApp and Desktop Connection or with RD Web Access
Microsoft VDI – Personal Desktop - Requirements
Active Directory forest schema minimum level Windows Server 2008
Domain functional level at least Windows 2000
Server native
The “Personal Virtual Desktop” tab requires
Windows Server 2008 R2 A.D.U.C
or Windows 7 with Remote Server
Administration Tools (RSAT)
The user and the computer must be both
members of an A.D. domain
A user is enabled to have only one virtual
desktop at a time
A virtual machine can be used as personal virtual
desktop for a single user at a time
The virtual machine name in Hyper-V Manager must match the computer FQDN
Connecting to a Personal Desktop
Connection starts with RD Web Access
or RemoteApp / Desktop Connection
RD Session Host server in redirection
mode redirects to the RD Connection
Broker
RD Connection Broker queries
Active Directory to match a virtual
machine name with the user
Connection Broker requires to the RD Virtualization Host to start the virtual
machine
RD Virtualization Host server gives the ip associated with the name to
the RD Connection Broker server
The RD Connection Broker forwards the information to the RD Session Host
RD Session Host forwards the above informations to the
client that now starts the connection
Client connects to the personal virtual
desktop
Connecting to a Personal Desktop
Microsoft VDI – Virtual Desktop Pools
A pool of virtual desktops is a group of virtual machines with identical
settings on a RD Virtualization Host
Users have access to the pool using RemoteApp or RD Web Access
We have identical virtual machines, so the users will have always the same working environment (if we have no
roaming profiles)
Microsoft VDI – Desktop Pools- Requirements
Virtua Machines in a pool of virtual desktops must be identical, including installed programs
A single virtual machine can be only in a given pool at a time
Using RD Web Access we’re able to create more than one virtual desktops poolThe user will have a different icon for every pool
User data must NOT be saved locally if we use virtual desktops in a pool
Connessione al Pool di Virtual Desktops
Connection starts with RD Web Access
or RemoteApp / Desktop Connection
RD Session Host server in redirection
mode redirects to the RD Connection
Broker
RD Connection Broker verifies if there is already a
session opened for the user
If there is already an active session, there is no need to start up a v.m. , else we go to the next step
Connection Broker requires to the RD Virtualization Host to start a virtual
machine
RD Virtualization Host server gives the ip associated with the name to
the RD Connection Broker server
The RD Connection Broker forwards the information to the RD Session Host
RD Session Host forwards the above informations to the
client that now starts the connection
Client connects to the personal virtual
desktop
Connecting to a Virtual Desktops pool
Windows Licensing for VDI
What is the license name?
Windows Virtual DesktopAccess (Windows VDA)
What is the scenario? Access to a virtual copy of Windowsclient OS (Windows 7, WindowsVista, Windows XP) in the datacenter
What devices can be covered?
Thin clients, non corporate PCs,devices that do not qualify forWindows Client SA
Is Microsoft Software Assurancea prerequisite?
No
What is the retail price? $100/year/device
Are there Software Assurance benefits?
Yes
What is the license type? Annual subscription
What is the licensing unit? Per accessing device
Windows Licensing Scenarios for VDI
http://download.microsoft.com/download/7/8/4/78480C7D-DC7E-492E-8567-F5DD5644774D/VDA_Brochure.pdf
Microsoft VDI – Microsoft RemoteFX
What’s
RemoteF
X
• Gives the “full” Windows experience to standard clients, thin clients, and ultrathin clients.
• Has a 3D virtual adapter, intelligent codecs, and redirection of ports and devices
RemoteFX is available on
• Windows Server 2008 R2 Standard with SP1• Windows Server 2008 R2 Enterprise with SP1• Windows Server 2008 R2 Datacenter with SP1• Microsoft Hyper-V Server 2008 R2 with Windows Server 2008 R2 SP1 update
RemoteFX on virtu
al desktop
• Windows 7 Enterprise with SP1• Windows 7 Ultimate with SP1
Microsoft VDI – RemoteFX features
• Graphic is elaborated on the host, not on the client
Host side rendering
• RemoteFX creates a graphic driver (Windows Display Driver Model ) and makes it available to the virtual desktop. More than one virtual desktop are enabled to share the single GPU on a single Hyper-V server
GPU Virtualization
• Evaluates the client – host network performances and regulates rendering and compression
• Identifies the modified zones on the screen
Intelligent Screen Capture
• Redirects USB ports from the client to the host (no device driver needed on the client side)
RemoteFX USB Redirection