Basic Administration for Citrix XenApp 6 - Telenet Service

Basic Administration for Citrix XenApp™ 6 CXA-204-1I Lab Guide June 2010

Table of Contents Module 3: Licensing XenApp Exercises........................................13 About Coolidge Financial, Inc..........................................................................................................15 Lab Scenario..................................................................................................................................16 User Credentials.............................................................................................................................17 Lab Environment.............................................................................................................................18 XenCenter Overview.......................................................................................................................19 Exercise 3-1: Installing the License Server for Coolidge Financial, Inc..............................................20 Installing the License Server........................................................................................................20 Exercise 3-2: Importing Coolidge's Citrix Licenses..........................................................................22 Configuring the License Server....................................................................................................22 Viewing the License Server Dashboard........................................................................................23 Exercise 3-3: Configuring License Monitoring..................................................................................25 Configuring EdgeSight to Monitor the License Server..................................................................25

Module 4: Installing XenApp Exercises.........................................27 Exercise 4-1: Installing XenApp on XenAppServer-1........................................................................29 Installing the XenApp Server Role................................................................................................29 Exercise 4-2: Configuring the XenApp Server..................................................................................31 Configuring the XenApp Server....................................................................................................31 Exercise 4-3: Adding XenAppServer-2 to the Farm.........................................................................33 Joining the Farm..........................................................................................................................33

Module 5: Configuring XenApp Exercises....................................35 Exercise 5-1: Delegating Administration to Other Accounts.............................................................37 Assigning Full Administration Privileges........................................................................................37 Assigning Custom Administration Privileges.................................................................................38 Exercise 5-2: Logging Configuration Changes.................................................................................40 Enabling Configuration Logging...................................................................................................40 Exercise 5-3: Creating Location- and Application-Based Worker Groups........................................42 Creating Worker Groups..............................................................................................................42

Module 6: Installing and Configuring Web Interface Exercises...45 Exercise 6-1: Installing Web Interface..............................................................................................47 Installing the Web Interface Role..................................................................................................47 Exercise 6-2: Building a XenApp Web Site......................................................................................49 Creating a XenApp Web Site.......................................................................................................49 Configuring the XenApp Web Site...............................................................................................50 Exercise 6-3: Building a XenApp Services Site................................................................................51 Creating a XenApp Services Site.................................................................................................51 Configuring the XenApp Services Site..........................................................................................52 Exercise 6-4: Customizing the XenApp Web Site with Coolidge Branding.......................................53 Viewing the Default Site Appearance...........................................................................................53 Customizing the Layout...............................................................................................................54 Customizing the Appearance......................................................................................................54

Customizing the Content.............................................................................................................55 Viewing the Changes...................................................................................................................55

Module 7: Delivering Applications and Content Exercises.........57 Exercise 7-1: Publishing Hosted Applications..................................................................................59 Publishing the CapitalReSources Application...............................................................................59 Publishing Notepad.....................................................................................................................60 Exercise 7-2: Publishing the San Francisco Server Desktops..........................................................62 Publishing a Server Desktop........................................................................................................62 Exercise 7-3: Testing and Managing Sessions................................................................................64 Testing the Published Resources................................................................................................64 Testing Workspace Control.........................................................................................................65 Managing Sessions.....................................................................................................................65

Module 8: Streaming Application Exercises.................................69 Exercise 8-1: Profiling Mozilla Firefox for Windows 7.......................................................................71 Installing Streaming Profiler..........................................................................................................71 Profiling an Application................................................................................................................72 Exercise 8-2: Profiling Mozilla Firefox for Window Server 2008 R2...................................................74 Profiling for Multiple Target Operating Systems............................................................................74 Exercise 8-3: Profile Linking Mozilla Firefox and Adobe Reader.......................................................77 Creating a Linked Profile..............................................................................................................77 Exercise 8-4: Publishing Firefox as a Streaming Application............................................................79 Publishing Firefox as a Streaming Application..............................................................................79 Testing Mozilla Firefox.................................................................................................................80

Module 9: Configuring Policies Exercises.....................................83 Exercise 9-1: Creating a Policy to Improve WAN Performance........................................................85 Improving Session Performance Across a WAN .........................................................................85 Exercise 9-2: Creating a Policy to Restrict User Access..................................................................88 Restricting User Access..............................................................................................................88 Exercise 9-3: Creating a Policy to Configure Shadowing.................................................................90 Configuring a Shadow Policy.......................................................................................................90 Exercise 9-4: Testing the Policies....................................................................................................92 Testing a Regular User Against Policy.........................................................................................92 Testing an Advisor User Against Policy........................................................................................93 Testing the Shadowing Policy......................................................................................................94

Module 10: Configuring Load Mananagement Exercises............97 Exercise 10-1: Assigning a Custom Load Evaluator........................................................................99 Configuring a Custom Load Evaluator.........................................................................................99 Assigning a Load Evaluator to a Server.....................................................................................100 Exercise 10-2: Creating a Failover Situation..................................................................................101 Load Balancing an Application..................................................................................................101 Testing a No Service Situation without Failover..........................................................................102 Exercise 10-3: Handling Failover with a Load Balancing Policy......................................................103 Adding Failover to the Load Balancing Policy............................................................................103 Testing a No Service Situation with Failover...............................................................................104 Restoring to the Default Load Evaluator.....................................................................................104

4

©

Copyright 2010 Citrix Systems, Inc.

Module 12: Configuring Self-Service Applications Exercises...107 Exercise 12-1: Simulating a Plug-in Deployment...........................................................................109 Installing Citrix Receiver ............................................................................................................109 Downloading Preconfigured Deliveries.......................................................................................110 Exercise 12-2: Creating a New Delivery for Citrix Dazzle................................................................111 Creating a Delivery Rule.............................................................................................................111 Configuring a Plug-In Deployment.............................................................................................112 Exercise 12-3: Using Citrix Dazzle.................................................................................................114 Configuring Citrix Dazzle............................................................................................................114 Testing Citrix Dazzle..................................................................................................................115

Module 13: Configuring Printing Exercises.................................117 Exercise 13-1: Identifying Printer Defaults.....................................................................................119 Verifying Default Printer Driver Creation.....................................................................................119 Exercise 13-2: Disallowing Auto-Creation of a Trouble Printer.......................................................121 Managing Driver Compatibility Lists...........................................................................................121 Exercise 13-3: Disabling Auto-Creation of Client Printers..............................................................123 Configuring Printing with Policies...............................................................................................123 Exercise 13-4: Creating Session Printers for All Employees...........................................................125 Configuring Session Printers......................................................................................................125 Exercise 13-5: Testing the Printer Policies.....................................................................................127 Testing the Printer Policies........................................................................................................127

Module 14: Securing XenApp Exercises.....................................129 Exercise 14-1: Setting Up ICA Proxy on a New XenApp Web Site.................................................131 Creating a New XenApp Web Site.............................................................................................131 Configuring Web Interface.........................................................................................................132 Configuring Access Gateway.....................................................................................................133 Exercise 14-2: Testing the ICA Proxy Configuration......................................................................135 Launching a Secure Application................................................................................................135

Module 15: Monitoring Exercises................................................137 Exercise 15-1: Viewing XenApp Licence Server Activity.................................................................139 Viewing License Usage Trends..................................................................................................139

©


5

Notices Citrix Systems, Inc. (Citrix) makes no representations or warranties with respect to the content or use of this publication. Citrix specifically disclaims any expressed or implied warranties, merchantability, or fitness for any particular purpose. Citrix reserves the right to make any changes in specifications and other information contained in this publication without prior notice and without obligation to notify any person or entity of such revisions or changes. © Copyright 2010 Citrix Systems, Inc. All Rights Reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the purchaser’s personal use, without express written permission of: Citrix Systems, Inc. 851 West Cypress Creek Road Fort Lauderdale, FL 33309 http://www.citrix.com The following marks are service marks, trademarks or registered trademarks of their respective owners in the United States and other countries. Mark

Owner

Flash®, Flex®, Reader®

Adobe Systems Incorporated

Apple®, iPhone™, Mac®

Apple, Inc.

Avaya™

Avaya, Inc.

Bloomberg™

Bloomberg Finance L.P.

Cisco®

Cisco Systems, Inc.

Branch Repeater™, Citrix®, Citrix Access Gateway™, Citrix Citrix Systems, Inc. Application Firewall™, Citrix Authorized Learning Center™, Citrix Certified Administrator™, Citrix Certified Enterprise Administrator™, Citrix Certified Integration Architect™, Citrix EasyCall™, Citrix Education™, Citrix Receiver™, Dazzle™, EdgeSight®, FlexCast™, HDX™, ICA®, NetScaler®, MyCitrix™, WANScaler™, XenApp™, XenDesktop® Android™

Google

Linux®

Linus Torvalds

Mark

Owner

Active Directory®, Internet Explorer®, Microsoft®, Microsoft Microsoft Corporation Internet Explorer®, SQL Server®, Windows®, Windows Mobile®, Windows Server®, Win32™, Access®, Excel®, InfoPath®, OneNote®, Outlook®, PowerPoint®, Project®, Publisher®, Visio® Firefox®

Mozilla Corporation

UNIX®

The Open Group

Oracle®

Oracle Corporation

Pearson VUE®

Pearson Education, Inc.

Blackberry®

Research In Motion Limited

Skype®

Skype Limited

Java®

Sun Microsystems, Inc.

Other product and company names mentioned herein might be the service marks, trademarks or registered trademarks of their respective owners in the United States and other countries.

Course Conventions This courseware uses the following typographic conventions to emphasize information. Convention UPPERCASE

Usage • Commands such as DIR and COPY • Filename extensions such as .COM and .INI • Drive letters such as A: and C: Case-sensitive items are the only exception to the usage listed.

lowercase

• • • • •

Command line parameters such as /w and -r URL addresses such as http://finance.yahoo.com Internet addresses such as www.citrix.com Domain names such as education.ctx Email addresses such as [email protected]

Case-sensitive items are the only exception to the usage listed. Bold Initial Capitalization

• Words or terms that are defined • Interface items that are selected, deselected, clicked, double-clicked or right-clicked such as options and menu items in lab exercises Case-sensitive items are the only exception to the usage listed.

ITALIC UPPERCASE

italic lowercase

• A variable in a system name such as XenAppX and ClientX • A variable in a user name such as UserX and AdminX • Variable drive letters such as z: and x: • Variable directory names such as %systemroot% and dir_name Case-sensitive items are the only exception to the usage listed.

This courseware uses the following icons. The Note icon identifies additional relevant information.

The Important icon identifies prerequisite information for a given task.

The Tip icon identifies information that can save time and effort.

The Warning icon identifies information that must be heeded in order to prevent harm to systems or users. The following table provides a list of updated Citrix product and component names used throughout the course. New Name

Old Name

Delivery Services Console

Access Management Console

License Administration Console

License Management Console

Citrix online plug-in

Citrix XenApp Plugin for Hosted Apps

Citrix offline plug-in

Citrix XenApp Plugin for Streamed Apps

Credits Instructional Designers:

Jeremy Boehl, Ben Colborn, Lydia Kellman, George Komoto, Brad Moczik, Meghan Myers, Adam Pallesen, Karla Stagray

Lab Developer:

Andrew Garfield

Education Media Specialists: Joshua Jack, Nathan Jackson Education Project Manager: Leah Thompson Editor:

Kathryn Morris

Subject Matter Experts:

Neil Alhadeff, Jenny Berger, Rob Blincoe, Ronald Brown, Blaise Cacciola, Victor Cataluna, Dave Coleman, Michael Delaguardia, Dan Feller, Jo Harder, Ann Harmison, James Hsu, Mark Ma, Abhishek Mandhana, Mike Melton, Robert Morris, Sridhar Mullapudi, Joseph Nord, Jan Penovich, Elisabeth Reynolds, Daniel Romig, Andrea Rutherford, Stacy Scott, Mark Simmons, Lenny Soletti, Wayne Stillson, Jay Tomlin, Danny Van Dam, Sharin Yeoh, Andy Zhu

Special Thanks:

Rob Blincoe, James Hsu, Mark Simmons

Module 3

Licensing XenApp Exercises

14

Module 3: Licensing XenApp Exercises

©


About Coolidge Financial, Inc Coolidge Financial, Inc is a small, privately held investment company that offers highly personalized financial services for a limited group of high profile clientele. The company's 350 employees service only 500 clients from its two offices in New York City and San Francisco. In addition to the highly personalized service, their clientele specifically choose Coolidge because of the company's excellent track record and emphasis on data privacy and security. Coolidge is facing several new IT requirements as the business continues to grow: • Privacy - Coolidge's senior management wants to increase their client's privacy and security by centralizing all data and applications. • Simplification - There is a push by senior management to simplify many of the business processes within the company. The IT department wants to simplify the employee laptop provisioning processes by not including any local applications on the laptop. Instead, new laptops will be provisioned with only Citrix Receiver installed. • Expansion - Coolidge is planning to acquire several smaller firms and will be opening more offices over the next year. The CTO wants an IT infrastructure in place that can easily handle these transitions. • Regulation - Management is expecting new regulation to be passed this year that will impact the company and is asking IT to create an infrastructure that has flexibility to easily adapt. • Remote Employees - Employees are increasingly working remotely but still need the ability to run their essential applications. In order to respond to these IT drivers, the company purchased Citrix XenApp 6 Platinum Edition and plans to implement it rapidly throughout the organization. Coolidge set an aggressive plan for an initial deployment within the company and has brought in a consultant, who is a Citrix Certified Integration Architect, to create and facilitate the design. They also hired into the company a Citrix Certified Enterprise Engineer to oversee the deployment and take charge of the Citrix environment.

©



15

Lab Scenario You are a new XenApp Administrator who was hired by Coolidge Financial, Inc to begin a rapid and wide-scale deployment of XenApp that will eventually reach all company employees. Your job is to work with a consultant who is a Citrix Certified Integration Architect and a full time Citrix Certified Enterprise Engineer to create, test, and deploy a XenApp farm and integrate it into the existing Active Directory system. The deployment is a multi-phase project; you are tasked with completing the first phase of the rollout. The goal of the first phase is to create the fundamental XenApp infrastructure and to deploy XenApp to the initial set of critical users while making sure to meet all technical and functional requirements. Management wants this initial phase of the implemention completed within the next five days. Due to the rapid pace required for this implementation you are given temporarily elevated access to the domain controller and other restricted parts of the IT infrastructure. The Citrix Engineer will help you with some parts of the implementation, but is unable to dedicate his full attention.

