Dear Friend

The document is but not clear on front because of my blogging tool.

Thanks

Aslam Latheef Shaik

 

 

 

1 Citrix Configuration

1.1 Introduction

The proposed Citrix solution consists of the following main components,

· XenServer - System Virtualization

· XenApp – Application Virtualization

· HP Thin client – For user access to applications.

1.2 Hardware Configuration

The table given below shows the hardware configuration of the machines used in the Citrix farm. (Refer Server Infrastructure Design document).

Role	Server Model	O/S Environment	Location	Configuration	Nos
XenServer Host	HP BL 460c Blade Server	XenServer OS on bare metal server	CPC	2* Quad Core /32 GB/ 2* 146 GB HDD/  Internal Raid Controller/ 2NIC/1HBA	2
SQL Servers · Data store	HP BL 460c Blade Server	Windows 2008 64bit Enterprise Edition/SQL 2005 Enterprise Edition	CPC	1*Quad Core/ 32GB/ 2*146 G B HDD / 2 NIC/ 1HBA 1*Quad Core/ 16GB/ 2*146 G B HDD / 2 NIC/1HBA	2
Management Server · XenCenter · Citrix management Console · Altiris management console	HP BL 460c Blade Server	Windows 2008 64bit Standard Edition	CPC	1*Quad Core/ 8GB/ 2*146 G B HDD / 2 NIC	1
AD Server · License Serve	HP BL 460c Blade Server	Windows 2008 64bit Standard Edition/Active directory server	CPC	1*Quad Core/ 8GB/ 2*146 G B HDD / 2 NIC	2
Thin Clients	HP T5530	Embedded Linux OS	CPC	WTOS,VIA C7 Eden 800GHz,256 MB RAM, ICA based, 10/100 Base-T Fast Ethernet twisted pair (RJ-45)Optional external USB 802.11b/g wireless adapter	400

1.3 XenServer Configuration Overview

Installing XenServer consists of installing two components on two separate machines – XenServer and XenCenter. Xenserver will be installed in the machine called XenServer host whereas XenCenter will be installed management server. XenCenter provides the management tools to administer the XenServer Host The following sections will discuss installation and configuration of various components.

· Installing XenServer

· Installing XenCenter

· Creating a resource pool

· Creating VMs

1.3.1 Installing XenServer

XenServer will be will installed in two XenSever host machines. The following section describes the installation procedure.

1.3.1.1 Pre-requisites

Before starting the XenServer installation, there are few items that need to be in place.

1. Domain controller is installed and Active directory environment is in place.

2. Users, Groups & computer objects created in the domain.

3. DNS, DHCP Scoping and Gateway are all configured.

4. Storage infrastructure is in place.

1.3.1.2 Installing the XenServer host

XenServer host will be installed from the CD as a direct install method. The installation steps are as below:

1. Insert the installation CD in the server and boot it from the CD.

2. After the initial boot messages, the installer does some hardware detection and initialization, and then presents a screen asking you to select the keyboard. Choose US.

3. Next, the "Welcome to XenServer" screen appears. Select Install XenServer Host to Hard Disk and click OK.

Figure 1: XenServer Welcome screen

4. Choose OK to proceed through the warning screens.

5. Accept the End User License Agreement (EULA) to proceed.

6. Next in the Image Media screen choose Removable Media.

Figure 2: XenServer Image media selection

7. The next screen gives the option to install Linux Pack from a second CD. Choose No.

8. The next screen gives the option to verify the integrity of the installation media. Select Yes and click OK to proceed.

9. In the next screen set the root password. (This will be the password that the XenCenter application will use to connect to the XenServer host.). Type Infy123+ as password and Retype to confirm the password.

10. You are next prompted to set up Networking for the management NIC which the XenCenter will use to connect to it. Select NIC 1 and choose OK to proceed.

11. Next you can select Static configuration, which prompts you to configure the NIC's properties manually.

12. Next specify the hostname and configure the name server. Refer Network Infrastructure Solution Architecture document) for details.

13. Next select Time Zone as IST and click OK to proceed.

