Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

VDI in Windows Server 2012


Published on

More info on

  • Be the first to comment

  • Be the first to like this

VDI in Windows Server 2012

  1. 1. Separating the desktop computinglayersMicrosoft delivers a broad range of desktop virtualization offerings to • Folder Redirectionaddress your unique business and IT challengesProfiles • Roaming Data & User Settings • User Experience Virtualization (UE-V) • Profile disks • Application Virtualization (App-V) Applications • RemoteApp Operating • Virtual Desktop Infrastructure System • Remote Desktop Services session- based desktops
  2. 2. Embracing BYOD/COIT Virtual Desktop Hosted Infrastructure Applications (VDI) (RemoteApp) Office 365 BENEFITS Powered by Remote Desktop Services (RDS) • Secure, fast browsing • Rich user experience; FIREWALL • Touch enabled with Windows 8 devices WINDOWS 8 ADVANCEMENTS • Centralized management • High fidelity RemoteFX experience on of app & data (IT) LAN / WAN • Multi-touch support for modern • Enhanced security applications and devices and compliance (IT) • Support for local USB, Lync, etc. • Great choice of Windows- based devices
  3. 3. Your computer IS your tool for work Your computer CONTAINS your tool for work
  4. 4. …. To this From this….Well its really asquare…..
  5. 5. Benefits of Microsoft VDIRich experience Best value for virtual Efficient managementeverywhere desktops Rich multimedia Fairshare Simplified wizard experiences True USB and multi-touch In-box management User disks remoting console Consistently rich Lower-cost storage Intelligently patching performance
  6. 6. Windows Server 2012 RDS Architectural Components SMB, SANs, or direct attached local storage
  7. 7. High availability for all RDS rolesNew in Windows Server Web farm Remote Remote Desktop Remote Desktop2012 Remote Desktop Connection Desktop Remote Desktop Virtualization Host Remote Desktop Virtualization Host Connection Broker Virtualization Host Connection • Active/active high availability Broker Broker Remote Desktop mode for brokers Remote Desktop Web Access Remote Desktop Web Access Remote Hyper-V Web Access Desktop cluster • Scale-out File Server and Connection Broker resiliency SQL Server Clustering Databas Remote Desktop e Remote Desktop Session Host • Requires Microsoft SQL Remote Desktop Session Host Session Host Server Remote Remote Desktop • Automatic data migration Remote Desktop Gateway Desktop Gateway from single instance to high Gateway Remote Remote Desktop Remote Desktop Session Host farm Web farm availability Remote Desktop Licensing Desktop Licensing Licensing Cluster
  8. 8. Configuring RD Connection Broker forhigh availability RD Virtualization Host Remote Desktop Connection Broker 01 Hyper-V clusterRD Client DNS Remote SQL Server Cluster Desktop Connection RD Broker 02 Gateway RD Gateway Farm Remote Remote Desktop Desktop Connection Session Host Broker 03 RD Session Host Farm HA Central Certificate Store
  9. 9. High Availability - RD ConnectionBroker configuration prerequisites• SQL Server (at least SQL Server 2008 R2) for connection broker servers to use• SQL server configured with full permissions granted to connection broker servers• Windows firewall on SQL server configured to “Allow SQL Server Access” from connection brokers• Network folder to store SQL database files (can be created on SQL server computer)• SQL client installed on connection brokers• Static IP addresses configured on the connection broker servers.• DNS “A” resource records for each of the static IP addresses that point to the same, shared name (enables DNS round robin)
  10. 10. HA Configuration BrokerConfiguration• Starting point for enabling HA is to configure a single RD connection broker for either virtual machine or session-based deployment• In Server Manager, configure RD connection broker for high availability• Enter SQL connection string, database folder, and DNS round- robin name
  11. 11. HA RD connection broker results• Local connection broker data migrated to SQL and the connection broker will start using SQL for data immediately• In Server Manager, the option to add additional connection broker servers to is enabled • If the connection broker role service is not already added to server, it will be added automatically• RD connection brokers use SQL to store data• The RD virtual host, session host and Web access (end nodes) are configured with all the RD connection broker server names • Will choose a connection broker name at random to connect to• RDP clients use the DNS round-robin name• If any RD connection broker loses connection to SQL, all connected end nodes immediately disconnected and will try to establish connection with other connection brokers
  12. 12. Virtual desktop deployment choices Desktop Pooled Personal Sessions VMs VMs Corporate Office Branch Office 1 platform • 1 experience • 3 deployment choices FIREWALL Home Library / Coffee house
  13. 13. Session Virtualization Requirements• The computer must be a member of a domain• The RD Connection Broker role service cannot be installed on the same computer as Active Directory Domain Services• Administrator must belong to the local administrators security group• A network share configured for storing user profile disks is required • All RD Virtualization Host computer accounts must have the ability to read and write to this location
  14. 14. VDI Infrastructure Requirements• The server must have hardware-assisted virtualization• The computer must be domain-joined• The RD Connection Broker role service cannot be installed on the same computer as Active Directory Domain Services• Administrator must belong to the local administrators security group• A network share configured for storing user profile disks is required • All RD Virtualization Host computer accounts must have the ability to read and write to this location• VDI Quick Start • The virtual desktop template (a virtual hard disk) • Must be generalized by using Sysprep (Virtual Machine Mode), and then shut down • A virtual switch must NOT be created on the server running Hyper-V (the Quick Start deployment type creates one)• VDI standard deployment • The virtual desktop template must • Have the correct virtual switch selected • Be generalized using Sysprep (Virtual Machine Mode), and then shut down
  15. 15. Desktop virtualization (VDI)deployment modes• Desktop Virtualization (VDI) • Standard • Installs appropriate roles on separate computers • Quick Start • Installs the RD Connection Broker and RD Web Access role services on a single computer • Creates a pooled virtual desktop collection with two pooled virtual desktops based on a virtual hard disk that’s the virtual desktop template • Creates a Hyper-V network switch named RDS Virtual
  16. 16. Standard Deployment a - VDI b - Session
  17. 17. Standard Deployment (cont.)
  18. 18. Standard Deployment (cont.) a - VDI b - Session If compatibility check succeeds, deployment proceeds
  19. 19. Quick Start Deployment a - VDI b- Session
  20. 20. Quick Start Deployment (cont.) a - VDI b - Session [Need screen shot of virtual desktop template from a machine with hardware virtualization enabled]
  21. 21. Preparing the Master or Gold VM (Virtual DesktopTemplate)a desktop virtual machine on the Hyper-V server• Configure • Snapshots ARE supported for the template VM • The VDI creation process will use the currently active (“Now”) snapshot • If static memory is configured, the minimum amount is 1024 MBs; if dynamic memory is configured, the maximum memory must be at least 1024 MBs • If using the standard deployment model, the master VM must be connected to a virtual switch that can communicate with a domain controller • Note: Quick Start creates a virtual switch• Install the operating system and any applications that need to be included in the template VM • OS must be at least Windows 7 with SP1 or Windows 8 • Installed in a workgroup • VMs are automatically joined to the domain specified in the VDI wizard• Apply any patches or updates to the VM as required• Make any other configuration changes as required • For example, you can create a customized default profile. Note that this would require you to use Sysprep and an unattend.xml file with the CopyProfile setting set to TRUE in the specialize phase of Windows setup • In this case, you must generalize the image and then run through Out-of-the-box experience (OOBE) set up again before the final preparation of the image• In the virtual machine run the following command from WindowsSystem32Sysprep directory: • Sysprep /oobe /generalize /mode: vm
  22. 22. Choosing the Right VDI Architecture
  23. 23. Detail: Personal vs. Pooled VMs
  24. 24. Virtual Desktop Collections with UserProfile Disks • Created in Remote Desktop Services tool of Server Manager* • 2 types of collections • Personal desktop • Update with WSUS • Shared (“pooled”) desktop • Update automatically using a VDI template • Connect to a collection with Internet Explorer https://<FQDN of server>/RDWeb*Session collections can also be created
  25. 25. Personalization with User Profile Disk• Benefits What should I deploy?• Available with pooled virtual • User profile disk with every machine collections and RDSH virtual machine pool and collections RDSH collection• Stores all user settings and data • UEV to roam settings across• Container for: collections • Roaming User Profile • FR to roam user data across • Folder Redirection cache collections • User Environment Virtualization • FR to centralize user data• Roams with user within backup collection• Appears as local disk, improves app compatibility
  26. 26. RemoteFX over LAN or WAN RemoteFX delivers a consistently rich user experience to users over LAN or WAN (regardless of deployment model) Hardware and software GPUs Rich multimedia Corporate LAN USB redirection Internet or WAN Multitouch WAN acceleration Single sign-on
  27. 27. RemoteFX – Improved UserExperience• Enables the delivery of a full Windows user experience to a range of client devices • Improved WAN performance • Multitouch support • Includes rich clients, thin clients, and • Configured through Group Policy ultrathin clients• Delivers a rich user experience for: • Virtual Desktop Infrastructure (VDI) • Provides a 3D virtual adapter, intelligent codecs, and the ability to redirect USB devices in virtual machines • Session-based desktops and RemoteApp programs to a broad range of client devices• Integrates with the RDP protocol • Enables shared encryption, authentication, management, and device support
  28. 28. Windows 8 RemoteFX Improved User ExperienceUnifying of the remoting experience • All features of RDP are available to both sessions and VMsWAN Improvements • Progressive download, H.264 encoding for video compression, and UDP as needed to reduce networking overheadSimplified connection • Users can connect to their personal collection of VMs and RemoteApp programs assigned to them by logging in with their email address and passwordImproved user personalization • User profile disks allow users to preserve user personalization settings across session collections and pooled virtual desktop collectionsMore integrated local and remote experience • Remoting of a broad range of USB devices (such as an all-in-one printer, a scanner, a biometric reader, a webcam, or a VoIP headset)
  29. 29. Windows 8 RemoteFX Improved User Experience, cont.Support for multi-touch and gesture remotingSimpler logins • Single sign-on for Remote App programs extended to include VMs assigned to a userEvenly distributed allocation of resources to everyone on a RD SessionHost server • No single user can consume all resourcesConcurrent reconnection • You can disconnect, go home, and then reconnect to the RemoteApp programs and VMs that you were using all at once, saving time as you restore your work environment
  30. 30. RemoteFX adaptive graphics Text Content Image Content Video/Animations
  31. 31. RemoteFX progressive rendering
  32. 32. Fair Share Dynamically distribute resources (bandwidth, CPU, and I/O)Help ensure high performanceacross user virtual machines Apply to both sessions andand sessions virtual machines
  33. 33. VDI Licensing componentsTwo main components: • License for connecting to the VDI Infrastructure: RDS CAL • For any solution using any of the Remote Desktop or RemoteFX services, including Citrix XenDesktop, Citrix XenApp, etc. • RDS CAL licensed per user or per device • Includes rights to use App-V with Remote Desktop sessions • License to access a virtual instance of a Windows Client OS: • Software Assurance (SA) • Virtual Desktop Access (VDA) • Windows Intune • Companion Subscription License (CSL)A license to access a virtualized instance of a client OS is always required • The circumstances and context determine what kind of license (SA, VDA, CSL, etc) is required
  34. 34. Software Assurance VDI Benefits• Access to Windows 8 Enterprise edition• Access rights for up to 4 VMs concurrently (local or remote)• Roaming Rights for access from non-corporate device• Access to Windows Thin PC for free• Option to purchase MDOP• 24*7 support, training vouchers and other benefits
  35. 35. VDA (Virtual Desktop Access)• Rights to access virtual copies of Windows via devices that don’t qualify for SA: • Thin Clients • Consumer Devices (e.g. iPads) • Third party devices (contractor PCs) • PCs not covered by SA• Licensed Per Device• Annual Subscription
  36. 36. Companion Subscription License• Optional add-on for primary user of SA or VDA licensed devices• Is for companion (non-primary) devices• Single license covers up to 4 additional devices• Eligible for any personally owned and/or non-x86 corp-owned devices anywhere (on/off-prem)• Includes Windows To Go and VDA rights• No local install rights• Offered in EA, EA subscription, Select Plus, and EES/CASA programs• No companywide commitment required and can be purchased in any quantity• Included with any Windows RT device
  37. 37. Licensing Windows SA, VDA, and CSL Primary work device? Primary User of (regardless of ownership No Yes Corp owned? No On Premises? and location) SA/VDA licensed device? No Yes No Yes Yes Windows RT Any Device Other x86/x64 PC Other x86/x64 PC (No License Required (Roaming Rights: No (Thin Client, iOS, (w/ Qualifying OS) (iOS, Android, etc)(w/ Qualifying OS) for VDI) License Required) Windows RT) VDA CSL SA
  38. 38. V-Alliance: Microsoft and Citrix Jointly Integrated, Unified Management User State Virtualization Application Virtualization OS Virtualization
  39. 39. Why Citrix for desktop virtualization?Work anywhere, made anywhereIf you need…• a mix of Windows Server 2003, 2008, 2008 R2 & 2012• a mix of Windows XP, Windows 7 & Windows 8 virtual desktops• a mix of Windows & non-Windows user devices• a mix of private, service provider and hybrid desktop infrastructures• a mix of use cases (e.g. VDI, streamed OS, remote, offline, 3D, apps…)• to scale hosted desktop, sessions, apps from hundreds to many thousands of end-points• to support heterogeneous hypervisors in the datacenter …then you need enterprise class desktop virtualization from Citrix
  40. 40. Summary VDI Simplified Citrix Improved High Partnership Availability RDS RemoteFX Improved Enhanced