Document management Category Tracking Information Company:

Document management Category Tracking Information Company:
Citrix Systems, Inc. Author(s): Beth Roberts Owner(s): Worldwide Technical Readiness Last modified: February 28, 2011 Version: 1.5 Length: 1 day with labs This presentation was created by the WW Technical Readiness team. If you have any questions please contact the presentation authors.

XenDesktop 5 Comprehensive Technical
Worldwide Technical Readiness February 28, 2011

Project Overview and Release notes New Concepts and Quick Deploy
Agenda (1 of 2) Project Overview and Release notes New Concepts and Quick Deploy Installation with Quick Deploy Components and Architecture Hosting Management Machine Creation Services

Active Directory-based Policies VM-hosted Applications
Agenda (2 of 2) Virtual Desktop Agent 5 Desktop Studio Desktop Director Active Directory-based Policies VM-hosted Applications Scalability and Best Practices

Project Overview and Release Notes

Key new features Simplified Install – Quick Deploy
Simplified Desktop Deployment and Machine Creation Fewer Management Consoles Active Directory-based Policies Printing Optimizations Simplified Desktop Deployment and Machine Creation. XenDesktop simplifies the task of creating, managing, and delivering virtual desktops to users. XenDesktop's wizards guide you through the process of setting up your deployment, provisioning desktops by building a master image and creating user desktops, and assigning desktops to users. Groups of user desktops are created and managed as a single entity, which enables you to assign, update and extend thousands of user desktops quickly and easily. XenDesktop supports desktops hosted on both VMs and on physical computers. Simplified Install. New installation wizards simplify the process of installing and setting up a XenDesktop deployment. A wizard guides you through the installation of server side XenDesktop components, including the controller, the Desktop Studio management console, licensing, and the Web Interface. The wizard also guides you through individual component installations, and pre-configures these for you (for example, it will build all the Web Interface sites). A separate wizard guides you through the installation of the Virtual Desktop Agent on virtual desktops or on a base image. Desktop Studio. This tool snaps into the Microsoft Management Console (MMC) and enables you to configure and manage your XenDesktop deployment. Desktop Studio provides various wizards to guide you through the process of setting up your environment, creating your desktops, and assigning desktops to users. Desktop Director. This Web-based tool enables level-1 and level-2 IT Support staff to monitor a XenDesktop deployment and perform day-to-day maintenance tasks. You can use the Desktop Director to monitor status, such as the health of the hypervisors and controllers in a site. You can manipulate sessions and desktops, such as restarting a desktop or logging off a session. You can also view and interact with a user's session, using Microsoft Remote Assistance, to troubleshoot problems. Active Directory-based Policies. XenDesktop 5 uses the Windows Active Directory based policy mechanism for Citrix policies. Citrix policies allow you to control user access or session environments, and are the most efficient method of controlling connection, security, and bandwidth settings. You can specify policies that are shared between XenDesktop and XenApp; for example, you can turn Client Drive Mapping off using one policy. Printing Optimizations. XenDesktop 5 provides administrators and users with the ability to optimize printing in their virtual desktop environment. Using printing preferences and policies to configure resolution, color depth and compression, administrators can optimize for better print quality or faster printing. Users can also modify print quality by adjusting dpi settings.

XenDesktop 5 release schedule
Release to Web (RTW) Dec 3, 2010 General Availability (GA) Dec 17, 2010

Features and editions “Eye Chart”
Licensing Express VDI Enterprise Platinum Named User 10 Included Device based Concurrent User Components Controller XenServer XenServer ENT Machine Creation Services PVS for desktops PVS for servers Workflow Studio Profile Management Storage Link Access Gateway ICA Full XenApp ENT PLAT HDX 3D EdgeSight for VDA Repeater plug-in Single Sign on XenClient SA Eligibility date is Sept 14 for ENT/PLT customers Citrix Confidential - Do Not Distribute

New Concepts and Quick Deploy

New Concepts in XenDesktop 5
Sites XenDesktop deployment in single geographical location Previously known as a Farm in XD4 Hosts Infrastructure comprised of hypervisors (resource pools or clusters), storage and other virtualization components Each site can have multiple host connections Farms are now called sites. A XenDesktop 5 site should not be spread across the WAN. There should be a site for each geographical location. A site can have multiple host connections from various hypervisors (XenServer, ESX and Hyper-V).

New Concepts in XenDesktop 5
Catalogs A grouping of similar desktop machines from 1 or more hypervisors Desktop Groups Desktops from one or more catalogs - not limited to a single hypervisor pool - assigned to users Single user may access multiple desktops in the group or a single desktop may be assigned for use by multiple users Similar to the concept of Desktop Groups in XD4 In XenDesktop, collections of user desktops are managed as a single entity called a catalog. Catalogs specify virtual machines (VMs) or physical computers that host user desktops, the Active Directory computer accounts assigned to those VMs or computers, and, in some cases, the master VM that is copied to create the user desktops. NOTE: All the machines in a catalog should be of the same machine type but is not restricted. Assignments and the virtual desktops they contain can be configured more flexibly. A single assignment can contain desktops from a number of catalogs rather than being limited, as in earlier versions, to a single hypervisor pool. Also, a single assignment can be published to users so that a single user may access multiple desktops in the group, and a single desktop may be assigned for use by multiple users. Desktops can also be assigned to client machines (IP address), rather than users, if required.

XenDesktop 4 vs XenDesktop 5
In XenDesktop 4 In XenDesktop 5 Farm Desktop Group DDC / broker /controller IMA data store AD Config Wizard Idle Pool Settings Site Desktop group (assignment) DDC / broker /controller SQL database Registry-based Desktop Group / Power Mgmt Citrix Confidential - Do Not Distribute

Site  Hosts, Catalogs, Desktop Groups
A single site can have many host connections, catalogs and Desktop Groups.

Desktop Catalogs Pooled Dedicated Existing Physical Machines Streamed
Machine Catalog Types Pooled Dedicated Existing Physical Machines Streamed Desktop Catalogs Machine type. Specifies where user desktops are hosted and how user personalization of desktops is accommodated. XenDesktop supports desktops hosted on both VMs and physical computers. If you decide to allow users to take ownership of a particular desktop and personalize it according to their needs, XenDesktop provides two different approaches to managing user customizations. You can choose to keep users' customizations, such as preferences or particular applications, separate from the master VM that the desktops are based on. This offers the advantage that you only need to work with a single VM to apply system-wide changes to thousands of users' desktops, such as applying Windows Updates or adding a new application. Alternatively, if you prefer, you can choose to manage desktops individually, in the same way that you currently manage physical computers. "Manually create virtual machines" - Pooled and dedicated catalog types are not available, only existing, physical and streamed will be in this pull down "Use XenDesktop to create desktops" if you want pooled or dedicated catalogs (all 5 types are available)