16


©


User Credentials Please use the following credentials as you complete these exercises: Coolidge\CitrixAdmin • • • •

Username: Coolidge\CitrixAdmin Password: Password1 Member of: Coolidge\Domain Admins; Coolidge\TestAccounts Description: This account was created to facilitate the initial phase of deployment for all Citrix Administrators. When the environment goes live, it will be replaced by specific accounts for each administrator. This is the account that will be used most often throughout the initial deployment.

Coolidge\CitrixEngineer • • • •

Username: Coolidge\Engineer Password: Password1 Member of: Coolidge\Domain Admins; Description: This account was created for the Citrix Engineer to access and administrate the XenApp farm.

Coolidge\TestAdvisor • • • •

Username: Coolidge\CitrixAdvisor Password: Password1 Member of: Coolidge\Advisors; Coolidge\TestAccounts Description: This account simulates a member of the Advisors team at Coolidge.

Coolidge\TestUser • • • •

Username: Coolidge\CitrixUser Password: Password1 Member of: Coolidge\TestAccounts Description: This account simulates the lowest common denominator user of the XenApp farm.

[email protected] • Username: [email protected] • Password: Password1 • Description: This account is used exclusively to login and manage EdgeSight.

©



17

Lab Environment The following table provides descriptions and roles of each virtual machine in the lab environment: Virtual Machine AccessGateway

Coolidge-DC

18

Role

OS

A virtual appliance which encrypts traffic Linux between the client device and the Web Interface server. • • • • •

Windows Server 2008 R2

Domain Controller EdgeSight Server License Server Filer Print Server

EndUserSimulator

A simulated user desktop for performing XenApp and deployment testing.

Profiler-2008R2

A system for profiling streaming Windows Server 2008 applications for Windows Server 2008 R2. R2

Profiler-Win7

A system for profiling streaming applications for Windows 7.

MerchandisingServer

Citrix Merchandising Server, which is used Linux to manage and deploy Citrix plug-ins to Citrix Receiver.

WebInterfaceServer

The Web Interface server.


XenAppServer-1

XenApp


XenAppServer-2

XenApp



Windows 7

Windows 7

©


XenCenter Overview Your virtual machines are hosted using Citrix XenServer. Each virtual machine is an independent system called a guest operating system. Citrix XenCenter allows you to connect to the XenServer environment and administer guest operating systems. Once you are connected to your XenServer system, you will notice a list of guests in the left pane of XenCenter. Selecting a guest will allow you to monitor and administer it. The Console tab allows you to see the selected guest operating system desktop. You can manipulate the console window to suit your preference. Useful functions for XenCenter console screens are listed in the following table. Control Send Ctrl-Alt-Del

Sends the Ctrl-Alt-Del sequence to the guest to access the Windows Security screen

Alt+Shift+U

Undock/redock (separate or join console screen)

Ctrl+Alt

Toggle full-screen mode

Scale

Scale the guest window to fit inside the console window

DVD Drive

Select a disc image to 'insert' into the guest DVD drive

Switch to Remote Desktop/

Toggle between VNC connection and RDP connection

Switch to Default Desktop

©

Function


Using RDP to connect can improve user interface performance


19

Exercise 3-1: Installing the License Server for Coolidge Financial, Inc. Scenario In preparation for installing and configuring XenApp, you must install a license server to support all of the Citrix products going forward. The Citrix Engineer wants you to install the license server on the existing domain controller in order to keep all servers consolidated and save time against the aggressive deployment schedule. Your job is to install the license server from the XenApp media onto the domain controller.

Before You Begin To begin this lab, ensure that the following virtual machines are started: • Coolidge-DC Estimated time to complete this exercise: 20 minutes

Installing the License Server Use the Coolidge-DC virtual machine logged in as the Coolidge\Administrator user for this task. Use the following procedure on the Coolidge-DC virtual machine to install and configure the Citrix License Server: 1. Log on to the Coolidge-DC virtual machine as the Coolidge\Administrator user. 2. Attach the XA6_2008R2_ML.ISO media to the Coolidge-DC virtual machine and start the installer. a) Attach the XA6_2008R2_ML.ISO media to the virtual machine. The AutoPlay window displays. b) Click Run autorun.exe in the AutoPlay window to start the installation. 3. Begin the XenApp Server role installation to install Platinum Edition components. a) Click Install XenApp Server. The XenApp Server Role Manager launches after a few moments.

20


©


b) Click Add server roles. The server role installer opens after a few moments. c) Click Platinum Edition. d) Accept the terms of the License Agreement and click Next. 4. Install the License Server role using the default values. a) Select License Server from the Common Roles section and click Next. b) Click Next in the Choose Role Subcomponents window and click Install. The installer begins to install the License Server role. c) Click Finish when the installation is completed.

©



21

Exercise 3-2: Importing Coolidge's Citrix Licenses Scenario You have just installed the Citrix License Server onto the domain controller and now you must configure it and add the licenses for XenApp and Access Gateway. The Citrix Engineer has placed the license files onto the filer so that you can import them to the license server.


Configuring the License Server Use the Coolidge-DC virtual machine logged in as the Coolidge\Administrator user for this task. Use the following procedure to configure the Citrix License Server on the Coolidge-DC virtual machine: 1. Configure the Citrix License Server using all default values and use Password1 as the password. a) Click Configure in the XenApp Server Role Manager. After a few moments the configuration screen will appear. b) Use the default values for the ports. Type Password1 in the Password fields and click OK. c) Click Do not show this window at logon in the XenApp Server Role Manager and click Close. 2. View the vendor daemon configuration in the License Administration Console using the admin, Password1 credentials. a) Click Start > All Programs > Citrix > Management Consoles > License Administration Console.

22


©


b) Click Administration and type admin in the User Name field and Password1 in the Password and Confirm Password fields and click Submit. The username and password are both case-sensitive.

c) Click Vendor Daemon Configuration. 3. Import the \\dc\filer \administration\licenses\xenapp_enterprise_coolidge_financial_dc.lic

XenApp license file into the license server. a) Click the Import License button in the License Administration Console. b) Click Browse and type \\dc\filer \Administration\licenses in the File name field and press Enter. c) Click the xenapp_enterprise_coolidge_financial_dc.lic file and click Open. d) Select Overwrite License File on License Server and then click Import License. The License Administration Console uploads the license file to the license server. e) Click OK. 4. Import the \\dc\filer \administration\licenses\cag_license_coolidge_ag.lic Access Gateway

license file into the license server. a) Click Import License. b) Click Browse and type \\dc\filer \Administration\licenses\ in the File name field. c) Click the cag_license_coolidge_ag.lic file and click Open. d) Select Overwrite License File on License Server and then click Import License. The License Administration Console uploads the license file to the license server. e) Click OK. 5. Restart the Coolidge-DC virtual machine.

Viewing the License Server Dashboard Use the Coolidge-DC virtual machine logged in as the Coolidge\Administrator user for this task. Use the following procedure to verify that the XenApp license was successfully uploaded to the license server: 1. Log on to the Coolidge-DC virtual machine as the Coolidge\Administrator user.

©



23

2. Log on to the License Administration Console using the admin, Password1 credentials. View the dashboard to ensure the license file was installed correctly and that no critical alerts were logged. a) Click Start > All Programs > Citrix > Management Consoles > License Administration Console. b) Click Dashboard in the License Adminstration Console. c) Verify that a Citrix XenApp license is listed under Concurrent licenses. d) Verify that no critical alerts are logged. 3. Close all open windows on the Coolidge-DC virtual machine.

24


©


Exercise 3-3: Configuring License Monitoring Scenario The Citrix Architect wants to keep constant tabs on the license usage in order to ensure that the appropriate number of licenses were purchased from Citrix. The Citrix Engineer has already installed Edgesight on the domain controller and needs you to configure it to monitor the license server that you recently installed.


Configuring EdgeSight to Monitor the License Server Use the Coolidge-DC virtual machine logged in as the Coolidge\Administrator user for this task. Use the following procedure to configure EdgeSight to monitor the license server: 1. Log on to the http://dc.coolidge.net/edgesight web site using the [email protected], Password1 credentials. a) Click Start > Internet Explorer, type http://dc.coolidge.net/edgesight/ in the Address field and press Enter. b) Log on to the web site as [email protected] and use Password1 as the password. 2. Configure EdgeSight to monitor the dc.coolidge.net license server and then test the connection to verify that it works. a) Click the Configure tab. b) Click New License Server to add a license server to monitor. c) Type dc.coolidge.net in the License Server field and Coolidge License Server in the Display name field.

©



25

d) Click Test Connection and then click Add License Server, if the test connection was successful. 3. Change the polling interval for the License server monitor to 30 minutes and disable sending emails when polling errors occur. a) Click Settings under License Monitoring Configuration on the left side of the screen. b) Select 30 in the Polling Interval (min) drop-down menu. c) Select Do Nothing in the Polling Errors drop-down menu and click Save Changes. 4. Close Internet Explorer.

26


©


Module 4

Installing XenApp Exercises

28

Module 4: Installing XenApp Exercises

©


Exercise 4-1: Installing XenApp on XenAppServer-1 Scenario You recently installed the Citrix License Server in preparation for installing XenApp and creating a new farm. In order to take an iterative approach to creating and deploying XenApp, the Citrix Architect initially wants you to create a small two server farm. The farm will have more servers added to it during the second phase of deployment. The Citrix Engineer has configured a server called XenAppServer-1 as your starting point. You need to install XenApp and all of its prerequisites on this server.

Before You Begin To begin this lab, ensure that the following virtual machines are started: • Coolidge-DC • XenAppServer-1 • XenAppServer-2 Estimated time to complete this exercise: 30 minutes

Installing the XenApp Server Role Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to install XenApp on the XenAppServer-1 virtual machine. 1. Start the XenAppServer-1 and XenAppServer-2 virtual machines and log on to the XenAppServer-1 virtual machine as the Coolidge\CitrixAdmin user: 2. Attach the XA6_2008R2_ML.ISO media to the XenAppServer-1 virtual machine and launch the XenApp 6.0 installer. a) Attach the XA6_2008R2_ML.ISO media to the virtual machine. The AutoPlay window displays. b) Click Run autorun.exe in the AutoPlay window to start the installation.

©



29

3. Begin the XenApp Server role installation to install Platinum Edition components. a) Click Install XenApp Server. The XenApp Server Role Manager launches after a few moments. b) Click Add server roles. The server role installer opens after a few moments. c) Click Platinum Edition. d) Accept the terms of the License Agreement and click Next. 4. Install the XenApp role using the default options. a) Select XenApp from the Common Roles section and then click Next. b) Click Next in the Choose role subcomponents. c) Click Next in the Review Prerequisites screen. d) Click Install to begin the XenApp Server role installation. The XenApp Server Role Manager automatically installs all prerequisite software. This may take several minutes. e) Click Finish when the installation is completed.

30


©


Exercise 4-2: Configuring the XenApp Server Scenario You just installed the XenApp role on XenAppServer-1 and you must now configure the XenApp server. The database administrator has created a database instance for the XenApp data store and given you credentials to access it. During configuration you must connect the XenApp server to this data store and to the license server.


Configuring the XenApp Server Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure on the XenAppServer-1 virtual machine to create the farm and configure XenApp: 1. Begin configuring the XenApp server. Create a new farm called Coolidge and configure it to use the dc.coolidge.net license server. a) Click Configure to begin configuring the XenApp server. After a few moments the server configuration screen will appear. b) Click Create a new server farm. c) Type Coolidge in the New XenApp Server farm name field and click Next. d) Select Use an existing license server, type dc.coolidge.net and click Next. 2. Configure XenApp to use the existing XenApp database on the DC\SQLSERVER database server.

©



31

a) Click Existing Microsoft SQL Server database and click Next. b) Type DC\SQLSERVER as the database server and XenApp as the database name. 3. Configure the database to use integrated Windows authentication with the Administrator, Password1 credentials. a) Select Integrated Windows authentication and click Next. b) Type Administrator and Password1 in the Windows Security screen and click OK. c) Click Test Connection to ensure that the information was entered correctly. d) Click OK and then click Next. 4. Complete the configuration by using the default shadowing settings and adding only the authenticated users to the Remote Desktop Users group. a) Click Next on the Configure shadowing screen to use the default shadowing configuration. b) Click Remote Desktop Users in the left pane. c) Deselect Add Anonymous users and Add the list of users from the Users group in the Remote Desktop Users section. d) Select Add the Authenticated Users and click Next. e) Confirm the settings and click Apply to complete the configuration. f) Click Finish when the configuration is completed. g) Click Do not show this window at logon in the XenApp Server Role Manager and click Close. 5. Restart the XenAppServer-1 virtual machine.

32


©


Exercise 4-3: Adding XenAppServer-2 to the Farm Scenario The Citrix Engineer installed XenApp onto another virtual machine called XenAppServer-2 but had to leave for an urgent meeting before he could configure and join it to the farm. Before he left, he asked you to run through the configuration process for this server to add it to the farm and connect it to the data store and the license server.


Joining the Farm Use the XenAppServer-2 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to join the XenAppServer-2 virtual machine to the Coolidge farm: 1. Log on to the XenAppServer-2 virtual machine as the Coolidge\CitrixAdmin user. 2. Open the XenApp Server Role Manager to configure XenApp on the XenAppServer-2 virtual machine. a) Click Start > All Programs > Citrix > XenApp Server Role Manager > XenApp Server Role Manager. It may take a few moments for the XenApp Server Role Manager to appear. b) Click Configure to begin configuring the XenApp server. Within a few moments the configuration wizard will launch. It may open behind other windows.

©



33