14. Next in the System Time screen select Using NTP.

15. It will ask for the NTP server name or IP address. Enter NTP server IP as 10.97.80.128.

16. Next screen will ask confirmation for the installation. Choose Confirm.

Figure 3: XenServer confirmation screen

17. A progress bar is displayed as the installation commences. It will show an installation completion screen after the installation is done as shown below.

Figure 4: Installation completion screen

18. Select OK. After the reboot XenServer displays xsconsole, a convenient system configuration console.

Similar process is followed for the installation of second XenServer host. The configuration details for the second XenServer host are as below (Refer Network Infrastructure Solution Architecture document). XenServer Licensing

Following are the steps to activate XenServer:

1. You will get alert message for activating the XenServers in the XenCenter machine. If the XenCenter box is connected to internet, then activation can be done by clicking on activate.

2. If the machine hosting XenCenter is not connected to internet, try to activate XenServers. The activation attempt times out and will give you a chance to save the activation XML data to a file.

3. On a machine with internet, launch https://activate.vmd.citrix.com. Upload the generated XML and complete the activation process. A license key file will be sent to the specified mail id for use for activation.

4. Download the license key file and copy it onto the machine hosting XenCenter. The license can be applied either by double clicking and launching it or using the XenCenter console – by pointing to the file.

1.3.2 XenCenter

XenCenter will be hosted on the management server (Refer Section 3.2). The management server (CAVSWP01) will have Windows Server 2008 Standard installed.

1.3.2.1 Prerequisites

The prerequisites for installing XenCenter are follows:

· Install .NET framework version 3.5 (Version 2.0 is minimum, 3.5 is recommended).

· Ensure connectivity with the XenServer hosts.

1.3.2.2 Installation

The installation steps for XenCenter as follows:

1. Log on to the system MANAGEMENTSERVER as an Administrator.
2. Insert the XenCenter CD into CD/DVD drive, and browse to XenCenter setup file and double click on it.
3. The Welcome Screen as shown will appear, click Next to continue

Figure 5: XenCenter welcome screen

4. Next, enter the installation folder as C:\Program Files\Citrix\XenCenter and select Everyone for the user for XenCenter.

Figure 6: XenCenter installation screen

5. The next screen will ask for confirmation to install. Confirm, then the installation completes. It will add a XenCenter short cut icon to the desktop.

1.3.3 Creating Virtual Machines (VMs)

Before creating VMs, make sure that the central storage is setup. Refer Section 3.3.6). Total 14 VMs will be created in the two XenServer hosts. The details of the VMs are show in the following table.

Physical Server	VMs	VM Name	Configuration	Base OS	Add Ons	Status	IP Address
XenServer1 (BRCPCXENHP01)	VM1	BRCPCADM1	1-VCPU, 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Active	10.97.80.136
VM2	CPSSRV2	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Active	10.97.80.137
VM3	BRCPCCPSWP03	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Active	10.97.80.138
VM4	BRCPCCPSWP04	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Active	10.97.80.139
VM5	BRCPCCPSWP05	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Active	10.97.80.140
VM6	BRCPCCPSWP06	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Standby	10.97.80.141
VM7	BRCPCCPSWP07	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit		Standby	10.97.80.142
XenServer2 (BRCPCXENHP02)	VM16	BRCPCADM2	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Active	10.97.80.152
VM17	BRCPCCPSWP17	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Active	10.97.80.153
VM18	BRCPCCPSWP18	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Active	10.97.80.154
VM19	BRCPCCPSWP19	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Active	10.97.80.155
VM20	BRCPCCPSWP20	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Active	10.97.80.156
VM21	BRCPCCPSWP21	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	XenApp 5.0	Standby	10.97.80.157
VM22	BRCPCCPSWP22	1-VCPU 4GB RAM, 20 GB Storage on SAN	Windows 2008 DCE 32-bit	None	Standby	10.97.80.158

The VMs will be created in the following way.

1. Create a master VM using VM template for windows 2008 DCE provided by XenCenter.

2. Prepare the first VM

3. Copy the VM to create other VMs.