Machine Type Definitions
Pooled - direct copies of the master VM, no customization Dedicated - permanently assigned to individual users, with customization Existing – previously created virtual machines Physical - desktops hosted on dedicated blade servers; no centralized power control Streamed - vDisk imaged from a master target device with Provisioning Services Pooled Pooled machines provide desktops that are allocated to users on a per-session, first-come first-served basis. Users of pooled machines get a brand new desktop every time they log on. Pooled machines are direct copies of the master VM, although profile management can be used to apply users' personal settings to their desktops and applications. Any changes to pooled machines made by users with local administrator permissions for their desktops are stored for the duration of the session. However, these customizations are discarded when users log off. Maintaining a single master VM in the data center dramatically reduces update and upgrade maintenance efforts, and can reduce your storage costs by up to 90 percent. Best for task workers who require standardized desktops, such as call center operators, retail workers, or students and faculty in educational institutions . Best when you want to minimize desktop management and storage costs by providing a locked down standardized environment for your users. Reduce support, maintenance, and upgrade costs through the use of homogeneous workspaces and hardware. Optimize hardware usage by providing only the number of desktops that are required at any one time rather than assigning each user a specific desktop. Maintain control over desktops by limiting user permissions and preventing customization. Dedicated machines provide desktops that are permanently assigned to individual users. Desktops can be assigned manually or automatically assigned to the first user to connect to them. Whenever users request a desktop, they are always connected to the same one. As a result, users can personalize the desktop to suit their needs. Desktop customizations are stored separately and overlaid on copies of the master VM to recreate users' desktops whenever a dedicated machine is started. Dedicated machines enable you to make significant savings on desktop management and storage costs by maintaining a single master VM in the data center for global updates such as operating system updates and upgrades, while users still get individual desktops that they can personalize. Dedicated Best when you want to reduce desktop management and storage costs while still providing your users with a personalized desktop experience . Reduce support and maintenance costs by standardizing certain aspects of users' desktops through the use of a common template . Support a wide range of different user requirements with the same common template . Deliver users' desktops to any endpoint device regardless of hardware capability . Minimize the time needed to provide additional desktops for new users. Best for task or knowledge workers who require individual desktops which they can take ownership of and personalize. Mobile workers who want to access the same desktop from a variety of endpoint devices over different networks and do not need to store data on their desktops The existing machine type enables you to use XenDesktop to manage user desktops that you have already migrated to VMs in the data center. As with traditional local desktops, changes and updates are permanent and must be managed on an individual basis or collectively using third-party electronic software distribution (ESD) tools. Managing your existing VM-based desktops through XenDesktop affords you greater control over their power states; for example, you can configure XenDesktop to shut down VMs when users log off to minimize unnecessary power consumption in the data center. Existing Best for personalized desktops on which they can store data . Want a high definition experience that matches their local desktops with the better reliability and higher availability offered by data center infrastructure. Best when you use XenDesktop to manage existing desktops hosted on VMs in the data center. Reduce support costs by centralizing user desktops in the data center without moving to a virtual desktop solution. The physical machine type enables you to use XenDesktop to manage user desktops hosted on dedicated blade servers, or a mixture of blade servers and VMs, in the data center. As with traditional local desktops, changes and updates are permanent and must be managed on an individual basis or collectively using third-party ESD tools. Using blade servers enables you to support small numbers of users who have particularly demanding performance requirements. This approach offers all the benefits of centralization, but ensures dedicated processing power for each user by hosting only one desktop per server. Physical Best for users who are technical workers or power users and use specialist graphics applications with demanding hardware requirements, such as computer-aided design and manufacturing (CAD/CAM) tools and geographic information system (GIS) applications . Have high performance level expectations for line of business applications . Require dedicated hardware Reduce support and maintenance costs by centralizing complicated specialist systems in the data center Need personalized desktops on which they can store data . Best when you need to support users of applications that require dedicated specialist hardware . Leverage powerful server hardware instead of purchasing expensive high end PCs The streamed machine type enables you to provide desktops to repurposed PCs and thin clients that have been configured to load the operating system over the network from Provisioning Services. Target devices are managed in Provisioning Services as a device collection and the desktops are delivered from a Provisioning Services vDisk imaged from a master target device. Using Provisioning Services to deliver desktops enables you to leverage the processing power of existing local hardware, while realizing all the benefits of centralized desktop management. This approach offers an inexpensive entry point to desktop virtualization using existing local resources and reducing to a minimum the need for additional processing and storage capacity in the data center. Streamed Best for task or knowledge workers who require either standardized desktops or individual desktops which they can take ownership of and personalize . Have existing PCs or thin clients that may be reaching the end of their lifecycle Maximize data security by delivering desktops to diskless target devices Best when you want to deliver desktops to device collections containing mixtures of different types of PCs and thin clients Do not need to access their desktops from outside the corporate network . Do not need to store data on their desktops Minimize the use of server resources Extend the lifecycle of existing local hardware while reducing support and maintenance costs

Catalog design increases scale and resilience
Desktop Group 1 Desktop Group 2 Desktop Group 3 Hypervisor Hypervisor A catalog can belong to more than one XS pool and there is no limit on group size. This design provides increased scale and resilience. Multiple assignments can be created from one catalog of machines. Hypervisor Hypervisor

Machines and Desktop Groups
3 assigned A machine can be unassigned in a catalog or a machine can be assigned without being in a catalog (pre assign to a user). When machines are viewed in a catalog that are unassigned, they will display without STATE, ASSIGNMENT or SERVER.

Users can run multiple desktops in a group
A user can be assigned multiple desktops from one pool but this configuration is not supported with Dazzle. The user will be shown the number of desktops from the group that he has access to.

Desktops assigned to user or client IP
Client IP Address A single desktop can be assigned to multiple users and also to client IP address (for shared use) – client hostname not supported.

Installation with Quick Deploy

*NEW* Installation – Server Side
No IMA in XenDesktop 5 Controller No IMA data store or local host cache No XML Blob No AD Configuration Wizard or Farm OU No Terminal Services requirement New SQL database – no support for Oracle or Access No IMA data store. XenDesktop 5 no longer uses the IMA data store as the central database in which to store configuration information. Instead, a Microsoft SQL Server database is used as the data store for both configuration and session information. In XenDesktop 5, this function is distributed evenly across all controllers in the site. Due to reliance on Microsoft SQL Server, to ensure failover should the database become unavailable, you must use either SQL clustering or mirroring, or deploy the database as a virtual machine and use your hypervisor's high availability features instead. For more information about planning for high availability, see High Availability Planning. Registry-based discovery. The default mechanism for desktops to find controllers is now registry-based. An Active Directory Organizational Unit is no longer required, although you can still use Active Directory-based registration. Active Directory is still needed in a XenDesktop deployment for authentication and authorization, therefore machines need to be domain-joined regardless of whether you use registry based discovery or not.