3. Join the server to the Coolidge farm and configure XenApp to use the existing XenApp database on the DC\SQLSERVER database server. a) Click Join an existing server farm. b) Click Existing Microsoft SQL Server database and click Next. c) Type DC\SQLSERVER as the database server name and XenApp as the database name. 4. Configure the database to use integrated Windows authentication with the Administrator, Password1 credentials. a) Select Integrated Windows authentication and click Next. b) Type Administrator and Password1 in the Windows Security screen and click OK. 5. Test the database connection. a) Click Test Connection to ensure that the configuration has been completed successfully. b) Click OK and then click Next. 6. Complete the configuration by using the default shadowing settings and adding only the authenticated users to the Remote Desktop Users group. a) Click Next on the Configure Shadowing screen to use the default shadowing configuration. b) Click Remote Desktop Users in the left pane. c) Deselect Add Anonymous users and Add the list of users from the Users group in the Remote Desktop Users section. d) Select Add the Authenticated Users and click Next. e) Confirm the settings and click Apply to complete the configuration. f) Click Finish when the configuration is completed. g) Click Do not show this window at logon in the XenApp Server Role Manager and click Close. 7. Restart the XenAppServer-2 virtual machine before continuing.

34


©


Module 5

Configuring XenApp Exercises

36

Module 5: Configuring XenApp Exercises

©


Exercise 5-1: Delegating Administration to Other Accounts Scenario Several other members of the IT staff require administrative access. Most notably you need to grant full administrator access to the Citrix Engineer's account and give custom access to the HelpDesk team so that they can begin training.


Assigning Full Administration Privileges Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to assign full administration privileges to the CitrixAdmin account: 1. Log on to the XenAppServer-1 virtual machine as the Coolidge\CitrixAdmin user. 2. Launch the Delivery Services Console and disable authenticode signature checking. a) Click Start > All Programs > Citrix > Management Consoles > Citrix Delivery Services Console. b) Click Disable Authenticode signature checking when prompted. 3. Launch the Delivery Services Console and begin the discovery process. Add the local computer using the XenApp Discovery wizard, but do not include Single Sign-On in your discovery. a) Click Next on the Discovery window, which appears automatically the first time the Delivery Services Console is opened.

©



37

b) c) d) e)

Deselect Single Sign-On and click Next. Click Add Local Computer and click Next. Click Next to configure the console. Click Finish to complete the Discovery wizard.

4. Make the Coolidge\CitrixEngineer account a full administrator of the XenApp farm. a) Expand the XenApp > Coolidge nodes in the Delivery Services Console, and right-click Administrators. b) Click Add administrator then click Add. c) Click Add List of Names and type Coolidge\CitrixEngineer. d) Click Check Names and click OK, if the name was validated successfully. If the names were not validated successfully, make sure they are spelled correctly and are in the Coolidge\AccountName format. e) Click OK to close the Add List of Names window and then click OK to finish selecting this user. f) Click Next to continue to the Privileges window. g) Select Full Administration and click Finish.

Assigning Custom Administration Privileges Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure on the XenAppServer-1 virtual machine to assign custom administration privileges to the HelpDesk group: 1. Make the Coolidge\HelpDesk group a custom administrator of the farm. a) Right-click Administrators, click Add administrator then click Add. b) Click Add List of Names and type Coolidge\HelpDesk. c) Click Check Names and click OK, if the name was validated successfully. If the names were not validated successfully, make sure they are spelled correctly and are in the Coolidge\AccountName format. d) Click OK to close the Add List of Names window and then click OK to finish selecting this user. e) Click Next to continue to the Privileges window. f) Select Custom and click Next. 2. Assign the HelpDesk group the following privileges: • • • •

38

View published Applications and Content View Session Management Reset Sessions Send Messages


©


• Log Off Users a) Click Applications and select View Published Applications and Content, View Session Management, Reset Sessions, Send Messages, and Log Off Users. b) Click Finish to complete the wizard.

©



39

Exercise 5-2: Logging Configuration Changes Scenario Many administrators will make changes to the farm, so the Citrix Engineer decides to enable Configuration Logging to track the changes made by all administrators. This will allow configuration missteps to be identified and fixed quickly as farm deployment plans continue. The database administrator created a new database instance for use as the Configuration Logging database.


Enabling Configuration Logging Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following steps to enable Configuration Logging for the Coolidge XenApp farm: 1. Open the farm properties to access the Configuration Logging options. a) Right-click the Coolidge farm node in the Delivery Services Console and click Farm Properties. b) Click Configuration Logging. 2. Configure the database for Configuration Logging using the following information: • Connection type: SQL Server • Server name: DC\SQLSERVER • Authentication mode: Use Windows integrated security

40


©


• • • •

Credentials: Coolidge\Administrator, Password1 Database: XA_ConfigurationLog Connection options: Use Encryption: No Connection pooling: Default

a) Click Configure Database to begin the database configuration. b) Specify SQL Server as the connection type and type DC\SQLSERVER as the server name. c) Specify Use Windows integrated security, type Coolidge\Administrator, Password1 in the credential fields and then click Next. d) Select XA_ConfigurationLog from Specify the database drop-down menu and click Next. e) Select No in the Use encryption drop-down menu under Connection options and click Next. 3. Test the database connection and complete the configuration. a) Click Test Database Connection and click OK, if a connection was successfully established. If a connection was not successfully established, confirm that all settings are configured correctly. b) Click Finish to complete the configuration. 4. Enable the logging of administrative tasks to the database. a) Select Log administrative tasks to Configuration Logging database. b) Click OK to return to the Delivery Services Console.

©



41

Exercise 5-3: Creating Location- and Application-Based Worker Groups Scenario The Citrix Architect wants to use the worker group feature to create server segment groupings based on server location and application. She wants you to create worker groups and populate them with the correct servers. More servers will be added later to these worker groups as the deployment is scaled out. You need to create the following worker groups and populate them with the XenApp servers listed: All Servers: XenAppServer-1, XenAppServer-2 San Francisco: XenAppServer-1 New York: XenAppServer-2 Firefox: XenAppServer-1, XenAppServer-2 CapitalReSources: XenAppServer-1, XenAppServer-2


Creating Worker Groups Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to create worker groups based on location and applications: 1. Create a worker group named All Servers.

42


©


a) Right-click Worker Groups in the Delivery Services Console and click Create worker group. The Create Worker Group window opens. b) Type All Servers in the Name field. 2. Add XenAppServer-1 and XenAppServer-2 to the All Servers worker group and then complete the worker group creation. a) Click the Select source drop-down and select Farm Servers. b) Click Add to add servers to the worker group. The Select Servers window opens. c) Double-click XenAppServer-1 and XenAppServer-2 and click OK. d) Click OK to close the Create Worker Group window and complete the worker Group creation process. 3. Use the above procedure to create the following worker groups and add the appropriate servers to the groups. Servers in Group Worker Group Name

©

San Francisco

XenAppServer-1

New York

XenAppServer-2

CapitalReSources

XenAppServer-1, XenAppServer-2

Firefox

XenAppServer-1, XenAppServer-2



43

44


©


Module 6

Installing and Configuring Web Interface Exercises

46

Module 6: Installing and Configuring Web Interface Exercises

©


Exercise 6-1: Installing Web Interface Scenario A fellow administrator provided you with a server for use as a Web Interface server. You need to install Web Interface and all of the prerequisites on this server in order to begin configuration.

Before You Begin To begin this lab, ensure that the following virtual machines are started: • • • •

Coolidge-DC WebInterfaceServer XenAppServer-1 XenAppServer-2

Estimated time to complete this exercise: 25 minutes

Installing the Web Interface Role Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure on the WebInterfaceServer virtual machine to install the Web Interface: 1. Start and log on to the WebInterfaceServer virtual machine as the Coolidge\CitrixAdmin user. 2. Attach the XA6_2008R2_ML.ISO media to the virtual machine and start the XenApp 6.0 installer. a) Attach the XA6_2008R2_ML.ISO media to the virtual machine. The AutoPlay window displays. b) Click Run autorun.exe in the AutoPlay window to start the installation. 3. Begin the XenApp Server role installation to install Platinum Edition components. a) Click Install XenApp Server. The XenApp Server Role Manager launches after a few moments.

©



47

b) Click Add server roles. The server role installer opens after a few moments. c) Click Platinum Edition. d) Accept the terms of the License Agreement and click Next. 4. Install the Web Interface role using the default values. a) Select Web Interface from the Common Roles section and click Next. b) Click Next in the Choose Role Subcomponents. c) Click Next on the Review Prerequisites screen. d) Click Install to begin the installation of the prerequisites and the Web Interface. e) Click Finish to complete the Web Interface installation.

48


©


Exercise 6-2: Building a XenApp Web Site Scenario Although the Citrix Architect wants users to access published resources through Citrix Dazzle, employees must also have the option of accessing their applications through a XenApp Web site. You need to create a XenApp Web site and configure it to integrate correctly with the farm in order to meet this requirement.




Creating a XenApp Web Site Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure on the WebInterfaceServer virtual machine to create and configure a XenApp Web site: 1. Use the XenApp Server Role Manager to start the Citrix Web Interface Management console and create a new XenApp Web site. a) Click Configure in the Citrix XenApp Server Role Manager. After a few moments the Citrix Web Interface Management console will appear. b) Click Create Site. c) Select XenApp Web and click Next. 2. Configure the web site as the default page for the IIS site and use the default values for all other choices. a) Select the Set as the default page for the IIS site check box and click Next.

©



49

b) Verify that At Web Interface is specified on the Specify Point of Authentication screen and click Next. c) Click Next on the Confirm Settings for the New Site screen. The wizard creates a new XenApp Web site. d) Click Next to configure the XenApp Web site.

Configuring the XenApp Web Site Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to configure the new XenApp Web site: 1. Specify Coolidge as the farm name and add both of the XenApp servers to the list of servers. a) Type Coolidge in the Farm name field. b) Click Add and type XenAppServer-1 and click OK. c) Click Add and type XenAppServer-2 and click OK. Click Next. 2. Use the default authentication method settings and restrict the XenApp Web site to only the Coolidge domain. a) Click Next on the Configure Authentication Methods screen. b) Select Restrict domains to the following and click Add. c) Type Coolidge in the Logon domain field, click OK and then click Next. 3. Complete the configuration by setting the logon screen to display messages and preferences and configure dual mode as the published resource type. a) Select Full and click Next. b) Select Dual mode and click Next. c) Click Finish to complete the initial configuration.

50


©


Exercise 6-3: Building a XenApp Services Site Scenario IT is implementing changes to how employees will access their applications on new laptops containing Windows 7. New laptops will be imaged with nearly bare-bone OS-only installs of Windows 7, and Citrix Receiver installed. All applications will be served through XenApp using Citrix Dazzle. In order for Citrix Dazzle to function correctly, you need to create a XenApp Services site and configure it to integrate correctly with the farm.




Creating a XenApp Services Site Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure on the WebInterfaceServer virtual machine to create and configure a XenApp Services site: 1. Use the Citrix Web Interface Management console to create a new XenApp Services site. a) Select XenApp Services Sites. b) Click Create site. 2. Create the web site using the default values for all choices. a) Click Next on the Specify IIS Location screen. b) Click Next on the Confirm Settings for the New Site screen. The wizard creates a new XenApp Services site.

©



51

c) Click Next to configure the XenApp Services site.

Configuring the XenApp Services Site Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to configure the XenApp Services site: 1. Specify Coolidge as the farm name and add both of the XenApp servers to the list of servers. a) Type Coolidge in the Farm name field. b) Click Add, type XenAppServer-1 and click OK. c) Click Add and type XenAppServer-2 and click OK. d) Click Next. 2. Complete the configuration by setting the published resource type to dual mode. a) Select Dual mode and click Next. b) Click Finish to complete the initial configuration.

52


©


Exercise 6-4: Customizing the XenApp Web Site with Coolidge Branding Scenario The Marketing department supplied you with some branding guidelines and logos. They want you to use these files and guidelines on the XenApp Web site to integrate it with Coolidge's look and feel. In addition, some departments will be given the chance to access XenApp through the web site before the final deployment. The Citrix Engineer wants you to add a warning to the site to remind all visitors not to use XenApp for production purposes until it is ready.




Viewing the Default Site Appearance Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to view the default web interface appearance: 1. Use the XenAppServer-1 virtual machine to access the http://webinterface.coolidge.net web site. a) Switch to the XenAppServer-1 virtual machine. b) Click Start > Internet Explorer, navigate to http://webinterface.coolidge.net and press Enter. 2. Make note of the default logos and text as they normally appear.

©



53

3. Log on to the XenApp Web site as the Coolidge\CitrixAdmin user and make note of the colors used by default on XenApp Web sites. 4. Close Internet Explorer.

Customizing the Layout Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to customize the layout of the XenApp Web site: 1. Use the Citrix Web Interface Management console to edit the appearance of the XenApp Web site. a) Click XenApp Web Sites and then click the XenApp Web site. b) Click Web Site Appearance to launch the Customize Web Site Appearance screen. 2. Edit the screen layout to use full graphics. a) Click Layout and then click the Overall Layout node. b) Select Full graphics in the Screen layout drop-down menu. 3. Use a single tabbed interface for all applications, desktops, and content. a) Click the Tab Settings node and click Single tab (consolidating all resource types). b) Click OK to close the Layout screen.

Customizing the Appearance Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to add the Coolidge logos to the XenApp Web site: 1. Copy the coolidgeart folder located in \\dc\filer \administration to the C:\INETPUB\WWROOT\CITRIX\XENAPP\MEDIA folder on the WebInterfaceServer. a) Click Start, type \\dc\filer \administration and press Enter. b) Right-click the CoolidgeArt folder and click Copy. c) Navigate to the C:\INETPUB\WWWROOT\CITRIX\XENAPP\MEDIA folder. d) Click Organize and click Paste to copy the art files folder into this location. e) Close the Media and Administration windows. 2. Use the Citrix Web Interface Management console to specify the CoolidgeLogoHeader.gif file located in the CoolidgeArt folder as the full graphics mode header image.

54


©


a) Click Appearance and then click the Header Area node. b) Type ../media/CoolidgeArt/CoolidgeLogoHeader.gif in the Full graphics mode field. 3. Use gray as the background color for the content area and then save the new appearance settings. a) Click the Content Area node and select Use color. b) Click the color box, select the gray color and click OK. c) Click OK to save the new appearance settings.

Customizing the Content Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to customize the language and system message: 1. Set the standard language for the content in the XenApp Web site to English. a) Click Content to open the Content window and click Add. Verify that Standard language code is selected. b) Select English [en] from the Standard Language code drop-down menu and click Next. 2. Add a system message to the logon screen that states "Currently for non-production use only." and then save the customizations. a) Select Logon screen text and click Next. b) Type Log on to access your applications. in the welcome message area. c) Type Currently for non-production use only. in the System message area and click Finish. d) Click OK to exit the content editing screen and click OK to save the customizations.

