TechInsight - Real World Implementation of VDI


Published on

Concept of VDI, Component and Capacity Planning for Remote Desktop Services and Citrix XenDesktop.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Session Summary: This session takes you through planning and deploying a Virtual Desktop Infrastructure solution. We will take a look at the considerations needed in sizing, networking, capacity, as well as the components and technologies needed to set things up. Last but not least, we will explore the TCO of VDI
  • Let go through our agenda today, As usual, I will talk about some introduction about VDI. Some of you may be first time heard about the concept of VDI.Then i will talk about the component and how it work using RDS and Citrix solution and lastly some tips and trick on VDI Capacity Planning.
  • Will Remote Desktop Session Host and Remote Desktop Virtualization Host kill Rich Clients?Did online banking and credit cards replace cash and wallets?Did public transport services replace individually owned vehicles?There’s a simple rule: Virtual Desktops are useful for all enterprises, but not for all users!Keep in mind:- “VDI fits for every customer but not for every desktop”
  • Moving on , Microsoft and Citrix has a strong partnership in VDI offering.Some of the key components of the Microsoft VDI offering are:First, on the Virtualization Platform. Microsoft has Hyper V R2. Hyper V R2 is a Hypervisor based virtualization system which allow you to virtualize Remote Desktop Services and Client operating system on a single physical machine. In R2, you can introduce Failover Cluster and Live Migration. Live migration allow you to migrate virtual machine from one node to another node without any interruption. User will not experience interruption when accessing to remote desktop.2. Next, on Desktop and Session Delivery. Last year November, Microsoft has launched Windows Server 2008 R2 which allow you to VDI with Remote Desktop Services. Desktop and application can make available to user by using RDS.3. Then on Application Delivery, Microsoft has Application Virtualization (in short form- called App-V) allow you to virtualize application and stream the application to the user desktop. For example, you have Microsoft Office 2010 and Office 2003. By using App-V, both application can run without any conflict. Meanwhile on R2, you can use RemoteApp to host application on the server and make it available to user. This is similar as terminal service.4. Moving on, on User profiles and data. Microsoft has Roaming profile feature in. Roaming profile is one of the features which allow you to have similar setting and desktop wallpaper when you access to desktop virtual machine. Folder redirection refer to automatic rerouting standard folder such as My Document, My Picture and Start Menu to a shared storage. By using folder redirection, you can introduce centralize data and backup.Lastly on Management side, Microsoft has System Center Management Suite.1. Systems Center Virtual Machine Manager 2008:VMM allow you manage physical and virtual machine infrastructure. You can use VMM to perform commissioning and decommissioning of virtual machine as well as to perform P2V (Physical to Virtual Machine conversion) . By using P2V, you can convert your existing physical desktop to virtual machine and store into data center.2. SCCM allow you to perform software update, software distribution, operating system deployment, asset management, hardware and software inventory.3. SCOM provide an end to end solution for monitoring. You can integrate with VMM to enable reporting and enable one of the feature called enable PRO TIP. PRO TIPS allow the system to react. Example: If physical host not enough RAM, PRO TIPS can move the host which has available system resources.Lastly, MDOP is available for Software Assurance and APP-V is part of MDOP.On Citrix technology, Danny will talk more about it later.---------------not important-----------------------------------Desktop delivery through Citrix Xen Desktop:Citrix XenDesktop™ offers a next-generation, user-centric desktop virtualization solution that provides a complete system for desktop delivery.  XenDesktop dynamically assembles virtual desktops on-demand, providing users a new, yet personalized, desktop each time they log on – ensuring that performance never degrades. In addition, XenDesktop’s high-speed delivery protocol provides unparalleled responsiveness over any network which helps in desktop optimization. Hence, in the WS08 R2 timeframe, we will have two options for implementing VDI:For large, complex enterprise deployments, the joint Microsoft and Citrix solution will continue to offer a superior set of features.For small scale departmental implementations, the Microsoft-only stack will provide the best balance of features and price.Organizations that are considering VDI today, are encouraged to deploy the current Microsoft-Citrix offering, as this will enable them to lay a foundation to grow their VDI infrastructure in the future.
  • Rich multimediaReal-time collaborationUSB plug-n-play3D graphics applicationsBest network performanceBranch office optimization
  • Now, let look into how RDS is working…
  • Instead of talking about RDS…let see RDS in action..
  • In a VDI architecture, users can be mapped either to a static, or “persistent” virtual desktop, or a dynamic (“non-persistent”) virtual desktop.In static mode, there is a one-to-one mapping of VMs to users. The more users you have, the more VMs you need. VMs are stored on a SAN or NAS and execute on the server. Static virtual desktops are a good fit for users who expect to find the exact same desktop environment upon login as they left it on the last logout. However, large numbers of static desktops lead to increased maintenance efforts and cost.In a dynamic architecture there is only one master image. Instead of having to manage many dedicated images, you support one image that is automatically replicated as needed for users. User applications are provisioned onto the VM either via Microsoft Presentation Virtualization (TS RemoteApp) or via Microsoft Application Virtualization (formerly known as SoftGrid) based on user profiles; the data are stored centrally on the server via Microsoft Profile Virtualization (folder re-direction). This makes it easier to manage the VMs and dynamically provision desktop environments, and it also helps reduce maintenance and support costs.In either scenario, virtual desktops are presented to any client device with a remote desktop client such as on a PC or a thin client.
  • Failover (live migration)Do you need HA for the guests? If not then do not implement Failover Clustering !Stand Alone node support up to 384 guestsWindows Failvoer Clustering scalability 1 host is dedicated as a failover host 15 nodes X 64 Guests = 960 Guests per cluster.Recommended VDI cluster size: 1000
  • SLAT is for processor support paging at the hardware level
  • he Microsoft team attributes this improved scalability to Windows 7 being a virtualization-aware operating system. Windows 7 includes several features which improve its performance in a virtualized environment. Windows 7 includes the Hyper-V Host Integration Services as part of the base operating system Windows 7 notifies the hypervisor when it is idle so the hypervisor does not schedule guest operations Windows 7 includes optimized device drivers for network and disk Windows 7 provides improved storage and optimized page file management
  • Network should not have more than 5 hops and latecy should be under 100ms.
  • Total Cost of Ownership is a holistic view of enterprise costs over time, and includesDirect CostsCAPEX – Hardware, SoftwareOPEX – Administration, Operations, FeesIndirect CostsEnd-User Operations
  • Presenters please use this slide to direct participants to websites, books, trials, product pages etc as a follow through to your presentation
  • In order to deploy VDI using RDS:-On the server side, You need to have Active Directory in place. You must extend the schema to Windows Server 2008 and domain function level should at least configure to Windows Server 2000 native mode.RD server roles and client operating system should join to domain environment.To install Remote Desktop Services, you must use Windows Server 2008 R2. On my previous slide I have explained about 5 different component of RDS: RD Connection Broker, RD Session Host, RD Gateway, RD Licensing and RD Web Access. You can virtualize all these roles except RD Virtualization Host. To secure access to the VDI infrastructure, it recommend to get 3rd party certificate or you can deploy Internal CA from Microsoft.On the client side, you can thin or rich client as long the client has IE 6 or later, Remote Desktop Connection client version 6.1 and most important is a reliable network connection.-----------------------------not important------------------------types of certificate existSelf signed certificate – no trusted by any client. For testing. Manually install certificate into client computerInternal CA – create by AD CA. Automatically trusted by client in the domain. Manually export & import certificate to client or use GPOExternal /Public CA – Issued & purchase by trusted public CA. Automatically trusted by client cause the trusted root certificate is automatically included in the OS
  • Static Virtual Desktop pool is depended on Active Directory. You need to extend the schema to Windows Server 2008 and domain functional level to Windows Server 2000 native mode.Example:- If you have upgrade the schema to Windows server 2008 and domain functional level has set to Windows 2000 native mode and you are running Windows Server 2003 domain controller. You will see this property page on your left.In order for you to see additional tab: Personal virtual desktop, you need to use Active Directory Users and Computer from Windows Server 2008 R2 or RSAT on Windows 7.
  • On VM naming, Static Virtual desktop need to name in FQDN format. You need to put exact computer name as similar inside the VM with . Domain name. For example: VDI01-Win7 is the computer is the domain name.
  • TechInsight - Real World Implementation of VDI

    1. 1.
    2. 2. A Real World Implementation of VDI<br />Lai Yoong Seng<br /><br />Consultant<br />Redynamics Asia SdnBhd<br />
    3. 3. Agenda<br />Introduction of VDI<br />How it works?<br />Demo:- Remote Desktop Services <br />Demo:- VDI using RDS<br />Demo:- VDI using Citrix with Microsoft Platform<br />VDI Capacity Planning<br />
    4. 4. What is Virtual Desktop Infrastructure (VDI)?<br />Virtual Desktop Infrastructure (or VDI) is an architectural model where a client OS runs in a server-based virtual machine environment and interacts with the user via a network connection.<br />The storage and execution of a desktop workload (OS, apps, data) is centralized on a virtual machine in the datacenter<br />Presentation of the UI is managed via a remote desktop protocol (such as RDP or ICA) to client devices<br />Desktop Workload<br />(OS, Apps, Data)<br />
    5. 5. Why Remote/Virtual Desktops?<br />Work from<br />Home<br />Centralized<br />Desktop<br />Mergers and<br />Acquisitions<br />Developers<br />Client OS <br />Migration<br />Contractors/<br />Offsite <br />worker<br />Remote<br />Admin Access<br />Application<br />Compatibility<br />
    6. 6. The Microsoft and Citrix VDI Technology Stack<br />Desktop and Session Delivery for Enterprise Deployments<br />Partner<br />Technology<br />XenDesktop 4<br />Roaming Profiles <br />Folder Redirection<br />User Profiles and Data<br />Application Delivery<br />VDI Suites<br />Desktop and <br />Session Delivery<br />Virtualization Platform<br />
    7. 7. HDX MediaStream<br />Seamless multimedia experience<br />HDX RealTime<br />Voice and video for real-time collaboration<br />HDX Rich Graphics with RemoteFX<br />High performance, full fidelity 2D and 3D graphics<br />HDX Plug-n-Play<br />Simple access to peripherals<br />HDX Broadcast<br />Optimized delivery over any network<br />HDX Adaptive Orchestration<br />Dynamically adjusts to conditions across the infrastructure and leverages available RemoteFX capabilities<br />HDX SmartAccess<br />Simple, highly available and secure user experience<br />HDX WAN Optimization<br />Performance acceleration for branch offices<br />
    8. 8. XenDesktop uses 64% less bandwidth than Competitor V<br />
    9. 9. How it works?<br />How it works?<br />
    10. 10. The core of VDI – Remote Desktop Services and VDI Architecture<br />System Center and App-V<br />RD Session Host with RemoteApp<br />RD Web Access<br />RD Client<br />RD Virtualization Host<br />RD Connection Broker<br />RD Gateway<br />Licensing Server<br />Active Directory®<br />
    11. 11. HTTPs<br />SSL<br />Remote Desktop Session Host<br />RD Web<br />Access<br />RD<br />Connection<br />Broker<br />RDP<br />Client<br />RD<br />Gateway<br />WS 2008 R2<br />RDSH<br />RemoteApp/<br />Published App<br />Active Directory<br />& Network<br />Policy Server<br />Authorization<br />Policies<br />
    12. 12. Why Sessions?<br />Session Virtualization scales more users per server than VDI<br />App-V works in both VDI and Sessions<br />The same RDP connection protocol is used in both<br />Much of the service infrastructure is shared<br />Upsides for VDI:<br />VDI offers better user operating system isolation<br />VDI has better native application compatibility<br />VDI allows users to be admins of their own images<br />Upsides for Session Virtualization:<br />Session Virtualization requires less hardware than VDI<br />Sessions are cheaper than VDI desktops<br />Server management is less than VDI<br />Remote Desktop Services enables both session virtualization and VDI! <br />
    13. 13. DEMO<br />Quick View of Microsoft Remote Desktop Services<br />
    14. 14. VIDEO<br />Quick View of Microsoft Remote Desktop Services<br />
    15. 15. Delivering the Virtual Desktop Image<br />Dynamic (“non-persistent”)<br />Virtual Desktops<br />Static(“persistent”)<br />VirtualDesktops<br />Profile Virtualization<br />(Roaming Profiles, Folder Re-direction)<br />Application Virtualization<br />(Streamed Apps)<br />Master<br />Presentation Virtualization<br />(Hosted Apps)<br />Clone<br />Clone<br />Clone<br />
    16. 16. RDP<br />SSL<br />HTTPs<br />Microsoft VDI using RDS<br />RD Web<br />Access<br />RDSH<br />Redirection<br />Mode<br />RD Connection<br />Broker<br />RDP<br />Client<br />AD<br />Domain<br />Service<br />Authorization<br />Policies<br />RD<br />Gateway<br />RD Virtualization Host<br />
    17. 17. DEMO<br />Quick View of Microsoft VDI Solution<br />
    18. 18. VIDEO<br />Quick View of Microsoft VDI Solution<br />
    19. 19. Citrix VDI Solution<br />XenDesktop Delivery Controller<br />request<br />license<br />ADOU<br />Licensing<br />Domain Controller<br />Data Store<br />Login Page<br />User Settings<br />policies<br />find desktop<br />sign & launch<br />validate<br />Power shell<br />Apps<br />Protocol<br />prepare<br />resume<br />OS<br /> Windows Server R2 2008<br />Hyper-V<br />Client<br />SCVMM<br />XenDesktop<br />Provisioning<br />Server<br />Dynamic Image<br />VHD<br />Storage<br />Static Image<br />
    20. 20. DEMO<br />Quick View of Citrix VDI Solution with Microsoft Platform<br />
    21. 21. VIDEO<br />Quick View of Citrix VDI Solution with Microsoft Platform<br />
    22. 22. VDI Capacity Planning<br />VDI Capacity Planning<br />
    23. 23. Building the BaseWhat do I need to start?<br />Hardware required:<br />One or two appropriately specified servers for the number of users required<br />Example: <br />Preferably dual quad Nehalem or equivalent AMD based processor<br />Optional: Second server purely for client VM’s<br />16-32GB or more of RAM<br />RAID 1 or 10 disk subsystem<br />Client PC<br />Software required – <br />Windows Server 2008 R2 Enterprise<br />Windows 7 Enterprise or Windows XP Professional<br />System Center Virtual Machine Manager<br />Active Directory<br />Citrix XenDesktop or Remote Desktop Services<br />
    24. 24. VDI Capacity Planning : Processor<br />Rule of thumb: If it doesn’t have SLAT don’t buy it<br /># of VMs per core is highly dependent on user scenarios<br />Application specific usage play a big role<br />Hyper-V supports:<br />Now supported ! 384 VMs per Server in Clustered scenarios <br />384 VMs per Server in non-Clustered scenarios<br />SLAT enabled processors provide up to 25% improvement in density<br />What is Second Level Address Translation (SLAT)? <br />Intel calls it Extended Page Tables (EPT)<br />AMD calls it Nested Page Tables (NPT) or Rapid Virtualization Indexing (RVI)<br />
    25. 25. VDI Capacity Planning : Processor<br />Single (Unclustered) server results:<br />Win7 VMs using 512 MBs RAM per instance – not supported!<br />Only supported with 8 VM’s per core<br />Though lab benchmark testing went as high as 11 VMs per Core at the limit<br />Server Hardware:<br />
    26. 26. VDI Capacity Planning : Disk IO<br />Rule of thumb: SANs are your new best friends<br />Disk performance is the most critical factor in achieving density<br />Internal testing showed Windows 7 having lower Disk IO than Windows XP<br />Minimum 15 IOPS (I/O Operations per second) per desktop <br />Example:- 50 desktop <br />50 * 15 = 750 IOPS per host<br />RAID 1 or 10 for highest performance<br />
    27. 27. VDI Capacity Planning : Disk IO<br />Peak of read/write @ 3500 IOPs on single un-clustered server (Starting 64 VMs simultaneously)<br />Multiply that by number of servers<br />Result is the rough guidance for the maximum SAN disk IOPS you need<br />Test for the most demanding user logon pattern (for example: 9 am scenario)<br />This test based on Windows 7 Enterprise<br />
    28. 28. VDI Capacity Planning : Memory<br />Rule of thumb: More is better<br />Biggest constraint of upper limit VM density (not performance related)<br />Constrained by:<br />Available memory slots in servers<br />Largest Available DIMMs<br />Buy as much RAM as you expect to scale the number of VM’s<br />Plan for and allocate at least 1GB per Windows 7 VM <br />Memory allocation should be determined by upper maximum limit of running apps<br />Allocate enough RAM to prevent the VM paging to disk<br />
    29. 29. VDI Capacity Planning : Network Performance<br />Rule of thumb: Rich User Experience requires rich bandwidth<br />LAN<br />Generally place VDI (RDVH) servers as “close” as possible to the users<br />VDI User experience is heavily dependent on network performance<br />LAN performance generally not a bottleneck (calculate to be sure)<br />Network redundancy is very important in switching fabric<br />When its down, the user is totally down<br />WAN <br />WAN issues now equals worse issues later<br />Latency kills user experience<br />Persistent protocols take bandwidth per connection<br />How to tell: Multiply the number of users by approximately 20kbps<br />Is that beyond the capacity of your internet/WAN network?<br />20kbps is the best case scenario based on HDX<br />20kbps represents a cut down user experience<br />Consider WAN optimization technologies or compression solutions<br />
    30. 30. Summary<br />Concept of VDI<br />How it works?<br />Remote Desktop Services<br />VDI using RDS<br />VDI using Citrix<br />VDI Capacity Planning<br />
    31. 31. Guidelines RDS<br />RD Session Host:-<br />1 X Quad Core 2.4Ghz - 16GB memory -> 150 to 200 sessions<br />2 X Quad core - 32GB memory -> 300 to 500 sessions<br />RD Gateway + Web Access<br />Processor extensive<br />2GB RAM -> 500 session<br />RD Licensing + Connection Broker<br />1GB RAM is fine for 500 session<br />Processor and memory is insignificant<br />
    32. 32. Citrix XenDesktop Sizing<br />
    33. 33. TCO<br />Total Cost of Ownership<br />
    34. 34. Perceptions Around Cost ReductionExpected VDI Cost Savings versus PC Costs<br /># Respondents (n= 105)<br />
    35. 35. Overview of Benchmark Research<br />
    36. 36. Considerations Prior to Adopting VDI<br />Application Performance<br />User Experience<br />Datacenter Upgrade Cost<br /><ul><li>Network dependent apps (i.e. VOIP) may have degraded performance
    37. 37. Graphic intensive applications may not perform well over WAN
    38. 38. No offline mode – unsuitable for non-connected workers
    39. 39. User experience degrades with server loading and reduced network capacity (i.e. WAN)
    40. 40. Additional investments in server, management, storage, and network infrastructure
    41. 41. Additional software for VDI management, user experience, and optimization</li></li></ul><li>Identify Appropriate Use Cases for VDI<br />Provide a Managed Desktop to Unmanaged Devices<br />• Contract workers<br />• Employee-owned PCs<br />Centralize Desktop Management for Remote Locations<br />• Branch offices<br />• Offshore locations<br />Task Worker Scenarios<br />• Call center workers<br />• Shared terminals, such as factory kiosks / nursing stations<br />Desktops That Demand High Levels of Security and Compliance<br />• Non-mobile desktops in specific industries (i.e. financial services / healthcare / government)<br />
    42. 42. Q&A<br />Questions & Answers<br />
    43. 43. Email<br /><br />
    44. 44. Resources<br />Required slide<br />Microsoft and Citrix Desktop Virtualization<br /><br />Desktop Virtualization hour<br /><br />Remote Desktop Services Team Blog<br /><br />Join MVUG (Malaysia Virtualization User Group)<br /><br />Lai Blog’s <br /> (Refer to VDI Tag) <br />
    45. 45. Required slide<br />WIN COOL PRIZES!!!<br />Complete the True Techie and Crazy Communities Challenge and stand a chance to win…<br />Look in your conference bags NOW!!<br />
    46. 46. Required slide<br />We value your feedback!<br />Please remember to complete the overall conference evaluation form (in your bag) and return it to the Registration Counter on the last day in return for a Limited Edition Gift<br />
    47. 47. Additional Slide<br />Additional slide<br />
    48. 48. Infrastructure Requirement<br />Server Components:-<br />Active Directory<br />Remote Desktop Services roles should install using Windows Server 2008 R2<br />Digital Certificate<br />Virtualization of RDS roles supported !<br />Client components:-<br />Thin or rich client<br />Internet Explorer 6 or later<br />Remote Desktop Connection client version 6.1<br />Reliable network connection<br />
    49. 49. Static Virtual Desktop Requirement <br /><ul><li>Schema must be Windows Server 2008
    50. 50. Domain functional level should be Windows 2000 Server native mode</li></li></ul><li>Static Virtual Desktop Requirement<br /><ul><li>VM name must be in FQDN format</li></ul>Virtual Desktop Pool<br />Static / Personal Virtual Desktop<br />
    51. 51. Web Interface 1/2<br />
    52. 52. Web Interface 2/2<br />Virtual Desktop Pool<br />Personal Virtual Desktop<br />
    53. 53. RemoteApp and Desktop Connection Interface<br />