Desktop Broker Administrator s Guide. Desktop Broker for CitrixPresentation Server Citrix Presentation Server 4.0

Transcription

1 Desktop Broker Administrator s Guide Desktop Broker for CitrixPresentation Server Citrix Presentation Server 4.0

2 Use of the product documented in this guide is subject to your prior acceptance of the End User License Agreement for Citrix Presentation Server 4.0. Note that copies of the End User License Agreement are included in the root directory of the MetaFrame Presentation Server CD-ROM and in the root directory of the Components CD-ROM. Copyright and Trademark Notice Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. Other than printing one copy for personal use, no part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Citrix Systems, Inc. Copyright Citrix Systems, Inc. All rights reserved. Citrix, ICA (Independent Computing Architecture), NFuse, Citrix Solutions Network, MetaFrame, MetaFrame XP, Program Neighborhood, and SpeedScreen are registered trademarks or trademarks of Citrix Systems, Inc. in the United States and other countries. RSA Encryption RSA Security Inc., All Rights Reserved. Trademark Acknowledgements Adobe, Acrobat, and PostScript are trademarks or registered trademarks of Adobe Systems Incorporated in the U.S. and/or other countries. All other trademarks and registered trademarks are the property of their owners. Document Code: September 12, :21 am (KT)

3 Contents 3 Contents Chapter 1 Chapter 2 Chapter 3 Before You Begin How to Use this Guide Using PDF Documentation Finding More Information Citrix on the World Wide Web Document Conventions Welcome Introducing the Desktop Broker for Citrix Presentation Server Why Use Desktop Broker Example Usage Scenarios Key Features Desktop Broker Components Overview Database Schema Database Service Session Manager Desktop Broker Console How It Works Getting Started - A Summary of Steps Planning Your Deployment Supported Deployments Configuration 1: Single Server Configuration 2: Two Servers Verifying Hardware and Software Requirements Database Schema Database Service Session Manager Desktop Broker Console Client Device Requirements

4 4 Desktop Broker Administrator s Guide Pre-Installation Tasks Configure Citrix Presentation Server Configure Web Interface for Presentation Server Configure Windows XP Workstations Create a Database Instance If You Plan to Use a Remote Database Server Create or Nominate a Domain Account Enable Network Distribute Transaction Coordinator (DTC) Access Enable Remote Connections on SQL Server Chapter 4 Installing Desktop Broker Software Pre-Installation Checklist Installing Desktop Broker Software Installing the Database Schema Installing the Database Service Installing the Session Manager Installing the Desktop Broker Console Post-Installation Tasks Enable COM+ Access to the Database Service Add Users or Groups to the Distributed COM Users Group Create and Apply Group Policies Remove Disconnect Option from the Shut Down Dialog Remove the Shutdown Command Remove Access to Context Menus for the Windows Taskbar Remove the Task Manager Other Policies to Disable Optional. Improving Audio Performance Configure Presentation Server Configure Audio Quality on the Web Interface User Specified Audio Quality on the Web Interface Configure Audio Settings on the Client Device Optional. User Experience Enhancements Visual Effects Image Acceleration Uninstalling Desktop Broker Software

5 Contents 5 Chapter 5 Chapter 6 Using Desktop Broker for Citrix Presentation Server Using the Desktop Broker Console Starting the Console Desktop Broker Console Interface Administrative Workflow Creating and Populating Desktop Groups Publishing Hosted Desktops Configuring Presentation Server Client Settings Viewing Status of Desktop Broker Components Using the Database Service Backing Up Your Data Viewing Database Service Status and Error Messages Database Service Session Synchronization Using the Session Manager Command Configuring Password Manager Troubleshooting Important Registry Settings for Desktop Broker Components Known Problems Automatic Session Expiry by Group Policy Administrative Logoff or Reset of Sessions Fails Using Multi-monitor Displays Printing to USB Printers Index

6 6 Desktop Broker Administrator s Guide

7 Before You Begin CHAPTER 1 This chapter contains a brief overview of this guide and other Citrix documentation. The following topics are covered: How to Use this Guide Finding More Information Citrix on the World Wide Web Document Conventions How to Use this Guide This guide is designed to assist Citrix administrators with all administrative tasks related to deploying, maintaining, and using the Desktop Broker for Citrix Presentation Server (Desktop Broker) in a Windows environment. It assumes that you are familiar with: Your Citrix Presentation Server environment, including Windows server and client operating systems The process of publishing applications on computers running Presentation Server The Citrix Presentation Server clients used to access published applications To get the most out of the Desktop Broker Administrator s Guide, review the table of contents to familiarize yourself with the topics discussed.

8 8 Desktop Broker Administrator s Guide This guide contains the following sections: Chapter Chapter 1, Before You Begin Chapter 2, Welcome Chapter 3, Planning Your Deployment Chapter 4, Installing Desktop Broker Software Chapter 5, Using Desktop Broker for Citrix Presentation Server Chapter 6, Troubleshooting Contents Provides an overview of this document. Provides an overview of Desktop Broker for Citrix Presentation Server. Provides an overview of system requirements and things to consider before deploying Desktop Broker for Citrix Presentation Server. Provides instructions for installing and configuring Desktop Broker components. Provides instructions for using the Desktop Broker software. Provides solutions to problems you might encounter during the installation process, or while using the Desktop Broker software. Using PDF Documentation To view, search, and print the PDF documentation, you need Adobe Acrobat Reader or later with Search. Download Adobe Reader for free from Adobe Systems Web site at Finding More Information For additional information, consult the following resources: The online help for the Desktop Broker Console. Use this help system for task-based assistance with the Desktop Broker Console. Display the online help by selecting Help from the Desktop Broker Console menu bar. You can also view context-sensitive help for a specific window by pressing F1 when your mouse focus is in the window. The Web Interface Administrator s Guide. Use this book for information about installing, configuring, and maintaining Citrix Web Interface. The guide is available from the Document Center, or from the Citrix Web site. The Citrix Password Manager Administrator s Guide. Use this book for information about enabling single sign-on or your Citrix environment using