Viewing the Changes Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to view the XenApp Web site and verify that it appears correctly: 1. Use the XenAppServer-1 virtual machine to access the http://webinterface.coolidge.net web site. a) Switch to the XenAppServer-1 virtual machine. b) Click Start > Internet Explorer and navigate to http://webinterface.coolidge.net.

©



55

2. Verify that the Coolidge logo is displayed in the upper left corner of the page. 3. Verify that "Currently for non-production use only." is displayed under the Logon box. 4. Log on to the XenApp Web site as the Coolidge\CitrixAdmin user and verify that the background of the application area is gray. a) Type your Coolidge\CitrixAdmin credentials and press Enter. b) Verify that the background of the application area is now a gray color. 5. Close Internet Explorer.

56


©


Module 7

Delivering Applications and Content Exercises

58

Module 7: Delivering Applications and Content Exercises

©


Exercise 7-1: Publishing Hosted Applications Scenario The Financial Specialists are a group of customer-facing employees based out of New York. They use a custom financial application called CapitalReSources every day. Due to this group's unique situation within the company and limited use of the application, the Citrix Engineer feels that this application would be good candidate for the initial rollout of the XenApp implementation. The Citrix Engineer wants to host this application on the XenApp servers. In addition, you decide to publish Notepad for use in testing throughout the remainder of the XenApp deployment. The Citrix Engineer has already installed the CapitalReSources application on the XenApp servers. You need to publish CapitalReSources and Notepad.




Publishing the CapitalReSources Application Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to publish the CapitalReSources application using Citrix XenApp: 1. Use the Publish Application wizard on the XenAppServer-1 virtual machine to begin publishing the CapitalReSources application. a) Expand the Coolidge farm node in the task pane.

©



59

b) Right-click Applications, click Publish application to start the Publish Application wizard and then click Next. 2. Use CapitalReSources as the name of the published application and do not specify a description. a) Type CapitalReSources in the Display Name field. b) Leave the Application Description field blank and click Next. 3. Configure the CapitalReSources application to be accessed from the server and specify the application's command line location as C:\Program Files (x86)\CapitalReSources\CapitalReSources.exe. a) Verify that Application and Accessed from a server are selected and click Next. b) Click the Browse button next to the Command line field. c) Navigate to C:\Program Files (x86)\CapitalReSources\CapitalReSources.exe, click Open and then click Next. 4. Publish CapitalReSources to the CapitalReSources worker group. a) Click Add and double-click Worker Groups. b) Double-click CapitalReSources. c) Click OK to select the worker group and then click Next. 5. Provide the Financial Specialists and Domain Admins groups with access to the CapitalResources application. a) Click Add to display the Select Users or Groups screen. b) Click Add List of Names and type Coolidge\FinancialSpecialists; Coolidge\Domain Admins. c) Click Check Names and then click OK, if the names were validated successfully. If the names were not validated successfully, make sure they are spelled correctly and are in the Coolidge\AccountName format. d) Click OK to close the Add List of Names window and click OK. e) Click Next to proceed to the Shortcut presentation screen. 6. Place the application in a folder called Financial and complete the wizard using the default values. a) Type Financial in the Client application folder field and click Next. b) Click Finish to complete the Publish Application wizard.

Publishing Notepad Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task.

60


©


Use the following procedure to publish Notepad for testing through Citrix XenApp: 1. Use the Publish Application wizard on the XenAppServer-1 virtual machine to begin publishing the Notepad application . a) Right-click Applications, click Publish application to start the Publish Application wizard and then click Next. 2. Use Notepad as the name of the published application and "Published for testing only" as the description. a) Type Notepad in the Display Name field. b) Type Published for testing only in the Application Description field and click Next. 3. Set the Notepad application to be accessed from the server and specify the application's command line location as C:\Windows\System32\Notepad.exe. a) Verify that Application and Access from a server are selected and click Next. b) Click the Browse button next to the Command Line field. c) Navigate to C:\Windows\System32\Notepad.exe, click Open and then click Next. 4. Publish Notepad to the All Servers worker group. a) Click Add and double-click Worker Groups. b) Double-click All Servers. c) Click OK to select the worker group and click Next. 5. Give the TestAccounts group access to the Notepad application. a) Click Add to bring up the Select Users or Groups screen. b) Click Add List of Names and type Coolidge\TestAccounts. c) Click Check Names and click OK, if the name was validated successfully. If the names were not validated successfully, make sure they are spelled correctly and are in the Coolidge\AccountName format. d) Click OK to close the Add List of Names window and click OK. e) Click Next to proceed to the Shortcut presentation screen. 6. Complete the Publish Application wizard using the default values. a) Click Next in the Shortcut presentation screen. b) Click Finish to complete the Publish Application wizard.

©



61

Exercise 7-2: Publishing the San Francisco Server Desktops Scenario Your team will not have daily access to the San Francisco datacenter but will require access to these server desktops for various reasons. The Citrix Engineer asked you to publish the San Francisco server desktops so that administrators can access them conveniently at any time.




Publishing a Server Desktop Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to publish a server desktop. 1. Use the Publish Application wizard on the XenAppServer-1 virtual machine to begin publishing the server desktop. a) Right-click Applications and select Publish application. b) Click Next. 2. Use XenAppServer Desktop as the name, do not specify a description and use Server desktop as the type of application to publish. a) Type XenAppServer Desktop in the Display name field. b) Leave the application description blank and click Next. c) Select Server desktop and click Next.

62


©


3. Publish the server desktop of the San Francisco worker group. a) Click Add to open the Select Servers screen. b) Double-click Worker Groups. c) Double-click San Francisco to select it as the server to publish and click OK. d) Click Next. 4. Publish the server desktop to the Coolidge\Domain Admins group only. a) Click Add to open the Select Users or Groups screen. b) Click Add List of Names and type Coolidge\Domain Admins. c) Click Check Names and click OK, if the name was validated successfully. If the names were not validated successfully, make sure they are spelled correctly and are in the Coolidge\AccountName format. d) Click OK to close the Add List of Names window and click OK. e) Click Next to proceed to the Shortcut presentation screen. 5. Complete the publish application wizard using the default values. a) Click Next in the Shortcut presentation screen. b) Click Finish to complete the Publish Application wizard. 6. Close the Delivery Services Console.

©



63

Exercise 7-3: Testing and Managing Sessions Scenario You recently published several applications and server desktops and configured the Web Interface server. You need to test your work to ensure that there are no issues with the XenApp implementation thus far. You have also been asked to verify that the Citrix Engineer's account you configured earlier has full access to administrate the farm.




Testing the Published Resources Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixEngineer user for this task. Use the following procedure to test access to the published resources: 1. Log off of the XenAppServer-1 virtual machine and log back on as the Coolidge\CitrixEngineer user. 2. Configure the Citrix online plug-in to use webinterface.coolidge.net as the server address and log on to the Citrix online plug-in as the Coolidge\CitrixEngineer. a) Log on to the XenAppServer-1 virtual machine as the Coolidge\CitrixEngineer user. The Citrix online plug-in starts automatically. If the plug-in does not start, click Start > All Programs > Citrix > Online plug-in.

64


©


b) Type webinterface.coolidge.net in the Server address field and click Update. The Citrix online plug-in negotiates with the WebInterface server and display a logon prompt. c) Type the Coolidge\CitrixEngineer credentials and then click OK to log on. 3. Open the Notepad, CapitalReSources and XenAppServer Desktop published resources to ensure that they were published correctly. Do not close them. a) Click the Citrix online plug-in icon and select Desktops > XenAppServer Desktop to launch the XenAppServer Desktop. b) Click the Citrix online plug-in icon in the navigation tray and select Applications > Notepad to launch Notepad. c) Click the Citrix online plug-in icon and select Applications > Financial > CapitalReSources to launch the CapitalReSources application. Verify that all of the published resources launch successfully. Do not close the applications.

Testing Workspace Control Use the XenAppServer-2 virtual machine logged in as the Coolidge\CitrixEngineer user for this task. Use the following procedure to test Workspace Control functionality: 1. Log on to the XenAppServer-2 virtual machine as the Coolidge\CitrixEngineer user and configure the Citrix online plug-in to use webinterface.coolidge.net as the server address. a) Log on to the XenAppServer-2 virtual machine as the Coolidge\CitrixEngineer user. The Citrix online plug-in starts automatically. If the plug-in does not start, click Start > All Programs > Citrix > Online plug-in. b) Type webinterface.coolidge.net in the Server address field and click Update. The Citrix online plug-in negotiates with the WebInterfaceServer virtual machine and display a logon prompt. c) Type the Coolidge\CitrixEngineer credentials and then click OK to log on. 2. Verify that the sessions from XenAppServer-1 have been automatically transferred to XenAppServer-2 using the workspace control feature. 3. Close all windows and applications except for the CapitalReSources application.

Managing Sessions Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixEngineer user for this task.

©



65

Use the following procedure to manage user sessions: 1. Launch the Delivery Services Console on the XenAppServer-1 virtual machine. a) Switch to the XenAppServer-1 virtual machine. b) Click Start > All Programs > Citrix > Management Consoles > Delivery Services Console. 2. Complete the discovery process. Add the local computer using the XenApp Discovery wizard but do not include Single sign-on in your discovery. a) Click Next on the Discovery window, which appears automatically the first time the Delivery Services Console is opened. b) Deselect Single Sign-On and click Next. c) Click Add Local Computer and click Next. d) Click Next to configure the console. e) Click Finish to complete the Discovery wizard. 3. Use the Delivery Services Console on the XenAppServer-1 virtual machine to verify that CitrixEngineer sessions are active. a) Expand the XenApp > Coolidge nodes and click the Servers node. b) Click the Users tab to view the current sessions. c) Verify that the CapitalReSources sessions exist for the CitrixEngineer user. 4. Send a message to the CitrixEngineer's CapitalReSources session warning that "This session will be disconnected soon." a) Right-click on the CitrixEngineer's CapitalReSources session and select Send message. The Message window opens. b) Type This session will be disconnected soon. in the Message field and click OK. 5. Switch to the XenAppServer-2 virtual machine to view and accept the message and then switch back to the XenAppServer-1 virtual machine. 6. Log off the CitrixEngineer's CapitalReSources session using the Delivery Services Console and then switch to the XenAppServer-2 virtual machine to verify that the CapitalReSources application closed. a) Right click the CitrixEngineer's CapitalReSources session, click Log off and then click Yes to confirm. b) Repeat Step 6a on all of the CitrixEngineer sessions until none are listed. c) Switch to XenAppServer-2 virtual machine and confirm that the sessions were terminated. 7. Log off of the XenAppServer-1 and XenAppServer-2 virtual machines.

66


©


The ability to access the Delivery Services Console, send messages to user sessions and end user sessions confirms that the CitrixEngineer's permissions were configured correctly.

©



67

68


©


Module 8

Streaming Application Exercises

70

Module 8: Streaming Application Exercises

©


Exercise 8-1: Profiling Mozilla Firefox for Windows 7 Scenario Many of the applications, such as the CRM and ERP systems, that are used daily in the company are web applications. The vendors for all of the systems only guarantee compatibility with Mozilla Firefox. Therefore Mozilla Firefox must be published to all employees. The Citrix Architect decided that Mozilla Firefox should be profiled as a streaming application in order to gain the most flexibility in delivery options. Because Mozilla Firefox is such a mission-critical application and requires high performance, the Citrix Engineer decided to allow the Windows 7 laptops that are provisioned through IT's new provisioning policies to stream the application locally. You must profile the Mozilla Firefox application for Windows 7.

Before You Begin To begin this lab, ensure that the following virtual machines are started: • • • • •

Coolidge-DC Profiler-Win7 WebInterfaceServer XenAppServer-1 XenAppServer-2


Installing Streaming Profiler Use the Profiler-Win7 virtual machine logged in as the CitrixAdmin user for this task. Use the following procedure to install the Streaming Profiler on the Profiler-Win7 virtual machine: 1. Start the Profiler-Win7 virtual machine and log on as the CitrixAdmin user. 2. Attach the XA6_2008R2_ML.ISO media to the Profiler-Win7 virtual machine and launch the XenApp 6.0 Installer.

©



71

a) Attach the XA6_2008R2_ML.ISO media to the virtual machine. The AutoPlay window displays. b) Click Run autorun.exe in the AutoPlay window to start the installation. 3. Launch the Streaming Profiler installer. a) Click Manually install components > Common Components. b) Click Plug-ins, Streaming Profiler, and Documentation and then click Streaming Profiler to launch the Streaming Profiler Installer. 4. Install the Citrix Streaming Profiler using the default options and restart the virtual machine, when prompted. a) Click OK to accept English as the language and then click Next. b) Select I accept the license agreement and click Next. c) Click Next to accept the default destination folder. d) Click Install, wait for the installation to complete and then click Finish. e) Click Yes to restart the virtual machine.

Profiling an Application Use the Profiler-Win7 virtual machine logged in as the CitrixAdmin user for this task. Use the following procedure to profile an application for streaming: 1. Log on to the Profiler-Win7 virtual machine using your CitrixAdmin credentials. 2. Using the Citrix Streaming Profiler create a profile called Mozilla Firefox. a) Click Start > Streaming Profiler to open the Streaming Profiler. b) Click New Profile to launch the New Profile Wizard and then click Next. c) Type Mozilla Firefox as the Profile name and click Next. 3. Use the default User Updates and Inter-Isolation Communications options and verify that Windows 7 is selected as the target operating system. Specify to profile for all languages. a) Click Next to accept the default settings for User Updates. b) Click Next to accept the default settings for Inter-Isolation Communication. c) Verify that Windows 7 is selected as the Target operating system. The Windows Vista and Windows Server 2008 target operating systems will also be checked. d) Click All Languages in the target language section and then click Next.

72


©