4. Configure all the VMs for unique attributes such as hostname, IP address etc.

5. Join the VMs to the domain corp.incometax.net.

6. Install XenApp.

1.3.3.1 Creating first VM through XenCenter

The steps for creating the first VM is as below.

1. Open XenCenter and click on Add your XenServer if the XenServer is not present already.

Figure 7: VM creation screen 1

2. In the next screen enter hostname as BRCPCXENHP01, Username as root and Password as Infy123+.

Figure 8: VM creation screen 2

3. After that the server will be added to XenCenter as show below.

Figure 9: VM creation screen 3

4. Write click on the server name and click on New VM as shown below.

Figure 10: VM creation screen 4

5. In the next screen select OS template as Windows Server 2008 32-bit.

Figure 11: VM creation screen 5

6. Enter the VM name as TemplateVM. Then click Next.

Figure 12: VM creation screen 6

7. For location, select Physical DVD drive and click Next.

Figure 13: VM creation screen 7

8. In the next screen enter number of vCPU as 1 and Initial memory as 4096. Click Next.

Figure 14: VM creation screen 8

9. In the next screen on Virtual Disks. Click on Edit. Edit disk size as 20 GB.

Figure 15: VM creation screen 9

10. Add one virtual Interface and click Next.

Figure 16: VM creation screen 10

11. Click on Finish to complete VM creation.

Figure 17: VM creation screen 11

After creating the first VM follow the steps 2-6 in

1.3.3.2 Preparing the Master VM

· Install Windows Server 2008 Datacenter Edition on it.

· Install Service Packs (SP2 in case the Base Media does not include the Service Packs)

· Install the XenSource PV drivers. The Citrix paravirtualized network and SCSI drivers (Citrix Tools for Virtual Machines) provide high performance I/O services without the overhead of traditional device emulation found in first-generation virtualization products. The steps for installing PV drivers are as follows:

1. Select the VM. In the VM menu click on Install XenServer tools. This will install PV drivers in the selected VM.

Figure 18: Installing PV Drivers

· Use sysprep utility to remove the unique attributes (SID, hostname etc) of the VM. Follow the steps below to run sysprep.

1. Copy the contents of \support\tools\deploy.cab from the Windows product CD to a new \sysprep folder in the VM.

2. Double click on sysprep.exe (Choose OOBE and Shutdown). This will shutdown the VM after sysprep.

1.3.3.3 Use the VM as template to create all the VMs

1. Select the VM in the Resources pane and right click and click on Copy VM on the shortcut menu as shown below

Figure 19: Copy VM 1

2. In the Copy Virtual Machine dialog box, enter the new VM name CPSSRV1 (Refer Table_VMs) in the Name box. Clear the check box Remove original VM afterwards.
3. Select the HBA LUN for the destination of VM's virtual disks.
4. Click Copy to copy the VM to the selected SR and close the dialog box. Refer figure below.

Figure 20: Copy VM 2

Similar procedure can be followed to create other VMs.

1.3.3.4 VM configuration

After the copy is done start the VM as show in the figure below

Figure 21: VM Configuration 1

Start the VM which will present a screen for basic configuration. Apply the following settings.

· Hostname and IP address for the virtual machines (Refer Table_VMs)

· Subnet Mask 255.255.255.0

· Default Gateway 10.97.80.1

· Primary DNS 10.97.80.128

· Secondary DNS 10.97.80.129

Join the VMs to the domain corp.incometax.net.

1.3.4 Installation of XenApp components

Before XenApp installation in the VMs, the following XenApp components need to be installed. The various components and the target installation machines are as shown in the following table:

XenApp Component	Target Installation Machine
Citrix Licensing Server	AD Server
· Access Management Console · Citrix XenApp Advanced Configuration · XenApp Web Interface · XenApp Document Library	MANAGEMENTSERVER
· Data Store	SQL Servers Cluster (MSSQLNLB)

1.3.4.1 Installing Licensing Sever

The Citrix licensing consists of two components, Licensing server and license management console. Both the components will be installed in the AD server Before installing the licensing server following prerequisites needs to be installed.