Installation – Server Side
XenDesktop Controller supports Windows Server 2008 and R2 only To use “Quick Deploy” all components must be on same box Quick Deploy assumes SQL Express on same machine Uses the same License Server as XenDesktop 4 (11.6.1) PowerShell 2.0 is downloaded during the installation GOTCHA : Manually install PowerShell if you don’t have internet access Controller runs on 2008 and 2008 R2 Server only ---The domain functional level of 2003 as the minimum XenDesktop 5 provides a new PowerShell SDK which allows you to perform the same tasks as you would with the Desktop Studio console. Desktop Studio is built upon the PowerShell SDK. Note that the new PowerShell SDK is not compatible with the SDK associated with previous XenDesktop releases.

Controller – System Requirements
Microsoft Windows Server 2008, Standard or Enterprise Edition, with Service Pack 2 Microsoft Windows Server 2008 R2, Standard or Enterprise Edition Service Pack 1 will be supported Microsoft .NET Framework, Version 3.5, with Service Pack 1 Microsoft Internet Information Services (IIS) and ASP.NET 2.0 IIS is required only if you are installing the Web Interface, the License Server, or Desktop Director Depending on which components you are installing, the following prerequisites are installed automatically if they are not already present on the computer: Microsoft Windows Management Framework, if you are using Windows Server 2003 or Windows Server 2008 (but not Windows Server 2008 R2). This download includes Microsoft Powershell 2.0, which is a prerequisite for XenDesktop. Microsoft .NET Framework 3.5 Service Pack 1. Microsoft Internet Information Services (IIS). When IIS is installed, port 80 is automatically opened. Microsoft SQL Express 2008. Java Runtime Environment 1.5 update 15. Microsoft Visual J# Redistributable Package version 2.0. Microsoft Visual C Service Pack 1 runtime redistributables. NOTE: 32- and 64-bit versions of the Windows 2008/R2 can be mixed within a site.

Controller – Database Requirements
Microsoft SQL Server 2008 R2 Microsoft SQL Server 2008 R2 Express Edition Microsoft SQL Server 2008, with Service Pack 2 installed Microsoft SQL Server 2008 Express Edition, with Service Pack 1 installed We will ship with SQL Server Express 2008 R2 Windows integration authentication required Connecting to SQL Server Express – Download and install SQL Management Studio To connect to a SQL Server Express Database Engine instance by using SSMSE, in the Connect to Server dialog box, specify the following: server name\sqlexpress Note The default installation of SQL Server Express uses an instance name (SQLExpress). This instance name must be supplied to connect to SQL Server Express by using SSMSE. If you have an instance name other than SQLExpress, connect by using computer name\instance name. The only supported database server is SQL Server or SQL Express (no Oracle or Access). This database must be configured to use windows integrated authentication.

Installation – Client Side
VDA now uses “registry based” registration. Broker details are stored in the registry of the desktop PowerShell scripts can be run to set up registry based VDA registration VDA command line options FORCEWDDMREMOVE – For physical machines or VMware NOWINRM – for WinXP GPO install of VDA is documented here In place VDA upgrade is supported Registry-based discovery. The default mechanism for desktops to find controllers is now registry-based. An Active Directory Organizational Unit is no longer required, although you can still use Active Directory-based registration. Active Directory is still needed in a XenDesktop deployment for authentication and authorization, therefore machines need to be domain-joined regardless of whether you use registry based discovery or not. FORCEWDDMREMOVE - For more information, see Unable to Connect to XenDesktop Virtual Desktop Agent on Vista or Windows 7 with WDDM Driver NOWINRM – for WinXP – The VDA install will look for WINRM by default. Windows XP does not have this by default. See CTX for more information.

**New Concept** Machine Creation Services - Provisioning Services for VDI
A collection of services (AD Identity Service, Provisioning Service, Machine Personality Service, and Hosting Unit Service) which work together to replicate machines based on the Master VM, set their identity, and manage them.

Provisioning Services with XenDesktop 4
Proven to scale Single image management workflows Actively being developed Additional console - PVS console Infrastructure requirements Windows Servers in the storage path Existing: Citrix Provisioning Services Global Deployment Model Unifies Management of Physical and Virtual Desktops Requires Deployment Investment PXE, Windows Servers in Storage Path

Active Directory with roaming profiles
XenDesktop 4 with PVS “desktop proxy stream” Desktop Delivery Controller SA N PVS Virtual Machines XenServer PVS was the only solution for single image management, but required a server to proxy the desktop stream Active Directory with roaming profiles XenApp

New Option with XenDesktop 5.0
New: Machine Creation Services Benefits of Provisioning Services Optimized for Hypervisor environments Low Deployment Investment Machine Creation Services: Citrix Machine Creation Service Creates new Virtual Machines Citrix AD Identity Service Manages Active Directory Computer Accounts Citrix Machine Identity Service Manages Virtual Machine Storage The easiest way to think about this is a replacement for the old setup tool Run everything in advance - This allows you to create your VM's on the fly Move away from the PVS replication images and rely on the capacity of the hypervisor to do the thin cloning We have a native component that we run on the VDA that does the PVS magic - Native DLL that we inherit from PVS - doing some AD work Infrastructure services – same configuration services directory for all services including configuration services in your site – your site being one database instance Host service – directory of all your hypervisors Machine creation services – start with AD identity service which manages the machine accounts in Active Directory

Storage Configuration
Provisioning Services: Hypervisor(s) Provisioning Services Storage Caches ‘base image’ in RAM for fast delivery Machine Creation Service: Storage Hypervisor(s) RAM Cache With PVS, we use the Provisioning Server to manage the vDisk and it can cache the read disk in RAM for fastest delivery. With MCS there is no additional server between the hypervisor and the storage. This reduces rack space in the data center. MCS can use the RAM cache on the storage in most cases for reads from the base image. Rack-friendly, 0U hit for RAM cache Caches ‘base image’ in RAM for fast delivery