4. Use the Quick Install option and specify the \\dc\filer \Software\Firefox Setup 3.6.3.exe installer. a) Select Quick Install and click Next. b) Click Browse, navigate to the \\dc\filer \Software\ folder, click Firefox Setup 3.6.3.exe and then click Open. c) Click Next to continue with the New Profile Wizard. 5. Install Mozilla Firefox from within the Streaming Profiler using the default options. a) Click Launch Installer to launch the Firefox installer. The Mozilla Firefox Setup window opens. b) Click Next on the Welcome screen and click Next to choose the default Standard Setup Type. c) Click Install to begin the Firefox installation and then wait for the Firefox installer to finish before continuing. d) Deselect Launch Firefox now and click Finish. 6. Use the Streaming Profiler to launch Firefox and run through its initial configuration without importing any settings and then close Mozilla Firefox. a) Click Next in the Run Installer window. b) Click Mozilla Firefox and click Run to launch Firefox and go through the initial configuration screens. The application opens. c) Click Don't import anything in the Firefox import wizard screen and then click Next. After a few moments, Firefox appears. d) Click File > Exit to exit Firefox. Click Quit to confirm. e) Click Next in the New Profile wizard. 7. Complete the Profiling wizard using the default choices and then save the profile to the \\dc\filer \Profiles folder. a) Click Next in the Select Applications screen to accept the default settings. b) Click Next in the Sign Profile screen to accept the default settings. c) Click Finish to build the profile. The profile for Mozilla Firefox builds. d) Click File > Save As and type \\dc\filer \Profiles as the profile save location and then click Save. The profile is saved to the application hub on the filer. 8. Shut down the Profiler-Win7 virtual machine.

©



73

Exercise 8-2: Profiling Mozilla Firefox for Window Server 2008 R2 Scenario Mozilla Firefox is considered a mission-critical application for Coolidge because it is used to access many web-based applications that are essential for the company's daily activities. The Citrix Engineer wants to ensure that all employees will have access to Mozilla Firefox even if direct streaming is not an option. The Citrix Engineer wants you to create a target for Windows Server 2008 R2 in the Mozilla Firefox profile in order to: • Allow the application to fall back to streaming to the server if the application is unable to stream directly to the client device. • Ensure that Mozilla Firefox can be streamed to additional servers without having to install it manually on each server. Another administrator has already started profiling other applications for Windows Server 2008 R2 on a virtual machine called Profiler-2008R2. This administrator has allowed you to use this pre-configured virtual machine for your purposes.


Coolidge-DC Profiler-2008R2 WebInterfaceServer XenAppServer-1 XenAppServer-2


Profiling for Multiple Target Operating Systems Use the Profiler-2008R2 virtual machine logged in as the Administrator user for this task.

74


©


Use the following procedure to add a target to an existing profile: 1. Start and log on to the Profiler-2008R2 virtual machine as the Administrator user. 2. Open the existing Mozilla Firefox profile located at \\dc\filer \Profiles\Mozilla Firefox\Mozilla Firefox.profile in the Streaming Profiler. a) Click Start > All Programs > Citrix > Streaming Profiler to launch the Citrix Streaming Profiler. b) Click Open Profile, navigate to \\dc\filer \Profiles\Mozilla Firefox, select Mozilla Firefox.profile and then click Open. 3. Add a Windows Server 2008 R2 target to the Mozilla Firefox profile for use with all languages. a) Right-click Mozilla Firefox and click Add New Target. b) Click Next to begin the wizard. c) Verify that Windows Server 2008 R2 64-bit Edition is selected. d) Select All languages in the Target Language section and click Next. 4. Use the Quick Install option and specify the \\dc\filer \Software\Firefox Setup 3.6.3.exe installer. a) Select Quick Install and click Next. b) Click Browse, navigate to the \\dc\filer \Software\ folder, click Firefox Setup 3.6.3.exe and then click Open. c) Click Next to continue with the New Target Wizard. 5. Install Mozilla Firefox from within the Streaming Profiler using the default options. a) Click Launch Installer to launch the Firefox installer. The Mozilla Firefox Setup window opens. b) Click Next and then click Next to choose the default Standard Setup Type. c) Click Install to begin the Firefox installation and then wait for the Firefox installer to finish before continuing. d) Deselect Launch Firefox now and click Finish. 6. Use the Streaming Profiler to start Firefox and run through its initial configuration without importing anything and then close Mozilla Firefox. a) Click Next in the New Target wizard. b) Select Mozilla Firefox and then click Run to launch Firefox and go through the initial configuration screens. The application opens. c) Click Don't import anything in the Firefox import wizard screen and then click Next. In a few moments, Firefox appears. d) Click File > Exit to exit Firefox. Click Quit to confirm.

©



75

e) Click Next in the New Target Wizard. 7. Complete the Profiling wizard using the default choices and then save the profile to the \\dc\filer \Profiles folder. a) Click Next in the Select Applications screen to accept the default settings. b) Click Next in the Sign Profile screen to accept the default settings. c) Click Finish to build the profile. The profile for Mozilla Firefox builds. d) Click File > Save. The profile is saved to the application hub on the filer. 8. Close the Mozilla Firefox profile to remove it from the Streaming Profiler. Do not close the Streaming Profiler. a) Verify that Mozilla Firefox is selected. b) Click File > Close to close the Mozilla Firefox profile. Do not close the Streaming Profiler.

76


©


Exercise 8-3: Profile Linking Mozilla Firefox and Adobe Reader Scenario The Citrix Engineer was reading over the deployment plan and came across an item that was previously overlooked. Users often have to use and generate PDFs from within the the CRM and ERP systems and therefore require a way to view the PDFs through the Mozilla Firefox streaming profile. In order to meet these new requirements, the Citrix Engineer created a profile for Adobe Reader and saved it to the Profiles folder on the filer. You must now create a profile that links these two profiles together so that the applications can communicate with one another.


Coolidge-DC Profiler-2008R2 WebInterfaceServer XenAppServer-1 XenAppServer-2


Creating a Linked Profile Use the Profiler-2008R2 virtual machine logged in as the Administrator user for this task. Use the following procedure to create a linked profile: 1. Create a new profile called "Mozilla Firefox with Adobe Reader" on the Profiler-2008R2 virtual machine. a) Click File > New within the Streaming Profiler to launch the New Profile wizard and click Next. b) Type Mozilla Firefox with Adobe Reader and click Next.

©



77

2. Use the default user updates settings and add both Adobe Reader and Mozilla Firefox into the inter-isolation environment. Specify to make this profile one that links to other profiles. a) Click Next on the Enable User Updates screen. b) Click Browse on the Set up Inter-Isolation Communication screen, type \\dc\filer \Profiles into the Profile directory field and click OK. c) Select the Adobe Reader and Mozilla Firefox profiles and click Next. d) Select Create a profile that only links to other profiles (no install needed) and click Next. 3. Complete the Profiling wizard using the default settings and then save the profile to the \\dc\filer \Profiles folder. a) Click Next on the Sign Profile screen and then click Finish to build the new linked profile. b) Click File > Save, type \\dc\filer \profiles\ in the Profile directory field and click Save to save the profile to this location. 4. Shut down the Profler-2008R2 virtual machine.

78


©


Exercise 8-4: Publishing Firefox as a Streaming Application Scenario You recently created robust profiles for Mozilla Firefox and Adobe Reader. You now need to publish these profiles as streaming applications and then test that the profiles are working correctly.




Publishing Firefox as a Streaming Application Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to publish streaming applications: 1. Log on to the XenAppServer-1 virtual machine as the Coolidge\CitrixAdmin user. 2. Use the Delivery Services Console to start publishing Mozilla Firefox. a) Click Start > All Programs > Citrix > Management Consoles > Delivery Services Console. b) Expand the XenApp > Coolidge nodes. c) Right-click Applications and click Publish application. d) Click Next to begin the Publish Application wizard. e) Type Mozilla Firefox in the Display Name field and click Next.

©



79

3. Configure the application to be streamed if possible otherwise accessed from a server. Specify for it to be a streamed to server application. a) Verify that Application is selected as the type of application to publish and click Streamed if possible, otherwise accessed from a server. b) Select Streamed to Server in the Server application type drop-down menu and then click Next. 4. Use the \\dc\filer \Profiles\Mozilla Firefox with Adobe Reader profile and specify Mozilla Firefox as the application to launch from the profile. a) Click Browse, navigate to the \\dc\filer \Profiles\Mozilla Firefox with Adobe Reader\ folder and double-click the Mozilla Firefox with Adobe Reader.profile file. b) Select Mozilla Firefox in the Application to launch from the Citrix streaming application profile drop-down menu. c) Click Next. 5. Click Next to use the default settings for offline access. 6. Publish the application to the Firefox worker group. a) Click Add to open the Select Servers screen. b) Double-click Worker Groups. c) Double-click Firefox to select it as the servers on which to publish the application and click OK. d) Click Next to proceed to the Users screen. 7. Publish Mozilla Firefox to all domain users. a) Click Add to open the Select Users or Groups screen. b) Click Add List of Names and type Coolidge\Domain Users. c) Click Check Names and click OK, if the name validates successfully. If the names were not validated successfully, make sure they are spelled correctly and are in the Coolidge\AccountName format. d) Click OK to close the Add List of Names window and click OK. e) Click Next to proceed to the Shortcut presentation screen. 8. Complete the Publish Application wizard using the default settings. a) Click Next and then click Finish to complete the Publish Application wizard.

Testing Mozilla Firefox Use the XenAppServer-2 virtual machine logged in as the Coolidge\CitrixAdmin user for this task.

80


©


Use the following procedure to verify that Mozilla Firefox can stream successfully to a server and to a client device: 1. Log on to the XenAppServer-2 virtual machine as the Coolidge\CitrixAdmin user. 2. Cancel out of the Change Server screen. Log on to the http://webinterface.coolidge.net web site as the Coolidge\CitrixAdmin user. a) Click Cancel in the Change Server - Citrix online plug-in screen. b) Click Start > Internet Explorer, type http://webinterface.coolidge.net in the Address field and press Enter to access the XenApp Web site. c) Log on to the site using the Coolidge\CitrixAdmin credentials. 3. Launch Mozilla Firefox from the Web Interface and use the Connection Center to verify that the application is being streamed to the server. a) Click Mozilla Firefox in the Web Interface to launch Firefox. b) Select Don't import anything and click Next, if prompted with the import wizard. After a few moments, Mozilla Firefox appears. c) Right-click the Citrix online plug-in icon in the Windows notification area and click Connection Center. The Citrix Connection Center launches and loads the ICA connection status. d) Locate the Mozilla Firefox published instance in the Connection Center. Mozilla Firefox appears as an ICA connection in the Citrix Connection Center because it is being streamed to a server and then delivered to the client device through the ICA protocol. This means that the application was successfully profiled for Windows Server 2008 R2 and published as a streamed to a server application.

4. Close all open windows. 5. Configure the Citrix online plug-in to use http://webinterface.coolidge.net as the server address. a) In the Windows notification area, right-click the Citrix online plug-in icon and click Change Server. b) Type http://webinterface.coolidge.net in the Server address field and click Update. The Citrix online plug-in log on window appears. 6. Log on to the Citrix online plug-in as the Coolidge\CitrixAdmin user and launch Mozilla Firefox. a) Type your Coolidge\CitrixAdmin credentials and then click OK to log on to the XenApp Services site through the Citrix online plug-in.

©



81

b) Click the Citrix online plug-in icon in the notification tray and click Applications > Mozilla Firefox. After a few moments, Mozilla Firefox will appear. 7. Verify that the application is being streamed to the client device and then close all open windows. a) Right-click the Citrix online plug-in icon and notice that the Connection Center option does not appear. The Connection Center only appears when there are active ICA sessions. When an application is streamed to a client device, an ICA connection is not used. The lack of the Connection Center means that the application was successfully profiled for Windows 7 and that it was successfully published to stream to a client device. b) Close all open windows.

82


©


Module 9

Configuring Policies Exercises

84

Module 9: Configuring Policies Exercises

©


Exercise 9-1: Creating a Policy to Improve WAN Performance Scenario Employees frequently work from remote locations as a result of the new Coolidge telecommuting program and client visits. Employees must be able to access their published applications and use them even over the most inconsistent WAN connections. The Citrix Engineer wants you to put a policy in place that will optimize the experience for employees logging in over a WAN connection.




Improving Session Performance Across a WAN Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to create a policy to improve session performance for users connecting across a WAN. 1. Use the Group Policy Management console on the XenAppServer-1 virtual machine to edit the Default Domain Policy and access the Citrix User Policies node. a) Click Start > Administrative Tools > Group Policy Management. b) Navigate to Forest: Coolidge.net > Domains > Coolidge.net. c) Right-click XenApp Domain Policy and select Edit. d) Navigate to User Configuration > Policies > Citrix Policies.

©



85

2. Create a new Citrix user policy called "WAN Access for All Users" and add an ICA audio setting to set the audio quality to medium - optimized for speech. a) Click New, type WAN Access for All Users as the policy name and click Next. b) Click Audio under the ICA category and select Audio quality. c) Click Add and select Medium - optimized for speech from the Value drop-down menu. d) Click OK to add the setting. 3. Add a setting to set the Menu animations to prohibited. a) Click Desktop UI under the ICA category and select Menu animation. b) Click Add and select Prohibited to prohibit menu animations. c) Click OK to add the setting. 4. Add a setting to prohibit the viewing of window contents while dragging. a) Click Desktop UI under the ICA category and select View window contents while dragging. b) Click Add and click Prohibited to prohibit showing window contents when dragging. c) Click OK to add the setting. 5. Add a setting to set the TWAIN compression level setting to high. a) Click TWAIN devices under the ICA category and select TWAIN compression level. b) Click Add and select High from the Value drop-down menu. c) Click OK to add the setting. 6. Create a filter that applies this policy against all domain users. a) Click Next to continue to the filters screen. b) Select User, click Add and then click Add in the New Filter window. c) Verify that Allow is selected in the Mode drop-down menu and type Coolidge\Domain Users in the User name field. d) Click OK to save the new filter element. 7. Create a filter that denies the policy to IP addresses within the Coolidge internal network IP range of 192.168.1.1-192.168.255.255. a) Click OK to close the new user filter screen. b) Select Client IP Address and click Add. c) Click Add in the New Filter window. d) Select Deny from the Mode drop-down menu. e) Type 192.168.1.1-192.168.255.255 in the Client IP address field and click OK to save the new filter element. 8. Finish adding filters, enable the policy and then save it.

86


©