· Install MSI 3.x if not already installed. It is available in the support folder of the installation media.

· Add the following roles in Internet Information Services (IIS) using the Server Manager:

· ASP.NET

· Windows Authentication Security

· IIS Management Compatibility

· Sun Java Runtime Environment (JRE) 1.6.0_5, 32-bit version

The installation steps are as below:

1. Log on into the AD server as an Administrator.

2. Install all the pre-requisites mentioned above.

3. Insert the installation media and from the Autorun screen, select Enterprise Edition.

4. Select Common Components > Citrix Licensing, and then navigate through the installation wizard, clicking Next to move to each subsequent page.

5. On the page that lists the destination folder where the licensing components will be installed, click Next to accept the default. By default, licensing components are installed in C:\Program Files\Citrix\Licensing.

6. Continue through the wizard and accept the default destination folder for the license files by clicking Next. The license files must be stored on the same drive as the license server software. By default, the license files are stored in C:\Program Files\Citrix\Licensing\MyFiles.

7. Enter license server and vendor daemon port The default numbers are:

a. License server port number is 27000

b. Vendor daemon port number is 7279

8. Select the Web server that will be used to display the License Management Console and click Next.

9. Click OK, and then Next to agree to stop and restart the Web server.

10. Click Next to start the installation. The installation continues until complete.

1.3.4.2 Installing XenApp Components in the Management Server

The prerequisites that need to be installed in the management server are as follows:

· Microsoft .NET Framework 3.5. On Windows Server 2008 systems, add the .NET Framework role, using the Server Manager

· Microsoft Visual C++ 2005 Redistributable Package, which is installed automatically by Autorun.

· Java Runtime Environment (JRE) Version 1.6.0_5, 32-bit version.

The installation steps are as below.

1. Insert the XenApp installation CD into the CD/DVD ROM and double click on Autorun.exe.

2. Next screen will show installation checklist. Select Enterprise Edition.

3. Select Application Virtualization in the next screen

4. Next screen will show the license agreement screen. Accept to proceed.

5. Next is the prerequisites installation pages, select the prerequisites if any and proceed.

6. Next is the component selection page. Select the following components.

a. Access Management Console

b. Citrix XenApp Advanced Configuration

c. XenApp Web Interface

d. XenApp Document Library

7. Click next to start the setup. Different installation wizards will show up for different components and the installation proceeds.

1.3.4.3 Setting up Data Store

The data store and data collector will be configured in the SQL Cluster MSSQLNLB. The pre-reqs for the servers composing this cluster are:

· MDAC 2.8

· Disk space: approximately 100MB for every 250 servers and 50 published applications in the farm.

· A "temp" database on a partition with at least 1GB of free disk space and set to grow automatically. Citrix recommends 4GB if the farm is large and includes multiple print drivers.

· An ODBC database client driver on each server that connects directly to the database.

Creating the Data Store Database: For SQL Server, the creation of the data store is not part of the XenApp installation. Therefore, data store database must be created before XenApp installation. The default settings and database sizes usually suffice for the XenApp data store. Create the data store database as CPC_CTX_DataStore.

Following are the steps to create a data store database:

1. Choose StartàProgramsàMicrosoft SQL Server 2005àSQL Server Management Studio.

2. In Management Studio’s left pane, expand <SQL Instance Name>àDatabases.

3. Right-click the Databases folder and choose New Database.

4. A dialog box appears. In the Name box, enter CPC_CTX_DataStore and click OK.

5. Expand the SecurityàLogins folder and right-click and choose New Login.

6. A dialog box appears with the General tab displayed. In the Login Name box, enter a name. Make note of the name because you will need it during the XenApp installation.

7. For the Authentication method, choose SQL Server Authentication and then enter a password (!Passw0rd). Remember the password; you must enter it during the XenApp installation.

8. For the Default database, change the database to the name you specified in step 4 and select the appropriate default language.

9. Click Server Roles in the left pane and choose admCitrix for the server role for this database.

10. Click OK. Database creation is complete.