High-level Service-Oriented Architecture
Desktop Studio Desktop Director WinRM (WMI) SDK available for automation PowerShell WCF Desktop Broker Machine Creation Service Host Service Virtual Desktop Machine Identity Service Broker Service AD Identity Service Central Config Service XenDesktop 5 has a new Service-Oriented Architecture with the Broker Service, Configuration Service, Host Service and Machine Creation Services ( Machine Creation Service & AD Identity Service & Machine Identity Service ) Wins: Deployment flexibility Division of labor Re-use LCM Costs: ‘Task-oriented’ activities are more complex Cross-SDK search performance Multiple connection points to Hypervisor services SQL Server

Provisioning Services for VDI (MCS)
hypervisor A A A A A A A Master VM storage A Once you got an image we communicate in a similar workflow as machine identity services – pre-made copy disk – list fo controllers, quick deploy, attach a thin clone differencing disk If service crashes in the middle of machine creation – it is recorded how many were actually successfully created – when service is restarted they know where is a partially completed activity in the database and it will start off from there. Image Optimizer – is a PVS component which used to adjust the OS parameters, we shared that we just have that as a binary (in Boston) This template is linked thru one of the documents Encryption support for the database that we share with the broker – one of the things the machine identity services have to manage and the ID service is the machine passwords so we don’t want those to be available – those are stored encrypted in the database diff disk identity Master VM image

Machine Creation Service: How it works
VM VM VM Storage Diff Disk Id Disk Diff Disk Id Disk Diff Disk Id Disk Persistent Identity uses little space Space reclaimed every boot Master Disk Set VM’s to be created – we fire up an event asking if there is an image for it? Then we pass an event to the master image to be replicated Do we have an image for it? If not it will replicate the master image on a separate storage place in your hypervisor – Just in case someone is adding more storage.. we do an extra check to say – is there an image on this storage locations? One copy of the base image shared by all VMs

Identity disk and diff disks
Citrix Confidential - Do Not Distribute

Identity Disk – Hidden by default
Protected by ACLs Citrix Confidential - Do Not Distribute

Provisioning / Update / Rollback
Patch history kept as snapshots (deep chain) Master VM Snapshot Flatten chain for best performance Can take time Snapshot #1. Consolidate Rapid provisioning of VMs Snapshot Patches Base Image Snapshot #2. Provision Golden Image Diff Diff Provisioning scheme – we will consolidate the snapshot image that is giving to a new master image XenDesktop verifies if there is an image for the new VM - If not it will replicate the master image on a separate storage place in your hypervisor Once you got an image we communicate in a similar workflow as machine identity services – pre-made copy disk – list of controllers, quick deploy, attach a thin clone differencing disk VM VM

Updating the master VM for pooled desktops
Update the master vm Modify the pooled machine catalog in Desktop Studio by choosing the “Update” option Specify the strategy as immediate or next login To update the master VM Once you have prepared and tested a new or updated master VM, modify the pooled machine catalog to use the new master VM. Desktops are updated with the new master VM the next time users log off. Citrix recommends that you save a copy or a snapshot before you modify an existing master VM that is being used to provide desktops to users. The XenDesktop database retains a historical record of the master VMs used with each catalog. Provided you do not delete, move, or rename the old master VMs (including any snapshots in the chains leading to the master VMs), you can quickly revert a catalog to use the previous version of the master VM should users encounter problems with updates that you have made. Log on to the computer running Desktop Studio. On the Windows Start menu, click All Programs > Citrix > Desktop Studio. In the left pane of Desktop Studio, click Machines, select your catalog in the results pane, and click Update machine. On the Overview page, click Next. On the Master Image page, select the host and the new or updated master VM that you want to use. Click Next. On the Strategy page, specify how the new or updated master VM will be applied to users' desktops and click Next. If you are deploying a non-urgent update and you want to minimize disruption to users, select None. The update is applied only when users next log off. If you are deploying a non-urgent update and you want to inform users, select Send message and enter a message. Users see the specified message and the update is applied only when they next log off. If you are deploying a critical update and you want to apply it to all users' desktops urgently, select Restart immediately. All users are automatically logged off and their desktops restarted. If you are deploying an urgent update and you want to allow users some time to save their work before upgrading their desktops, select Send message then restart after delay. Enter a message and specify the time delay before applying the update. The timer starts only when Desktop Studio finishes making a copy of the new or updated master VM in the appropriate location. Users see the specified message and the update is applied when they next log off or, if the specified time limit is reached, users are automatically logged off and their desktops restarted. On the Summary page, check that the details are correct and click Finish. Citrix Confidential - Do Not Distribute

Dedicated Catalog Updates
User changes are persistent and kept in diff disk Updates must be managed on a individual basis or using 3rd party EDS tools For dedicated, existing, and physical machine catalogs, updates to users' desktops must be managed outside of XenDesktop, either on an individual basis or collectively using third-party electronic software distribution tools. Dedicated machines provide desktops that are assigned to individual users. Machines can be assigned manually or automatically assigned to the first user to connect to them. Whenever users request a desktop, they are always connected to the same machine, so you can allow users to personalize their desktops to suit their needs. Dedicated desktops are provisioned from the master VM the first time that users log on, but all subsequent changes made to the desktops are persisted. As with traditional local desktops, changes and updates are permanent and must be managed on an individual basis or collectively using third-party electronic software distribution (ESD) tools. Changes made to desktops are stored in difference disks that expand as required, so storage space is used only as it is needed. Citrix Confidential - Do Not Distribute

Machine Creation Service: Compatible Storage
Almost any shared storage will work, but... NFS Low Scale: FC iSCSI DAS XenServer NFS Low Scale: VMFS ESX CSV (Clustered Shared Volume) Hyper-V Recommended When using NFS, the diff disk is dynamic and uses less storage. When using iSCSI, the diff disk must allocate the full size of the master to storage.

Desktop Studio Desktop Director WinRM (WMI) SDK available for automation PowerShell WCF Desktop Broker Machine Creation Service Host Service Virtual Desktop Machine Identity Service Broker Service AD Identity Service Central Config Service XenDesktop 5 has a new Service-Oriented Architecture with the Broker Service, Configuration Service, Host Service and Machine Creation Services ( Machine Creation Service & AD Identity Service & Machine Identity Service ) Wins: Deployment flexibility Division of labor Re-use LCM Costs: ‘Task-oriented’ activities are more complex Cross-SDK search performance Multiple connection points to Hypervisor services SQL Server

Citrix Confidential - Do Not Distribute
AD Account Management Create Active Directory accounts tracked at all times Pool AD Admin XD Admin Import Provision Id Disk VM Import De-provision Combined Admin New in XD 5! Create Reset Citrix Confidential - Do Not Distribute