a) Click OK to close the New Filter screen. b) Click Next to finish adding filters. c) Verify that Enable this policy is selected and then click Save.

©



87

Exercise 9-2: Creating a Policy to Restrict User Access Scenario One of the most important issues for Coolidge's clientele is privacy. This need for privacy and the desire to keep all data in the datacenter was also one of the driving factors for the adoption of XenApp at the company. The Citrix Engineer wants you to create a Citrix policy to help restrict the ability for employees to store or copy data locally. However, the Coolidge Advisors team requires the ability to store and manipulate customer data locally. The members of this team have received special security and privacy training and have laptops with full drive encryption. Management wants you to make sure that this policy will not affect the Advisors team. The Citrix Engineer also wants you to implement an important XenApp best practice that hides server drives from within delivered hosted applications in order to prevent users from saving to or accessing any parts of the server hard disks.




Restricting User Access Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to prevent users from accessing their client clipboard and client drives: 1. Create a new user policy called "Restricting Local Data Transfer" and add a setting to prohibit client clipboard redirection.

88


©


a) b) c) d)

Click New, type Restricting Local Data Transfer and click Next. Click ICA and select Client clipboard redirection. Click Add and then select Prohibited. Click OK to add the setting.

2. Add a setting to prohibit client drive redirection. a) Click File Redirection under the ICA category and select Client Drive Redirection. b) Click Add and then select Prohibited. c) Click OK to add the setting. 3. Create a filter that applies this policy against all domain users. a) Click Next to continue to the filters screen. b) Select User, click Add and then click Add in the New Filter window. c) Verify that Allow is selected in the Mode drop-down menu and type Coolidge\Domain Users in the User name field. d) Click OK to save the new filter element. 4. Create a filter that denies this policy to the Advisors group. a) Click Add in the New Filter window. b) Select Deny in the Mode drop-down menu, type Coolidge\Advisors in the User name field and click OK to save the new filter element. 5. Finish adding filters, enable the policy and then save it. a) Click OK to close the New Filter screen. b) Click Next to finish adding filters. c) Verify that Enable this policy is selected and then click Save.

©



89

Exercise 9-3: Creating a Policy to Configure Shadowing Scenario The new manager of the Coolidge Help Desk has been working to find ways to increase support quality and reduce call and issue resolution times. He plans to use XenApp to allow help desk employees to shadow other employees, with permission, while on a help desk call so that they can more easily diagnose and fix the issue. You have been asked to create a policy that allows the Help Desk to shadow all Coolidge employees with their consent.




Configuring a Shadow Policy Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to configure a shadow policy: 1. Create a new user policy called "Shadowing" that allows input from shadow connections. a) Click New, type Shadowing in the Name field and click Next. b) Click Shadowing under the ICA category and select Input from shadow connections. c) Click Add, confirm that Allowed is selected and then click OK. 2. Add a setting to log all shadow attempts. a) Select Log shadow attempts. b) Click Add, confirm that Enabled is selected and then click OK.

90


©


3. Assign shadowing rights to the Coolidge\Domain Admins and Coolidge\HelpDesk groups. a) Select Users who can shadow other users and click Add. b) Click Add and type Coolidge\Domain Admins;Coolidge\HelpDesk in the Enter the object names to select field. c) Click Check Names to validate the names. If the names were not validated successfully, make sure they are spelled correctly and are in the Coolidge\AccountName format. d) Click OK and then click OK to add the users to the setting. 4. Add a setting to notify users of shadowing requests and then enable the policy. a) Select Notify user of pending shadow connections. b) Click Add, confirm that Enabled is selected and then click OK. 5. Create a filter that applies this policy against all domain users. a) Click Next to continue to the filters screen. b) Select User, click Add and then click Add in the New Filter window. c) Verify that Allow is selected in the Mode drop-down menu and type Coolidge\Domain Users in the User name field. d) Click OK to save the new filter element. 6. Create a filter that denies this policy to the Advisors group. a) Click Add in the New Filter window. b) Select Deny in the Mode drop-down menu, type Coolidge\Advisors in the User name field and click OK to save the new filter element. 7. Finish adding filters, enable the policy and then save it. a) Click OK to close the New Filter screen. b) Click Next to finish adding filters. c) Verify that Enable this policy is selected and then click Save.

©



91

Exercise 9-4: Testing the Policies Scenario You recently created three new policies that improve session performance when connecting from a WAN, restrict user access to the clipboard and client drives and enable shadowing by the Help Desk. Now you need to test each of these policies to ensure that they are configured correctly and produce the expected outcome. To aid in testing, the Citrix Engineer created two new accounts: TestUser and TestAdvisor. TestUser is a user that simulates a standard user, while TestAdvisor is a member of the Advisor's active directory group and is being used to simulate a member of the Advisor's team.




Testing a Regular User Against Policy Use the XenAppServer-2 virtual machine logged in as the Coolidge\TestUser user for this task. Use the following procedure to verify that a regular user cannot save files to a client drive as a result of the Restricting Local Data Transfer policy: 1. Log off as the CitrixAdmin user on the XenAppServer-2 virtual machine and log on as the Coolidge\TestUser user. 2. Access the http://webinterface.coolidge.net web site. a) Click Start > Internet Explorer. b) Navigate to http://webinterface.coolidge.net.

92


©


3. Log on to the Web Interface as the Coolidge\TestUser user and launch the published Notepad application. a) Type the Coolidge\TestUser credentials and log on to the Web Interface site. b) Click Notepad to launch Notepad through the Web Interface. Within a few moments, Notepad launches. c) Select Do not ask me again for this site and click Yes on the USB/Other devices security warning, if it appears. 4. Attempt to save the Notepad document through client drive mapping to the XenAppServer-2 desktop. a) Click File > Save As, click Computer to see all of the connected drives. No network drives appear. Locally mapped drives would normally appear as network drives, so it is confirmed that this user is unable to save to the local XenAppServer-2 virtual machine due to the Restricting Local Data Transfer policy that was previously created. 5. Close Notepad, log off of the Web Interface and log off of the XenAppServer-2 virtual machine. a) Click Cancel to close the Save as screen and click File > Exit to close Notepad. b) Click Log off in the Web Interface to log off the TestUser from the Web Interface. c) Click Start > Logoff to log off of the XenAppServer-2 virtual machine.

Testing an Advisor User Against Policy Use the XenAppServer-2 virtual machine logged in as the Coolidge\TestAdvisor user for this task. Use the following procedure to verify that members of the Advisors group are not prevented from saving files locally by the Restricting Local Data Transfer policy: 1. Log on to the XenAppServer-2 virtual machine as the Coolidge\TestAdvisor user and access the http://webinterface.coolidge.net web site. a) Log on to the XenAppServer-2 virtual machine as the Coolidge\TestAdvisor user. b) Click Start > Internet Explorer and navigate to http://webinterface.coolidge.net. 2. Log on to the Web Interface as Coolidge\TestAdvisor user and launch the published Notepad application. a) Log on as the Coolidge\TestAdvisor user. b) Click Notepad to launch Notepad through the Web Interface. Within a few moments, Notepad launches.

©



93

3. Save the Notepad document as "Document Saving Test" to the XenAppServer-2 desktop. a) Click File > Save As and click Computer to see all of the connected drives. Network drives appear in the Other section that maps to the drives on the XenAppServer-2. Even though the policy forbids this, it was not applied to the Advisors group to which the TestAdvisor user is a member. b) Double-click Local Disk (C: on XenAppServer-2) c) Select Do not ask me again for this site and click Yes in the File Security warning. d) Navigate to the \Users\TestAdvisor\Desktop folder. e) Type Document Saving Test in the File name field and click Save. f) View the XenAppServer-2 desktop and verify that the Document Saving Test file has been saved successfully. Because the file saved successfully to the local desktop from a published application, the policy Advisors group was successfully omitted from the policy that restricts access to client drives. 4. Do not close Notepad or log off of the XenAppServer-2 virtual machine.

Testing the Shadowing Policy Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to verify that the Shadowing policy allows the Coolidge\CitrixAdmin account to successfully shadow a user session: 1. Use the Citrix Delivery Services Console on the XenAppServer-1 virtual machine to view the active sessions in the farm. a) Click Servers in the Delivery Services Console to view server information. b) Click the Users tab to view the current ICA sessions on the servers. An entry appears showing the TestAdvisor account is currently connected to the Notepad application. 2. Shadow the TestAdvisor's session from the Delivery Services Console using your Coolidge\CitrixAdmin credentials. a) Right-click the TestAdvisor session and click Shadow to initiate a Shadow request. b) Click OK to begin the shadowing session. In a few moments the shadowing session will begin but will be paused until the shadowed user accepts the request. This request will time out after a few seconds. c) Type the Coolidge\CitrixAdmin credentials to log on to the shadowing session. 3. Accept the shadowing request on the XenAppServer-2 virtual machine and then switch back to the XenAppServer-1 virtual machine. a) Switch to the XenAppServer-2 virtual machine.

94


©


b) Click Yes in the Remote Control Request dialog. The Shadowing indicator box appears in the upper left corner indicating that the session is currently being shadowed. c) Switch to the XenAppServer-1 virtual machine. 4. Type "Hello World!" in the shadowed Notepad application and verify that the message is reflected on the XenAppServer-2 virtual machine. a) Type Hello World! within the shadowed Notepad session. b) Switch to the XenAppServer-2 and verify that the Hello World message is reflected in the Notepad application. 5. Stop the shadowing session and log off the session from the XenAppServer-2 virtual machine. a) Click Stop shadowing on the XenAppServer-2 virtual machine to end the shadowing of the session. b) Click Start > Logoff to log the TestAdvisor user off the XenAppServer-2 virtual machine. 6. Use the Delivery Services Console on the XenAppServer-1 virtual machine to reset all user sessions. a) Switch to the XenAppServer-1 virtual machine and bring the Delivery Services Console to the front. b) Right-click the TestAdvisor session and click Reset. Click Yes to confirm.

©



95

96


©


Module 10

Configuring Load Mananagement Exercises

98

Module 10: Configuring Load Mananagement Exercises

©


Exercise 10-1: Assigning a Custom Load Evaluator Scenario The Citrix Engineer is working on creating a load balancing and failover policy between the San Francisco and New York datacenters. He needs you to create a scaled down example of a planned custom load evaluator to test the behavior of a failover policy when a server or site shows a full load.




Configuring a Custom Load Evaluator Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to configure a custom load evaluator: 1. Use the Citrix Delivery Services Console, on the XenAppServer-1 virtual machine to view the default load evaluators. a) Click Start > All Programs > Citrix > Management Consoles > Citrix Delivery Services Console, on the XenAppServer-1 virtual machine, if the Delivery Services Console is not already open. b) Navigate to Citrix Resources > XenApp > Coolidge > Load Evaluators. c) View the existing load evaluators.

©



99

2. Create a new Load Evaluator called [Test] Max 1 Instance Per Server that uses the application user load indicator to report a full load when the number of users running the Notepad application equals 1. a) Right-click Load Evaluators and select New > Add load evaluator. b) Type [Test] Max 1 Instance Per Server in the Name field. c) Select Application User Load and type 1 in the Report full load when the number of users for this application equals field. d) Click Browse, and select Notepad and click OK in the Select an Application window. e) Click OK in the Add Load Evaluator window.

Assigning a Load Evaluator to a Server Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to assign a custom load evaluator to a server: Assign the [Test] Max 1 Instance Per Server load evaluator to the XenAppServer-1 server. a) Expand the Servers node in the Delivery Services Console. b) Right-click XENAPPSERVER-1 and select Other tasks > Assign load evaluator. c) Select [Test] Max 1 Instance Per Server from the Load Evaluator drop-down menu and click OK.

100


©


Exercise 10-2: Creating a Failover Situation Scenario You recently created a custom load evaluator in order to test a load balancing policy. You need to create a load balancing policy and demonstrate that requests will fail over to the other site when servers in the first site become full. Use the test load evaluator that was previously created in order to simulate a server experiencing a full load.




Load Balancing an Application Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to create a load balancing policy: 1. Use the Citrix Delivery Services Console to create a new Load Balancing policy called San Francisco Failover to New York. a) Right-click the Load Balancing Policies node and select Create load balancing policy. b) Type San Francisco Failover to New York in the Name field. 2. Create a filter for the San Francisco Employees group. a) Navigate to Filters > Users then select Filter based on user. b) Click Add and click OK in the warning dialog.

©



101

c) Type Coolidge\San Francisco Employees in the Enter object names to select field, click Check Name and then click OK, if the name is validated successfully. If the names were not validated successfully, make sure they are spelled correctly and are in the Coolidge\AccountName format. 3. Configure the application connection preference based on worker group by adding the San Francisco worker group only. a) Click on the Worker Group Preference node. b) Select Configure application connection preference based on worker group and click Add. c) Double click San Francisco and click OK in the Select Servers window. d) Click OK to finish and save the new load balancing property.

Testing a No Service Situation without Failover Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to test a service failure situation without a failover specified: 1. Log out of the Citrix online Plug-in on the XenAppServer-1 virtual machine and log back on as the TestUser account. Launch the CapitalReSources application. a) Use the Citrix online plug-in to log on as the Coolidge\TestUser user. b) Click the Citrix online Plug-in icon and click Notepad to launch the application. Wait for the application to launch before continuing. 2. Log on to the XenAppServer-2 virtual machine as the CitrixAdmin user, log on to the Web Interface using the CitrixAdmin account through Internet Explorer and launch the Notepad application. a) Switch to the XenAppServer-2 virtual machine. b) Log on to the XenAppServer-2 virtual machine as the CitrixAdmin user. c) Click Start > Internet Explorer and navigate to the Web Interface site at http://webinterface.coolidge.net. d) Log on to the Web Interface as the CitrixAdmin user. e) Launch the Notepad application. An error appears. The load evaluator that was created and applied to XenAppServer-1 is reporting a full load and is no longer accepting connections.

3. Log off of the Web Interface and close Internet Explorer.

102


©


Exercise 10-3: Handling Failover with a Load Balancing Policy Scenario You recently created an artificial failover policy failure in which a server was reporting a full load but could not failover to another server. Now you need to complete the failover policy so that it works as intended and verify that it does so. Once you verify that the failover policy is working correctly, restore each server to the default load evaluator.