Create a Data Source Name (DSN) file to configure the XenApp connection to the data store. This DSN files gets automatically created while installing XenApp.

The steps for setting up the data collector will be as follows:

1. In the left pane of XenApp Advanced Configuration, select the farm.
2. On the Actions menu, click Properties.
3. Select Zones.
4. In the list of zones and their servers, locate the server, select it, and click Set Election Preference.
5. Select the ranking for the server by choosing from the following election options:
   • Most Preferred : CPSSRV1

The server is always the first choice to become the data collector. It is recommended that only one server per zone be given this setting.

• Preferred: CPSSRV2

When electing a new data collector, XenApp elects the next collector from the preferred servers if the Most Preferred server is not available.

1.3.5 Load Manger

Load Manager is a component of and installed by default with XenApp. Load Manager calculates the load on a server using load evaluators and rules. Each load evaluator contains one or more rules.

Load Manager calculates a server load using the load evaluators attached to a server or published application. When any rule for a relevant load evaluator reports full load or exceeds its threshold, Load Manager removes the load-managed server from the internal list of available servers. The next request for an ICA connection to a published application is routed to the next available load-managed server in the list.

A rule queries specific conditions and performance metrics for servers or published applications. The following are the rules to be configured.

• Application User Load. Not configured.
• Context Switches.
  • Full load: 14400 (Default 16000)
  • No load: 900
• CPU Utilization
  • Full load: 80%
  • No load: 10%
• Disk Data I/O: 32767 kilobytes per second (Default).
• Disk Operations
  • Full load: 90% (Default 100%)
  • No load: 0%
• IP Range: Not configured
• Load Throttling: 30 (No of concurrent sessions per server)
• Memory Usage:
  • Full load: 80%
  • No load: 10%
• Page Fault:
  • Full load: 1800 (Default 2000)
  • No load: 0
• Page Swap:
  • Full load: 90 (Default 100)
  • No load: 0
• Scheduling: Not configured

Creating New Load Evaluators

The Default and Advanced load evaluators provided with Load Manager are intended for use with computers running XenApp. New load evaluator will be created by copying the advanced load evaluator and changing the properties.

1. In XenApp Advanced Configuration, select Load Evaluators in the left pane.
2. Select the load evaluator that you want to copy.
3. From the Actions menu, select Load Manager > Duplicate Load Evaluator. The Duplicate Evaluator dialog box appears.
4. Edit the properties

a. Name: CPC_CTX_Load_Eval

b. Description: Load evaluator for ITD-CPC Citrix farm

c. Configure rules (Refer rules) and click OK.

Assign a load evaluator to a server

1. In the Access Management Console, select the server to which you want to attach a load evaluator.
2. From the Action menu, select All Tasks > Assign load evaluator.
3. On the Assign Load Evaluator dialog box, select the required load evaluator.

1.3.6 Storage setup

A storage repository (SR) is a storage container on which virtual disks are stored. Both storage repositories and virtual disks are persistent, on-disk objects that exist independently of XenServer.

Storage repositories can be shared between servers in a resource pool and can exist on different types of physical storage device, both internal and external, including local disk devices and shared network storage

In the ITD-CPC environment Fiber Channel (FC) storage area networks (SAN) will be used. The XenServer host machines will be connected to the storage device through a FC switch.

Fiber Channel (FC) storage area networks (SANs) are supported through Emulex or QLogic host bus adapters (HBAs). All FC configuration is required to expose a FC LUN to the host must be completed manually via the XenServer CLI, including storage devices, network devices, and the HBA within the server. Once all FC configurations are complete, the HBA will expose a SCSI device backed by the FC LUN to the server. The SCSI device can then be used to access to the FC LUN as if it was a locally-attached SCSI device.

After the SAN is setup one or more LUNs are zone in to each XenServer Host. After that the LUNs will be available to the XenServer host.

1.3.6.1 Attaching Storage Repository (SR)

1. Open XenCenter click on New Storage on the tool bar.

2. Under Virtual disk storage, select Hardware HBA as the physical storage type and then click Next.