MCS – Additional Information
Image Optimizer PVS component used to adjust OS parameters Encryption support for the database CDF tracing enabled on machine creation services Image Optimizer – is a PVS component which used to adjust the OS parameters, we shared that we just have that as a binary (in Boston) This template is linked thru one of the documents Encryption support for the database that we share with the broker – one of the things the machine identity services have to manage and the ID service is the machine passwords so we don’t want those to be available – those are stored encrypted in the database

MCS isn’t linked clones…..
Sysprep thrashes storage Doesn’t manage AD accounts Store credentials in DB No sysprep, PVS identity management Active AD account management and re-use AD Account import Master VM. If you are creating pooled or dedicated machines, you must prepare a VM that can be copied to provide user desktops. In the case of streamed machines, you prepare a master target device from which the vDisk is imaged by Provisioning Services. For pooled machines, users are not permitted to personalize their desktops, which are exact replicas of the master VM. With dedicated machines, user customization is permitted so the master VM enables you to manage those aspects of the desktop that are common to all users, such as the operating system, antivirus software, and a default set of applications. Pooled and dedicated machines require a master VM that will form the basis of your users' desktops. The master VM should contain all those elements that you plan to manage centrally and will be common to all users, such as antivirus software, Citrix Receiver, or other default programs. In the case of streamed machines, you must install the default programs on a master target device (either a VM or a physical computer) and image the vDisk from this target device using Provisioning Services. Citrix Confidential - Do Not Distribute

Citrix Confidential - Do Not Distribute
When to use which ….. MCS PVS POC / Pilots / Demos Smaller scale VDI To start with Scale will be proved with testing VDI Only POC / Pilots for mixed Large scale VDI FlexCast Mixed desktops Citrix Confidential - Do Not Distribute

Concept of “Quick Deploy” Using MCS
Create a virtual machine (Win7, WinXP or Vista) and install the VDA and other basic applications Install XenDesktop 5 and select all components Select Quick Deploy configuration and use the virtual machine as the master vm Master VM. If you are creating pooled or dedicated machines, you must prepare a VM that can be copied to provide user desktops. In the case of streamed machines, you prepare a master target device from which the vDisk is imaged by Provisioning Services. For pooled machines, users are not permitted to personalize their desktops, which are exact replicas of the master VM. With dedicated machines, user customization is permitted so the master VM enables you to manage those aspects of the desktop that are common to all users, such as the operating system, antivirus software, and a default set of applications. VM specification. If you are creating pooled or dedicated machines, you can specify the number of CPUs, the amount of memory, and the hard disk size for user desktops. These settings are applied to all desktops created with the catalog, even if several different master VMs are specified in the same catalog. Active Directory accounts. If you are creating pooled or dedicated machines, you must create or supply Active Directory computer accounts for the new desktops. For existing and physical machines, you must assign each desktop to both an Active Directory computer account and a user account.

Quick Deploy Installation & Configuration
All components must be on same box Assumes SQL Express on same machine Works with XenServer, Hyper-V or ESX Choice of Pooled or Assigned (VDI) desktops only with single Desktop Group Uses limited desktop naming convention After installation, Desktop Studio runs and you must choose quick deploy, join site or full deploy to get to the full console/dashboard Once configured, you cannot get back to the first option screen.

Quick Deploy. The wizard does all of this…
Site Creates the XD Site with db, WI sites Host Connects to the Hosting Infrastructure Resources Connects to the Storage Infrastructure Master Image Determines the Master VM Image VM Information Specifies the VM Information Users Defines which users can access desktops The Site (farm) is created. The SQLexpress database gets created and then the PowerShell SDK from Desktop Studio talks to services via WCF and tells them where the db is and they register with the database. The Host with hypervisor address is input and the connection object is created. Then assigned desktop group is created. "Initializing components" is creating the WI sites.

…and does this Configuring Host
Identify and configure specified hypervisor connection and hosting unit (via ‘Hyp’ service) Create broker catalog and hypervisor connection Configure ’Acct’ service identity pool Configuring Services Obtain schema creation SQL scripts from services Create database and apply schema creation SQL scripts Point services at newly created database Register and join services with config service Configuring Desktop Group Create broker desktop group (including access policy rule, entitlement policy rule, power time schemes etc) Add machines from catalog to the desktop group Configuring Machine Creation Create machine accounts in the identity pool Create a provisioning scheme by copying master VM Create machines using the provisioning scheme Add machines to the broker catalog

LAB Exercise 1: Quick Deploy LAB Exercise 2: Observe the Installation

Components and Architecture

Desktop Studio Desktop Director WinRM (WMI) SDK available for automation PowerShell WCF Desktop Delivery Controller Machine Creation Service Host Service Virtual Desktop Machine Identity Service Broker Service AD Identity Service Central Config Service XenDesktop 5 has a new Service-Oriented Architecture with the Broker Service, Configuration Service, Host Service and Machine Creation Services ( Machine Creation Service & AD Identity Service & Machine Identity Service ) Wins: Deployment flexibility Division of labor Re-use LCM Costs: ‘Task-oriented’ activities are more complex Cross-SDK search performance Multiple connection points to Hypervisor services SQL Server

SQL Server SQL Database Each service is informed of the database connection details Each service is registered with the central config service Each service has specific database tables created by scripts The XenDesktop installer creates the db called CitrixXenDesktopDB but it could be created by a DBA with the scripts from the DDC. There is a option during configuration called “Generate Scripts”. The session data is real time only. The Connectionlog table will keep some historical data but no other history. (This is 48hrs). Stored procedures are used to create tables and maintain data, evaluate policies, get the state of the VDA, etc. DAL calls Stored Procedures to execute SQL transactions ADO.NET PS c:\>Get-BrokerDBSchema -Databasename vi .\schema.sql

Configuration Schema:
SQL Database: Broker Service Schema Worker Endpoints Worker Registrations Worker Index Worker Names DiagWorker Workers Brokered Sessions Sessions WI Sessions Desktop Groups Desktops Catalogs Licenses Configuration Schema: chb_Config State Schema: chb_State Soft Registrations The Broker Service Schema includes configuration tables and VDA state tables. The state tables is more dynamic with many reads and writes from the brokers.

Main Broker Interactions
Reads/Writes to SQL Database Interacts with WI & AG & NetScaler during launch requests Uses XML component rewritten in .NET License Server Licensing wrapper written in .NET uses License Policy Engine DLL SDK - WCF to PowerShell snap-in Hosting unit – ‘HCL’ and plugins with connection details VDA agent service – WCF/CBP Machine Identity Service ResetVM The XenDesktop 5 DDCs interact with the SQL database. The broker service uses 443/80 and incorporates functionality of XML, IMA, CDS and Pool Mgmt from XD4. The broker interacts with Web Interface, Access Gateway and Netscaler with XML component written in .NET during launch requests. Other interactions include the license server, Desktop Studio, Host services, MCS and VDA.