Adding Failover to the Load Balancing Policy Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to add failover to the load balancing policy: 1. Log out of the Citrix online plug-in on the XenAppServer-1 virtual machine. a) Switch to the XenAppServer-1 virtual machine. b) Right-click the Citrix online plug-in icon in the notification area of the XenAppServer-1 virtual machine and click Log off. 2. Use the Delivery Services Console to edit the San Francisco Failover to New York load balancing policy. a) Click the Load Balancing Policies node in the Delivery Services console.

©



103

b) Right-click San Francisco Failover to New York and select Modify properties. 3. Add the New York worker group to the Load Balancing Failover Group. a) Navigate to Load Balancing Policies > Worker Group Preference and click Add. b) Double click New York and click OK. c) Confirm that the New York worker group priority is set to 2 and then click OK.

Testing a No Service Situation with Failover Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to test a service failure situation with failover: 1. Log back in to the Citrix online plug-in as the Coolidge\TestUser user and launch the Notepad application. a) Use the Citrix online plug-in to log on as the Coolidge\TestUser user. b) Click the Citrix online plug-in icon and click Notepad to launch the application. Wait for the application to launch before continuing. 2. Switch to the XenAppServer-2 virtual machine and use Internet Explorer to log on to the Web Interface and launch the Notepad application. a) Switch to the XenAppServer-2 virtual machine. b) Launch Internet Explorer and navigate to http://webinterface.coolidge.net. c) Log on to the Web Interface as the CitrixAdmin user. d) Click Notepad from the Web interface to launch the application. The application should launch normally indicating that the failover is in effect. 3. Close Notepad, log off of the Web Interface and close Internet Explorer on the XenAppServer-2 virtual machine. 4. Log off of the Citrix online plug-in on the XenAppServer-1 virtual machine.

Restoring to the Default Load Evaluator Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to restore the load evaulator back to the default: 1. View the load evaluator assigned to the XenAppServer-1 virtual machine. a) Expand the Servers node. b) Right-click XENAPPSERVER-2 and click Other Tasks > Assign load evaulator.

104


©


2. Change the load evaluator back to Default. a) Select Default from the Load Evaluator drop-down menu. b) Click OK to save these changes.

©



105

106


©


Module 12

Configuring Self-Service Applications Exercises

108

Module 12: Configuring Self-Service Applications Exercises

©


Exercise 12-1: Simulating a Plug-in Deployment Scenario The Citrix Engineer configured the Citrix Merchandising Server to deliver and support Citrix Receiver, which will be installed on all client devices. He also created a default deployment which includes the Citrix online, Citrix offline and Citrix Dazzle plug-ins. You must do a test deployment of Citrix Receiver on the EndUserSimulator virtual machine to verify that everything is configured correctly.

Before You Begin To begin this lab, ensure that the following virtual machines are started: • • • • • •

Coolidge-DC EndUserSimulator MerchandisingServer WebInterfaceServer XenAppServer-1 XenAppServer-2


Installing Citrix Receiver Use the EndUserSimulator virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to install Citrix Receiver using Merchandising Server: 1. Start the MerchandisingServer virtual machine. Start and log on to the EndUserSimulator virtual machine as the Coolidge\CitrixAdmin user. 2. Access the MerchandisingServer web site at http://merchandisingserver.coolidge.net and install Citrix Receiver. a) Click Start > All Programs > Internet Explorer to open Internet Explorer.

©



109

b) Navigate to https://merchandisingserver.coolidge.net. Be sure to use SSL/TLS to connect to Merchandising Server by specifying https in the address field. c) Select I agree to the Terms of Use and click Download Now to begin the Citrix Receiver download. d) Click Run to install Citrix Receiver. Wait while the installer installs and configures Citrix Receiver. This may take a few minutes. Citrix Receiver will automatically launch after it is successfully installed.

Downloading Preconfigured Deliveries Use the EndUserSimulator virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to download a plug-in package to the EndUserSimulator virtual machine using Citrix Receiver: 1. Log on to Citrix Receiver on the EndUserSimulator virtual machine as the Coolidge\CitrixAdmin user and allow the preconfigured plug-in package to download and install. a) Allow Citrix Receiver to automatically launch. b) When prompted to authenticate, log on using your Coolidge\CitrixAdmin credentials. Citrix Receiver begins installing the plug-ins that were pre-configured by the Citrix Engineer. c) Click Restart Now to restart the EndUserSimulator virtual machine, when prompted. 2. Log on to the EndUserSimulator virtual machine as the Coolidge\CitrixAdmin user. 3. Verify that the Citrix online plug-in, Citrix offline plug-in and Citrix Dazzle plug-ins were installed successfully. a) Click Start > Control Panel > Uninstall a program. b) Verify that the Citrix online plug-in, Citrix offline plug-in and Citrix Dazzle plug-ins are listed. There appears to be an issue. The Citrix Dazzle plug-in is not installed. The Citrix Engineer must have forgotten to include it in the plug-in delivery.

4. Restart the EndUserSimulator virtual machine, if prompted.

110


©


Exercise 12-2: Creating a New Delivery for Citrix Dazzle Scenario The plug-in package delivered by Citrix Receiver from the Merchandising Server was missing a plug-in. The Citrix Engineer must have forgotten to include the Citrix Dazzle plug-in in the original plug-in delivery. When you notified him of the error he asked you to create a new delivery to deploy Citrix Dazzle and fix his mistake. Because Citrix Dazzle will only be used initially with newly provisioned laptops from IT, you must create a new package that will only deliver Citrix Dazzle to new Windows 7 client devices.




Creating a Delivery Rule Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to create a delivery rule that will deliver the Citrix Dazzle plug-in to Windows 7 client devices: 1. Log on to the Merchandising Server Administration Console (https://merchandisingserver.coolidge.net/appliance), on the XenAppServer-1 virtual machine using the Coolidge\CitrixAdmin credentials . a) Switch to the XenAppServer-1 virtual machine.

©



111

b) Open Internet Explorer and navigate to https://merchandisingserver.coolidge.net/appliance to access the

Merchandising Server Administration Console. The Merchandising Server Administration Console is displayed. c) Log on using the Coolidge\CitrixAdmin credentials. 2. Create a new rule called Windows 7. a) Click Rules in the Citrix Merchandising Server Administrator Console. b) Click Create and type Windows 7 in the Name field. 3. Set the rule to check for the Windows 7 operating system and then save the rule. a) Select Operating system from the Field drop-down menu. b) Verify that Is is set as the operator and select Windows 7 in the Value field. c) Click Save.

Configuring a Plug-In Deployment Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to configure the delivery package for use with Merchandising Server and Citrix Receiver: 1. Create a new delivery in the Merchandising Server Console and configure the delivery package information with the following information: • • • • • •

Delivery name: Citrix Dazzle Evaluation order: 1 Default delivery: False Silent install: Yes Check for updates: 1 Completion text: Citrix Dazzle has been successfully installed.

a) b) c) d) e) f)

Click Deliveries and then click Create. Type Citrix Dazzle in the Delivery name field. Select 1 as the Evaluation order. Select Yes for Silent install. Type 1 in the Check for updates field. Type Citrix Dazzle has been successfully installed. in the Completion text field.

2. Add the Citrix Dazzle plug-in to the delivery. a) Click the 2 - Plug-ins tab and click Add.

112


©


b) Select Dazzle plug-in and click Add. 3. Use the following information to configure the Dazzle plug-in stores. Allow users to add stores and save passwords. • Store name: The Coolidge Store • Address: http://webinterface.coolidge.net/Citrix/PNAgent/config.xml • Store description: The Coolidge Dazzle Store a) Click the 3 - Configuration tab. b) Type The Coolidge Store;http://webinterface.coolidge.net/Citrix/PNAgent/config.xml;on;The Coolidge Dazzle Store in the Store configuration field.

Ensure that the address information is entered correctly as shown in the format Store name;Location;on;Store description. If it is not entered correctly, subsequent exercises may not work. c) Type A in the Allow users to add stores and the Allow users to save passwords fields to enable these features. 4. Add the Windows 7 rule to the delivery in order to only install these plug-ins on Windows 7 machines. a) Click the 4 - Rules tab. b) Click Add, select the Windows 7 rule listed and click Add. 5. Set the delivery to deliver now and then complete the delivery configuration process. a) Click the 5 - Schedule tab. b) Verify that Deliver Now is selected and then click Schedule.

©



113

Exercise 12-3: Using Citrix Dazzle Scenario You recently created a delivery rule to deploy the Citrix Dazzle plug-in to Windows 7 client devices. You need to test the delivery to make sure that it was successfully configured and then test Citrix Dazzle to verify that you can install self-service applications.




Configuring Citrix Dazzle Use the EndUserSimulator virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to test the delivery of the Citrix Dazzle plug-in using Citrix Receiver: 1. Log on to the EndUserSimulator virtual machine as the Coolidge\CitrixAdmin user. 2. Configure Citrix Receiver to always be present in the Windows 7 notification tray. a) Click the Show hidden icons arrow in the notification tray and click Customize. b) Select Show icon and notifications from the Behaviors drop-down menu next to the Citrix Receiver Application entry. c) Click OK to save the change and close the window. 3. Allow Citrix Receiver to automatically start and download any new plug-ins. Citrix Dazzle will prompt you when the new plug-in is installed.

114


©


a) Allow Citrix Receiver to automatically start and download new plug-ins. b) Click Continue when prompted.

Testing Citrix Dazzle Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to verify that self-service applications can be added to Citrix Dazzle: 1. Log on to Citrix Dazzle using the Coolidge\CitrixAdmin credentials. a) Click Get Started. b) Log on to the Coolidge Dazzle Store using the Coolidge\CitrixAdmin credentials. 2. Add the CapitalReSources, Mozila Firefox and Notepad applications to the EndUserSimulator virtual machine. a) Click Add next to the CapitalReSources, Mozilla Firefox and Notepad entries to add each application. b) Click Dazzle Apps and verify that CapitalReSources, Mozilla Firefox and Notepad are present. 3. Launch CapitalReSources, Mozilla Firefox and Notepad to ensure that they are configured correctly. a) Click Start > All Programs > Dazzle Apps > CapitalReSources to launch the application. b) Click Start > All Programs > Dazzle Apps > Mozilla Firefox to launch the application. c) Click Start > All Programs > Dazzle Apps > Notepad to launch the application. 4. Close all open windows after all applications launch successfully.

©



115

116


©


Module 13

Configuring Printing Exercises

118

Module 13: Configuring Printing Exercises

©


Exercise 13-1: Identifying Printer Defaults Scenario The Citrix Architect wants you to report on the default XenApp printer behavior for common printers that are in use at Coolidge to ensure that her plans to lock down printer access will be successful. Your job is to investigate how XenApp handles the printer drivers for several of the networked and locally connected printers that are common within the company.




Verifying Default Printer Driver Creation Use the EndUserSimulator virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to verify the default printer driver creation behavior: 1. Launch the Notepad application through Citrix Dazzle on the EndUserSimulator virtual machine. a) Click Start > All Programs > Dazzle Apps > Notepad. After a moment, the Notepad application will launch through XenApp. b) Select Do not ask me again for this site and click Yes on the USB/Other devices security warning, if it appears. 2. Use the Print dialog to verify what each auto-created printer is using as its default printer driver. a) Click File > Print in Notepad.

©



119

b) Right-click HP Color LaserJet 9500 PCL 6 (from ENDUSER) and click Properties. Make note of the printer driver listed in the Model field. c) Repeat the previous step to check the default printer drivers for the HP Color LaserJet 4600 PCL 6, HP Color and LaserJet CP2020 Series PCL 6. Verify that all of the listed printers are using their native print drivers except for the HP Color LaserJet 4600 PCL 6 that is using the Citrix Universal Print Driver. 3. Close Notepad and log off of the EndUserSimulator virtual machine. a) Click File > Exit to close the Notepad application. b) Click Start and then click the Arrow near Shut down. Click Log off to log off of the EndUserSimulator virtual machine.

120


©


Exercise 13-2: Disallowing Auto-Creation of a Trouble Printer Scenario You recently gave a report to the Citrix Architect about how XenApp is handling drivers. She noticed, with your report, that one of the printers in common use around Coolidge causes issues in some situations and that a fix from the vendor is expected soon. In the interim, the Citrix Architect wants you to use the Driver Compatibility List to disallow the auto-creation of these printers.




Managing Driver Compatibility Lists Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to manage driver compatibility lists: 1. Use the Group Policy Management Tool on the XenAppServer-1 virtual machine to modify the XenApp Domain Policy. Access the Citrix User Policies node. a) Click Start > Administrative Tools > Group Policy Management to launch the Group Policy Management Tool. b) Navigate to Forest: coolidge.net > Domains > coolidge.net, right-click XenApp Domain Policy and select Edit. c) Navigate to User Configuration > Policies > Citrix Policies.

©



121

2. Create a new policy called Do Not Allow HP 4600 that restricts driver mapping for the HP Color LaserJet 4600 Series PCL6 printer. Once created, continue to the filters screen. a) Click New, type Do Not Allow HP 4600 and click Next to continue to the settings screen. b) Select ICA > Printing > Drivers, click Printer driver mapping and compatibility and click Add. c) In the Add Setting window, click Add, type HP Color LaserJet 4600 PCL6 in the Driver Name field and select Do not create. d) Click OK in the Add driver mapping and Add Setting windows. 3. Create a filter that applies this policy to all domain users. a) Click Next to continue to the filters screen. b) Select User, click Add and then click Add in the New Filter window. c) Verify that Allow is selected in the Mode drop-down menu and type Coolidge\Domain Users in the User name field. d) Click OK to save the new filter element. 4. Finish adding filters, enable the policy and then save it. a) Click OK to close the New Filter screen. b) Click Next to finish adding filters. c) Verify that Enable this policy is selected and then click Save.

122


©


Exercise 13-3: Disabling Auto-Creation of Client Printers Scenario One of the client data privacy safeguards is to control and restrict where employees can print the data. The company's privacy policy specifies that printing may only be done on approved printers within the company. You need to create a policy that disables the auto-creation of client printers for all employees, except for the Advisors team which has special permission and training to handle sensitive data.


Coolidge-DC EndUserSimulator WebInterfaceServer XenAppServer-1 XenAppServer-2


