This document discusses a strategic approach to implementing and managing desktop virtualization at Quinnipiac University. It outlines the benefits of virtualization such as providing consistent access to applications from any device. XenDesktop is used as the virtualization broker and XenServer as the hypervisor. Factors to consider include software compatibility, user needs, and collaboration tools. Challenges include storage performance, user personalization, and gaining user acceptance. AppSense is used to help with profiles and application management. Close collaboration between IT teams and end users is important for adoption. Locations set to deploy virtual desktops include various labs, libraries, and administrative offices.
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
A Strategic Approach to Desktop Virtualization in Education
1. A Strategic Approach to Managing and Implementing
Desktop Virtualization in Education
PRESENTED BY: FABIANO IACUSSO AND JEREMY
ANDERSON
2. Featured Speakers
Fabiano Iacusso – Systems Administrator – Systems, Technology, & Planning Team.
• Contact Info:
• FIacusso@Quinnipiac.edu
• D: 203-582-3342
Jeremy Anderson - Instructional Technologist
3. Why We Use Desktop Virtualization?
• I believe Technology in Education is evolving to Self-Service
• Required Laptop Program has been diminished – BYOD
• Main attraction – Provide computer Lab access for students and teachers from anywhere
• Benefit - Provide consistent user experience regardless of age of hardware or device
• Assist in leveraging Data Security in our Staff areas
• Data and workspace is driven out of our Data Center (Executive, Registrar, and Bursar Offices)
• Green initiative – power and cost savings over-time
• Reduction of break/fix calls for our Help Desk
• Ability to provision additional capacity in minutes (compared to week long lab refresh)
• Allows us to be competitive as Technology Leaders in Higher Education
4. VDI Broker - XenDesktop
• Why XenDesktop?
• 20 plus years of experiences with Application Virtualization
• Been a XenApp Customer previously
• Support for multiple hypervisors (Xen, Hyper-V, VMWare)
• Desktop Director – web-based management for Client Service Group
• FlexCast Delivery – all types of Virtual Desktops (local, streamed, hosted, etc)
• OS Streaming to the Desktop – attractive – for example, utilizing local GPU resources
• HDX Adaptive Orchestration and Multistream – render on device if possible 1st
• HDX – WebCam Support – Lync 2013 and Online Support
• GPU Pass-through from Hypervisor to vDesktop
5. Hypervisor - XenServer
o Free
o HA and Failure recovery – promote new master within Farm
o Easy to monitor and manage
o Minimal training for Client Services
o Perfect for Labs and Staff VDI, where we use profile management tools to re-direct data
6. Factors to consider when planning to
implement VDI
1. Software – will it work? Some licensing models will not honor a pooled deployment
2. Assess the Clients needs
◦ Job Function – task worker/researcher/data analyst
◦ Application Set – any 3D requirements?
◦ Peripherals
◦ Mobility Requirement
3. Collaborative Support
◦ Should be able to support our VoIP and Teleconferencing solutions
4. Max out server memory – more VM’s hosted
5. Create a Cost Analysis - example
8. Implementing and Managing VDI in
IS
IT Roles
◦ System Administrators
◦ Architect Environment
◦ Focus on Capacity Planning and Data Security – provision desktops
◦ Client Services/Computer Lab Administrators
◦ Create Images, customize applications
◦ Support Users and Devices (PCs, Macs, and Thin Clients)
◦ Network Operations
◦ Assist with Network Configurations (802.3ad) in storage and provisioning servers
◦ VLAN assignments – thin client network, DHCP Boot options
9. Technology Challenges in VDI
1. Storage Challenge
◦ Raid-10 - A good rule of thumb is to expect between 30% to 40% reads and 60% to 70% writes
◦ We have HP Lefthand P4500 multi-site SAN shared among Exchange, SQL, File-Servers, etc…
◦ At peak business hours, noticeable delayed reboot and logon times observed.
10. Challenges Continued…
2. User Personalization
◦ Ensure Data and Custom settings persist and follow the client from Virtual Desktop to Virtual
Desktop
◦ The need to mimic a physical desktop computing environment into virtual is very important to our
clients, or VDI is dismissed
11. AppSense – how it helps?
o Environment Manager
o Roaming Profiles with Folder Redirection (utilize DPM to backup data hourly)
o Online Exchange Mode with Personalization turned on to capture customizations
o Custom triggers per use-case (launch application -> execute script or reg change)
o Application Manager
o Restrict applications via AD Groups (control licenses)
o Allows us to bake many applications into 1 shared image (distributed across various staff offices)
13. The Human Challenges to VDI
Key relationships:
1. Client-IT barrier
2. Siloed clients
3. Siloed IT
14. Circle the wagons
Enhanced collaboration in IT: TILE Committee & Staff VDI Committee
Team composition: Systems, Networking, Academic Tech, Client Services
Weekly meetings
Shared resources
15. Bridging the gap to clients
Engage the decision maker (TILE)
Needs assessments – key stakeholder(s)
Build & demo image – all hands
Pilot a few clients
Scale up to a full space
Regular health checks – key stakeholder(s)
Ongoing planning (TILE)
16. Sustain relationships, sustain growth
DO: simplify experience in one system
DO: respect the needs assessment
DO: be truthful about challenges
DO: engage in discussions about costs
DO: be proactive
17. VDI Locations
o Financial Technology Center
o Biology and Physical Science Labs
o Library (including Law School)
o School of Communications – BYOD
o Computer Information Systems – BYOD
o Chartwells, Bursar, Registrar, Development, Graduate Admissions, and Executive Offices
o Soon to be – School of Medicine
Hinweis der Redaktion
IT-Client barrierMain relationship was with Client Services, a department built on imaging and break-fix triage. Could facilitate a “set it and forget it….until it finally breaks” mentality leading to old images and machines with legacy software and peripheral devicesWhere is the money for refreshes and finding new tools? Is it client budgets or the central IT budget?Siloed clientsWithin schools and staff departments multiple layers of stakeholders > who to engage when? Shared learning spaces (chem and physics lab, e.g.) and public spaces with different stakeholder needs - Silos occur naturally in Academia; multiple levels of stakeholders - Each silo (school, department, course) has it’s own idea of what works, but doesn’t share - Strategy: go to the lynch pin of their system (associate dean or director, e.g.) and market/sellSiloed ITused to having individual responsibilities new paradigm = shifted & new responsibilities
Systems, networking, etc…. Each group is key to success Systems: build and maintain infrastructure and images Networking: providing reliable connectivity to solutionsAca Tech: exploring curricular needs and managing licenses CS: frontline support of clients and devicesWeekly meetings: plan new spaces invite key stakeholders review break-fix and new requestsShared resources: Team site hardware inventory software licensing & documentation team calendar collected notes
Build and demo often includes 5 – 10 peoplePilot usually a handful of thin clients during light-use timeRegular health checks – Lab CoordinatorsOngoing planning
Simplify: unify images into one umbrella image…makes it easier for IS to maintain (less stress), faculty share a tailored imageNeeds assessment: search out solutions to the challenges brought….but if the needs don’t meet the paradigm, they don’t meet the paradigm (yet)Be truthful: this software/hardware won’t work (microscope cam, e.g.), this software/hardware peripheral should be refreshed (old BioPac units, ancient 640x480 flash based apps)Costs: make a plan for paying for the infrastructure, clients, software, peripheralsProactive: plan checks and support for first week – install receiver / wash BYOD machines; clients often won’t report – reach out to them for health checks; maintain contact with decision maker to maintain buy in; search out updates for Citrix Receiver / client firmware, etc.