1 / 32

Citrix Design Project

Citrix Design Project. Application Virtualization Assessment Requirements Analysis Presentation. Agenda/Discussion Points. Project Goals. Key Findings. Summary of Next Steps. Citrix Presentation Server Architecture. Next Steps. Project Goals. Project Goals.

dara
Télécharger la présentation

Citrix Design Project

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. Citrix Design Project Application Virtualization Assessment Requirements Analysis Presentation

  2. Agenda/Discussion Points Project Goals Key Findings Summary of Next Steps Citrix Presentation Server Architecture Next Steps

  3. Project Goals

  4. Project Goals • Assist Western Health in designing an access platform that caters for the diversified needs of the new facilities; namely Teaching, Training & Research Centre, Radio Therapy Building and the Sunbury Hospital • Through interactive meetings, document criticality, readiness, requirements, and risks foreach infrastructure component. This information will allow Western Health to understand the environmental status and considerations for optimisation, rollout, and/or expansion. • Define a detailed architecture for the Citrix XenApp Platinum Application Virtualization Platform and the Citrix Access Gateway Secure Remote Access Platform

  5. Key Findings

  6. Users • While the majority of users are medical research staff the environment also caters for students, academics, visiting academics, medical practitioners. The principal of these users come from either: • Western Health (WH) • Victoria University (VU) • Melbourne University (UoM/MU) • The users can be broadly categorized as follows: • Staff • Student • Guest

  7. Users • Staff users consists of research staff, medical practitioners, the Allied Health team. It is has been assumed that Administrative staff within the research and medical do not have any special application or access requirements. Similarly Post Graduate students have the same access to computing resource requirements as other staff. • Students comprise of undergraduates, interns and have VU or UoM login • Guest users do not have an assigned WH/VU/UoM login and comprise of the short term day contractors, visitors and library users.

  8. Users • The total number of concurrent staff users is currently unknown although it is projected that total concurrent users will be approximately 360. These are comprised from: • TTR: 290 users (80%) • Radio Therapy: 30 users (9%) • Sunbury: 40 users (11%) • The total number of concurrent students is anticipated as 135.

  9. Client Devices • All client devices at TT&R, Radio Therapy and Sunbury premises to be owned and managed by Western Health • Western Health has decided on thick clients with at minimum Intel Core2Duo processors and 2GB RAM • The Managed Operating Environment (MOE) is to be based on Windows XP SP3 and/or Windows 7 • Western Health is to rely on Microsoft System Center Configuration Manager and Active Directory to deploy and upgrade Citrix Plugin software on the client devices

  10. Client Devices • All users are to be provided controlled non-administrative access to the client devices. The MOE is to be configured with auto-login using a shared account with minimal permissions. • Personal devices will be allowed controlled access to specific resources. Apple MacBook, iPad and iPhone are supported by the Citrix Online Plugin and will thus facilitate access to Western Heath and Victoria University hosted applications and desktops

  11. Application Access – Western Health

  12. Application Access – Victoria University

  13. Application Access – Melbourne University

  14. Application Access – Ideal Scenario

  15. Application Access – Ideal Scenario • Access to Western Health, Victorian University and Melbourne University resources is controlled by Citrix Access Gateway • Users presented with an option to decide which organization’s resources he/she wishes to access • Each organization is responsible for hosting their own applications on XenApp/XenDesktop platform • Citrix Access Gateway and associated firewalls to allow access only to the hosted applications and/or desktops • Citrix Access Gateway to rely on organization specific (WH, VU and UoM) directory sources for LDAP Authentication

  16. Application Characteristics • Melbourne University Applications identified as follows: • Office Productivity Applications (MS Office, Shared Drives) • Client Server Applications (Themis, Library Journals, SPSS) • Standalone Applications (End Note, Dreamweaver, INdesign, PRISM, Filemaker PRO, Stata, Adobe Professional, QPDF writer) • Victoria University in the process of building a XenDesktop and XenApp farm which will be utilized to deliver business critical and office productivity applications to their staff and guest users based at the TT&R building

  17. Application Characteristics • Western Health have identified a list of business critical clinical applications and office productivity applications. Some of these applications have unique requirements: • PACS: Diagnostic imaging software (also known as a picture archiving system) is provided by Fuji. The software generally uses third party supplied hardware server and high resolution monitors for displaying images. The equipment is usually purchased by the radiology department. PACS is a highly critical system - resolution and clarity of images (Medical X-ray Images) are vital. • The Paper Chart Management software: Scanning services are required. The hardware has not been defined since the vendor has not been finalised. • GE centricity: Software requires IE6 to be present. It is used by the Cardiology department and is licensed per device/machine.

  18. Application Testing and Installation • Traditionally Western Health follow the following workflow for testing application deployment/upgrade : • Preliminary testing conducted by the packaging team to ensure successful installation, launch etc. • User Acceptance Testing carried out by the business • Mass rollout of the application to the end user desktops

  19. Application Testing and Installation • In a shared environment such as Citrix XenApp, Citrix Consulting recommends a dedicated Development and/or Test environment. • Moving forward Western Health should consider successful functional, integration and scalability testing before transitioning an application to the pre-production environment for Pilot • Western Health have decided on Microsoft App-V for streaming applications to the Citrix XenApp application servers.

  20. Citrix XenApp Farm • It is recommended to design for component level redundancy to ensure fault tolerance • Provision Primary and Backup Zone Data Collector and XML Broker Servers • Two Web Interface Servers load balanced using NetScaler Server Load Balancing • Multiple XenApp Application Servers • A dedicated SQL Server to host Citrix XenApp Data Store, Configuration Logging and EdgeSight databases

  21. Citrix XenApp Farm

  22. Citrix Licensing and Administrative Consoles • Western Health to rely on the shared HealthSmart Citrix License Server • Licensed for Citrix XenApp/XenDesktop Platinum • The universities are required to host their own Citrix Licensing server • The Western Health Help Desk (Level 1) team will have read-only access to the Citrix Delivery Center Console • The Western Health Desktop Administration (Level 2) team will have custom administrative privileges defined within the Citrix Delivery Center Console • The Western Health Enterprise Administration (Level 3) team will have full administrative rights and complete access to the Citrix Delivery Center Console

  23. Support • Western Health will be primarily responsible for managing all infrastructure components housed in the TT&R, Sunbury Hospital and Radio Therapy buildings • The Shared Services Group will continue to provide Western Health users with Level 1 Help Desk services which include basic account creation and password resets. UoM and VU will have their own Help Desk for tasks such as account creation etc (regardless of what solution is proposed). • The Western Health Desktop Administration team will include 4 x FTEs. It is imperative that Level 2 Desktop Administration team be adequately equipped to deal with Citrix issues to take the load off the limited Level 3 personnel. • The Western Health Level 3 Enterprise Administration team will include 2 x FTEs and will be responsible to manage support across all aspects of IT. • Appropriate escalation paths from WH Support to UoM and VU Support will need to be defined.

  24. Windows Server and Active Directory • Western Health XenApp farm to be hosted on Windows Server 2008 Enterprise x32 • Victoria University has decided on Windows Server 2008 R2 as the base OS platform for their XenApp farm • Western Health to rely on Microsoft System Center Virtual Machine Manager for provisioning Virtual Machine images • Western Health and Victoria University rely on Microsoft Active Directory for authentication and authorization • Melbourne University is in the process of deploying an OpenSSO solution. The protocol of choice for authentication is LDAP

  25. Server Hardware • Western Health may decide on Cisco Unified Computing System as the hardware platform for hosting the Citrix XenApp farm • Microsoft Hyper-V Server 2008 will provide the server virtualization layer • Detailed hardware specification to be outlined during the design phase • Resource allocation for virtual workloads as follows: • 2 x Web Interface (2 vCPU & 4 GB RAM Per VM) • 2 x Data Collectors (2 vCPU & 4 GB RAM Per VM) • 1 x EdgeSight Server (2 vCPU & 4 GB RAM Per VM) • 1 x SQL Server (2 vCPU & 4 GB RAM Per VM) • n x XenApp Application Servers (2 vCPU & 4 GB RAM Per VM)

  26. Systems Monitoring and Management • Microsoft System Center Operations Manager is the Western Health standard server monitoring platform • Citrix XenApp WMI interface will be utilized to monitor critical metrics • EdgeSight will be also utilized in conjunction with SCOM for real-time troubleshooting • Cisco UCS monitoring tools will be utilized for monitoring the server hardware • Network monitoring for Western Health networking equipment will be defined by the Shared Services Group • VU and UoM will be responsible for monitoring their assets (Where applicable)

  27. Network Connectivity • 100 Mb link shared by Western Health, Melbourne Health (inc Royal Melbourne), Northern Health and Women’s Hospital. • Western Health has decided on redundant 10 Gb fibre connectivity between the TT&R, Sunshine and Radiotherapy buildings (Ring Network). • A redundant 100 Mb fibre link (Optus) will connect the Sunbury building to the TT&R network • Both the UoM and VU have decided on individual 1 Gb VERN links to allow connectivity between the TT&R and University networks

  28. Network Connectivity

  29. Summary of Next Steps

  30. Next Steps • Define a detailed Citrix XenApp Architecture • Define a detailed Citrix Access Gateway Architecture

  31. Questions and Answers

More Related