1 / 20

Global Delivery of Large Scale VDI with Quest and Microsoft

Global Delivery of Large Scale VDI with Quest and Microsoft. Daniel Bolton Information Services Kingston University Mission Statement : To provide a University without walls. About Kingston University. 23,000 Students – 1500 distance learning.

reid
Download Presentation

Global Delivery of Large Scale VDI with Quest and Microsoft

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. Global Delivery of Large Scale VDIwith Quest and Microsoft Daniel BoltonInformation ServicesKingston UniversityMission Statement: To provide a University without walls

  2. About Kingston University • 23,000 Students – 1500 distance learning. • 2500 Staff (excluding temporary staff and guests). • 4 Campuses and multiple satellite offices. • 7000 Desktops (Windows, OS X, Linux). • EST 1000+ Mobile devices (Smart phones, Laptops, Tablets). • Courses run all over the world, China, India, Russia, Greece, etc. • Multiple affiliate institutions.

  3. Business Drivers Original Business Drivers: • To provide “managed” services to mobile and “non-managed” users. • Service delivery for long distance learning students. • Reduce the complexity of the traditional desktop model. • Windows 7 Migration.

  4. Business Drivers Evolved Business Drivers: • Lower the total cost of ownership (where feasible). • Improve service continuity.

  5. Technical Requirements • Location aware – Ability to assign “resources” based on location. • Support for, Windows, Mac and Linux clients. • User environment management. • Integration with Remote Desktop Services (terminal services). • Application Integration – MSI installs, Application Virtualization, etc. • Granular administration – Helpdesk roles, etc. • Connectivity over high latency connections.

  6. Obstacles • User acceptance (at all levels). • Novell lingering on! • IP address allocation. • Applications. • User installed applications. • Identifying the different user types.

  7. User Identification

  8. Our Choice • Quest vWorkspace • Microsoft Hyper-V • Microsoft App-V

  9. Phase 1 – Initial Infrastructure • Designed to support 300 Windows 7 Desktops and 200 RDS sessions. • Utilize existing SAN infrastructure. • Virtual Desktops and RDS servers hosted on Hyper-V (managed by SCVMM). • No Desktop replacements – value added only

  10. Infrastructure

  11. What we are Achieving • Desktops as a Service (DaaS). • Centralised desktop management. • Dynamically assembled desktops.

  12. Dynamically Assembled Desktops

  13. Decisions For Moving Forward • Persistent desktop or non-persistent desktop? • Virtual machine storage, SAN or local disk? • User profiles – folder redirection? Registry capturing? Etc? • Virtualize RDS servers? • Use App-V’s shared cache feature?

  14. Phase 2 – Goals By the end of March 2011 we will (“should”) have the following; • Support for additional 2500 - 3000 virtual Windows 7 desktops. • Support for additional 1500 - 2000 Remote Desktop Services connections. • 300 - 600 Windows 7 RemoteFX “ready” virtual desktops. • Applications streamed using App-V (with shared cache). • Started the next phase of our client hypervisor pilot with vWorkspace integration.

  15. Phase 2 - Infrastructure • 2 Additional vWorkspace connection brokers. • 2 Additional vWorkspace web portals. • An additional vWorkspace user profile server for redundancy. • An additional MS SQL server for fault tolerance vWorkspace DB. • Utilize existing “intelligent” load balancing appliance for web portal connectivity and use to replace the SSL gateway.

  16. Phase 2 - Infrastructure • 50 Additional Hyper-v hosts each with, • 12 CPU Cores • 120GB Memory • 10 146GB 15k SAS drives • 4 Network ports • 1GB GFX card • This gives us (per server), • At least 40 Windows 7 virtual machines with 2GB RAM60 virtual machines was achievable with acceptable performance • 4 – 12 RemoteFX enabled virtual machines • 20 RDS sessions35 sessions with acceptable performance

  17. Infrastructure

  18. Advice • DO NOT RUSH INTO ANYTHING. • ONE SIZE DOES NOT FIT ALL. • IDENTIFY USER REQUIREMENTS. • VIRTUAL DESKTOPS ARE NOT VIRTUAL SERVERS! • YOU DO NOT HAVE TO USE THIN CLIENTS!

  19. Quest and Microsoft • Working with Quest. • Working with Microsoft.

  20. Q & maybe some A

More Related