Broker Service Detailed Interactions
Citrix Confidential - Do Not Distribute

Central Configuration Service
Stores ‘Global’ meta-data about all services Service configuration information Minimizes configuration (avoid WI/XML service situation in future) Minimize dependencies on Active Directory The Central Configuration Service stores configuration meta-data for all services. This minimizes configuration and dependencies on Active Directory.

Site Services Functionality modules that run in the broker service
Runs on only one broker per site (configurable) There is a heartbeat from other brokers so failover will take place if it goes down PS C:\> Get-BrokerSite The only function that runs on a single broker per site is the Site Services. This is a similar concept to the farm master but does not cause a bottleneck since it does not restrict hypervisor communication. The other brokers maintain a heartbeat so failover will take place if this broker goes down. PS c:\> Get-BrokerSite shows which broker is running the site service

What does Site Services do?
Reaper services - finds and marks failed controllers, finds and kills expired launch sessions Cache Refresh - does async AD lookups of DDC, VDA and user names Licensing - communicates with license server to manage ‘permanent’ licenses Registration Hardening – completes soft registered machines Power Policy - manages idle pool levels and initiates policy power actions Group Usage - monitors how many desktops are in use in each group Site Services are functionality modules that run in the broker service. There are a number of site services, each doing its own job within the broker service (but only actually doing it on one of the broker service instances in the site). The set of jobs done by the different site services are: · Controller Reaper (finds and marks failed controllers) · Controller Name Cache Refresh (does async AD lookups of DDC machine names) · Licensing (communicates with license server to manage ‘permanent’ licenses) · BrokerReaper (finds and kills expired launch sessions etc.) · Registration Hardening (finds any soft registered machines that have now been added to groups and hardens the registration) · Worker Name Cache Refresh (does async AD lookups of VDA machine names) · Account Name Cache Refresh (does async AD lookups of user names) · Power Policy (manages idle pool levels and initiates policy power actions) · Group Usage (monitors how many desktops are in use in each group – historical data) · Address Name Resolver (another name resolver – not sure about this one) There are separate site services for each of the items listed, and each site service is dynamically allocated to a DDC at run time separately. There is a site service for each broker hypervisor connection, which has the name of the hypervisor connection. For the site services associated to hypervisor connections (one per HC) you can set which is the ‘preferred’ DDC to run that site service (using the ‘Set-BrokerHypervisorConnection’ cmdlet), but all the other site services are allocated to DDCs automatically. The hypervisor connections are associated to the site rather than to a particular DDC (except this ‘preferred controller’ setting) so the ‘site’ can have 3 different HCs, and they can all the set to have the same DDC as their ‘preferred’ controller or they can be spread out amongst the DDCs in the site.

Hosting Management

Host Management Overview
The Host service is responsible for creating and managing hypervisor connections and Hosting Units. It also provides the browsing facilities for the Hypervisor connections and Hosting Units. HCL Hypervisor Communication Library is used for machine cloning, restart, etc by the MCS and also by broker to stop and start VMs. The Host service is written in .NET and uses legacy plug-ins from XD4. PS C:\> Get-BrokerHyperVisorConnection

Hosting Unit Service Creates and manages hypervisor connections and hosting units Broker service polls the host service for hypervisor credentials and passes them on to the HCL for access to VMs Hypervisor Communication Library (HCL) is a wrapper around the plugins (XS, ESX, HyperV) Does machine cloning Stops and starts VMs The Host service is responsible for creating and managing hypervisor connections and Hosting Units. Hosting Connection is Address(s), Credentials Hosting Unit is Hosting Connection, Storage, Network

Host Connections XenDesktop 5 Site Catalog Catalog SCVMM – HyperV
Virtual Center -ESX XenServer Pool 2 XenServer Pool 1 SCVMM – HyperV Catalog Desktop Groups Broker talks to hypervisor via HCL and plug-ins. Host service is polled for credentials and state of hypervisor by the broker to pass on the HCL and plug-in. A single site can have multiple host connections to various hypervisors. Catalogs of machines can be created from multiple host connections. Desktop Groups can belong to more than one XenServer pool. No limit on group size since there is no longer a bottleneck with one farm master. All DDCs handle launch requests and VDA registration and all DDCs connect to the SQL database. The Host Service is a replacement for Pool Management in XD4.

Power Action Queues Idle Pool Count is configured under "Power Management" in the properties of Desktop Groups Stops/starts performed on hypervisor are queued in the SQL database Throttling is configurable with SDK Power Action Queues- actions to be performed on the hypervisor are queued with priority so not to overload the hypervisor. Throttling of these are configurable. This queue is in the database and can be configured with the SDK PS c:\> Get-BrokerCatalog PS c:\> Get-BrokerHypervisorConnection shows which broker is running the site service PS c:\> Get-BrokerPowerTimeScheme PS c:\> set-BrokerPowerTimeScheme PS c:\> Get-BrokerHostingPowerAction

Power Time Schemes and Policy Actions
Time scheme defines which hours are peak or off peak Time scheme defines the pool size and pool size is the number of machines in the running state Buffer size is the % of machines in the pool to keep in the IDLE state Power Policy Actions are defined for each desktop group Power Time Schemes – Determine which hours are peak/offpeak and what the pool size. The pool size value is the number of machines running. (-1 is a special value meaning don’t do the action) Buffer size is the % to keep IDLE state (one for peak, one for off peak) Power Policy Actions are per desktop group - do <action> after x number of minutes (ie 10 miuntes after logoff, shutdown) Broker SDK - configure catalogs , hypervisor connections, power policy, pool size, power actions

Virtual Desktop Agent 5

VDA 5 Architecture ** New Services: Group Policy Engine
Pvs for VMs Service VDA Registration works the same as XD4 and is logged in the broker.log. Soft and hard registrations are logged. There are two new services in the VDA 5. Group Policy Engine – Applies the settings configured by the HDX policies to the Virtual Desktop and user. Pvs for VMs – used with Machine Creation Services for machine password updates

VDA Installation Registry based VDA registration with FQDN of brokers in the registry during install PowerShell script can be run to set up registry based VDA registration for full desktop deployments Port 80 is default registration port VDA command line options FORCEWDDMREMOVE (for physical or VMware) NOWINRM (for WinXP only) Registry-based discovery. The default mechanism for desktops to find controllers is now registry-based. An Active Directory Organizational Unit is no longer required, although you can still use Active Directory-based registration. Active Directory is still needed in a XenDesktop deployment for authentication and authorization, therefore machines need to be domain-joined regardless of whether you use registry based discovery or not. Unable to Connect to XenDesktop Virtual Desktop Agent on Vista or Windows 7 with WDDM Driver