3. XenCenter probes for available LUNs and then displays a page listing all the LUNS found. Enter the name of the new SR as CPC_XenApp_storage and select a LUN from the list.

4. Click Finish to complete the new SR configuration and close the wizard.

1.4 XenApp Installation and Configuration

This section explains installation of XenApp in the VMs. Citrix Data store needs to be setup on the SQL server prior to XenApp installation so that all the information starting from the farm configuration is captured in the data store.

1.4.1 Prerequisites

Prior to the installation of XenApp there are certain pre-requisites that needs to be completed on the Virtual machine.

· Java Runtime Environment (JRE) Version 1.6.0_5. The 32-bit JRE 1.6.0_5 package is available from http://www.java.com. (Gets installed as a part of XenApp setup)

· Install Microsoft Hotfix 958652, available from http://support.microsoft.com.

· Add the following roles using server manager

o Terminal Services

o Application Server

1.4.2 XenApp installation in the VMs

The installation steps are as below:

1. Insert the XenApp installation CD into the CD/DVD ROM and double click on Autorun.exe.

2. Next screen will show installation checklist as shown below. Choose Enterprise Edition.

Figure 22: XenApp Installation 1

3. Next screen will show the installation category as show below. Select Application Virtualization

Figure 23: XenApp Installation 2

4. Next screen will show the license agreement screen. Accept and click Next.

5. The prerequisites installation screen shows up. Click Next, it will install prerequisites.

Figure 24: XenApp Installation 3

6. Next screen is the component selection screen. Choose Citrix XenApp as shown below.

Figure 25: XenApp Installation 4

7. For pass through authentication for pass through clients, select Yes and click Next. Refer figure below.

Figure 26: XenApp Installation 5

8. In the following screen, enter the name of the server which will host the Citrix Web Interface. MANAGEMENTSERVER.CORP.INCOMETAX.NET.

Figure 27: XenApp Installation 6

9. The XenApp welcome screen shows up. Click Next to proceed with XenApp installation.

10. Click Next.

Figure 28: XenApp Installation 7

11. Choose Create a new farm for the first time XenApp installation. In all subsequent installation go for add to an existing farm. Click Next.

Figure 29: XenApp Installation 8

12. On the “Create a server farm setup page” enter the following information. Refer figure below

a. Enter the name of the farm as CPC_CTX_Farm.

b. Select Use the following database on a separate database server and select the SQL Server.

c. Use the default zone name.

Figure 30: XenApp Installation 9

13. Click Next. Setup automatically creates a Data Source (DSN) file based on the information you enter and names it MF20.dsn. Enter description “CPC Data Store”. Enter the SQL Server instance name as MSSQLNLB. Click Next.

Figure 31: XenApp Installation 10

14. Next is for authentication method for the SQL data store. Chose With Windows NT authentication using a network login ID.

Figure 32: XenApp Installation 11

15. Enter the default database name as CPC_CTX_DataStore.

Figure 33: XenApp Installation 12

16. In the next screen accept defaults and click on Finish.

Figure 34: XenApp Installation 13

17. In the next screen, click on Test Data Source to check connectivity. Click OK to proceed.

Figure 35: XenApp Installation 14

18. Enter the user credentials for data store access. Enter user name as itdcpc\admCitrix and password !Passw0rd. Click Next.

Figure 36: XenApp Installation 15

19. Next screen is for assigning farm administrator credentials as show in the figure below.

Figure 37: XenApp Installation 16

20. The next screen is for IMA encryption enabling. Follow the steps below to enable IMA encryption.

a. On the Enable IMA Encryption page, Check Enable IMA Encryption check box and click Next.

b. On the IMA Encryption Key Type page, select Generate and Install New Key and save the key to any folder on the local computer.

Figure 38: XenApp Installation 17

21. Next screen will ask for specifying Citrix License Server: Enter the hostname as BRCPCADSWP01.

Figure 39: XenApp Installation 18

22. Next screen is for Configuring Session Shadowing. Select Allow shadowing of user sessions on this server and select Force a shadow acceptance popup.

Figure 40: XenApp Installation 19

