Upload
navid
View
37
Download
3
Tags:
Embed Size (px)
DESCRIPTION
Planning, Deploying and Managing a Microsoft VDI Infrastructure Level 300 - Advanced. Who Am I ? Nicola Ferrini. Trainer Technical Writer Systems Engineer Server & Application Virtualization Technology Specialist Most Valuable Porfessiona ( MVP) Technet Speaker - PowerPoint PPT Presentation
Citation preview
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Planning, Deploying and Managing a Microsoft VDI
Infrastructure
Level 300 - Advanced
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Who Am I ? Nicola FerriniTrainerTechnical WriterSystems EngineerServer & Application Virtualization Technology SpecialistMost Valuable Porfessiona (MVP)Technet SpeakerMicrosoft System Center InfluencerSTEP Program MemberMore on:
http://www.nicolaferrini.it/ita/competenze.htmlhttp://www.windowserver.it/ChiSiamo/Staff/tabid/71/Default.aspx
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
AgendaIntroductionDesktop virtualization solutions
Local Desktop VirtualizationCentralized Desktop VirtualizationSession Virtualization
Remote Desktop Session HostRemote Desktop Virtualization HostVDI Virtual Desktop Models
Personal Virtual DesktopPooled Virtual Desktops
VDI Design ConsiderationsChallengesQ&A!
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Management
Virtualization Solutions
Profile VirtualizationDocument redirectionOffline files
Presentation Virtualization
Desktop Virtualization Application Virtualization
Server Virtualization
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
The Different Desktop Options
Local Hosted
PC Laptop VMs Sessions
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Hosted Desktops – Server Side
RDP
Remote DesktopSession Host
OS
Hardware
Sessions
Virtualized RDSession Hosts
PersonalVirtual Desktops
Hypervisor
Hardware
Hypervisor
Hardware
PooledVirtual Desktops
Datacenter
VDIRDS
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Hosted Desktops – Client Side
DesktopHosting Server
Remote DesktopClient
RemotingProtocol
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Microsoft Virtual Desktops Suite
Remote DesktopVirtualization Host
Remote DesktopSession Host
Remote Desktop Protocol
Home
Mobile
Office
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Why Remote/Virtual Desktops?
Contractors/Offshoring
Work fromHome
CentralizedDesktop
DevelopersMergers andAcquisitions
RemoteAdmin Access
ApplicationCompatibility
EnhancedAgility
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
What Is RDS?RDS is presentation virtualization technology that provides access to session-based desktops, virtual machine–based desktops, and applications
RDS provides the following benefits:
• Run an application or an entire desktop on centralized servers• Manage session-based desktops, applications, or virtual
machine–based desktops on centralized servers• Provide an entire desktop, or just application window• Provide integration of local and RemoteApp programs• Enable secure remote access without establishing a VPN
connection• Centrally control which RD Session hosts can be accessed, who
can access them, and device redirection
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Remote Desktop Session Host
HTTPs
SSL
WS 2008 R2RDSH
RDConnection
Broker
RDPClient
RDGateway
RD WebAccess
Active Directory& Network
Policy ServerAuthorizationPolicies
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Client Experience Features with RDSThe following enhancements are available to Remote Desktop users in Windows Server 2008 R2:
Windows media redirection
True multimonitor support
Audio input and recording
Improved audio and video
synchronization Enhanced bitmap
redirection Aero Glass support
Language bar redirection Task scheduler
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
What is Virtual Desktop Infrastructure?
Virtual Desktop Infrastructure (VDI) is a key technology for enabling successful desktop virtualization implementations – in all organizations, for network connected users. As a deployment model, VDI allows these users to access their personal desktops in the datacenter.
Desktops, Applications, User Data
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Access Points(PC, Thin clients)
Servers Storage
Virtualization Platform
ManagementApplication Delivery
User State Virtualization
Desktop Delivery
VDI Components
Hardware Layer
VDI Offering
Access Points
Network
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Remote Desktop Virtualization Host
HTTP
RD ConnectionBroker
RD WebAccess
RDSHRedirection
Mode
RDP
ADDomainService
RD Virtualization Host
RDP
RDPClient
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Benefits of Virtual Desktop Infrastructure
VDI is a centralized desktop delivery architecture, which allows you to centralize the storage, execution, and management of Windows desktops
Benefits of VDI:
• Provides access to data and applications from any device• Improves data security and compliance • Simplifies management and deployment of applications• Improves business continuity • Integrates management of physical, virtual, and session-
based desktops• Centralizes data storage and backup
Key deployment scenarios of VDI are persistent virtual machines and pooled virtual machines
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Desktop Virtualization SolutionsLocal Desktop Virtualization
Provide virtualization at the local physical desktopRequires rich client operating systemUses local resourcesOffline solution
Centralized Desktop VirtualizationProvide virtualization from the data centerData is centrally stored and protectedUpdate challengesMultiple operating system support available to meet needs
Session VirtualizationProvide virtualization from the data centerEasier to configure and manageRemote desktop or remote applicationSingle (shared) operating system instance
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
VDI Virtual Desktop Models
Personal Virtual DesktopOne-to-one mapping between a user and a virtual machineModel requires the creation of a virtual desktop for each userUsers can perform specialized tasks that require administrator access to their desktopUsers can access their personalized desktop from any computer while retaining the last saved state (persistent configuration)Application streaming and application hosting support with App-V and RemoteAppBest for Knowledge Workers (software developers, testers, and so on)
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
VDI Virtual Desktop Models
Virtual Desktop PoolOne-to-many mapping between a virtual machine and usersModel requires a master VHD image that is duplicated or difference-based as needed to support user workloadUsers can perform standardized routine tasks and have access to common applications (such as Microsoft Office)Configuration state rolls back at logoff to provide a “clean” desktop for the next user’s session, but previous user’s state can be saved offlineApplication streaming and application hosting support with App-V and RemoteAppAnalysis suggested to determine if session-based desktop is more efficientBest for Task or Office Workers (CRM, ERP, and similar users)
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Virtual Desktop Pool Considerations
Identical Virtual Machine ConfigurationOperating systemApplications
ManagementVHD duplication and storageSingle image update
Windows Client Operating SystemsDoes not support Windows Server operating systemsDoes not support 3rd party operating systems
Single Pool MembershipVirtual machines are restricted to membership in a single virtual desktop pool
User Data Non-PersistentData saved by user in a VM may not be accessible after log offUsers may be connected to different virtual machine at next log on
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
How Virtual Desktop Infrastructure Works
A user can connect to a virtual machined based on the VDI configured for:
Personal virtual desktops
1. A user initiates the connection to the personal virtual desktop
2. The user sends the request to the RD Session Host server running in redirection mode
3. The RD Session Host server forwards the request to the RD Connection Broker server
4. The RD Connection Broker server queries AD DS and retrieves the name of the virtual machine that is assigned to the requesting user account
5. The RD Connection Broker server sends a request to the RD Virtualization Host server to start the virtual machine
6. The RD Virtualization Host server returns the IP address of the FQDN to the RD Connection Broker server
7. The RD Session Host server redirects the request to the client computer that initiated the connection
8. The client computer connects to the personal virtual desktop
Pooled virtual desktops
1. A user initiates the connection to the virtual desktop pool 2. The user sends the request to the RD Session Host server
running in redirection mode3. The RD Session Host server redirects the request to the RD
Connection Broker server4. The RD Connection Broker server verifies whether any existing
session exists for the requesting user account5. The RD Session Host server redirects the request to the client
computer that initiated the connection6. The client computer connects to the virtual desktop pool
A user can connect to a virtual machined based on the VDI configured for:
Personal virtual desktops
Pooled virtual desktops
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Virtual Machines for Virtual DesktopRD Virtualization Host can assign each user a unique virtual machine, a personal virtual desktop, or can redirect users to a shared virtual machine pool, where a virtual machine is dynamically assigned
After installing a virtual machine, you must configure the following to work with RDS:
1. Join the virtual machine to a domain2. Enable Remote Desktop3. Add user accounts to the local Remote Desktop Users security group4. Allow RPC5. Create a firewall exception to allow Remote Services Management6. Add permissions to RDP
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Core VDI ComponentsWindows Server 2008 R2 Hyper-V
Supports the creation, isolation, and execution of virtual desktopsProvides the assignment and control of system resourcesEnables implementation of high-availability and fault-tolerance functionality
Active Directory Domain Services (ADDS)Stores the access rights mapping between users and virtual desktops
Remote Desktop Session Host (RDSH)Executes in redirection mode to disallow interactive user sessionsCommunicates with RD Connection Broker to obtain VM IP address and redirect RDP client to connect to the VMSecurely redirects a user RDP connection to an identified VM
Remote Desktop Connection Broker (RD Connection Broker)Identifies a VM for a user to make an RDP connectionCommunicates with RDVH to prepare VM for RDP connection, start a VM from saved stateManages sessions to redirect users to existing VMs
Remote Desktop Virtualization Host (RDVH)Executes on Hyper-V hosts to serve requests for virtual desktops running in VMsPrepares VMs for RDP connection based on request from RD Connection BrokerMonitors VM sessions and relays session information to RD Connection Broker
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Other VDI ComponentsRemoteApp
Enables abstraction of applications from virtual desktop imageIntegrates into virtual desktop for seamless access to applications running on RDSHEnables applications to present on virtual desktop in their own resizable windowSolution for applications that are incompatible with virtual desktop operating system
Application Virtualization (App-V)Enables abstraction of applications from virtual desktop imageProvides streamed delivery and isolated execution of applications on virtual desktopsRequires an App-V client on the virtual desktopSolution to run multiple versions of applications or incompatible applications simultaneously
System Center Virtual Machine Manager (VMM)Provides a single, integrated console to manage physical Hyper-V hosts and VMsProvides functionality to automatically provision virtual desktopsProvides functionality to deploy VMs to most suitable Hyper-V host
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
VDI Design ConsiderationsDeployment Scale
Enterprise, multiple locations, departmentalFor large scale deployment, consider Citrix XenDesktop Solution with Hyper-V
User CategorizationIdentify user categories, connection, and desktop permissions requirementsDefine with respect to personal or pooled virtual desktops, and session-based options
Client Operating SystemsVDI architecture dependent on performance and available features of client operating system
ApplicationsDefine application set, characteristics, execution, and delivery requirementsIdentify application delivery and presentation restrictions
Virtual Desktop Image Thin: dynamically assembled virtual desktop (user state and application virtualization)Rich: static virtual desktop (local user state and applications)Hybrid: some base applications with user state and application virtualization
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
VDI Design ConsiderationsClient Devices
Thin client devices (terminals, and so on)Rich client devices (PCs, laptops, and so on)
ConnectivityIdentify connection requirements (LAN, WAN, Dial-up, ISP)Identify encryption requirements
StorageIdentify storage requirements for user state and dataIdentify storage requirements for virtual desktop VMs
SecurityIdentify groups, departments, locations that require higher security levelsIdentify infrastructure impact based on additional instance requirements
High-AvailabilityIdentify virtual desktops that must be highly availableIdentify high-availability solutions for VDI infrastructure servers, networks, and storage
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Major ChallengesUser Density
Application Performance
User-Mode Resource Isolation
Kernel-Mode Resource Isolation
Application Compatibility
Software Vendor Support
Availability of Skilled Staff
Network Bandwidth and Latency
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Additional ChallengesIndividual IP Addresses
Multiple Time Zones
Multiple Languages
Single Sign-on
App Self Assignment
Profile Management
License Management
Multiple Monitors
Web Integration
Access Control
Data Security
Load Balancing
Desktop Templates
Printers & Peripherals
Thin Client Integration
Resource Management
!
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Challenge – App Compatibility
Administrator
User
Registry: HKCU (User Profile – Admin)Registry: Shadow Keys – Write Global .ini Files (%WinDir%, \WINDOWS)Global Temp Files (%Temp%)Global API Calls (GetWindowsDirectory)
Registry: HKCU (User Profile – User)Registry: Shadow Keys – Read Adapted .ini Files (%WinDir%, \WINDOWS)Specific Temp Files (%Temp%)Specific API Calls (GetWindowsDirectory)
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Challenge – WAN
Remote Desktop Protocol
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Challenge – Application Publishing
Remote Desktop Protocol
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Questions and
Answers
Microsoft and Community Tour 2011 – Infrastrutture in evoluzione
Thank you!