VDA Installation Post-install configuration
“ConfigRemoteMgmt.exe” tool turns on Remote Access and WinRM “ConfigurationApp.exe” runs a desktop optimization for virtual machines Upgrade the VDA first Not backward compatible VDA 4.0 cannot register with XenDesktop 5 VDA 5.0 can register with XD4 DDC * In place upgrade is supported for VDA Registry-based discovery. The default mechanism for desktops to find controllers is now registry-based. An Active Directory Organizational Unit is no longer required, although you can still use Active Directory-based registration. Active Directory is still needed in a XenDesktop deployment for authentication and authorization, therefore machines need to be domain-joined regardless of whether you use registry based discovery or not. AD Config Wizard is replaced by Powershell script that supplies broker address to the VDA

VDA features Printing enhancements require 12.1 client and VDA 5
Webcam Redirection - Supports OCS New popup welcome screen (can be disabled via GPO) MediaStream disconnect/reconnect - Media Player can now continue playing (pause/resume) after a reconnected session. All XD4 SP1 fixes (Project Medoc) are in the VDA 5 Also for MediaStream, the MmvdHost will also host a seamless plug-in Speedbrowse has been removed CGP now uses SDK ACR Automatic Client Reconnect

LAB Exercise 3 LAB Exercise 4

Desktop Studio

Desktop Studio MMC console for XenDesktop Configuration and Administration Read/writes to DDC, AD and PVS Replaces the Delivery Services Console Desktop Studio. This tool snaps into the Microsoft Management Console (MMC) and enables you to configure and manage your XenDesktop deployment. Desktop Studio provides various wizards to guide you through the process of setting up your environment, creating your desktops, and assigning desktops to users.

Desktop Studio Architecture
XD Services Desktop Studio Configuration The rest of the environment XenServer, VDAs UI Broker Interface MCS Scripts PoSH WCF Host AD Identity 54321 LDAP(S) A scripts layer with PowerShell interacts with broker and PVS . The broker communicates with all other components (XS, VDA….) Uses the public XD API PowerShell SDK so it is extensible Unity.config file controls the layout of Desktop Studio console Built on top of some parts of the MX framework – MMC Bridge + a few support classes Communicates with the rest of the system via Power Shell SDKs (transport mechanism does not need to be known) Bootstraps from configuration service, used to detect all other XD services Active directory communicated with for account lookups and OU browsing PvS only used for creating catalog/adding machines to a PvS based catalog PvS Active Directory