23. The next screen is for Configuring the Citrix XML Service Port. Select Use a separate port and specify the port number as 81.

Figure 41: XenApp Installation 20

24. Next screen is for Adding Users to the Remote Desktop Users Group. Select Skip this step, and add users later.

Figure 42: XenApp Installation 21

25. Next is the summary screen. Click on Finish.

Figure 43: XenApp Installation 22

This completes the XenApp setup and Citrix farm creation. Similarly XenApp will be installed in all the VMs. On subsequent installation of XenApp, add to the existing Farm option will be selected.

1.4.3 Configuring Web Interface

XenApp site provides an interface to the users for accessing applications. Sites are configured as bellow:

1. Open Citrix Access Management Console (AMC)

Figure 44: XenApp site creation screen 1

2. Click Web Interface in the left column under Citrix Resources -> Configuration Tools and then click Create site under Common Tasks.

Figure 45: XenApp site creation screen 2

3. Create Site wizard starts.  Choose XenApp Services.

Figure 46: XenApp site creation screen 3

4. In the Specify IIS Location screen accept defaults and click Next.

Figure 47: XenApp site creation screen 4

5. Click Next on the Confirm Settings for New Site screen.

Figure 48 : XenApp site creation screen 5

6. Next screen shows the progress of site creation.

Figure 49: XenApp site creation screen 6

7. Make sure Configure this site now is checked.  Click Next.

Figure 50: XenApp site creation screen 7

8. In the next screen enter the farm name as CPC_CTX_Farm. Enter XML Service port 81 and transport type HTTP. Click on Add to add a server. Add all the servers (Refer Table_VMs)

Figure 51: XenApp site creation screen 8

9. Next for configuring domain restriction click on Add.

Figure 52: XenApp site creation screen 9

10. Enter domain name as cpc.itd.com.

11. The domain will be added as shown below.

Figure 53: XenApp site creation screen 10

12. Specify log on screen appearance as Full.

Figure 54: XenApp site creation screen 11

13. Select published resource type as Remote.

Figure 55: XenApp site creation screen 12

14. Verify the settings and click on Finish on the confirmation screen. The site will be created.

1.4.4 Application publishing

Once the XenApp configuration is completed, applications can be published through the access management console. The following steps are followed for application publishing.

1. In Citrix Access Management Console click on Applications in the left Navigation window.

Figure 56: Application publishing screen 1

2. In the right pane under Common Tasks select NewàPublish Application

Figure 57: Application publishing screen 2

3. Click Next on the publish application wizard.

Figure 58: Application publishing screen 2

4. Enter display name as Internet Explorer.

Figure 59: Application publishing screen 2

5. In the next screen choose Application and under Application type select Accessed from a server.

Figure 60: Application publishing screen 4

6. In the next screen click on Browse and locate the path of the executable of the application to be published.

Figure 61: Application publishing screen 5

7. To point to the location of the server, click on Add.

Figure 62: Application publishing screen 6

8. The next screen will show all the servers available in the farm. Double click on the server name and click on OK.

Figure 63: Application publishing screen 7

9. The server name will appear in the next screen. Click on Next to continue.

Figure 64: Application publishing screen 9

10. In the next screen select allow only configured users and click on Add.

Figure 65: Application publishing screen 10

11. Double click on the server name.

Figure 66: Application publishing screen 10

12. Double click on the users.

Figure 67: Application publishing screen 11

13. Click on OK.

Figure 68: Application publishing screen 12

14. Now the required user groups are assigned. Click on Next.

Figure 69: Application publishing screen 13

15. Click on Next.

Figure 70: Application publishing screen 14

16. Select Configure Advance Settings Now and Click on Next.

Figure 71: Application publishing screen 15

17. Leave the defaults and click on Next.

Figure 72: Application publishing screen 16

18. Click Next.

Figure 73: Application publishing screen 17

19. Click Next.

Figure 74: Application publishing screen 18

20. Uncheck the box Enable legacy audio to remove all Windows sounds from this Published Application and click Next.

Figure 75: Application publishing screen 19

21. Accept all defaults and click on Finish.