9 Chapter 1 Before You Begin 9 Citrix on the World Wide Web Citrix Password Manager. It is available from the Document Center, or from the Citrix Web site ( The Citrix home page is at The following resources are available from the Citrix Web site: ICA Clients. Download clients for all supported platforms. Select Download. Support options. Access program information about Citrix Preferred Support Services options. Select Support. Software downloads. Find the latest service packs, hotfixes, utilities, and product literature. Select Download. Online knowledgebase. View an extensive collection of application notes, technical articles with answers to frequently asked questions, troubleshooting tips, and white papers. Select Support > Knowledge Center. Discussion forums. Interact with the online Solution Forums in discussions about technical issues with other Citrix users. Select Support > Knowledge Center > Support Forums. Education. Participate in a variety of instructor led training (ILT) and Webbased training (WBT) solutions. ILT courses are offered through Citrix Authorized Learning Centers (CALCs). CALCs provide high quality classroom learning using professional courseware developed by Citrix. Many of these courses lead to certification. These certification programs include Citrix Certified Administrator (CCA), Citrix Certified Enterprise Administrator (CCEA), and the new Citrix Certified Integration Architect (CCIA). Citrix certifications demonstrate the highest level of product knowledge and competency. Citrix WBT courses are available through CALCs, and resellers. Select Education. Contact information. View contact information for Citrix offices, including the worldwide headquarters and headquarters for Asia Pacific, European, and Japan operations. Select Contact. Developer network. Access an open-enrollment membership program that provides access to developer toolkits, technical information, and test programs for software and hardware vendors, system integrators, ICA licensees, and corporate IT developers who incorporate Citrix computing solutions into their products. Select Resources For Developers.

10 10 Desktop Broker Administrator s Guide SDKs. View the free Citrix Server Software Development Kit (SDK). Most of the operations you can perform through Citrix GUI tools can be scripted by using the Citrix Server SDK. The SDK also lets you customize most aspects of Citrix Presentation Server. Select Download > SDKs. Document Conventions The following conventional terms, text formats, and symbols are used throughout the printed documentation: Convention Boldface Italics UPPERCASE Monospace %SystemRoot% Meaning Commands, names of interface items such as text boxes and option buttons, and text displayed at a command prompt. Placeholders for information or parameters that you provide. For example, filename in a procedure means you type the actual name of a file. Italics also are used for new terms and the titles of books. Keyboard keys, such as CTRL for the Control key and F2 for the function key that is labeled F2. Text displayed in a text file. The Windows system directory, which can be WTSRV, WINNT, WINDOWS, or other name specified when Windows is installed. { braces } A series of items, one of which is required in command statements. For example, { yes no } means you must type yes or no. Do not type the braces themselves. [ brackets ] Optional items in command statements. For example, [/ping] means that you can type /ping with the command. Do not type the brackets themselves. (vertical bar) A separator between items in braces or brackets in command statements. For example, { /hold /release /delete } means you type / hold or /release or /delete. (ellipsis) You can repeat the previous item or items in command statements. For example, /route:devicename[, ] means you can type additional devicenames separated by commas.

11 Welcome CHAPTER 2 This chapter contains an overview of the Desktop Broker for Citrix Presentation Server. The following topics are covered: Introducing the Desktop Broker for Citrix Presentation Server Why Use Desktop Broker Example Usage Scenarios Key Features Desktop Broker Components Overview How It Works Getting Started - A Summary of Steps

12 12 Desktop Broker Administrator s Guide Introducing the Desktop Broker for Citrix Presentation Server Organizations who use Citrix Presentation Server to centralize application deployment, can now use the Desktop Broker to centrally deploy and manage desktop environments in the data center. Windows XP workstations, referred to as hosted desktops, are hosted in the data center and published using Presentation Server. The Desktop Broker provides the management interface which makes this possible. Businesses can use the Desktop Broker to provide a virtual work environment for employees who need access to a hosted Windows XP desktop that provides a user experience similar to having a dedicated, physical Windows XP workstation on their desktops. Users can connect, using thin terminals running a Web browser and a Presentation Server client, and access these hosted desktops just as they would a published application. Desktop Broker for Citrix Presentation Server is ideal for deployment at offsite facilities used for development, call centers, back order processing, or other transaction-based tasks where confidential information and intellectual property can be securely stored and maintained in the corporate data center. Why Use Desktop Broker Desktop Broker for Citrix Presentation Server provides the following benefits: Centrally Deploy and Manage Hosted Desktops With Desktop Broker, companies can host Windows XP workstations in their data centers. Users access hosted desktops remotely from a client device using Presentation Server clients. Since the hosted desktops are managed centrally at the data center, IT departments have better control over their client desktop environments. Routine administrative tasks such as installations, upgrades, patches, and backups can be performed without user intervention and disruption of user s productive hours. Retain Control of Offshore Locations from the Data Center The Desktop Broker solution lets companies control the security of their corporate network at remote or offsite facilities. Because remote users access hosted desktops that reside within the enterprise data center, companies can more easily comply with regulatory requirements, while ensuring valuable data and intellectual property does not leave the confines of the data center. Deliver Complete Desktop Environments The Desktop Broker solution extends the application publishing functionality available through Presentation Server to include publishing of complete PC environments that end users find familiar, and which is not limited by hardware or location.

13 Chapter 2 Welcome 13 Provide secure, seamless access to hosted desktops Desktop Broker provides the tools required to centrally deploy, publish, and manage Windows XP workstations in the data center. Individual hosted desktops can be securely accessed by employees in telecommuting, branch office, and Business Process Outsourcing & Offshoring (BPO) work environments. Each user is allocated a dedicated desktop, which can subsequently be customized to his/her requirements. Ensure Business Continuity Deploying Desktop Broker to manage centrally hosted desktops ensures business continuity. In the event of a natural disaster or disruption to important social infrastructure, an employee can access their desktop remotely and still be productive. In general, hosted desktop sessions are not interrupted or affected by one user s desktop crashing. In the event of a crash, support personnel can ensure quick recovery, reprovisioning, and reestablishment of user access to desktop environments. Meet Compliance Requirements The Desktop Broker solution enables organizations to move sensitive data normally stored on a personal computer into the corporate data center to maintain data integrity and meet regulatory compliance requirements (for example, HIPAA, Sarbanes-Oxley, and Gramm-Leach-Bliley). Reduce Costs A standardized, centrally deployed, and managed desktop environment can generate significant savings for the administration, support, and maintenance functions of the IT department. Example Usage Scenarios The following scenarios provide an insight into the benefits that a Presentation Server customer may derive from using Desktop Broker. Offshore Programmers. A leading software development company in the US, has outsourced development of certain software components to a company in India. Programmers are provided an office facility in Bangalore. The Director of Development wants to ensure that all company intellectual property, software tools, and code generated by the offshore programmers remains secure in the datacenter in the US. Citrix consulting staff are advising the company about deploying Desktop Broker for Presentation Server to provide dedicated, hosted desktops to staff located in India. Windows XP workstations are hosted in the data center in New York, offshore programmers use a Windows-based terminal to access dedicated, hosted desktops. All necessary applications and tools are available to the programmers, however all code and related project documents are saved to network locations and remains in the control of the IT department in NY.

14 14 Desktop Broker Administrator s Guide Productivity Workers. The IT department in a leading insurance company is planning IT infrastructure upgrades for the current financial year. They wish to move away from providing personal computers to the data entry staff in their claims processing branch office. The branch office has 50 operators who each use a dedicated Windows XP workstation. The workstations are running Windows XP Professional, an insurance claims processing application that is designed to run on Windows XP, Outlook, and Microsoft Word. The function of these workers is to enter details of insurance claims received by the department. A single data entry operator averages claims entry per day. The support calls received from this department average 20 per day. Resolution of these support calls is expensive and time-consuming as a support person has to personally travel to the branch office and troubleshoot and resolve issues onsite. The operator s work is disrupted and claims entry is delayed until the support call is resolved. To cut costs and streamline operations, the company has retained Citrix Consulting to design and setup a secure, hosted desktop solution. The solution is to move the Windows XP workstations into the data center and invest in Windows based terminals for data entry desktops. Support calls can be resolved in the data center, and a replacement can be provided instantaneously when a problem is logged. Key Features This section describes the key features of the Desktop Broker solution. Centralized deployment All components of the Desktop Broker solution can be deployed in the data center and managed centrally. Significant savings in time and cost of routine maintenance, upgrades, and support can be realized because IT staff have full control of the infrastructure at all times. Scalable The Desktop Broker solution is flexible and can be scaled quickly when you need to deploy additional workstations to meet the needs of a growing user population. You can deploy Desktop Broker as a stand-alone solution, or integrate it into your existing Presentation Server farm to provide your users with access to hosted desktops as published applications. Easy Installation and Management Interface The Desktop Broker software is easy to install and configure. The Desktop Broker Console has an easy to use interface, that you can use to manage user connections to hosted desktops. Pooled and Private Desktops You can use the Desktop Broker solution to deploy pools of generic hosted desktops that any user can connect to as needed. Typically, you d do this in a desktop replacement scenario for productivity workers like data entry personnel who use a single application or suite of applications to their jobs every day. The solution also enables you to deploy pools of hosted desktops that are permanently allocated to individual users on first use. Such workstations can be customized by the associated user and will remain in their control.

15 Chapter 2 Welcome 15 Improved Data Security Deploying Desktop Broker enables companies to have better control of data which normally resides at their remote or offsite facilities. Centrally deployed workstations can be locked down to ensure that valuable data and intellectual property does not leave the confines of the data center. You can also use the Management Console for Presentation Server to control access to client devices, network devices, and so on. Secure, Remote Access Users can work at any location and securely connect to one or more hosted desktops just as if they were at the office. Single Sign-on The Desktop Broker solution provides single sign-on functionality through Citrix Password Manager. This enables users to logon once to a hosted desktop and have their user credentials reused throughout the lifetime of their sessions. Enhanced Manageability Hosted desktops sessions are launched through Presentation Server and therefore, you can use the Management Console for Presentation Server to manage and control access to network resources, user experience, audio, bandwidth control, printing and so on, just as you do for any published application today. Desktop Broker Components Overview To deploy the Desktop Broker solution, it is assumed you have one or more servers running Citrix Presentation Server to provide access to published applications and resources on the enterprise network.

16 16 Desktop Broker Administrator s Guide The following software components need to be installed to deploy a Desktop Broker solution: Database Schema The Database Schema creates and initializes database tables required by the Database Service. The Database Schema must be installed on a server running a Microsoft SQL database instance as described later in this document. Database Service The Database Service is the management component that is responsible for managing database transactions and providing connection details for hosted desktops to the Session Manager in the system. It uses the information in the database to provide the key functionality of machine brokering and session tracking. Session Manager The Session Manager is the component used to launch a hosted desktop connection through Presentation Server. The Session Manager interacts with the Database Service to select the appropriate hosted desktop and exchange information about the current state of the hosted desktop connection. Desktop Broker Console The Desktop Broker Console provides the management interface to the database for the system. System administrators can use the console to create, update, or delete entries for hosted desktops in the database. The Desktop Broker Console also enables administrators to check status of hosted desktop connections and take appropriate actions, if required.

17 How It Works Chapter 2 Welcome 17 To establish a connection to a hosted desktop through the Desktop Broker, the following interactions need to occur: 1. A remote user opens a Web browser to access the Web Interface logon page and enters her user credentials. Alternatively, users can logon through the Program Neighborhood or the Program Neighborhood Agent interface. 2. If authentication is successful, a list of hosted desktops, which the authenticated user has access to, appears. 3. The user initiates the next step by clicking a hosted desktop icon in the web page. 4. An ICA file is sent to the Web browser on the client device in response to the connection request. 5. The Web browser uses the ICA file to establish an ICA session to Presentation Server. 6. The Session Manager is launched within the user s ICA session on Presentation Server. 7. The Session Manager contacts the Database Service and requests connection details to the hosted desktop specified in its command line. 8. The Database Service returns connection details for the specified hosted desktop to the Session Manager.

18 18 Desktop Broker Administrator s Guide 9. The Session Manager launches the RDP client and passes it the connection details for the hosted desktop. 10. The RDP client connects to the hosted desktop specified and starts an RDP session. 11. The Session Manager informs the Database Service that the user has successfully logged on to the hosted desktop and a session is in progress. When a user logs out from the hosted desktop, the following interactions take place before the hosted desktop is released by the system: 1. Logging off from the hosted desktop results in a RDP session logoff. 2. The Session Manager informs the Database Service about the logoff event and the hosted desktop is released. 3. The Database Service updates the status of the hosted desktop as idle/available. 4. The Session Manager terminates the ICA session. Getting Started - A Summary of Steps The following section summarizes the steps you need to perform to deploy Desktop Broker for Citrix Presentation Server. 1. Select the deployment scenario suitable for your environment. See Planning Your Deployment on page 19 for an overview of supported deployment scenarios. 2. Read Verifying Hardware and Software Requirements on page 23 of this book, and prepare the required hardware and software for Desktop Broker components. 3. Read Pre-Installation Tasks on page 26 and complete procedures necessary to prepare your environment before installing Desktop Broker software. 4. Install and configure Desktop Broker components as described in Installing Desktop Broker Software on page Create database entries for hosted desktops you wish to publish, as described in Creating and Populating Desktop Groups on page Publish hosted desktops using the Published Application wizard as described in Publishing Hosted Desktops on page When you complete the steps outlined above, your Desktop Broker deployment is fully functional. For troubleshooting information and known problems at the time of this release, see Troubleshooting on page 65.

19 Planning Your Deployment CHAPTER 3 This chapter covers the planning steps that you will need to consider before you install the Desktop Broker software and publish hosted desktops to your users. The following topics are covered: Supported Deployments Verifying Hardware and Software Requirements Pre-Installation Tasks

20 20 Desktop Broker Administrator s Guide Supported Deployments Depending on the size of your user base and the number of servers running Citrix Presentation Server, you can choose to deploy Desktop Broker in either of the following configurations: All Desktop Broker software components installed on a single server The Session Manager and the Database Service on separate servers. Configuration 1: Single Server This is an acceptable configuration for evaluating the Desktop Broker solution, for serving a small user population. You can install all Desktop Broker software components on a single server running Citrix Presentation Server. You do not require any additional hardware or software to run Desktop Broker for Presentation Server. The deployment comprises the following components: Citrix Presentation Server. A server in the Presentation Server farm also serves as the host for all Desktop Broker components, including the Database Schema, the Database Service, the Session Manager, and the Desktop Broker console. Optionally, you can install the Desktop Broker Console on a separate workstation to enable remote management of hosted desktop connections.

21 Configuration 2: Two Servers Chapter 3 Planning Your Deployment 21 This deployment scenario is suitable for an enterprise sized Citrix Presentation Server farm. The Session Manager is installed on a server running Presentation Server as described in Configuration 1: Single Server on page 20. The Database Schema and the Database Service are installed on a separate server as shown below. The deployment comprises the following components: Citrix Presentation Server A server in the Presentation Server farm also hosts the Session Manager, and the Desktop Broker Console. Optionally, as shown in the illustration above, you can install the Desktop Broker Console on a separate workstation to enable remote management of hosted desktop connections. Database Schema and Database Service The Database Schema must be installed on a server running a supported version of Microsoft SQL. The Database Schema creates and initializes the database tables required for the Database Service to function correctly. After successful installation of the Database Schema, you must also install the Database Service on this server. Consider deploying Desktop Broker in this configuration, if your enterprise infrastructure includes a shared, database server for the Presentation Server farm. Note You can install the Database Schema on a SQL server and install the Database Service on a remote machine, if required. You may need to consider this configuration if best practices dictate that third-party applications cannot be installed on database servers.

22 22 Desktop Broker Administrator s Guide Regardless of the configuration in which you choose to deploy the Desktop Broker solution, your Citrix environment must also contain the following Citrix components: Web Interface provides the Web-based user interface, allowing users to log on to Presentation Server and access hosted desktops. For information about configuring the Web Interface for use with Desktop Broker, see Configure Web Interface for Presentation Server on page 26 Password Manager provides single sign-on functionality, which enables the Desktop Broker software to reuse user credentials entered to log on to the Web Interface to automatically authenticate the user to the hosted desktop. Important If your environment does not contain Password Manager, users must enter their user credentials twice to logon to a hosted desktop. For information about configuring Password Manager for use with Desktop Broker, see Configuring Password Manager on page 62. Client Devices Users access the Web Interface and their hosted desktops using a client device. A client device is any computer capable of running a supported Presentation Server Client and a Web browser (see Client Device Requirements on page 25). Client devices include Windows terminals, desktop PCs, and network computers. Users log on, view, and access their hosted desktops using a Web browser. When they launch a hosted desktop connection, a session is established between the Presentation Server and the client device, allowing the user to access the hosted desktop in the data center. Important For installation and configuration information about the above Citrix software, please see the appropriate product documentation available from the Citrix Presentation Server media or from the Citrix web site. Hosted Desktops Windows XP workstations, which are configured for remote access, running on stand-alone PCs, blade PCs, or in virtual machines. These are the hosted desktops that users access, just as they do published applications through Presentation Server.

23 Verifying Hardware and Software Requirements Chapter 3 Planning Your Deployment 23 Important This guide assumes that you plan to deploy the Desktop Broker for Citrix Presentation Server in a supported deployment scenario as described in Supported Deployments on page 20. Ensure the servers on which you plan to install Desktop Broker software meet the minimum requirements described below. Database Schema The Database Schema must be installed on a server running a database instance such as MSDE or Microsoft SQL Server. Review the following requirements to ensure that the database server on which you intend to install the Database Schema meets the installation prerequisites Hardware Recommended minimum requirements for Microsoft Windows Server Refer to the product documentation or see the Microsoft Web site for more information. Software Microsoft Windows Server 2003 Server with Service Pack 1 Additional 2GB of available hard disk space..net Framework Version 1.1 Microsoft SQL Server 2000 Desktop Engine (MSDE) Release A. or Microsoft SQL Server 2000 SP3a or SQL Server 2005 (Standard, Enterprise, or Express Editions)

24 24 Desktop Broker Administrator s Guide Database Service The Database Service software can be installed on the same server as the Database Schema. Review the following requirements to ensure that the server on which you intend to install the Database Service meets the installation prerequisites: Hardware Recommended minimum requirements for Microsoft Windows Server Refer to the product documentation or see the Microsoft Web site for more information. Software Microsoft Windows Server 2003 Server with Service Pack 1 Additional 2GB of available hard disk space..net Framework Version 1.1 Important On Windows 2003 Server, ensure that Network COM+ access is enabled. For more information this feature, see the Microsoft Knowledgebase article available at Session Manager Review the following requirements to ensure that the server on which you intend to install the Session Manager meets the installation prerequisites: Hardware See the Citrix Presentation Server Administrator s Guide Software Windows Server 2003 with Service Pack 1.NET Framework Version 1.1 Citrix Presentation Server 4.0 (with the latest Hotfix Rollup Pack installed). Web Interface for Presentation Server Optional. Password Manager for Presentation Server to provide single sign-on functionality.

25 Chapter 3 Planning Your Deployment 25 Desktop Broker Console Review the following requirements to ensure that the workstation on which you intend to install the Desktop Broker Console meets the installation prerequisites Hardware Recommended minimum requirements for Microsoft Windows Server 2003 or Microsoft Windows XP. Refer to the product documentation or see the Microsoft Web site for more information. Software Windows Server 2003 with Service Pack 1 or Microsoft Windows XP with Service Pack 2..NET Framework Version 1.1 Client Device Requirements To operate with the Desktop Broker, your client devices must have a supported Presentation Server Client and Web browser. Client software is available on the Citrix Presentation Server media or you can download them for free from the Citrix Web site. For detailed information about Presentation Server Clients, refer to the appropriate client Administrator s Guide.

26 26 Desktop Broker Administrator s Guide Pre-Installation Tasks Before you install Desktop Broker software, you need to complete the following tasks to prepare your Presentation Server environment. Configure Citrix Presentation Server Ensure Presentation Server is configured and running correctly. Refer to the Citrix Presentation Server 4.0 Administrator s Guide, available from the Citrix Knowledgebase, /Administrators_Guide.pdf, for detailed information. Configure Web Interface for Presentation Server In a Desktop Broker deployment, you need to configure Web Interface so that it can correctly handle published, hosted desktops. These configuration changes are required to enable Presentation Server sessions to run in full-screen mode and capture special key combinations. The configuration changes need to be applied to the default ICA file that the Web Interface uses to generate ICA files for each published resource. Typically, this file resides in the location, \Inetpub\wwwroot\Citrix\MetaFrame\conf\default.ica. To modify the default.ica file, do the following: 1. Open the default.ica file using a text editor, such as Notepad. 2. Add the following parameters to the [Applications] section: ; enable seamless windows DesiredHRES=-1 DesiredVRES=-1 TWIMode=On ; pass Windows key combination to the remote session whenever it has focus TransparentKeyPassthrough=Remote ; prevent user from shutting down CPS server DisableCtrlAltDel=On 3. If you selected the Enable bandwidth control checkbox in the Manage Client Connection Settings task in the Web Interface configuration screen, you also need to apply the above changes to the following files: C:\Inetpub\wwwroot\Citrix\MetaFrame\conf\bandwidth_high.ica C:\Inetpub\wwwroot\Citrix\MetaFrame\conf\bandwidth_low.ica C:\Inetpub\wwwroot\Citrix\MetaFrame\conf\bandwidth_medium.ica C:\Inetpub\wwwroot\Citrix\MetaFrame\conf\bandwidth_medium_high.ica

27 Configure Windows XP Workstations Chapter 3 Planning Your Deployment 27 The following procedures must be completed to ensure that users are able to access Windows XP desktops available in the data center. Ensure the Windows XP desktops you plan to use as hosted desktops are started and running in the data center. Configure the Windows XP desktop (s) to allow remote access using RDP. For instructions about configuring Windows XP to enable remote access, see Make note of the IP addresses, fully qualified domain names, or host names of the workstations on which these Windows XP desktops are running. Create a Database Instance The Database Schema must be installed on a server running a database instance such as Microsoft SQL Server or MSDE. The Database Schema creates and initializes data tables required for functioning of the Desktop Broker system. For information about compatible database products which you can use, see minimum requirements outlined in Database Schema on page 23. To create a database instance, follow the procedure outlined below: 1. Ensure you have a database such as SQL Server or MSDE installed and running. 2. Create a database instance, as follows: If you are running MSDE 2000, use the following command to create a database instance name: setup INSTANCENAME=<instance name> SAPWD=<password> This creates a database instance named instance name. Alternatively, if you are running SQL Server editions, use the Setup Wizard to create a database instance. Refer to the appropriate SQL Server documentation for instructions about doing this. Make a note of the database location (either the server hostname or the database instance name) so you can enter it when you are prompted during Database Schema installation.

28 28 Desktop Broker Administrator s Guide If You Plan to Use a Remote Database Server If you plan to deploy the Database Schema on a SQL server and the Database Service on a different machine, first ensure that both machines are in the same, or in a trusted, domain. You also need to complete the following procedures to ensure that the two machines can communicate with each other. Create or Nominate a Domain Account The nominated domain account acts as the security principal and is used for communications between the Database Service and the SQL server. Ensure that you use best practice security guidelines to ensure the nominated domain account is secured with a strong password and has only necessary privileges. Make a note of the particulars of this domain account and nominate it during Database Schema and Database Service installation. Enable Network Distribute Transaction Coordinator (DTC) Access Network Distributed Transaction Coordinator (DTC) access must be enabled on the SQL Server on which you plan to install the Database Schema, as well as on the server running the Database Service. This enables the Database Service to access the database tables created by the Database Schema for transaction processing. For instructions about enabling network DTC access, see the Microsoft Knowledgebase article at Enable Remote Connections on SQL Server If you plan to install the Database Schema on a server running a SQL 2005 and the Database Service on a separate machine, you must enable remote access on the SQL Server. Detailed instructions about enabling SQL Server 2005 for remote connection and configuring firewalls, if necessary, are provided in the Microsoft Knowledgebase article available at Note If you plan to install an instance of MSDE 2000, use the command line switch, DISABLENETWORKPROTOCOLS=0, during database installation.

29 Installing Desktop Broker Software CHAPTER 4 This chapter contains complete instructions for installing and configuring the Desktop Broker for Presentation Server. Topics in this chapter include: Pre-Installation Checklist Installing Desktop Broker Software Post-Installation Tasks Uninstalling Desktop Broker Software

30 30 Desktop Broker Administrator s Guide Pre-Installation Checklist Before you begin installing Desktop Broker software, make a note of the following information for reference during installation and configuration of Desktop Broker components. Item Details Examples Details of Windows XP workstations that you plan to deploy as hosted desktops Database Schema Database Service Domain account for communications between the SQL Server and the Database Service List of IP addresses, fully qualified domain names, or host names of the workstations or servers running Windows XP instances. Ensure all of the workstations you list here are accessible from the Presentation Servers in the farm. Address of the server on which you plan to install the Database Schema and the Database Service components. A server address can be specified in the form of an IP address, or a hostname. Name of the database instance created using the procedure described previously. This domain account must be nominated during installation of the Database Schema and the Database Service. Desktop Broker Console Determine which user(s) or groups need access privileges to the Desktop Broker Console. After installation, configure access to the Desktop Broker Console to allow these users/groups sufficient access privileges so they can perform administrative tasks , or pc01.company.com, or pc or CPSHost01 hostname\dbinstance domain\dbcps_comms Important Ensure that all servers and workstations running Desktop Broker components are members of the same network domain.

31 Installing Desktop Broker Software Chapter 4 Installing Desktop Broker Software 31 From the Citrix web site, download the Desktop Broker installation package, DBCPSweng.exe, to a temporary folder and extract its contents. Run the Desktop Broker installation wizard, DesktopBroker.exe, to install Desktop Broker components. Citrix recommends that you install Desktop Broker components in the sequence that they appear above. Installing the Database Schema 1. Log on as an administrator to the server running the database instance you created previously as described in Create a Database Instance on page Run the Desktop Broker installation wizard, DesktopBroker.exe. 3. Click Database Schema (install this first!).

32 32 Desktop Broker Administrator s Guide 4. The Database Schema Setup wizard appears. 5. Accept the end-user license. 6. You are prompted to enter the name of a valid database instance and nominate a Windows user account. Enter the name of the database instance you created previously and the Windows user account as discussed in Create or Nominate a Domain Account on page 28. Click Next. 7. Click through the remaining setup wizard screens, and click Finish.

33 Installing the Database Service Chapter 4 Installing Desktop Broker Software Log on as an administrator to the server reserved for Database Service installation. 2. Run the Desktop Broker installation wizard, DesktopBroker.exe. 3. Click Database Service. The Database Service Setup wizard appears. 4. Accept the end-user license. 5. You are prompted to enter details of the database instance and a Windows user account. The values you enter for the SQL Server instance and Windows user account

34 34 Desktop Broker Administrator s Guide should be identical to the values you entered during Database Schema installation. Also enter the correct password for the Windows user account. Click Next. 6. The wizard prompts you to accept the default installation folder location, %ProgramFiles%\Citrix\Desktop Broker\Service. To choose a different installation folder, click Browse and select a different installation folder. Click Next. 7. Click through the remaining setup wizard screens, and click Finish. Installing the Session Manager The Session Manager application must be installed on a server running Citrix Presentation Server 4.0. To install the Session Manager application, follow procedure described below: 1. Log on as an administrator to the Presentation Server reserved for Session Manager installation. 2. Run the Desktop Broker installation wizard, DesktopBroker.exe. 3. Click Session Manager. The Session Manager Setup wizard appears.

35 Chapter 4 Installing Desktop Broker Software Accept the end-user license. 5. Enter the IP address or hostname of the server running the Database Service, if it was installed on a different server(s). Click Next.

36 36 Desktop Broker Administrator s Guide 6. The wizard prompts you to accept the default installation folder location, %ProgramFiles%\Citrix\Desktop Broker\Session Manager. To choose a different installation folder, click Browse and select a different installation folder. Click Next. 7. Click through the remaining setup wizard screens, and click Finish. For information about using the Session Manager command, see Using the Database Service on page 59. Installing the Desktop Broker Console The Desktop Broker Console snaps into the Microsoft Management Console (MMC) to provide a central, easy to install, and easy to use location for managing your Desktop Broker deployment. You can install the Desktop Broker Console on computers other than those running the Database Service or the Session Manager, such as workstations and laptop computers. Important Ensure the server running the Database Service is accessible from the machine running the Desktop Broker Console. The Desktop Broker Console is used to administer and manage the contents of the Desktop Broker database, which contains information about hosted desktops available in the data center. To install the Desktop Broker Console application, follow steps outlined below: 1. Log on as an administrator to the workstation on which you wish to install the Desktop Broker Console. 2. Run the Desktop Broker installation wizard, DesktopBroker.exe.

37 Chapter 4 Installing Desktop Broker Software Click Desktop Broker Console. The Desktop Broker Console Setup wizard appears. 4. Accept the end-user license. 5. Enter the hostname of the server running the Database Service and click Next. 6. The wizard prompts you to accept the default installation folder location, %ProgramFiles%\Citrix\Desktop Broker\Console. To choose a different installation folder, click Browse and select a different installation folder. Click Next. 7. Click through the remaining setup wizard screens, and click Finish.

38 38 Desktop Broker Administrator s Guide Post-Installation Tasks The following sections describe procedures you need to complete to prepare your environment prior to publishing hosted desktops. Enable COM+ Access to the Database Service The Database Service is a COM+ application. To enable COM+ applications to work remotely, a number of additional configuration steps need to be performed as described below: 1. Select Start > Control Panel. 2. Select Add Remove Programs. 3. In the Add Remove Programs window, click Add/Remove Windows Components icon. The Windows Component Wizard appears. 4. Scroll through the listed components and ensure the Windows component Application Server > Enable Network COM+ Access is installed. If this component is missing, install it before you proceed further. Add Users or Groups to the Distributed COM Users Group Complete the following procedure if you deployed Desktop Broker software as described in Configuration 2: Two Servers on page 21. In Windows 2003 Server SP1, a new group was added to restrict network access to COM+ applications. Because the Database Service is a COM+ application, you must add users or groups attempting to access the Database Service to the Distributed COM Users group. To add users or groups to the Distributed COM Users Group, follow the procedure described below: 1. Select Start, right-click My Computer and select Manage. 2. Browse to System Tools > Local Users and Groups > Groups 3. In the right pane, right click Distributed COM Users group and select Properties. 4. Add entries for the domain users or groups who will access the Database Service. The following categories of users need to be added: All administrative user accounts that will operate the Desktop Broker Console. The Desktop Broker Console is used for administrative tasks such as adding, modifying, or deleting hosted desktops.

39 Chapter 4 Installing Desktop Broker Software 39 Any end user accounts which will be used to launch and run a hosted desktop from a client device. By default the Database Service permits Everyone unrestricted access privileges. Citrix recommends that you edit the default settings to restrict access to the Database Service. You also need to modify access privileges to the Database Service as outlined below: 1. Select Start > Administrative Tools > Component Services. 2. In the MMC window, browse to Component Services > Computers > My Computer > COM+ Applications > Desktop Broker Database Service > Roles. The following sub-nodes are available under the Roles node: RDBAdministration: This role controls access to performing tasks such as adding a new hosted desktop. RDBManagement: This role controls access to the functions used by the Session Manager to request a hosted desktop for use and release it when it has been disconnected, that is, all users who will connect to hosted desktops need to be in this role. Under each role is a Users folder. Observe that the Everyone account is already listed in the Users folder of both roles. 3. Edit the entries in the Users folder as appropriate. At a minimum, Citrix recommends that you do the following: Delete the Everyone entry from the RDBAdministration role. Add an Administrator group or administrator users to the role. It may seem that setting the permissions for the Database Service coincides with the configuration you performed earlier using the Distributed COM Users group, and to a degree it does. It is important to perform both configuration steps because: Configuring only the Distributed COM Users group does not prevent regular users (who launch hosted desktops) from accessing the Database Service. If your server was running multiple COM+ applications that need to be remotely available, then all users of all your COM+ applications need to be in the Distributed COM Users group. However, you probably do not want all these users accessing every COM+ application.

40 40 Desktop Broker Administrator s Guide Create and Apply Group Policies As a best practice, Citrix recommends that the workstations you deploy as hosted desktops are members of a domain to which group policies can be applied. To ensure that the Desktop Broker solution runs correctly in your environment, you need to create and apply the following key group policies to Users and Groups who will access hosted desktops, and to Computers which are published as hosted desktops in the domain. Remove Disconnect Option from the Shut Down Dialog This policy is essential to ensure the integrity of the Desktop Broker solution. Apply this policy to all Users or Groups who need to connect to hosted desktops. Locate this policy under Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Remove Disconnect option from Shut Down dialog and set it to Enabled. Important Failure to apply this group policy can result in incorrect synchronization of session states in the database. Remove the Shutdown Command This policy setting removes the Shut Down option from the Windows Start menu. It also disables the Shut Down command on the Windows Security dialog box, which appears when you press the CTRL+ALT+DEL key combination in a hosted desktop session. This setting is required to prevent users from pressing Shut Down within a hosted desktop session. If you press Shut Down in a hosted desktop session, the hosted desktop could be set to a failed state in the database, which would require manual intervention from the system administrator. Apply this policy to all Users or Groups which connect to hosted desktops. Locate this policy under Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Remove Windows Security item from Start menu and set it to Enabled. Remove Access to Context Menus for the Windows Taskbar This setting is optional and is recommended to prevent user initiated Restart or Shut Down from the Task Manager. Enabling this policy prevents users accessing hosted desktops from starting the Task Manager (taskmgr.exe); it serves to hide the context menu that appears when you right-click the Windows Taskbar. The Windows Taskbar context menu

41 Chapter 4 Installing Desktop Broker Software 41 provides access to items such as the Start button, the clock, and other taskbar icons and buttons. Locate this policy under User Configuration\Administrative Templates\Start Menu and Taskbar\Remove access to the context menus for the taskbar and set it to Enabled. If you enable this policy, users attempting to start the Task Manager will see a message explaining that a group policy disabling access to the Task Manager is in force. Remove the Task Manager The Windows Task Manager provides users with controls to start and stop programs, monitor the performance of their computers, view and monitor all programs running on their computers, including system services, find the executable names of programs, and change the priority of the processes in which programs run. This setting is optional, however Citrix recommends removing access privileges to the Task Manager for all users/groups who need access to hosted desktops. Locate this policy under User Configuration\Administrative Templates\System\Ctrl+Alt+Del Options\Remove Task Manager and set it to Enabled. Other Policies to Disable Citrix recommends that you also disable the following group policies which specifically apply to ICA connections, to ensure the integrity of the Desktop Broker solution. Time Limit for Active but Idle Sessions. This policy is found under Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Sessions and at User Configuration\Administrative Templates\Windows Components\Terminal Services\Sessions and is used to set a time-out limit for sessions that are active but idle. Time Limit for Disconnected Sessions This policy is found under Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Sessions and at User Configuration\Administrative Templates\Windows Components\Terminal Services\Sessions and is used to set a time-out limit for disconnected sessions.

42 42 Desktop Broker Administrator s Guide Optional. Improving Audio Performance The default audio settings for Desktop Broker connections are not optimized for high quality audio playback. If your users require better audio quality over a hosted desktop connection, complete the procedures below. Configure Presentation Server You can configure Presentation Server to allow users to customize audio quality. A default installation of Presentation Server has audio quality for all ICA connections set to Medium. To allow users to select a higher quality setting, do the following: 1. Click Start > All Programs > Citrix > Administration Tools and select Citrix Connection Configuration Tool. 2. Right click the ica-tcp connection and select Edit. 3. Select ICA Settings. 4. Select High from the combo-box. Note This does not make ICA connections use high quality audio. This simply enables users to set audio quality to High, if desired. Configure Audio Quality on the Web Interface The default sound quality setting for ICA sessions launched through the Web Interface can be changed by modifying the template ICA file on the server which is pushed down to the ICA Client. To do this: 1. Log on as an administrator to the server running the Web Interface. 2. Start Notepad and open the file, \Inetpub\wwwroot\Citrix\MetaFrame\conf\default.ica. 3. Browse to the [Application] section in the file and under this section, add the following parameter and save the file: AudioBandwidthLimit=0 Clients connecting henceforth are forced to use the audio setting specified on the server. User Specified Audio Quality on the Web Interface You can also allow users connecting through the Web Interface to configure audio quality as per their requirements. To begin with, you must configure Presentation Server to allow client-side, audio configuration. To ensure that the client device has sufficient permissions, do the following:

43 Chapter 4 Installing Desktop Broker Software Log on as an administrator to the server on which you installed the Access Suite Console for Presentation Server. 2. Click Start > Citrix > MetaFrame Presentation Server > Access Suite Console for Presentation Server. The Access Suite Console is displayed. 3. In the Console, expand Suite Components > Configuration Tools > Web Interface and select the Web Interface site you wish to configure. 4. Select Manage client connection settings from the commands listed in under Common Tasks. 5. Select the Allow user to customize audio quality checkbox and click OK. Henceforth, users logging on to the Web Interface can customize audio quality using controls on the Web Interface page. To customize the audio quality, users need to do the following: 1. Logon to the Web Interface as a valid user. 2. Locate the three icons at the top right of the section that lists available applications. 3. Select the icon in the middle with the tooltip Click here to customize the user interface. 4. Select Connection Preferences. 5. Choose the desired audio quality in the Audio Quality combo-box. 6. Click OK. Note If you configured sound settings as described in Configure Audio Quality on the Web Interface on page 42, users need not perform the procedure described above. Configure Audio Settings on the Client Device There are a range of options for specifying the sound quality that Presentation Server Clients use. Depending on the method used to launch ICA connections, these may be on the client or server side. These options are discussed below. If none of these methods are used, then audio quality is set to Medium; this is the default audio quality setting on the server and cannot be changed. Citrix Program Neighborhood - Custom ICA Connections To modify audio quality properties for custom ICA connections defined in Citrix Program Neighborhood, do the following: 1. Right-click the custom ICA connection and select Properties.

44 44 Desktop Broker Administrator s Guide 2. In the Properties window, select the Options tab. 3. Clear the Sound custom default checkbox. 4. Ensure the Enable sound checkbox is selected. 5. From the Sound quality combo-box, select the sound quality setting you need. Citrix Program Neighborhood - Application Sets To modify audio quality properties for an application set, do the following: 1. Right click the application set you wish to configure and select Application Set Settings. 2. Clear the Server sound default checkbox. 3. Select the Enable Sound checkbox. 4. Select the desired Sound quality from the combo-box. Citrix Program Neighborhood Agent To modify audio quality properties for the Citrix Program Neighborhood Agent, do the following. 1. Right click the Program Neighborhood Agent icon in the taskbar and select Properties. 2. Select the Session Options tab in the dialog displayed. 3. In the combo-box at the bottom of the window, select the audio quality you require.

45 Chapter 4 Installing Desktop Broker Software 45 Optional. User Experience Enhancements You can configure the following user experience policies available on Presentation Server to improve the overall performance of hosted desktop sessions over slow connections. Visual Effects Windows visual enhancements such as displaying the desktop background, animation of menu items, and displaying contents of windows while dragging can be disabled using a policy in the Presentation Server Management Console. To set these policies, do the following: 1. Open the Management Console for Citrix Presentation Server. 2. On the left pane, select and right-click Policies and select Create Policy from the context menu. 3. Enter an appropriate policy name and a description to match. 4. Select the Optimize initial policy settings for a connection type checkbox, to apply this policy for specific connection speeds. 5. In the Policy Properties window, expand the Bandwidth node on the left pane. 6. Expand the Visual Effects node. 7. Select the Turn off desktop wallpaper option. 8. Select the Turn off menu animations option. 9. Select Turn off window contents while dragging option 10. Click OK to save and close the Policy Properties window. 11. You must now apply this policy by a filter type as follows: In the Management Console window, right-click the entry for the newly created policy and select Apply this policy to from the context menu. Select from the five available filter types to apply the policy. Image Acceleration To improve the user experience of hosted desktop sessions in a LAN environment, we recommend configuring Image Acceleration settings. This prevents image compression being applied to hosted desktop sessions. You can however set image compression policies for users on slow connections or those connecting from remote sites.

46 46 Desktop Broker Administrator s Guide To configure Image Acceleration settings, do the following: 1. Open the Management Console for Citrix Presentation Server. 2. On the left pane, select and right-click Policies and select Create Policy from the context menu. 3. Enter an appropriate policy name and a description to match. 4. Select the Optimize initial policy settings for a connection type checkbox, to apply this policy for specific connection speeds. 5. In the Policy Properties window, expand the Bandwidth node on the left pane. 6. Expand the SpeedScreen node. 7. Select the Image acceleration using lossy compression option. 8. Select the Use lossy compression to compress images option. 9. Select Medium compression; good image quality from the list. 10. Select the Restrict compression to connections under this bandwidth checkbox. We recommend enabling this option to limit the compression applied to sessions over slow connections. 11. Set a Bandwidth threshold, for example 128Kb. 12. Click OK to save and close the Properties window. 13. You must now apply this policy by a filter type as follows: In the Management Console window, right-click the entry for the newly created policy and select Apply this policy to from the context menu. Select from the five available filter types to apply the policy. Uninstalling Desktop Broker Software To remove Desktop Broker components from a server or workstation, use the Add/Remove Programs option as described below: 1. Click Start > Settings > Control Panel > Add or Remove Programs. 2. In the Add or Remove Programs window, select the Desktop Broker application that you wish to remove and click Change/Remove. 3. Follow the uninstall prompts to remove the software.

47 Using Desktop Broker for Citrix Presentation Server CHAPTER 5 This chapter describes the administrative workflow required to configure the Desktop Broker solution and publish hosted desktops for use. Topics include: Using the Desktop Broker Console Using the Desktop Broker Console Viewing Status of Desktop Broker Components Using the Database Service Using the Session Manager Command Configuring Password Manager

48 48 Desktop Broker Administrator s Guide Using the Desktop Broker Console The Desktop Broker Console provides a management interface that enables you to administer and manage your deployment. The Desktop Broker Console is a stand-alone snap-in to the Microsoft Management Console (MMC). Starting the Console You use the console to configure and manage entries for hosted desktops and to monitor user connections. To start the console Choose Start > Programs > Citrix > Management Consoles > Desktop Broker Console. Desktop Broker Console Interface The main user interface of the Desktop Broker Console consists of two panes: The left pane contains the console tree. The details pane on the right displays items and information associated with the selected node in the console tree. In addition, the tool bar at the bottom of the right pane displays command buttons associated with the contents of the right pane.

49 Chapter 5 Using Desktop Broker for Citrix Presentation Server 49 Typically, you move around in the console as follows: Selecting a node in the left pane updates the items and information displayed in the details pane. To modify or otherwise administer an item, you select it, and click a command button in the tool bar at the bottom of the details pane. The following nodes are available in the console tree: Desktop Broker This console tree provides details about the contents of the Desktop Broker database table. At first use, the database table is empty. You need to create entries for the following: Desktop Group A desktop group is a named, logical group that constitutes a firstlevel node in the Desktop Broker Console. A desktop group is enabled for use if the Enable Desktop Group checkbox is selected; attempting to launch Session Manager with a desktop group which is not enabled for use, results in a connection launch error. Click a desktop group name to view its contents. Typically, an administrator may create desktop groups for the various departments in the company, such as Finance, Engineering, and Legal. When a member of the Engineering staff attempts to access a published hosted desktop, the Desktop Broker system retrieves and allocates a hosted desktop from the respective departmental desktop group. A desktop group contains one or more desktop revisions. Desktop Revision Lists the desktop revisions available in the selected desktop group. A desktop revision is a named, logical group that constitutes a second-level node in the Desktop Broker Console. A desktop revision contains one or more hosted desktops. The term, desktop revision, implies that the hosted desktops contained within, were added to the database with a fixed set of system data; including the operating system (for example, Windows XP, Service Pack 2 and other system patches), applications (that is, a particular version of Microsoft Office, Acrobat Reader, WinZip, etc.), and a standard set of system utilities (for example, antivirus, personal firewall, etc.). For example, a desktop revision called SAP_Apps contains one or more hosted desktops running SAP applications used by staff in the Finance department.

50 50 Desktop Broker Administrator s Guide Only one desktop revision can be set to active at a given time. The concept of active/inactive desktop revisions is particularly useful for migration purposes. For example, a desktop revision called WindowsXP_SP1 is currently active and is reserved for Finance personnel. When IT Services needs to roll out Windows XP Service Pack 2, the system administrator can create a new desktop revision, called WindowsXP_SP2 containing workstations running Windows XP with Service Pack 2. When the hosted desktops are ready for use, the administrator sets Windows XP SP2 desktop revision as active. The Desktop Revision called Windows XP, SP1 is now inactive and can be retired. A new desktop revision contains pooled hosted desktops unless you select the Contains Private Hosted Desktops checkbox. In a desktop revision containing pooled machines, allocation of hosted desktops occurs on a per session, first-comefirst-served basis. A desktop revision that contains private hosted desktops is no different from one which contains pooled hosted desktops. The difference occurs during hosted desktop allocation. When a hosted desktop at is accessed by a user, for example, User A, for the first time, it is thereafter permanently associated with that user account. Subsequent connection requests from User A for a hosted desktop always results in the allocation of the hosted desktop at IP address As a result, User A now owns the private hosted desktop with the IP address, A combination of private and pooled hosted desktops in a desktop revision is not supported. Selecting a desktop revision, displays its contents in the details pane. You can add entries for hosted desktops to a desktop revision. Hosted Desktops A hosted desktop is a description of a machine, running Microsoft Windows XP, hosted in the data center. When you add a hosted desktop entry, you need to provide the following details: Hostname / IP Address: Specify a valid hostname, IP address, or Fully Qualified Domain Name (FQDN) for a machine running Windows XP. The value specified here is used to establish an RDP connection to the hosted desktop machine. Enable Hosted Desktop: Select the checkbox to mark this hosted desktop as available for allocation. Clear this checkbox if you wish to make this hosted desktop unavailable. After you add a hosted desktop to the database, the following additional information is displayed in the details pane.

51 Chapter 5 Using Desktop Broker for Citrix Presentation Server 51 Administrative Workflow User: Displays the Domain/Username of the user account currently logged on to the hosted desktop. State: Displays the current state of the hosted desktop. A hosted desktop can be in one of the following states: Idle: No connection exists and the hosted desktop is available for allocation to a user. Initializing: A request for a hosted desktop connection has been received. Authenticating: Authentication required for a connection is taking place. Logged On: An active connection to a hosted desktop exists. Disconnected: This state can result because of an interruption to the hosted desktop connection, possibly due to a network failure. The hosted desktop in this state is still associated with the current user; in this case the current user can attempt to reconnect by clicking the connection icon. Failed: The connection to the hosted desktop was interrupted because the Session Manager is unable to contact the Database Service, or the hosted desktop is unavailable. When a hosted desktop is in a failed state, you can reset it, so that it is made available for use. Host Presentation Server: The Presentation Server through which this hosted desktop is published. Date Created: The date this hosted desktop was created. After you install Desktop Broker software, you can use the Desktop Broker Console to create database entries in the database, for hosted desktops in the data center, prior to publishing them for use. The workflow requires you to perform the following tasks: Starting the Console on page 48 Creating and Populating Desktop Groups on page 52 Publishing Hosted Desktops on page 54 Configuring Presentation Server Client Settings on page 57 The following sections contain detailed procedures to help you perform the above tasks.

52 52 Desktop Broker Administrator s Guide Creating and Populating Desktop Groups As described in previous sections, a desktop group is a named, logical group that constitutes a first-level node in the Desktop Broker Console tree. A desktop group contains one or more desktop revisions, of which, one must be active. Each desktop revision, contains one or more hosted desktops. The following procedures describe creation of a desktop group, a desktop revision, and addition of hosted desktop entries to the desktop revision. To create a desktop group 1. To start the Desktop Broker Console, choose Start > Programs > Citrix > Management Consoles > Desktop Broker Console. 2. Right-click the Desktop Broker node. 3. Select Add Desktop Group from the context menu. The Add Desktop Group dialog box appears. 4. Enter a maximum of 128 characters as the Desktop Group Name, for instance, Finance The Enable Desktop Group checkbox is selected as default. To disable the desktop group, clear the checkbox. 6. Click OK to continue. To create a desktop revision 1. In the Desktop Broker console tree, right-click the Desktop Group (for example, Finance01) in which you wish to create a new desktop revision and select Add Desktop Revision. The Add Desktop Revision dialog box appears.

53 Chapter 5 Using Desktop Broker for Citrix Presentation Server Enter a maximum of 128 characters as the Desktop Revision Name, for instance, WinXP_SP2. 3. Enter a suitable description of upto 1024 characters, in the Description field. 4. If you wish to allocate hosted desktops for private use from this Desktop Revision, select the Contains Private Desktop checkbox. 5. Click Add to complete creation of the new desktop revision. To add one or more hosted desktops 1. In the Desktop Broker Console tree, navigate to the Desktop Revision node to which you wish to add a new hosted desktop. 2. Right-click the entry for the Desktop Revision and select Add Hosted Desktops. The Add Desktop dialog box appears. 3. In the Add Desktop dialog box, enter a maximum of 256 characters as the hostname, IP address, or FQDN for the hosted desktop you wish to add. To add multiple entries, enter details of each desktop on a separate line. Important Ensure that the IP address, FQDN, or host name that you enter, exists and is accurate. The system does not verify if the hosted desktop exists. 4. The Enable Desktop checkbox is selected as default. To disable the desktop, clear the checkbox. 5. Click Add to complete procedure.

54 54 Desktop Broker Administrator s Guide Publishing Hosted Desktops When you have created desktop groups, desktop revisions and added hosted desktops to the database using the Desktop Broker Console, you can use the Published Application wizard on Presentation Server to publish hosted desktops for use. Important Before you proceed, ensure that the hosted desktops you plan to publish, are running and are accessible remotely. 1. Launch the Published Applications wizard on Presentation Server. In the Welcome screen, enter appropriate values in the Display Name and Application Description fields. Click Next. The Specify What to Publish screen appears.

55 Chapter 5 Using Desktop Broker for Citrix Presentation Server In the Specify What to Publish screen, for Application Type, select Application and press TAB. The Command Line contains the path to the executable for the Session Manager, that is, SessionManager.exe. Use the Browse button to locate and select the file. Append the name of the desktop group (for example, Finance01), that you wish to publish to the command line as above. Important Ensure that the Isolate Application checkbox is not selected. Application isolation is not applicable to hosted desktops. Click Next to continue. 3. In the Specify Application Appearance dialog, select Full Screen from the Session Window Size drop down list. Press TAB.

56 56 Desktop Broker Administrator s Guide Select True Color (24 bit) from the Colors drop down list. Press TAB. In the Application Startup Settings, clear the Hide application title bar checkbox. Also, clear the Maximize application at startup checkbox. Click Next. 4. In the Specify Application Limits dialog select the Allow only one instance of application for each user checkbox. 5. Complete remaining application publishing wizard procedure as normal for your environment and click Finish to save published application settings.

57 Chapter 5 Using Desktop Broker for Citrix Presentation Server 57 Configuring Presentation Server Client Settings If you created an application set in Program Neighborhood for hosted desktop connections, instruct your users to configure the following default properties so that hosted desktops are displayed correctly on the client device. 1. Open Program Neighborhood, select the Application Set to configure and click Application Set Settings. 2. In the Application Set Settings dialog box, select the Default Options tab. 3. Under Window Properties, ensure that the Colors Server Default option is selected for Window Colors. Ensure the server default is set to High Color or True Color. 4. Under Window Properties, ensure that the Size Server Default option is not selected for Window Size. Set the Window Size to Seamless. 5. Click OK to save changes. 6. To disable use of ICA Hotkeys in hosted desktop sessions, from the Tools menu, select ICA Settings to display the ICA Settings dialog box. 7. Select the Hotkeys tab. 8. Disable all hotkeys by setting them to (none). 9. Click OK to save your changes.

58 58 Desktop Broker Administrator s Guide Viewing Status of Desktop Broker Components All the Desktop Broker components provide status and error messages that you can use to diagnose and troubleshoot problems with your deployment. Desktop Broker Console You can use the Desktop Broker Console to routinely monitor health and status of hosted desktop connections. There are three hosted desktop connection states which you need to be aware of, so you can take appropriate action, if required. To illustrate, let s consider the screen shown above. Notice that the hosted desktop at is currently in a Logged On state, which denotes a healthy connection. The hosted desktop at is currently in a Disconnected state. This denotes that the connection was interrupted, but the user can reconnect by clicking on the hosted desktop icon. The hosted desktop at is currently in a Failed state. This denotes that the hosted desktop connection has failed. In this case, reset the hosted desktop state to idle by selecting the connection entry and clicking Reset. Session Manager Status and Error Messages The Session Manager application creates a Citrix node in the system Event Viewer. Database Service Status and Error Messages The Database Service application creates a Citrix node in the system Event Viewer.