Desktop Studio runs on PowerShell
PowerShell scripts interact with the broker Uses the public XD API PowerShell SDK Unity.config file controls the layout of DesktopStudio console Logging is enabled through mmcsnapin.dll.config file (disabled by default) PowerShell scripts also interact directly with PVS Computers running Desktop Studio must meet the following criteria: One of the following operating systems: Windows Server 2003 (Standard, Enterprise, or Datacenter Edition) with Service Pack 1 or 2 installed (32- and 64-bit versions). Windows Server 2003 R2 (Standard, Enterprise, or Datacenter Edition, (32- and 64-bit versions). Windows XP Professional with Service Pack 3 (32- and 64-bit versions). Windows Vista (32- and 64-bit versions). Windows 7 (32- and 64-bit versions), all editions. Microsoft Windows Server 2008 (32- and 64-bit versions). Microsoft Windows Server 2008 R2. Microsoft .NET Framework, Version 3.5, with Service Pack 1. If you do not have this on your computer, it is installed automatically for you. The XenDesktop installation media also contain this installer in the Support\DotNet35 folder. Microsoft Management Console 3.0 (MMC 3.0) must be installed. Microsoft Windows Installer (MSI) 4.5. If you do not have this on your computer, it is installed automatically for you. Disk space requirements: 75 MB. Microsoft Windows PowerShell version 2.0

Desktop Studio Dashboard
Configurable alerts to the dashboard Can use SDK to get alerts Categories are not configurable Hypervisor may be bottleneck on backend when large amounts of data are collected Same dashboard is part of Desktop Director New terms for VDA Session States in XenDesktop 5 Idle  Ready Disconnected In Use  Connected Not Registered  Unregistered Off Suspended  Off

Error popups in Desktop Studio
Red X can mean that it cannot display correct data – It does a best effort Press CTRL-C for pop up messages to get error details and paste into notepad (when Details>> is not present) PowerShell scripts will be the better way in many cases for large environments Desktop Studio will give a best effort to display data but in large environments or times where there is a lot of data, it may return a RED X. It is expected that enterprise customers will use PowerShell SDKs and scripts to gather data.

Desktop Director

Desktop Director Web based administration for real time data
Designed for Help Desk to monitor and manage Displays session details Search per user / desktop No SSO support at present To install Desktop Director, computers must meet the following criteria: One of the following operating systems: Microsoft Windows Server 2003, Standard or Enterprise Edition, with Service Pack 2 installed Microsoft Windows Server 2003 R2, Standard or Enterprise Edition, with Service Pack 2 installed Microsoft Windows Server 2008, Standard or Enterprise Edition, with Service Pack 2 installed Microsoft Windows Server 2008 R2, Standard or Enterprise Edition, with Service Pack 1 installed (64-bit only) Both 32- and 64-bit versions of the above operating systems are supported, unless stated otherwise. Microsoft .NET Framework, Version 3.5, with Service Pack 1. If you do not have this on your server, it is installed automatically for you. The XenDesktop installation media also contain this installer in the Support\DotNet35 folder. Microsoft Internet Information Services (IIS) and ASP.NET 2.0: For Windows Server 2003 with Service Pack 2, Microsoft IIS Version 6.0. For Windows Server 2008, Microsoft IIS Version 7.0. For Windows Server 2008 R2, Microsoft IIS Version 7.5. If you do not have these on your server, you are prompted for the Windows Server installation media, and they are installed for you. Microsoft WinRM 1.1 or above (WinRM 2.0 is installed automatically by the installer as part of Microsoft Windows PowerShell version 2.0 / Windows Management Framework) To run the web-based Desktop Director, you must use one of the following browsers: On Windows, Microsoft Internet Explorer 7.0 and 8.0, and Mozilla Firefox 3.5. On Macintosh, Apple Safari 4 and Mozilla Firefox 3.5.

Administration Components – Desktop Director
XD Services Broker MCS Host AD Identity Configuration DD website Windows Metrics WMI/WBEM HTTPS WCF WCF Workstation Agent WCF Desktop Director. This Web-based tool enables level-1 and level-2 IT Support staff to monitor a XenDesktop deployment and perform day-to-day maintenance tasks. You can use the Desktop Director to monitor status, such as the health of the hypervisors and controllers in a site. You can manipulate sessions and desktops, such as restarting a desktop or logging off a session. You can also view and interact with a user's session, using Microsoft Remote Assistance, to troubleshoot problems. The browser connects to the Desktop Director website which communicates with the services via WCF. For Windows metrics and other rich data, the broker uses WMI/WBEM to get data from WinRM on the VDA. PortICA

Management through Workflow
Full administrator - Full administration rights. Only local administrators have this role by default and can create further full or delegated administrators Read-only administrator – View all but no changes. Attempted edits will not be saved Machine administrator - owns the catalogs, builds the virtual desktops and specify which Desktop Group administrators can consume the images created Desktop Group administrator – creates desktop groups from catalogs and assigns them to users. Can specify which helpdesk administrators are permitted to support these users Help desk administrator - performs day-to-day monitoring and maintenance tasks, such as restarting a desktop or logging off a session The full delegated administrators functionality that was introduced with XD4 SP1 (Project Jeroboam) is not included in this initial release of XenDesktop 5. It is, however, on the roadmap and should be available in a future release to provide granular control over what each type of administrator can and can’t do.

Viewing WinRM data Provides rich WMI data from VDA such as perfmon, event logs, hardware data and policy reports WinRM is on Windows 7 by default but must be manually installed on WinXP Must have local admin rights on VDA to view in Desktop Director WinRM 2.0 uses port 5985 and is a SOAP service WinRM in VDA installs by default and sends CPU/latency stuff to dashboard when configured in HDX policies The browser connects to the Desktop Director website which communicates with the services via WCF. For Windows metrics and other rich data, the broker uses WMI/WBEM to get data from WinRM on the VDA.

Shadowing Virtual Desktops
Shadowing is done in Desktop Director Uses MS Remote Assistance, not ICA shadowing VDA install turns on Remote Assist by default Remote Assist must be enabled via Group Policy Client side Flash rendering cannot be shadowed Uses DCOM – potential firewall issues, browser settings Can be hidden in the UI and disabled via GPO

Administration Components – Summary
Management Workstation Delivery Controllers Desktop HTTPS WMI/WBEM Web Browser DMC Web App Windows Metrics WCF WCF Workstation Agent MMC 3 Back-end Services WCF WCF PowerShell PortICA Registry GPMC Full Armor Client AD Registry, File System

Active Directory-based Policies

Active Directory based HDX policies
Full Armor implementation same as with XenApp 6 Configured in Desktop Studio and stored in SQL database or configured and stored in Active Directory Desktop Studio will show both GPO and HDX policies Machine policies are reapplied at logon with user policies User policies evaluated at login and re-evaluated on reconnects Backward compatible with XD4 – VDA 5 will translate the XML blob Active Directory-based Policies. XenDesktop 5 uses the Windows Active Directory based policy mechanism for Citrix policies. Citrix policies allow you to control user access or session environments, and are the most efficient method of controlling connection, security, and bandwidth settings. You can specify policies that are shared between XenDesktop and XenApp; for example, you can turn Client Drive Mapping off using one policy.

Active Directory based HDX policies
Site policies, machine policies and user policies are all GPO based so gpupdate /force will update all policies GPO is processed by Windows and Site Policy is processed by Citrix Group Policy service – resultant set of policies is written to the registry Session based policies: HKLM\Software\Policies\Citrix\<session>\... Machine based policies: HKLM\Software\Policies\Citrix\... Machine based defaults (settings): HKLM\Software\Citrix\Group Policy\Defaults\...

Administration Components – Global HDX Policy
PortICA Virtual Desktop Registry Desktop Studio AD Group Policy Service Policies have UI and can be set via Desktop Studio or GPEDIT Settings have no UI, typically don’t change, can be set using the registry Policies and Settings are defined in GPFX files GPFX files are “compiled” to generate accessor APIs \src\ica\HostCore\Policies\...\*.gpfx .GPFX file describes all policies; Accessor API reads policies out of registry as needed EX - icasettings.gpfx contains idle time out settings and the API reads the settings and puts them in the registry

Printing Optimization Policies
Configure resolution, color depth and compression Optimize for better print quality or faster printing Users can also modify print quality by adjusting DPI settings

VM-hosted Applications

VM-hosted Apps Fully integrated with XenDesktop 5 in Desktop Studio
Apps can be launched from same desktop every time App is associated with a desktop and the Access Policy Rule associates an application with a user Provides persistent data and experience for user Checks out a XA license (must be ENT or PLAT XD) Content Redirection - must manually import file types with VDA in maintenance mode with “update file types”

VM hosted apps SharedApp – pooled desktop group will launch the app
PrivateApp – assigned desktop to run the app. Can be pre- assigned or AoFU (App of first use) User initiates RequestAppData which starts with XMLservice BrokerDAL  DB stored procedure which enumerates resources for user AppResoluiton then processes credentials, creates a ticket, ….. gets a brokered session and then launches the VM- hosted app and checks out a license.

LAB Exercise 5 LAB Exercise 6

Scalability and Best Practices

Scalability, Tips and Tidbits
No more bottleneck with farm master (XD4) All DDCs load balance launch requests All DDCs load balance VDA registration All DDCs talk to SQL database Single server scalability - disk I/O could be the bottleneck and logon rate plays a role here DDCs should be close to SQL Server

DB failure = Broker failure = Site failure SQL Mirror – best option for HA Database sizing -150 MB for 20,000 VDAs - more to follow on sizing and scaling SQL transaction log is required for mirroring and could get very large Broker log is enabled in CDSController config – same as in XD4

Multi-site deployment is same as with XD4 (Use WI to aggregate sites) Site services - runs on only one broker per site but there is a heartbeat from other brokers so failover will take place if it goes down AG needs 'TrustRequestsSenttoXMLport=TRUE' (default is FALSE)

Resources Product Documentation
XenDesktop 5 Reference Architecture CXD Citrix XenDesktop 5 Overview XenDesktop 5 Quick PoC Kit (requires mycitrix login) XenDestop Setup Wizard Workaround for XenDesktop 5 and Provisioning Services 5.6

LAB Exercise 7 LAB Exercise 8 LAB Exercise 9

Document management Category Tracking Information Company:

Similar presentations

Presentation on theme: "Document management Category Tracking Information Company:"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Document management Category Tracking Information Company:

Similar presentations

Presentation on theme: "Document management Category Tracking Information Company:"— Presentation transcript:

Similar presentations

About project

Feedback