Figure 76: Application publishing screen 20

22. The published application will appear under the applications in the left navigation pane as shown.

Figure 77: Application publishing screen 21

1.4.5 Printer configuration in XenApp

In the CPC environment, the printers are configured in XenApp using Network printing pathway in which print jobs that are routed from the farm server hosting the user’s session to a print server and spooled remotely. The printers are provisioned through XenApp dynamically, so the printers that appear in a session are not predetermined and stored. Rather, the printers are assembled, based on policies, as the session is built. In order to control what printers users have in their sessions and ensure printers are available when users start their sessions, provision their printers through autocreation.

XenApp makes printers available in sessions by creating all printers configured on the client device automatically, including locally attached and network printers. After the user ends the session, the printers for that session are deleted. The next time a session starts; XenApp evaluates any policies for printer creation and enumerates the appropriate printers from the client device.

The printing infrastructure at CPC consists of one print server and 4 printers all in the same LAN. Making printer available to users required two tasks in sequence. They are:

· Import the printer objects and information about them into the XenApp farm.

· Assigning the imported network printer to user sessions through the Session Printer policy rule.

1.4.5.1 Import Print Server to XenApp farm

The steps for importing the printer objects into the XenApp farm as follows:

1. In the left pane of the Advanced Configuration tool, select the Printer Management node.
2. On the Actions menu, select Printer Management > Import Network Print Server. As shown in the following figure.

Figure 78: Importing Print Server

3. In the Server box enter the name of the print server MANAGEMENTSERVER.
4. Enter credentials to authenticate to the print server by doing one of the following:
   • Clear the Use your Citrix Administrator credentials check box and enter credentials for a network user account with access to printers on the specified server.
   • Select the Use your Citrix administrator credentials check box if you want to use the local user credentials that you enabled in Pass-Through Authentication.

Do not enter any user information, so that the printers are available to all the users. After the completion of print server import, the print server appears on the Network Print Servers tab in the Advanced Configuration tool.

1.4.5.2 Import Drivers to XenApp farm

1. In the left pane of the Advanced Configuration tool, select Printer Management > Drivers.
2. On the Actions menu, select Printer Management > Compatibility. As shown in the following figure.

Figure 79: Adding printer drivers

3. Choose the required platform from the drop-down list.
4. Select one of the following Compatibility list options Refer figure below:
   • Allow only drivers in the list. Keeps a list of incompatible drivers that are not allowed to be used by client printers and allow all others.
   • Allow all drivers except those in the list. Keeps a list of compatible drivers that client printers are allowed to use and bans all others.

Figure 80: Updating Driver compatibility list

5. Update the list and click OK.

1.4.5.3 Assigning printers using the session printers policy rule

The steps for assigning printers to users are as follows:

1. In the Advanced Configuration tool, select the Policies node.

2. From the Contents tab, choose Session Printer policy.

3. From the Actions menu, choose Properties.

4. In the policy’s Properties dialog box, expand Printing, then select Session printers and apply.

1.4.5.4 Adding a network printer while configuring the Session printers rule

1. On the Printing > Session printers policy rule page, click Add. If the rule is not currently enabled, click Enabled on the Session Printers rule page to display the Add button (Refer Figure 81: Assigning printers to session).

2. In the Add printers dialog box, click New.

3. In the Add Network Printers to Farm dialog box, select either authentication method:

· Select Console Administrator to use the current administrator credentials.

· Select other to enter different credentials for authentication. These credentials must have Access permissions for the printer.

4. Click Next.

5. Using one of the following options, specify the Network Printer Location:

· Choose Enter UNC Path to enter the path using the format servername\printername.

· Choose Browse for Printer to locate a printer on the network.

6. 

Figure 81: Assigning printers to session

1.4.5.5 Specify a default printer for a session

To specify a network printer, it must already be imported it into your farm and added to the policy (Refer Figure 81: Assigning printers to session)

· On the Session printers rule page, from the Choose client’s default printer drop-down list, choose Name of the network printer you want to be default for this policy.

· Apply the policy to the group of users (or other filtered objects) you want to affect.