1 / 37

Virtual Desktop Infrastructure ( = VDI)

Virtual Desktop Infrastructure ( = VDI). Sébastien Pittet & Lionel Zufferey. IT was centralized. The future isn’t what it used to be. The technology cannot be stopped . Virtualization. What is VDI ?!. VDI is not a new product !. VDI is a new Concept !.

callie
Télécharger la présentation

Virtual Desktop Infrastructure ( = VDI)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Virtual Desktop Infrastructure ( = VDI) Sébastien Pittet & Lionel Zufferey

  2. IT was centralized...

  3. The future isn’t what it used to be...

  4. The technology cannot be stopped ...

  5. Virtualization

  6. Whatis VDI ?! VDI is not a new product ! VDI is a new Concept !

  7. Solutions for appsdelivery ?

  8. Digital Natives are coming !

  9. Car as a Service

  10. Microsoft Confidential Hot-desking between Desktop PCs Flexibly work from home and offsite contractor locations Why Centralize with VDI? Desktop LocationIndependence Data Security & Compliance Business Continuity • Quicker recovery from device malfunctions • Centralized data storage and backup reduces losses from stolen devices • Keeps data safe in the datacenter • Centralized tracking helps simplify the burden of regulatory compliance Centralized Management • Reduced IT travel to user workstations for support • Improved desktop lifecycle management through quick access to centralized desktops. 10

  11. Trend

  12. Architecture

  13. Concept - Architecture

  14. Microsoft VDI – Today's Offering Small and large scale deployments: Microsoft + 3rd Party Connection Broker (CITRIX XenDesktop) Remote App • 3rd Party Connection Broker Centralized Desktop (VECD) XenDesktop

  15. MS VDI with Citrix XenDesktop • Citrix XenDesktop Administrator’s Console Web Interface XenDesktop Setup Tool Citrix License Server • Citrix Desktop Delivery Controller Windows PowerShell™ • Citrix Provisioning Server Citrix XenDesktop Agent Citrix XenDesktop Agent Citrix XenDesktop Agent Virtual Machine Virtual Machine Virtual Machine

  16. Licensing Windows Clients: VECD Windows VECD Windows VECD for SA Vista Enterprise Centralized Desktop (VECD) • Thin clients, client PCs without Software Assurance, & 3rd party owned devices • Annual subscription which includes Windows Software Assurance • Option to purchase MDOP • Re-assignment after 90 days • Listed at $110/year/device (Retail ERP) • Client PCs with Software Assurance • Annual subscription in addition to Windows Software Assurance • Option to purchase MDOP • Re-assignment rights after 90 days to any SA covered PC • Listed at $23/year/ device (Retail ERP) VECD is required for all VDI implementations, regardless of choice of technology vendor (MS, VMWare) LicensingProcess

  17. VDI – Implementation Questions • Should I be using TS? • Image management & Storage • Roaming Profiles • Patching • Application Deployment • Network • Sysprep

  18. How do I … ? • Provide unique environment for each and every user ? • Customizeeveryenvironmentwithdifferentapps and settings ? • Grant users more control to allowtheminstall and modifyapplciations ? • Runappsthat are not multi-user friendly?

  19. Centralized Desktops: TS vs. VDI User requirements should dictate mode chosen Remoting protocol is common factor for both models Expect to have mix of both models

  20. Planning questions: VDI Image Management / Storage 2 Primary Models: • Personal VM’s – 1 VHD per user, VHD state full • Temporary Pooled VMs – VHDs shared between users, state reset at logoff Personal VMs: Day 1 Day 2 Day n • How Important are these 2 scenarios? • What % of your VDI user population will use each scenario? • What type of users will use each scenario? • In the pooled VMs how do you plan to handle user state? • In pooled VMs how often do you hope to ‘refresh’ the pool with new images? • What features do you need to help place and mange these VMs? • What type of load management? • Support for VM libraries? Clone User 1 Day 2 Day n Golden Image User n Day 2 Day n Temporary Pooled VMs: Pool Day 1 Day 2 Day 3 1 User 1 User 1 Golden Image Clone User 1 n

  21. Planning questions: what about user state? • User state can bloat VHD • DO: • Use roaming or mandatory profiles. • Use folder redirection • Place profile servers close to VDI hosts • Don’t: • allow folder synchronization if using pooled vm • Place OSTs / PSTs in redirected folders or profile • User pro-quota to stop users abusing their desktop

  22. Planning questions: patching • DO: • Have planned patching cycles • Understand how pathing will affect re-creation of master images • Understand how patching will affect VHD size over time • Use automated patching services • Use App-V to reduce patching of apps in image • DON’T: • Allow patching to dictate use of pooled vs personal

  23. Planning questions: what about user applications? • More apps in image = more disk • More apps in image = hard to patch • More apps in image = more ‘golden images’ Using App-V is essential • Considerations: • Consider deploying ubiquitous applications in image • Consider using App-V ability to redirect user state to network location (not into profile) • Suite applications that need to run together

  24. Microsoft Confidential Planning questions: network • Network bandwidth planning is key: • Plan for use of profiles and redirection • Plan for per user bandwidth required for RDP / ICA etc • Ensure the host VM server has adequate NIC bandwidth to other server infrastructure (applications, file, print etc) • Make sure the user of SAN to host the VHDs is factored if SAN will run over an IP network

  25. And what for Tomorrow ? VDI with Windows Server 2008 R2 and Windows 7

  26. VDI – Windows Server 2008 R2 Large scale, complex deployments: Microsoft + CITRIX technology Small scale, simpler deployments: Microsoft only technology Remote App VECD for R2 Connection Broker Options Large scale XenDesktop OR Small scale R2 R2 28

  27. Connection Brokering Architecture Active Directory 3. Query Personal Desktop for User VM Connection Broker 4.Query/ Start VM RDV Host Agent Hyper-V 2.Get Target Machine 5.Return Target Machine TSV TSV TSV RD Redirector VM 1.Connect to MyPersonalDesktop 6.Redirect To Machine 7.Connect to Machine Client

  28. Windows 2008 R2& XenDesktop 3 Demo

  29. Some Cool Information • 5-7 VMs • by Hosts’Core • Consolidation Rate • Client devices :

  30. VDI – isthat THE solution ? Some Pros Some Cons Network dependency Availability Latency impacts Can becomplex • Best of both world • Virtualizationbenefits • A PC for each user • Data Security • Instant provisioning of new desktops • Mobility • Multiple Desktops

  31. Resources • VDI MakeSense! (downloadlink) • Desktop VirtualizationStrategy(link) • BLOG (Deployment Guys), article VDI (link) • Step by step guide (link)

  32. Call to action ! • Formations LANexpert • Workshop VDI • Microsoft • Citrix • http://www.lanexpert.ch/training • Programme détaillé disponible

  33. C Beaugrand - LANExpert Architecture Sécurisée Sécurisation par GPO Portail Web DataCenter LAN Users ExternalUsers

  34. Save the date for tech·days nextyear! 14 – 15 avril 2010, CICG

  35. Premium Sponsoring Partners Classic Sponsoring Partners

More Related