Configuring Printing with Policies Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to create a policy to disable auto-creation of client printers: 1. Create a new Citrix user policy called Disable Client Printer Auto-creation and add an ICA Client Printer setting to disable auto-creation of client printers. a) Click New, type Disable Client Printer Auto-creation and click Next. b) Click ICA > Printing > Client Printers and select Auto-create client printers. c) Click Add and select Do not auto-create client printers from the Value drop-down menu. d) Click OK to add the setting.

©



123

2. Create a filter that applies this policy against all domain users. a) Click Next to continue to the filters screen. b) Select User, click Add and then click Add in the New Filter window. c) Verify that Allow is selected in the Mode drop-down menu and type Coolidge\Domain Users in the User name field. d) Click OK to save the new filter element. 3. Create a filter that denies this policy to the Advisors group. a) Click Add in the New Filter window. b) Select Deny in the Mode drop-down menu, type Coolidge\Advisors in the User name field and click OK to save the new filter element. 4. Finish adding filters, enable the policy and then save it. a) Click OK to close the New Filter screen. b) Click Next to finish adding filters. c) Verify that Enable this policy is selected and then click Save.

124


©


Exercise 13-4: Creating Session Printers for All Employees Scenario You have been tasked with locking down the printing functionality in XenApp in order to adhere to the company's strict client privacy policy. You need to continue to implement these changes by using policies to create the initial set of approved internal session printers that will be available for employees to print.




Configuring Session Printers Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to configure session printers for the initial set of employees: 1. Create a new policy called Session Printers and Forced Universal Printer Drivers a) Click New, type Session Printers and Forced Universal Printer Drivers. b) Click Next to continue to the settings screen. 2. Add the Session printers setting to automatically create the following session printers: • \\dc\HP Color LaserJet 2800 Series PS • \\dc\Lexmark x945e PS (MS)

©



125

a) Click ICA > Printing and select Session printers. Click Add to add the default session printers. b) Click Add in the Add settings window, type \\dc\ in the Printer UNC path field and then click Browse. c) Navigate to Entire Network > dc, click HP Color LaserJet 2800 Series PS and click OK. d) Repeat steps b and c to add the Lexmark x945e PS (MS) network printer. e) Click OK to complete the Session printers setting and close the Add settings screen. 3. Add the Universal Printing setting and set it to Use universal printing only. Continue to the filters screen. a) Click ICA > Printing > Universal Printing, select Universal printing and click Add to specify default settings. b) Select Use universal printing only from the value drop-down menu in the Add settings window and click OK. 4. Create a filter that applies this policy against all domain users. a) Click Next to continue to the filters screen. b) Select User, click Add and then click Add in the New Filter window. c) Verify that Allow is selected in the Mode drop-down menu and type Coolidge\Domain Users in the User name field. d) Click OK to save the new filter element. 5. Finish adding filters, enable the policy and then save it. a) Click OK to close the New Filter screen. b) Click Next to finish adding filters. c) Verify that Enable this policy is selected and then click Save.

126


©


Exercise 13-5: Testing the Printer Policies Scenario You recently created three new polices that stopped the creation of a problem printer, disabled the auto-creation of client printers and created session printers for all employees. Now you need to test each of these policies to ensure that they are correctly implemented and only affect the correct users.




Testing the Printer Policies Use the EndUserSimulator virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to test the printer policies: 1. Log on to the EndUserSimulator virtual machine as the Coolidge\CitrixAdmin user. 2. Launch the Dazzle published Notepad application. a) Click Start > All Programs > Dazzle Apps > Notepad. b) Log on to the Coolidge Dazzle store using the Coolidge\CitrixAdmin credentials, if requested.

©



127

3. Use the print screen to verify that only the Lexmark x945e PS (MS) and HP Color LaserJet 2800 Series PS session printers are available for printing and that they are both using their native printer drivers. a) Click File > Print, in Notepad. b) Verify that only the Lexmark x945e PS (MS) and HP Color LaserJet 2800 Series PS session printers are available for printing. c) Verify that both printers are using their native drivers. d) Close the Print dialog box and Notepad. 4. Use Internet Explorer to log on to the Web Interface as the TestAdvisor user and launch the published Notepad application. a) Launch Internet Explorer and navigate to the Web Interface server located at http://webinterface.coolidge.net. b) Log in to the Web Interface using as the Coolidge\TestAdvisor user. c) Click Notepad to launch the published Notepad application. d) Select Do not ask me again for this site and click Yes on the USB/Other devices security warning, if it appears. 5. Verify that all of the client printers are auto-created and using the Citrix Universal Printer Driver. Verify that the two session printers were also created and using their native print drivers. a) Click File > Print, in Notepad. b) Verify that all of the client printers are automatically created and using the Citrix Universal Printer Driver, except for the session printers which are using their native printer drivers. 6. Close all open windows. The HP 4600 printer was not auto-created according to the policy that was previously created. The CitrixAdmin account only had access to the session printers and did not have local client printers auto-created according to policy. Finally, the TestAdvisors account had access to session printers and had all of the client printers created using the Citrix universal print driver. This confirms that all policies are in place and working as intended.

128


©


Module 14

Securing XenApp Exercises

130

Module 14: Securing XenApp Exercises

©


Exercise 14-1: Setting Up ICA Proxy on a New XenApp Web Site Scenario Due to the increased instance of employees working at home and requiring access to XenApp published resources, the Citrix Architect decides to encrypt all external ICA traffic through the use of the ICA Proxy feature and the Citrix Access Gateway virtual appliance. She wants you to create a new XenApp Web site that will be used to handle all of the secure requests. Then she wants you to implement ICA Proxy on the Access Gateway and Web Interface servers. The Citrix Engineer will be installing all of the required SSL certificates on the servers as you work and expects to be done by the time you are ready to test.

Before You Begin To begin this lab, ensure that the following virtual machines are started: • • • • • • •

AccessGateway Coolidge-DC EndUserSimulator MerchandisingServer WebInterfaceServer XenAppServer-1 XenAppServer-2


Creating a New XenApp Web Site Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to create a new XenApp Web site for use with secure connections from the Access Gateway: 1. Start the AccessGateway virtual machine.

©



131

2. On the WebInterfaceServer virtual machine, launch the Citrix Web Interface Management console and create a new XenApp Web site. a) Click Start > All Programs > Citrix > Management Consoles > Citrix Web Interface Management to launch the Web Interface Management console. b) Click Create site. c) Select XenApp Web and click Next. 3. Set the path of the Web Interface site to be /Citrix/Secure and name the site Secure. Do not make this site the default IIS site. Continue through the creation of the XenApp Web site using the default values. a) Type /Citrix/Secure in the Path field and ensure that Secure is automatically populated into the Name field. Click Next to continue through the wizard. b) Verify that At Web Interface is specified on the Specify Point of Authentication screen and click Next. c) Click Next on the Confirm Settings for the New Site screen. The wizard creates a new XenApp Web site. d) Click Next to configure the XenApp Web site. 4. Specify Coolidge as the farm name and add both of the XenApp servers to the list of servers. a) Type Coolidge in the Farm name field. b) Click Add, type XenAppServer-1 and click OK. c) Click Add, type XenAppServer-2 and click OK. Click Next. 5. Use the default authentication method settings and restrict the Web Interface to only the Coolidge domain. a) Click Next on the Configure Authentication Methods screen. b) Select Restrict domains to the following and click Add. c) Type Coolidge in the Logon domain field and click OK. Click Next 6. Use the Full site appearance and configure dual mode as the published resource type. Complete the Web Interface site initial configuration. a) Select Full and click Next. b) Select Dual mode and click Next. c) Click Finish to complete the initial configuration wizard.

Configuring Web Interface Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task.

132


©


Use the following procedure to configure the Secure XenApp Web site: 1. Use the Citrix Web Interface Management console to edit the secure access settings of the Secure XenApp Web site. a) Click XenApp Web Sites and click the Secure site entry. b) Click Secure Access to open the Secure Access settings. 2. Edit the default access method and set it to Gateway Direct. Specify the Access Gateway's server details (ag.coolidge.net) then continue to the Secure Ticket Authority configuration. a) Select Default and and click Edit. b) Select Gateway Direct in the Access Method drop-down menu. c) Click OK to add the new Access route. d) Click Next to continue to the Access Gateway server details. e) Type ag.coolidge.net in the Address (FQDN) field and click Next to continue to the Secure Ticket Authority configuration screen. 3. Add new Secure Ticket Authority URLs for both XenApp servers. Leave all other settings as default and complete the new secure access settings. a) Click Add to add a new Secure Ticket Authority URL. Type http://xenappserver-1.coolidge.net/scripts/ctxsta.dll. Click OK. b) Click Add to add a new Secure Ticket Authority URL. Type http://xenappserver-2.coolidge.net/scripts/ctxsta.dll. Click OK. c) Click Finish to complete the new secure access settings.

Configuring Access Gateway Use the WebInterfaceServer virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to configure the Access Gateway for ICA Proxy mode: 1. Launch the Citrix Access Gateway Administration tool. Log on to the Access Gateway using the hostname ag.coolidge.net and root/Password1 credentials. a) Click Start > Access Gateway Administration Tool 4.6.2 to launch the Access Gateway administration tool. b) Type ag.coolidge.net as the Host, use root/Password1 as the administrator credentials and click Connect. Allow the administration tool to connect and refresh itself before continuing. 2. Add a new Secure Ticket Authority for the XenAppServer-1 and XenAppServer-2 virtual machines. a) Click the Authentication tab and then click the Secure Ticket Authority tab.

©



133

b) Type xenappserver-1.coolidge.net in the Server running the STA field and click Add to add the Security Ticket Authority settings. c) Click Initialize when the Service Interruption warning appears and then click OK to acknowledge that the STA server is verified. d) Repeat the previous two steps with the XenAppServer-2 server. 3. Use the Access Policy Manager to set the Gateway Portal to redirect to the Web Interface server web site. a) Click the Access Policy Manager tab, right-click Default under User Groups and click Properties. b) Click the Gateway Portal tab to access the portal settings and select Redirect to Web Interface. c) Type /Citrix/Secure in the Path field and webinterface.coolidge.net in the Web server field. d) Click OK to close the properties window. 4. Turn off logon page authentication by the Access Gateway in the Global Cluster Policies and then minimize the Access Gateway Administration Tool. a) Click the Global Cluster Policies tab and deselect Enable logon page authentication. b) Click Submit to create the changes and click OK when complete. c) Minimize the Access Gateway Administration tool.

134


©


Exercise 14-2: Testing the ICA Proxy Configuration Scenario You recently set up a new XenApp Web site and implemented ICA Proxy mode in order to encrypt all external ICA traffic through the Access Gateway. Now you must test to make sure that all of the applications can launch through ICA Proxy mode.

Before You Begin To begin this lab, ensure that the following virtual machines are started: • • • • • • •

AccessGateway Coolidge-DC EndUserSimulator MerchandisingServer WebInterfaceServer XenAppServer-1 XenAppServer-2


Launching a Secure Application Use the XenAppServer-1 virtual machine logged in as the Coolidge\CitrixAdmin user for this task. Use the following procedure to test ICA Proxy mode by launching an SSL secured application: 1. Use Internet Explorer on the XenAppServer-1 virtual machine to securely access the Access Gateway's SSL site at https://ag.coolidge.net. a) Switch to the XenAppServer-1 virtual machine and launch Internet Explorer.

©



135

b) Use Internet Explorer to navigate to https://ag.coolidge.net/, making sure to specify https. The Access Gateway receives the secure connection and forwards the request to the /Citrix/Secure Web Interface site on the back end.

2. Log on to the Access Gateway as the Coolidge\CitrixAdmin user and launch the published Notepad application. a) Log on to to the Access Gateway as the Coolidge\CitrixAdmin user. b) Click Notepad to launch the published application. Wait a few moments as the application is launched. c) Select Do not ask me again for this site and click Yes on the USB/Other devices security warning, if it appears. 3. Use the Connection Center to verify that the Notepad application is secured using 128-bit SSL. When complete, close all open windows. a) Right-click the Citrix online plug-in icon and click Connection Center. b) Click XenAppServer-1 and click Properties to view the connection properties of the applications being delivered by XenAppServer-1. c) Verify that Basic. 128-bit SSL/TLS is listed as the encryption level and click OK. d) Close all open windows. The application is showing as using 128-bit TLS encryption when using Citrix Access Gateway to access applications. This allows the Coolidge employees to work remotely while protecting customer and company data.

136


©


Module 15

Monitoring Exercises

138

Module 15: Monitoring Exercises

©


Exercise 15-1: Viewing XenApp Licence Server Activity Scenario Early in the XenApp implemention, you configured the EdgeSight server to monitor the license usage on the license server. The Citrix Architect wants to ensure that it has been working as intended and wants a brief usage report by the end of the day. Your job is to verify that the license server monitoring is functioning properly and to look at the license usage during the initial deployment phase of the last week.


AccessGateway EndUserSimulator MerchandisingServer WebInterfaceServer XenAppServer-1 XenAppServer-2


Viewing License Usage Trends Use the Coolidge-DC virtual machine logged in as the Coolidge\Administrator user for this task. Use the following procedure to monitor the XenApp license usage: 1. Access the Edgesight server web site at http://dc.coolidge.net/edgesight using Internet Explorer. Log on with the email address [email protected]. a) Click Start > Internet Explorer and navigate to http://dc.coolidge.net/edgesight/. b) Log on with the email address [email protected] and password Password1.

©



139

2. View the License Usage Trending data graphically and then view it as a grid. a) Click on the Track Usage tab and click License Usage Trending. b) Deselect Select All, select XenApp and click Go. View the graphical results of this request. c) Click the View in Grid icon. View the results of this request as a list. 3. View the License Usage Summary data graphically and then view it as a grid. a) Click License Usage Summary. b) Deselect Select All, select XenApp and click Go. View the graphical results of this request. c) Click the View in Grid icon. View the results of this request as a chart. 4. Make note of the many different ways that the license data is viewable. 5. Close all open windows.

140


©


©



141

851 West Cypress Creek Road Fort Lauderdale Florida 33309 USA | (954) 267 3000 | www.citrix.com Rheinweg 9 8200 Schaffhausen Switzerland | +41 (0) 52 63577 00 | www.citrix.com ©Copyright 2010 Citrix Systems, Inc. All rights reserved.

142


©
