XenApp Installation

Use this documentation to help prepare your XenApp environment and then install the XenApp server software.

XenApp comprises many features and technologies, many of which have their own preparation, installation, and configuration instructions. This documentation does not cover those topics; see the documentation for the feature or technology (for example, Web Interface, Access Gateway, Secure Gateway, and Citrix plug-ins). Additionally, features and technologies offered in the XenApp editions (such as Single sign-on, Provisioning services, Load testing services) have their own installation documentation.

Building a XenApp Farm

The first time you install XenApp, you create a farm. When you install XenApp on other computers, you join the farm you created on the first computer.

Before you build a XenApp farm, read about XenApp deployment planning, and complete the preparation tasks.

A typical high-level installation sequence is:

1. Install Citrix Licensing. (You can do this before, during, or after Setup; see the Citrix licensing documentation for instructions.)

Note: If you plan to install multiple components on the same 64-bit server, install the Web Interface before the License Management Console or XenApp.

2. Install the Web Interface, if you will be using it. (See the Web Interface documentation for installation instructions; it is not covered in this section.)

3. Install one or more Citrix plug-ins on the server on which you are creating the farm. (You can do this before or during XenApp Setup.)

4. Install the management consoles. (These tools can be installed on a XenApp server either before or during Setup; they can also be installed on other systems.)

5. Create a farm by installing XenApp on the server you want to function as the data collector for the first (or only) zone.

6. Install XenApp on other infrastructure servers and then on servers that will host published applications.

7. XenApp prompts you to restart at the end of installation. You must restart XenApp for it to integrate properly with Terminal Services.

After installing XenApp, perform the required post-installation configuration tasks.

The information that follows is based on using the wizard-based installation. Generally, the sequence and explanations also apply to custom installations.

Preparing Your Environment

Updated: 2010-03-02

Before installing XenApp, complete the following preparation tasks, in any order. Some tasks are required only if you want to use a particular feature or technology. Most tasks apply when you are creating the XenApp farm; for preparation tasks when joining a farm, see Joining a Server Farm.

Use the left column to mark completed tasks.

  Review the Installation Checklist and install any prerequisites that will not be installed by Setup.

  Know which XenApp edition you will be installing (Platinum, Enterprise, or Advanced).

  Choose a name for your farm. Farm names can include spaces, and up to 32 characters. If you plan to use the Configuration Logging feature with an Oracle database, do not use hyphens in the farm name.

  Choose an installation method.

  Obtain the domain credentials for the user who will be the first administrator on the XenApp farm. That administrator has full permissions to the farm and can create additional administrator accounts.

  Ensure the operating system clock on each server has the correct time.

  Complete the requirements for the database you will be using for the XenApp data store. (This can include installing the database software, installing the database client, and (for direct access) installing appropriate ODBC drivers.) For database planning information, see Planning the XenApp Data Store. If you plan to use the IMA encryption features, see Planning for Configuration Logging and IMA Encryption.

The Data Store Database Reference topics contain database installation guidance, plus additional information that might affect installation.

If you are using a Microsoft SQL Server, Oracle, or IBM DB2 database for the data store, and are not using the wizard-based Setup, see Creating a DSN File for XenApp Setup.

  If you will be running Setup on a system with User Access Control (UAC) enabled, see Planning for UAC.

  Install Citrix licensing, unless you choose to install it during or after Setup (Setup prompts you for licensing information).

  Install the Web Interface (if you plan to use it), unless you choose to install it during Setup. If you want the XML Service to share a port with IIS, you must install the Web Interface before running Setup. Configure a XenApp Web or XenApp Services site. For more information, see Planning for the Web Interface and XML Broker and the Web Interface documentation.

  If you want to change the accounts under which certain XenApp services run, see Substituting Domain Accounts for User Accounts.

  Install XenApp plug-ins on each server in the farm, unless you want Setup to install them. Setup requires installing at least one XenApp plug-in for functionality such as pass-through client authentication and shadowing to work correctly. If you invoke Setup from Autorun, the XenApp hosted plug-in and the XenApp streaming plug-in are installed automatically by default.

  If you plan to use Philips SpeechMike devices with XenApp, install the drivers on all servers hosting sessions that record audio.

  If you plan to enable Windows Multilingual User Interface (MUI) support, see Planning for Supported Languages and Windows MUI Support.

  If you plan to use session shadowing, see Planning for Shadowing.

  If you plan to use passthrough client authentication, see Planning for Passthrough Client Authentication.

  If you plan to use the XenApp Management Pack for Microsoft Operations Manager 2005 or Microsoft Systems Center Operations Manager 2007 to monitor either your XenApp farm or Citrix Licensing, install the XenApp Provider and the Licensing Provider, which are the XenApp Windows Management Instrumentation (WMI) providers.

Creating a Farm

Start the wizard-based installation by double-clicking autorun.exe. (You cannot start Setup by double-clicking mps.msi.)

The following list summarizes the task sequence to create a XenApp farm. Links are provided to separate topics if a task is extensive or requires further description.

Choosing the Edition

Choosing an Installation Category

After selecting Application Virtualization as the installation category, the License Agreement page appears. Read the License Agreement and indicate your agreement.

The Prerequisites Installation page lists the items to install before installing XenApp. If you are using the wizard-based installation, some of these prerequisites are installed automatically. This information is also available in the XenApp Installation Checklist.

Selecting Components

Enabling and Configuring Passthrough Client Authentication

Installing the License Server

Installing the Access Management Console

The Access Management Console is a framework into which you install snap-ins or extensions. Each extension provides additional administrative functionality for your Citrix environment. For example, when installing XenApp Platinum Edition, extensions for features such as Password Manager are installed.

Important: Do not install different versions of Access Management Console on the same server.

Selecting Components of XenApp

Specifying the Farm Name, Data Store, Zone, and Credentials

Enabling and Configuring IMA Encryption

Specifying the Citrix License Server

Enabling and Configuring Session Shadowing

Configuring the Citrix XML Service Port

Adding Users to the Remote Desktop Users Group

Installing XenApp Advanced Configuration

Important: Do not install different versions of XenApp Advanced Configuration on the same server.

Installing the XenApp Document Library

Important: The XenApp Documentation Library contains information available when this version of XenApp released. The most current documentation is in Citrix eDocs.

Choosing the Edition

Start the installation by double-clicking autorun.exe. (You cannot start Setup by double-clicking mps.msi.)

The initial Autorun page has the following options:

Option Description

Installation Checklist Displays XenApp installation prerequisites and system requirements. Reading this can help avoid delays during Setup.

Platinum Edition, Enterprise Edition,Advanced Edition

XenApp is available in three editions. The components and features available for installation vary with each edition.

Citrix on the Web Provides links to the Citrix Web site and the Citrix Support Web site.

To continue installation, select your XenApp edition.

Choosing an Installation CategorySelect an installation category. The components and features displayed vary according to the XenApp edition you selected previously; the following display is for the Platinum Edition.

Option Description

Application Virtualization Installs Citrix Licensing, XenApp, Web Interface, Access Management Console, Advanced Configuration tool, and documentation.

Application Session Recording Installs SmartAuditor administration features, the SmartAuditor Player, and the SmartAuditor Agent.

Application Performance Monitor Installs EdgeSight Server and the EdgeSight Agent.

Single Sign On Installs the Citrix Password Manager service, the plug-in, and the Central Store.

Common Components Installs components such as the Citrix XenApp plug-ins, Streaming Profiler, Access Management Console, XenApp Configuration tool, Web Interface, Secure Gateway, Citrix Licensing, and documentation

To install the XenApp server, select Application Virtualization.

Selecting Components

On the Component Selection page, select the major components you want to install. By default, all components except the license server and the EdgeSight agent are enabled for installation. When you click Next, a sequence of separate wizards guides you through the installation of the selected components.

Depending on the components selected, some configuration options might not be available or might appear in a different order.

Option Description

Citrix Licensing (disabled by default) Installs or upgrades the licensing components for your Citrix product. Every server farm must have access to a Citrix License Server. Do not install Citrix Licensing every time you run XenApp Setup. Instead, point your XenApp servers to a common license server.

Access Management Console Installs the console framework for managing Citrix components; this console snaps in to the Microsoft Management Console (MMC).

Web Interface Installs the Web Interface.

Citrix XenApp Installs XenApp and its components. There are two suboptions:

Pass-through client. Installs Program Neighborhood and the XenApp hosted plug-in. You can select either or both.

Citrix XenApp Plugin for Streamed Apps. Installs the XenApp streaming plug-in. Even if you are not streaming applications on this server, install this client to stream applications on other servers in the farm.

XenApp Advanced Configuration or Presentation Server Console

Installs the tool that manages printing, policies, load manager, and zones.

XenApp Document Library Installs the XenApp Document Library, which is a help system for all major XenApp components and plug-ins. If you disable this component, no help will appear in any server-side XenApp components.Note: See Citrix eDocs for the most current documentation.

EdgeSight Presentation Server Agent (disabled by default)

Installs the agent for Resource Manager powered by EdgeSight.

If you select Citrix Licensing, see the Citrix Licensing documentation. For Web Interface and EdgeSight installation information, see their respective documentation.

Enabling and Configuring Passthrough Client Authentication

To enable passthrough client authentication, select Yes on the Passthrough Authentication for the Passthrough Client page.

After you enable passthrough client authentication, the Server Address for the Passthrough Client page appears.

If you installed the XenApp hosted plug-in as the passthrough client, specify the URL for your XenApp Services site (for example, http://yourservername/Citrix/PNAgent).

If you installed the Web Interface on this server, specify either localhost or the full URL for the XenApp Services site. If you installed the Web Interface on a different server, specify the full URL for the XenApp Services site.

If you are provisioning your servers using a third-party cloning program or using them in a virtual environment, specify the name of the Web Interface server, not localhost.

If you have not installed the Web Interface, click Next and enter the address after installation.

For more information, see Planning for Passthrough Client Authentication.

Installing the License ServerIf you deselected the Citrix Licensing component in the Component Selection page, a Warning! page appears, containing two options:

Option Description

Install a license server now Launches the license server Setup, which installs the Citrix License Server and the License Management Console.

I already have a license server, or will use the installation media to install one later.

Defers the requirement to specify a license server name until later in Setup. You can also defer installing the licensing components until after Setup.

Selecting Components of XenAppThis page might not appear for all XenApp editions, and the components listed may vary. This page contains the following options:

Application Streaming (enabled by default)

Load Manager (enabled by default)

WMI Providers (enabled by default)

Click Disk Cost to display the amount of disk space required by the selected components.

Specifying the Farm Name, Data Store, Zone, and Credentials

Three pages appear during the process of creating a server farm.

Create or Join a Server Farm Page

Select Create a new farm. The Create a Server Farm page appears.

Create a Server Farm Page1. Enter a name for the new server farm. Farm names can contain up to 32 characters and include spaces. If

you will be using Oracle as your Configuration Logging database, do not use hyphens in the farm name.

2. Select the data store database.

o If you are using a Microsoft SQL Server, Oracle, or IBM DB2 database for the data store, select Use the following database on a separate database server, and select the database from the list. If your driver does not appear on the list, cancel Setup, install the driver, and then restart Setup. (After you complete this page, Setup creates a Data Source Name (DSN) file and names it MF20.dsn.)

o If you are using a Microsoft Access or SQL Server Express database for the data store, select Use a local database on this server, and select the database from the list.

3. If you want to change the default server farm zone name (Default Zone), clear the Use default zone name check box and enter the new name.

For more information about the data store, see Planning the XenApp Data Store and Data Store Database Reference. For information about zones, see Planning for WANs by Using Zones.

Assign Farm Administrator Credentials Page

Enter the domain credentials for the user who will be the first farm administrator. This administrator has full permissions to the farm after XenApp is installed, and can create additional administrator accounts in the Access Management Console.

Enabling and Configuring IMA Encryption

If you enable IMA encryption when you create a farm, you must enable it on all servers that join that farm, using a key specified during Create Farm Setup. After enabling IMA encryption, you cannot disable it without reinstalling all existing farm servers.

To enable IMA encryption during Setup, keys must be specified and loaded (activated in the data store). Specifying a key does not necessarily load it.

If you have multiple farms in your environment, Citrix recommends that you generate separate keys for each farm.

Citrix recommends installing XenApp using network credentials when enabling IMA encryption during Setup.

1. On the Enable IMA Encryption page, select the Enable IMA Encryption check box and click Next.

2. On the IMA Encryption Key Type page, select one of the following options:

Option Description

Install Key From File Select this option if you already generated a key file for this farm.

This option specifies the key file and loads it. If you already loaded the key, use theUse Previously Loaded Key option.

Generate and Install New Key Select this option if you have not yet generated a key for this farm. This option generates a key and installs it on the local computer.

Use Previously Loaded Key Select this option if you already generated a key using the CTXKEYTOOL and loaded the file on this server before you started Setup. (This option is not available if the key file is not on this server.)

o If you select Install Key From File, browse to the location of the key file (USB flash drive, diskette, or other location you can access). If the key file is on a network location, use a UNC path to specify the location.

After you select the key file, the Citrix License Settings page appears; this indicates you successfully loaded the key.

o If you select Generate and Install New Key, save the key to any folder on your local computer.

Important: Citrix recommends choosing a meaningful key name, such as one that matches the farm (for example, C:\Alpha Farm Key\alphafarmkey.ctx). You can specify any extension that is not in use. Citrix also recommends backing up the key file.

After you click Save, the Citrix Licensing Settings page appears. This indicates you successfully configured and enabled IMA encryption.

o If you select Use Previously Loaded Key and you loaded a valid key, the Citrix Licensing Settings page appears. This indicates you successfully configured and enabled IMA encryption.

For more information, see Planning for Configuration Logging and IMA Encryption.

Specifying the Citrix License ServerBefore users can connect to XenApp, you must configure the first server in the farm to use a Citrix License Server. Select one of the following options:

Option Description

Enter the host name for the machine hosting your Citrix License Server

Type the host name. If the license server is not using the default port number (27000), enter the port number. By default, servers joining the farm use the information you enter here.

You cannot leave the license server name blank.

Enter the correct host name later If you do not know the license server name and port number, you can enter this information later using the Access Management Console.

Enabling and Configuring Session Shadowing

Session shadowing lets you monitor and interact with user sessions. When you shadow a user session, you can remotely view the user session display and interact with the session using your own keyboard and mouse.

Caution: Shadowing restrictions are permanent. If you disable shadowing or shadowing features during Setup, you cannot reconfigure them after Setup, and they apply to any policies for user-to-user shadowing.

Choose among the following options:

Option Description

Prohibit shadowing of user sessions on this server

Disables user session shadowing on this server.

Allow shadowing of user sessions on this server Enables user-session shadowing by the server. You can apply the following restrictions:

Prohibit remote control. By default, authorized users can view a session they are shadowing and use their keyboard and mouse to interact with it. This option lets authorized users know their session is being shadowed.

Force a shadow acceptance popup. By default, an acceptance prompt notifies users when an authorized user attempts to shadow their sessions. This option prevents authorized users from shadowing sessions without sending an acceptance prompt.

Log all shadow connections. Enables logging of shadowing attempts, successes, and failures in the Windows event log.

For more information, see Planning for Shadowing.

Configuring the Citrix XML Service Port

XenApp uses the Citrix XML Service to supply the Web Interface server and its connecting clients with the names of applications available in a farm. By default, Internet Information Services (IIS) uses port 80 for HTTP traffic and port 443 for HTTPS traffic, if configured.

Important: All servers in the farm must use the same TCP port for the Citrix XML Service.This page has the following options:

Option Description

Share default TCP/IP port with Internet Information Services(default)

The XML Service and IIS use the same port for communications. This option requires the Web Interface be installed before running XenApp Setup.

Use a separate port Opens a different port number on the XenApp server for XML Service communications with the Web Interface and the clients.

Make sure other applications do not use the port number. For a list of ports in use, type netstat -a at a command prompt. Configure Web Interface servers (and any clients connecting to it) to use the new port number.

Select the port sharing option if:

You plan to send data to the Web Interface over a secure HTTP connection using SSL. You can run the Citrix XML service over port 443 using SSL in two ways:

o Configure IIS for HTTPS traffic on port 443.

o Configure SSL relay on port 443. It does not matter whether you choose port sharing or not.

The Web Interface and XenApp are installed on the same server.

The Web Interface and the Citrix XML Service are installed on the same server.

Select the separate port option if:

You want to install the Citrix XML Service on a dedicated XML server

You do not want the Citrix XML Service to share the TCP port with IIS

If you want to change the Citrix XML Service port after installation, you must do it manually; there is no option on the Server Properties > XML Service page.

For more information, see Planning for the Web Interface and XML Broker,

Adding Users to the Remote Desktop Users Group

Only users who are members of the Remote Desktop Users group can connect to published applications. By default, there are no users in the Remote Desktop Users group. Until you add users to this group, only administrators can connect remotely to the server.

This page has the following options:

Option Description

Add the Authenticated Users now Adds domain accounts in the Windows Users group to the Remote Desktop Users group. Users added to the Windows Users group in the future will also added to the Remote Desktop Users group.

Add the list of users from the Users group now Copies all current users from the Users group to the Remote Desktop Users group. After Setup, if you add user accounts, you must add the accounts to the Remote Desktop Users group manually.

Skip this step, and add users later Does not add any users to the Remote Desktop Users group.

Joining a Server Farm

After installing XenApp on the first server in the farm (creating the farm), you can install XenApp on other servers. When you install XenApp on other servers, you join the farm, and see a subset of the options in the Create Farm Setup.

This topic provides information about the tasks in Join Farm Setup that differ from Create Farm Setup.

Preparation for Join Farm SetupBefore you join servers to an existing server farm, have the following information available:

The farm name.

If you are using a Microsoft SQL Server, Oracle, or IBM DB2 database on a dedicated server for the data store, you need the logon credentials of a user authorized to access the database.

If you are using a Microsoft Access or SQL Server Express database on the first server in the farm for the data store, you need the name of that server and the logon credentials of a user authorized to access the database.

If you enabled IMA encryption when you created the farm, either:

o Copy the key you used for the first server in the farm to a network share that you specify with a UNC path, or

o Access the key you generated when you created the farm from a portable storage device (such as a USB flash drive).

You cannot generate a new key when joining a farm.

Citrix recommends that you delete the key from the server after you complete the installation of the farm.

Initial Setup When Joining a Farm

Until you reach the Create or Join a Server Farm page, Setup is identical to creating a farm. Install the components and features you want on that server. Servers joining farms might not need as many components as the first server in the farm.

On the Create or Join a Server Farm page, select Join an existing farm. The Join a Server Farm page appears.

Configuring Zones and the Server Connection to the FarmOn the Join a Server Farm page:

1.  If you have more than one zone in your farm, clear the Use default zone name check box, and enter name of the zone where you want add the server. For environments with only one zone, leave the Use default zone name check box selected.

2. To connect to the data store directly (typically when using a Microsoft SQL Server, Oracle, or IBM DB2 database on a dedicated server for the data store):

a. Select Connect directly to the database using ODBC

b. Select your database from the list and click Next.

c. Configure the ODBC driver associated with the database, using the instructions in the database vendor documentation.

To connect to the data store indirectly (typically when using a Microsoft Access or Microsoft SQL Server Express database):

d. Select Connect to a database on this server, specify the name of the server hosting the database, and click Next. The default communication port is 2512.

e. On the Access the Database on a Citrix XenApp computer page, specify credentials for the server to which you are connecting, and click Next.

After completing the Join a Server Farm page, either the Citrix Licensing Settings page or the IMA Encryption Key Type page appears, depending on whether or not IMA encryption is enabled on the farm you are joining.

Specifying the IMA Encryption Key File Location

Setup automatically detects if IMA encryption is enabled on the farm you are joining, and prompts you to specify the location of the same key used on the first server in the farm.

To configure IMA encryption during Join Farm Setup, complete one of the following:

Add the key file to each computer before installation

Put the key file in a shared network location that is accessible by specifying a UNC path

Put the key file on a portable storage device, such as CD or USB drive that you use for every installation

Select one of the following methods of specifying the key file location:

Option Description

Install Key From File Select this option if you did not load a key file on this server. Browse to the location of the key file. If the key file is on a network location, use a UNC path to specify the location.

Use Previously Loaded Key This option is available only if you already loaded the key for this farm onto this server. If you loaded a valid key, the Citrix Licensing Settings page appears.

To verify that IMA encryption is enabled and configured properly on the servers, use the CTXKEYTOOL command with the query option, which is located in the Support folder on the installation media.

Using Farm Licensing SettingsWhen joining a farm, you can use the same settings as the farm or point to a different license server. On the Citrix Licensing Settingspage, select one of the following options:

Option Description

Enter the host name for the machine hosting your Citrix License Server

Points to a different license server than the other servers in the farm.

Use the global farm settings for the license server

Points to the same license server as the other servers in the farm.

Enter the correct host name later If you do not know the license server name and port number, you can enter this information later using the Access Management Console.

Migrating to XenApp 5.0The term migrating means the process of moving data and settings from an older release to this release. There are three ways in which you can move servers in your farm to the next release.

Server Migration A new installation of XenApp on a clean system in an existing farm. Because you do this by performing a full installation (not the Upgrade wizard), no settings are carried over on the server. However, the server gets its farm settings from the existing farm.

Farm Upgrade The existing farm and data store are maintained, but at least one server in the farm is migrated to the new XenApp release.

Farm Migration A new farm and data store are created, based on the installation of at least one new server (that is, the first server in the farm).

A mixed farm comprises servers running different versions of XenApp and Presentation Server.

Important:

Citrix does not support upgrading any components from Windows Server 2003 to Windows Server 2008 unless noted.

Migrating from Release Preview versions of XenApp to the official released version is not supported.

To have a mixed farm, you must add the XenApp 5.0 for Windows Server 2008 servers to the XenApp 5.0 for Windows Server 2003 or Presentation Server 4.5 with Feature Pack 1 farm. You cannot add computers running Presentation Server 4.5 with Feature Pack 1 to a XenApp 5.0 for Windows Server 2008 farm.

Interoperability of XenApp 5.0 for Windows Server 2008 with servers and farms prior to Presentation Server 4.5 with Feature Pack 1 is not supported.

Downgrading a server from XenApp 5.0 for Windows Server 2008 to Presentation Server 4.5 or XenApp 5.0 for Windows Server 2003 is not supported.

Choosing a Farm Migration StrategyThere are two migration methods.

Migrating servers individually, which gradually converts the farm to the current release and maintains the existing farm name and data store; this is a phased migration

Creating a new farm and, as you reimage or create servers with the next release, adding them to the new farm and manually copying farm settings and policies

When determining whether to migrate all or part of a farm, consider the features users require. For example, if users sync PDAs, consider keeping one server with either XenApp 5.0 for Windows Server 2003 or Presentation Server 4.5 with Feature Pack 1 in your farm.

Phased Migration

If your farm is running Presentation Server 4.5 with Feature Pack 1, you can perform a phased migration by joining newly imaged XenApp 5.0 for Windows Server 2008 servers to the existing farm, as you remove Presentation Server 4.5 with Feature Pack 1 servers.

This type of migration maintains existing policies and their rules. When a XenApp 5.0 for Windows Server 2008 server joins a Presentation Server 4.5 with Feature Pack 1 farm, any policy rules introduced with the new release are set to Not Configured. On the XenApp 5.0 for Windows Server 2008 server, you can enable new rules in existing farm policies. However, servers running earlier releases disregard the new rules.

The migration of any server in a farm, regardless of zone designation, upgrades the entire farm and places the farm into a mixed-farm mode. If a pilot zone is used for pre-production testing and XenApp 5.0 for Windows Server 2008 is installed on a server in this zone, the farm is now running in mixed mode. Unexpected issues might develop. Citrix strongly recommends that all testing be done in a segregated farm to avoid impacting production users.

Running a mixed-farm environment for the period that you are migrating individual servers can make administration more complex. Although you can keep your farm in production, it is not as clean a method as creating a new farm. Citrix recommends running in mixed-mode for the shortest period of time possible.

Creating a New Farm

Consider creating a new farm when a significant number of changes will be implemented. This reduces the possibility of data corruption. If your existing farm is based on any version except Presentation Server 4.5 with Feature Pack 1 or XenApp 5.0 for Windows Server 2003, you must create a new farm.

This method does not retain settings, so you must manually key in all policies and configurations. While migrating your farm, consider using the Web Interface as the primary point of entry. Users can access both the old farm and the new farm during the migration period, because the Web Interface can merge applications available from different farms and display them on the same Web page.

Creating a Migration PlanAn effective migration plan defines four key steps: requirements, the design, testing, and implementation.

Identify and confirm requirements - Business (such as cost of ownership or personnel), technical (such as existing infrastructure, complexity), and user requirements (such as passthrough authentication and ease of access).

Document the design - The design document is a blueprint for the new environment; it incorporates new features and major changes that will impact the server farm. Citrix recommends creating detailed design documents for migration similar to those you created for the initial installation.

Test - Check the effect of new functionality, such as how using a Windows Server 2008 system affects your farm configuration.

Implementation plan - Create a timeline. An implementation plan is often based on the design document and includes a project plan with schedules, resources, and dependencies. The implementation plan can also include the method of imaging servers, configuration of settings, application installation method, help desk training, user training, the stages of the rollout (if applicable), and the plan for decommissioning the old farm (if applicable).

Infrastructure Server Design Considerations

As farms expand in size or the number of user connections increases, you might need to increase the number of servers dedicated to hosting infrastructure in your environment. For example, if you have added application servers to your farm, you might need to migrate from a infrastructure server hosting the Citrix License Server, the data collector and the XML Broker to a server hosting just the data collector and the XML Broker or a dedicated server for each function.

Load Manager Design Considerations

Because 64-bit servers support a higher number of users, check the Load Manager design in your farm to ensure its efficiency, particularly if you are using the Default or Advanced Load Evaluator. If your load evaluators use percentages primarily (such as CPU or memory), you might not need to reconfigure your load-balancing implementation. If you migrated your servers to 64-bit hardware, you might be able to reduce the number of load balanced servers, because 64-bit servers can support more resources.

Consider Replacing Secure Gateway with Access GatewayEvaluate your security configuration and determine if you want to replace the Secure Gateway with the Access Gateway for remote access. Access Gateway:

Supports additional applications and protocols.

Consolidates all remote access solutions in one appliance, and secures remote farm connections and access to non-published resources (such as email, internal Web applications, and network file shares).

Replaces a server in the DMZ with a hardened appliance.

Allows you to add VPN functionality while retaining the ability to access published applications.

Allows a broad range of client devices to connect to published applications in the secure network using XenApp plug-ins.

Migrating to the Access Gateway can change your farm topology. When you remove Secure Gateway from the DMZ and replace it with the Access Gateway, you can move the Web Interface to your internal secure network. The Access Gateway authenticates and authorizes users and then connects to the Web Interface. This provides greater security because there are fewer Windows servers in the DMZ.

Migrating from the Secure Gateway to the Access Gateway includes:

Opening the appropriate firewall ports

Either migrating the security certificates from Secure Gateway or creating new ones for the Access Gateway

Installing the Access Gateway appliance

For more information, see the Access Gateway documentation.

Changes in This Release of XenApp

XenApp 5.0 for Windows Server 2008 introduces changes that might affect your farm design and installation methods, plus feature offerings and operations.

Changes Affecting Farm DesignThese changes might affect the location of components in your Citrix environment:

Unless your farm is dispersed across a WAN, Citrix recommends having only one zone in your environment. See the documentation about planning your XenApp deployment for more information.

Due to operating system requirements, Citrix does not recommend installing the SmartAuditor server on the same server as XenApp.

Changes to SetupThese changes affect the sequence or packaging of installation components:

The XenApp Media Kit, which contains the installation media, is now on a DVD.

The server URL in the Server Address for the Passthrough Client page no longer defaults to localhost because this can create issues for server provisioning.

The XenApp Hosted Plug-in now has its own .msi file, XenAppHosted.msi.

The XenApp Advanced Configuration tool now has its own installation package, CMC.msi. This package is on the installation media in Administration\XenApp Advanced Configuration. Although still installed by default, the XenApp Advanced Configuration tool is no longer included as part of the core XenApp Setup (mps.msi).

XenApp_Documentation.msi replaces the previous documentation installation package, docs.msi.

The Create a Server Farm page in XenApp Setup no longer uses your server subnet as the default zone name.

The Access Management Console now supports uninstalling all Access Management Console extensions simultaneously.

Changes Affecting Custom Installations

There is no longer a default installation type. When using Windows Installer commands (msiexec), set the CTX_MF_SERVER_TYPE property regardless of the type of installation; otherwise, Setup fails.

XenApp plug-ins must be installed before you begin XenApp Setup (plug-ins are installed by default only in the wizard-based installation).

The XenApp Hosted Plug-in in XenApp Setup now references XenAppHosted.msi. This affects XenApp server installation scripts.

o Because plug-ins must be installed before XenApp Setup begins, add commands to install the them before the commands for installing XenApp.

o Configure passthrough authentication as part of the XenApp Hosted Plug-in installation.

o Plug-in Setup properties have changed: CLIENT_INSTALLDIR is now INSTALLDIR, and ADDLOCAL was added.

o XenApp Setup fails without the plug-ins, and you might not get a warning message during a silent installation.

Update your scripts to accommodate new .msi files and their associated properties, and ensure they are in the correct sequence:

o Separate .msi files for the XenApp Advanced Configuration tool (Administration\XenApp Advanced Configuration\cmc.msi)

o XenApp_Documentation.msi replaces docs.msi

Component and Feature ChangesThese changes might affect your farm design or how you install components:

To run this release, you must have the license server that is available from Autorun or from the Citrix download site.

This version of XenApp does not support Active Sync or Windows Mobile. If you must support PDAs or other mobile devices, use a computer running Presentation Server 4.5 with Feature Pack 1 (that is, run two farms in parallel or have a mixed-farm environment).

Remapping server drive letters is no longer supported.

Conferencing Manager is no longer included with XenApp. Citrix recommends using Citrix GoToMeeting.

The Access Management Console now supports uninstalling all Access Management Console extensions simultaneously.

Citrix has replaced Resource Manager with Resource Manager powered by EdgeSight.

o If you use Resource Manager, see Finding EdgeSight Documentation.

o Resource Manager powered by EdgeSight cannot monitor computers running Presentation Server 4.5 with Feature Pack 1

For monitoring in a mixed-farm environment, use Resource Manager for the computers running Presentation Server 4.5 with Feature Pack 1 and Resource Manager powered by EdgeSight for the XenApp servers. Alternatively, you can use EdgeSight for XenApp to monitor both versions.

Using XenApp on Windows Server 2008

It is important to understand the differences in settings and behavior between Windows Server 2003 and Windows Server 2008. Some applications published successfully in a Windows Server 2003 environment might not behave as expected if they are not Windows Vista or User Account Control (UAC) compliant.

There are restrictions on running non-Vista compliant applications on Windows Server 2008.

In Windows Server 2008, the Restrict each user to a single session option in the Terminal Services Configuration tool is now enabled by default. To ensure users can connect to multiple sessions simultaneously, Citrix recommends setting this option to No.

Citrix recommends using the server and farm-wide settings in XenApp to control the number of concurrent sessions a user can launch.

Migration Requirements and RestrictionsMigrating to XenApp 5.0 has the following requirements and restrictions:

 If you are running the license server that came with Presentation Server 4.5 with Feature Pack 1, you must upgrade to the license server included with this release (or the current version). Your existing license files are compatible with the new license server.

If you migrate printer drivers, the drivers must be compatible with Windows Server 2008. For example, Windows NT 4.0 Kernel mode drivers are not supported in Windows Server 2008. Ideally, drivers installed on XenApp servers should be Vista certified.

 When you upgrade the Access Management Console from versions supplied with previous releases of XenApp, note that there are restrictions on how the later version of the console recognizes any My Views created with, or items discovered by, the earlier version. If, after upgrading, you are prompted whether or not you want to upgrade your .msc configuration file, choose one of the following:

o Upgrade - The file is upgraded; you cannot use the earlier version of the console to open the file or see any My Views created with it. However, you can use the later version.

o Don’t Upgrade - The file is not upgraded; you can use both versions of the console to see the My Views. However, you can edit and save My Views only in the earlier version.

o If you are using Secure Gateway, you must install and configure version 3.1 or later.

Important:

o Citrix does not support upgrading any components from Windows Server 2003 to Windows Server 2008 unless noted.

o Migrating from Release Preview versions of XenApp to the official released version is not supported.

o To have a mixed farm, you must add the XenApp 5.0 for Windows Server 2008 servers to the XenApp 5.0 for Windows Server 2003 or Presentation Server 4.5 with Feature Pack 1 farm. You cannot add computers running Presentation Server 4.5 with Feature Pack 1 to a XenApp 5.0 for Windows Server 2008 farm.

o Downgrading a server from XenApp 5.0 for Windows Server 2008 to Presentation Server 4.5 or XenApp 5.0 for Windows Server 2003 is not supported.

To migrate from the previous releaseBefore beginning this procedure, review To uninstall XenApp and remove a server from a farm.

1. Upgrade the Citrix License Server and download current licenses.

2. Migrate your data store to a version supported by XenApp 5.0, if necessary.

3. Upgrade or perform a new installation of the XenApp Advanced Configuration tool, Access Management Console, and Web Interface.

(To upgrade these components automatically and preserve custom configuration settings, use the default settings in their Setup programs when invoked from Autorun.)

Note: You can use the Upgrade wizard in Setup to upgrade the Access Management Console and XenApp Advanced Configuration only if you are upgrading these components on the same operating system platform (for example, Windows Vista to Windows Vista).

4. Remove any servers from the farm that you want to reimage; see To uninstall XenApp and remove a server from a farm.

5. Install XenApp 5.0 for Windows Server 2008 on the reimaged or new servers using Join Farm Setup. Migrate the servers in this order:

a. Zone data collectors

b. Infrastructure servers

c. Servers hosting published applications

6. If you are using Secure Gateway, install and configure version 3.1 or later.

Rebuilding and Renaming XenApp Servers

When replacing a server due to hardware failure, or renaming a farm server using the operating system, follow specific steps in the XenApp farm maintenance documentation to prevent corruption of the data store records and ensure the server is properly integrated in the farm.

To uninstall XenApp and remove a server from a farmBefore uninstalling XenApp and removing a server from a farm:

In farms with direct and indirect connections to the data store, Citrix recommends uninstalling indirectly connected servers before uninstalling the server they connect through (that is, the server connecting directly). If XenApp is uninstalled from a server with a direct connection to the data store, indirectly connected servers cannot access the data store. Information such as applications or Citrix Administrators is lost, and indirectly connected servers cannot be uninstalled from the data store.

Citrix does not recommend uninstalling XenApp from within a Remote Desktop Connection (RDC) session because the uninstall program logs off all remote users as it uninstalls XenApp. If you need to uninstall XenApp remotely, use tools such as Microsoft Configuration Manager.

Although you can remove a server from a farm using only the Access Management Console, Citrix recommends using the method described below because it is safer.

1. With the server on the network and online in the farm, uninstall XenApp. From the Start menu, select Control Panel > Programs and Features > Citrix XenApp 5.0 > Uninstall.

2. On a different server, open the Access Management Console, run Discovery and verify that the server was removed from the farm successfully. If the server from which you uninstalled XenApp still appears in the Access Management Console:

a. In the left pane of the Access Management Console, select the server.

b. From the Action menu, select All Tasks > Remove from farm.

3. After verifying the server no longer appears in the farm in the Access Management Console, disconnect the server from the network.

Caution: Do not reconnect the server to the network until you reimage it or remove its XenApp software. If it reconnects to the network, it can corrupt your farm.

4. Run the dscheck command on the data store to repair any consistency errors.

5. If you want to reuse the hardware for that server, perform a new installation of the operating system (that is, a clean installation and not an upgrade) and XenApp 5.0.

To migrate a server farm by creating a new farm1. Use the Citrix Client Packager to provide the latest plug-ins to users, repackage the XenApp plug-in, and

include the URL of your XenApp Services site.

Some XenApp 5.0 features require new plug-ins. Citrix recommends upgrading user plug-ins before migrating so you can address any issues that arise before migrating the farm. Upgrading plug-ins before migrating the farm makes it easier to determine if issues are related to the plug-ins or the farm servers.

Instead of using the Citrix Client Packager, you can deploy the new package to client desktops using an Active Directory Group policy, Microsoft System Center Configuration Manager, or another third-party deployment product. This deployment method requires no user input.

For more information, see the plug-in documentation.

2. If the data store is not hosted on a Microsoft Access database, create a new data store. Install XenApp 5.0 for Windows Server 2008 on a server that is independent of your existing farm and give it a name that is different from the existing farm. This is the first server in the new farm.

3. Use the Access Management Console and the XenApp Advanced Configuration tool to configure your newly installed XenApp server to match the settings of your existing farm. Ensure that you also match the settings for published applications. Alternatively, you can create a script to export and import published application information. See the Citrix Developer Network for additional information.

4. Deploy the Web Interface as the primary entry point for your newly installed farm. Use DNS CNAME (alias) records for the Web Interface servers. Use a simple mnemonic for the DNS alias, such as myapps. (For

example, Citrix could have an internal Web Interface deployment with multiple servers that share the DNS alias myapps.citrix.com.) See the Web Interface documentation for more information.

5. Open the new deployment for testing by pilot users.

6. After refining the pilot deployment, switch users to it. Instruct users to access your Web Interface server URL. (Using the example above, http://myapps.citrix.com.)

7. Decommission the farm running the legacy release of XenApp.

Mixed Farms

Updated: 2010-06-17

Citrix recommends that, where possible, you upgrade all of the servers in a farm simultaneously so that you do not have different versions of XenApp and Presentation Server running in the same farm. However, XenApp 5.0 for Windows Server 2008 servers can coexist with XenApp 5.0 for Windows Server 2003 or Presentation Server 4.5 with Feature Pack 1 servers. In addition, XenApp 5 for Windows Server 2008 supports both 32-bit and 64-bit editions of Windows operating systems in the same farm.

To discover a mixed farm, run discovery using the latest Access Management Console for a XenApp 5.0 for Windows Server 2008 server. New features might not be available if you do not use the latest Access Management Console.

After discovery completes, the functionality and display vary depending on the version of the server you select. For example, if you select a server running Presentation Server 4.5 with Feature Pack 1, you see Resource Manager information (if installed); if you select a server running XenApp 5.0 for Windows Server 2008, you will not see this.

You can also manage multiple farms; for example, one farm comprising XenApp 5.0 for Windows Server 2008 servers and another farm comprising either Presentation Server 4.5 with Feature Pack 1 servers or XenApp 5.0 for Windows Server 2003 servers. Again, you must use the latest Access Management Console to discover the farms.

When installing XenApp 5.0 for Windows Server 2008 in a mixed-farm environment, if you are creating domain accounts for services, make sure that the accounts do not have the same name as the accounts on the servers running the earlier release. If the privileges associated with one of the accounts are higher for one version of XenApp than another, the accounts might conflict.

Citrix does not recommend running in mixed-mode indefinitely. If it is necessary to retain Presentation Server 4.5 with Feature Pack 1 or XenApp 5.0 for Windows Server 2003 for specific features, Citrix suggests having two farms and using the Web Interface to integrate them.

Important:

To have a mixed farm, you must add the XenApp 5.0 for Windows Server 2008 servers to the XenApp 5.0 for Windows Server 2003 or Presentation Server 4.5 with Feature Pack 1 farm. You cannot add computers running Presentation Server 4.5 with Feature Pack 1 to a XenApp 5.0 for Windows Server 2008 farm.

Interoperability of XenApp 5.0 for Windows Server 2008 with servers and farms prior to Presentation Server 4.5 with Feature Pack 1 is not supported; only Presentation Server 4.5 with Feature Pack 1 and XenApp 5.0 for Windows Server 2003 are supported for a mixed farm.

The Access Management Console included with XenApp 5.0 for Windows Server 2008 can manage servers running Presentation Server 4.5 with Feature Pack 1 only when at least one XenApp 5.0 for Windows Server 2008 server is installed in the farm.

Downgrading a server in your farm from XenApp 5.0 for Windows Server 2008 to Presentation Server 4.5 or XenApp 5.0 for Windows Server 2003 is not supported.

Increasing Graphics Memory Limit in a Mixed Farm

In XenApp 5.0 for Windows Server 2008, the default graphics memory limit is 32MB and the maximum graphics memory limit is 64MB. In a mixed farm, the default graphics memory limit is 5MB; the maximum graphics memory limit is 8MB. These limits derive from the Presentation Server 4.5 with Feature Pack 1 defaults.

In a farm comprising only XenApp 5.0 for Windows Server 2008 servers, you can use the Access Management Console to increase the graphics memory limit for all servers in the farm or for individual servers. In a mixed farm,

only the XenApp 5.0 for Windows Server 2008 servers respect the limits set using the Access Management Console. The Citrix Knowledge Center has information about how to allow more memory for session graphics on Windows Server 2003.

Administering Resource Manager in a Mixed Farm

In XenApp 5.0 for Windows Server 2008, Resource Manager has been replaced by Resource Manager powered by EdgeSight. As a result, Dashboard and My Knowledge are no longer available. However, in a mixed-farm environment, you can administer the Resource Manager that is installed on a server running Presentation Server 4.5 with Feature Pack 1. For farms containing XenApp 5.0 for Windows Server 2003 servers and XenApp 5.0 for Windows Server 2008 servers, you can use either the original Resource Manager or the new Resource Manager.

On a server running Presentation Server 4.5 with Feature Pack 1, the original Resource Manager documentation is available in the Documentation Center; it is also available in the Citrix Knowledge Center.

Administering Installation Manager in a Mixed Farm

In XenApp 5.0 for Windows Server 2008, Installation Manager has been replaced by a new tool, also called Installation Manager, which is based on Microsoft Windows Task Scheduler 2.0 and Windows PowerShell 1.0. However, in a mixed-farm environment, the previous version of Installation Manager on a Presentation Server 4.5 with Feature Pack 1 or XenApp 5.0 for Windows Server 2003 server is available through those servers' versions of the Access Management Console and the Presentation Server Console.

Administering Isolation Environments in a Mixed Farm

In XenApp 5.0 for Windows Server 2008, application streaming replaces isolation environments. In a mixed-farm environment, you can administer isolation environments on Presentation Server 4.5 with Feature Pack 1 or XenApp 5.0 for Windows Server 2003 servers using those servers' versions of the Presentation Server Console.

SNMP Considerations in a Mixed Farm

In XenApp 5.0 for Windows Server 2008, Simple Network Management Protocol (SNMP) traps can be enabled/disabled through the Access Management Console. In a mixed-farm environment, you can enable/disable SNMP alerts on Presentation Server 4.5 with Feature Pack 1 or XenApp 5.0 for Windows Server 2003 using the Resource Manager on those servers.

Provisioning Servers and Configuring XenApp

Provisioning refers to the process of distributing XenApp software across a group of servers.

After XenApp Setup completes, you can refine the configuration of infrastructure servers and zones, and configure application servers.

You can run scripts to perform configuration tasks such as publishing applications, setting data collector election preferences, and applying load evaluators. You can make changes on a per-server basis, as needed. For information about scripting, see the Citrix Developer Network.

Provisioning Farm Servers

After you install XenApp on the second server in your farm, you can provision other servers in the farm.

When provisioning farm servers, consider these methods:

Using Citrix Provisioning services - Certain XenApp editions support Citrix Provisioning services, which streams operating systems and applications, including XenApp, to farm servers. The streamed data is not persistent, so images must include everything you want to stream (that is, the operating system, XenApp, published applications). For more information, see the Citrix Knowledge Center; an implementation guide is available in CTX120513, and an integration utility in CTX116063.

Deploying Windows Installer Packages using Active Directory - You can use Active Directory to push out Windows Installer packages to multiple servers and workstations simultaneously. You can use XenApp

transforms to select the installation options and enter data. Using Active Directory for imaging can reduce the number of times you need to directly interact with a server during the imaging process. You can install prerequisites (depending on the vendor for the prerequisite support), run XenApp installation, and then install applications. You do not need to connect to the target server to invoke the installation programs manually.

Cloning servers with preconfigured images - You can use third-party imaging programs, such as Symantec Altiris, to create a copy of the installation and configuration of a server that joined the farm. Then, use this image to create additional servers in the farm. This process is referred to as cloning. You can also clone virtual machines with products such as XenServer.

Using the XenApp unattended installation - With unattended installations, you create an answer file that specifies your configuration. You then run Setup on a system, using that answer file. This method does not let you include prerequisites in the installation and requires more manual interaction; however, a template is provided.

See the Custom XenApp Installation topics for more information about using Windows Installer packages and unattended installations.

Simultaneous Installation Considerations

When you install multiple servers simultaneously, servers write configurations to the same data store indexes. Consequently, the more servers you install simultaneously, the more likely you are to create deadlocks on the database server.

During XenApp Setup, deadlocks can occur when one server times out while waiting to write to a piece of data that is locked by another server. Deadlocks can cause installation to fail on some servers or cause them to install much slower than necessary.

When installing servers simultaneously, Citrix recommends:

Server Hosting Data Store Maximum Number of Servers to Install Simultaneously

Dual processor or greater 30

Older server 10

Do not install multiple servers and create a zone at the same time. Create the zone first and then perform the simultaneous installations. Having the zone in place before running simultaneous installations prevents the new servers from being configured as the data collector.

loning XenApp ServersCloning a XenApp server involves the following:

1. Creating a template image from a configured farm server, which means removing the image identity so that the image becomes a template you can reuse (servers have properties that contribute to their unique identity, such as the server name, domain membership, and Security ID (SID)).

2. Distributing the image to the farm servers.

3. Recreating the unique identity of each of these servers.

Cloning techniques are used when creating a XenApp farm with provisioning technologies such as Citrix Provisioning services or Symantec Altiris. These techniques are also used with virtualization technologies that host XenApp, such as Citrix XenServer, the Windows Server 2008 Hyper-V feature, and VMWare environments.

Typical candidates for cloning are servers you must repeatedly install. In small or medium farms, you might only need to make cloned images of servers that will host published applications. In large farms, you might also create cloned images for the Create Farm server and infrastructure servers.

When preparing a server for cloning with Citrix Provisioning services, you can include any applications and other settings you want to appear in that image.

Although XenApp is compatible with server cloning, issues resulting from cloning software can cause the operating system or its add-ons to function incorrectly. When cloning XenApp servers, clone one server and check its operation in a test environment before deploying the image to the rest of the farm.

Preparing your Servers for CloningBefore changing the SID on the server used to access the XenApp Advanced Configuration tool, add one of the following as a Citrix Administrator with read-write privileges:

A domain administrator

The Local Administrators group

A local administrator from a server where the SID will remain static

Important: Do not create an image of a server with an SSL certificate installed; SSL certificates are unique to the hardware.

Configuring Servers after Cloning

Zone settings are not retained when cloning a server. When the Citrix Independent Management Architecture service on the cloned server starts for the first time, the cloned server joins the Setup default zone. When deploying images to servers in multiple zones, assign zone information for each server after the cloning process.

After imaging your servers, join these servers to your farm by using the CHFARM command.

To clone a serverThis task requires a system preparation utility, such as Microsoft Sysprep, third-party imaging software, and a text editor.

This task assumes you want to clone a server for the purpose of hosting published applications and that a relational database (Oracle, SQL Server, or DB2) is hosting the data store. C is the drive on which XenApp is installed.

If you are using Citrix Provisioning services, using the PVS PS Integration Utility can accelerate the integration process by automating some steps.

Important: Citrix strongly recommends that you create initial images on a test farm, not in a production environment. These instructions are for guidance only, and will vary depending on the environment and imaging software.Caution: The following procedure requires editing the registry. Using Registry Editor can cause serious problems that can require you to reinstall the operating system. Citrix cannot guarantee that problems resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

1. After creating your farm, install XenApp on another server using Join Farm Setup, and join the farm you created.

2. Configure the server with settings you want on all servers. (For example, you might want to configure policies, set the data collector election preference to Not Preferred if this image will be used for servers hosting published applications, or add printer drivers.)

3. Configure XenApp services.

o Stop the Citrix MFCOM Service, and set its Startup type to Manual.

o Stop the Citrix Independent Management Architecture, and set its Startup type to Manual.

o Stop the Citrix WMI Service

4. Configure the registry.

a. In the registry on the server, set HKLM\SOFTWARE\Wow6432Node\Citrix\IMA\RUNTIME\PSRequired to 1. This key is in HKLM\SOFTWARE\Citrix\IMA\Runtime\PSRequired on XenApp, 32-bit edition. This forces the server to communicate with the data store so that the local host cache is updated with the new information.

b. Delete the value for HKLM\SOFTWARE\Wow6432Node\Citrix\IMA\ServerHost. This key is in HKLM\SOFTWARE\Citrix\IMA\ServerHost on XenApp, 32-bit edition.

5. Delete the contents of database local persistent cache files.

a. Delete the contents of the Local Host Cache in C:\Program Files (x86)\Citrix\Independent Management Architecture\imalhc.mdb by running dsmaint recreaterade.

b. Delete the contents of the Application Streaming Offline database cache in C:\Program Files (x86)\Citrix\Independent Management Architecture\RadeOffline.mdb by running dsmaint recreatelhc.

c. In mixed farm environments, if you are cloning a Presentation Server 4.5 with Feature Pack 1 server, delete the Resource Manager database cache in C:\Program Files (x86)\Citrix\Citrix Resource Manager\LocalDB\RMLocalDatabase.mdb.

6. Remove the workstation Identification (WSID) from DSN files. Using a text editor, open the files MF20.dsn and RadeOffline.dsn inC:\Program Files (x86)\Citrix\Independent Management Architecture, and delete the line that specifies the WSID.

7. If you are cloning a system which might have had an older XenApp plug-in installed on it at one time, delete the C:\WFCName.ini file. This file was created by previous versions of the XenApp hosted plug-in.

8. Create an image of this installation using Citrix Provisioning services, Citrix XenServer, or third-party imaging software.

9. Deploy this image to other servers using the tools provided by the imaging software.

10. To begin initializing the cloned image, restart the server where the image was deployed.

11. Using a system preparation utility or the imaging software, assigned the cloned image a new computer name.

12. Set HKLM\SOFTWARE\Wow6432Node\Citrix\IMA\Logging\HostName to the new computer name. This key is in HKLM\SOFTWARE\Citrix\IMA\Logging\HostName on XenApp, 32-bit edition.

13. Edit the CtxSta.config file to create a unique STA ID. (If you do not change this to a unique STA ID, the Secure Gateway and other components cannot uniquely identify the new server.)

a. Using a text editor, open the CtxSta.config file in C:\Program Files (x86)\Citrix\System32.

b. Use the MAC address of the new server to which you applied the clone to create the STA ID. Remove any colons or spaces from the MAC address and preface it with “STA.” (For example, the MAC address 02-00-68-55-4D-01 becomes STA020068554D01.)

c. Enter the STA ID in the UID field in the CtxSta.config file. (For example, UID=STA020068554D01.)

14. In the Windows Services panel:

a. Set the Startup type for Citrix Independent Management Architecture and the Citrix MFCOM service to Automatic.

b. Start the Citrix Independent Management Architecture service.

c. Start the Citrix MFCOM service.

d. Start the Citrix WMI service.

Configuring Infrastructure Servers After Setup

Although you can configure infrastructure servers when you install your initial farm components, you can refine the configurations for certain infrastructure elements after XenApp Setup.

Configuring Data Collectors After Setup

By default, Setup configures the Create Farm server as the data collector by setting its server election preference to Most Preferred. All servers that join the farm are set to Default Preference.

To dedicate a server as the data collector, use the XenApp Advanced Configuration tool to set it to Most Preferred and do not use it for any other functions, including hosting published applications. After configuring the data collector, set the election preferences of servers hosting published applications to Not Preferred, the lowest election preference so that the possibility of those servers acting as a data collector is low.

Configuring Zones After SetupWhen configuring zones for a WAN, Citrix recommends the following:

Do not enable load balancing across zones. Use the Zone Management feature in the Advanced Configuration tool to specify the Do not share load information option.

Direct users requests for applications to the nearest geographic location by setting up a preferred zone connection order in theUser Workspace > Connections > Zone preference and failover policy rule. Routing users to connect to servers in their own zone can reduce traffic across high latency connections. This feature only affects the XenApp plug-in and the Web Interface.

Configuring XenApp after InstallationAfter you install XenApp and configure infrastructure servers, complete the following tasks. For details, see the XenApp administrator documentation.

1. Change essential settings, including the following:

o To allow users to reconnect to sessions consistently, set the Restrict each user to a single session option to No in the Terminal Services Configuration tool. (In Windows Server 2008, this setting is enabled by default.)

o Citrix recommends using the server and farm-wide settings in XenApp to control the number of sessions users can launch.

2. After installing the Web Interface, use the Access Management Console or Delivery Services Console to create one or more sites, so that users can connect through the Web Interface or the XenApp plug-in.

3. Use the console to discover the servers in your farm.

4. Create administrative accounts.

5. Publish applications.

6. Perform other customization, such as setting policies, configuring printing, changing server election settings, and configuring load balancing.

7. Create plug-in packages and deploy them to users. See the plug-in documentation for details.

Custom XenApp Installation

XenApp offers alternatives to the wizard-based installation. Custom installations are useful when installing XenApp on large numbers of servers. See Custom XenApp Installations for custom installation method descriptions.

See XenApp Windows Installer Properties Reference for information about the properties specified in custom installations.

Custom Installations of the XenApp Management ConsolesThe XenApp management consoles have their own .msi files. The .msi file referenced by Autorun cannot be used for custom installations.

Delivery Services Console or Access Management Console - The .msi file is in Administration\console_name\setup on the XenApp installation media. Citrix recommends running CtxInstall.exe, which installs all of the extensions. If you install this console using another method, the extensions must be installed in a specific sequence or installation fails. To install this console silently, runCtxInstall.exe /silent.

Advanced Configuration or Presentation Server Console - The .msi file is in Administration\console_name\setup on the XenApp installation media. Citrix recommends running cmc.msi.

Generating an Installation Log FileInstallation and uninstallation log files are not created automatically for Windows Installer packages. You can create log files with the following methods:

Use the logging command to create log files for only the Windows Installer operations

Turn on automatic logging for all Windows Installer operations by creating a new registry string value.

Caution: Using Registry Editor incorrectly can cause serious problems that can require you to reinstall the operating system. Citrix cannot guarantee that problems resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Make sure you back up the registry before making changes to it.

Key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer

Type REG_SZ

Name Logging

Value data voicewarmup

A log file is created in the %Tmp% directory for each operation.

Use the Active Directory Group Policy Editor to configure logging properties for an Active Directory group. To edit the Logging policy, open the Group Policy Editor and select Computer Configuration > Administrative Templates > Windows Components > Windows Installer.

reparing for Custom XenApp Installations

Updated: 2010-03-02

Generally, preparing for a custom installation is the same as preparing for a wizard-based installation; see Preparing Your Environment. There are several exceptions and considerations.

Prerequisites that are automatically installed during a wizard-based Setup are not installed during a custom installation. Therefore, install all prerequisites.

A wizard-based Setup includes automatic installation of a XenApp plug-in by default. For a custom installation, install the plug-in before you install XenApp; otherwise, functionality such as pass-through authentication and shadowing might not work correctly.

The Citrix online plug-in installation packages,CitrixOnlinePluginFull.exe and CitrixOnlinePluginWeb.exe, are in the Online Plug-in folder in the installation media. You can install the online plug-in, the online plug-in web, or a combination. Install the online plug-in web package if you are configuring the Web Interface on the server.

Citrix recommends also installing the Citrix offline plug-in, CitrixOfflinePlugin.exe, which is in the Offline Plug-in folder in the installation media.

Important: If you are upgrading plug-ins/clients on the server, uninstall all previous versions, including offline plug-ins, and then install the new plug-ins.

Installing XenApp by Modifying Windows Installer Packages

XenApp and several of its components and features are compiled into a Windows Installer package (.msi) file. Windows Installer technology comprises the Windows Installer Service for the Windows operating systems and the package .msi file format used to hold information about the application setup. The XenApp Windows Installer package, mps.msi, is located in the XenApp Server folder in the XenApp installation media.

If you encounter problems when running a Windows Installer package, check the Windows Event Viewer. Also check the Application Log for entries in the Source column of type “MSIInstaller.”

Using the Windows Installer msiexec Command

Use the msiexec command to install, modify, and perform operations on Windows Installer (.msi) packages from the command line. Set properties by adding Property=”value” after other switches and parameters.

The following sample command line installs the XenApp Windows Installer package and creates a log file to capture information about this operation. This example does not include required properties.msiexec /i mps.msi /L*v c:\output.logThe following table lists several common options for the msiexec command.

Option Syntax

Install or configure a product msiexec /i {package|ProductCode}

Uninstall a product msiexec /x {package|ProductCode}

Set a logging level (use with Install or Uninstall option)

msiexec /L [i][w][e][a][r][u][c][m][p][v][+][!] LogFile

Option Syntax

To include the v option in a log file using the wildcard flag, type /L*v.

Install a transform (use with Install or Uninstall option)

msiexec /i package TRANSFORMS=TransformList

Set the user interface level (use with Install or Uninstall option)

msiexec /q {n|b|r|f}

See the Microsoft documentation for more command information. See XenApp Windows Installer Properties Reference for property descriptions and XenApp Windows Setup Properties Script Examples for sample scripts.

Applying Transforms to Setup

XenApp provides four sample Windows Installer transform (.mst) files in the Support\Install directory for XenApp Create Farm, Join Farm, and Citrix Licensing installations. Applying transforms is one method of installing XenApp through Active Directory.

Transforms you create to customize a XenApp installation package remain cached on your system. They are re-applied to the base installation package (mps.msi) when you install hotfixes (whenever the Installer needs to modify mps.msi). However, you can apply transforms only when you initially install XenApp; you cannot apply transforms to XenApp after it is installed.

To set a property in the .msi file to “Null,” delete the property in the transform file.

Creating a Customized Transform Using the Sample TransformYou need a third-party tool to edit Windows Installer packages.

1. Using the Windows Installer package editing tool, open the XenApp installation package (mps.msi) in the XenApp Server\w2k8x64 and the XenApp Server\w2k8 folders of the XenApp installation media.

2. Apply the transform that includes the properties and values you want to modify. At a command prompt, type the following, wherepackage is the name of the XenApp installation package and TransformList is the list of the transforms you want to apply (separate multiple transforms with a semicolon):

msiexec /i package TRANSFORMS=TransformList

3. Enter new values for the properties you want to change.

4. Generate the transform file and save it with a new name.

Sample TransformsSample transforms are provided in the Support\Install folder of the XenApp installation media.

thirdpartydb_create_direct.mst Creates a new XenApp farm that uses an enterprise database (Microsoft SQL Server, Oracle, or IBM DB2) for the data store on a separate dedicated server. The database is configured for direct access.

thirdpartydb_join_direct.mst Joins an existing XenApp farm that uses an enterprise database for the data store on a separate dedicated server. The new server joining the farm accesses the data store directly.

Localdb_access_create.mst Creates a new XenApp farm that uses a Microsoft Access or Microsoft SQL Server Express database for the data store. The database is stored locally on the first server in the farm on which XenApp is installed.

Join_Indirect.mst Joins an existing XenApp farm that uses Microsoft Access or Microsoft SQL Server Express for the data store. The database is stored on one of the XenApp servers.

This transform does not enable IMA encryption. If you want to enable IMA encryption, enable it manually after installation using CTXKEYTOOL.

To install the Citrix License Server through Active Directory, you can use the transform ActiveDirectoryLicensingInstallSupport.mst, which is associated with ctx_licensing.msi. For information, see the Citrix Licensing documentation.

The following table lists the property values in the sample transforms. The columns are:

A - thirdpartydb_create_direct.mst

B - thirdpartydb_join_direct.mst

C - Localdb_access_create.mst

D - Join_Indirect.mst

An empty cell indicates that property is not included in the sample transform.

Property A B C D

CTX_MF_CREATE_FARM_DB_CHOICE ThirdParty   Local  

CTX_MF_DOMAIN_NAME Domain1   Domain1  

CTX_MF_ENABLE_VIRTUAL_SCRIPTS     Yes Yes

CTX_MF_FARM_SELECTION Create Join Create Join

CTX_MF_INDIRECT_JOIN_DOMAIN_NAME       Domain1

CTX_MF_INDIRECT_JOIN_PASSWORD       (see note 2)

CTX_MF_INDIRECT_JOIN_USER_NAME       Administrator

CTX_MF_JOIN_FARM_DB_CHOICE   Direct   Indirect

CTX_MF_JOIN_FARM_SERVER_NAME       Server1

CTX_MF_JOIN_FARM_SERVER_PORT       2512

CTX_MF_LICENSE_SERVER_NAME License_Server

License_Server

License_Server License_Server

CTX_MF_LOCAL_DATABASE     SQLEXPRESS  

CTX_MF_MSDE_INSTANCE_NAME     CITRIX_METAFRAME

 

CTX_MF_NEW_FARM_NAME Farm-ThirdParty

  FarmAccess  

CTX_MF_ODBC_PASSWORD citrix citrix    

CTX_MF_ODBC_RE_ENTERED_PASSWORD citrix citrix    

CTX_MF_ODBC_USER_NAME sa sa    

CTX_MF_SERVER_TYPE e e a a

CTX_MF_SHADOW_PROHIBIT_NO_LOGGING

No No No Yes

CTX_MF_SHADOW_PROHIBIT_NO_NOTIFICATION

Yes Yes No No

CTX_MF_SHADOW_PROHIBIT_REMOTE_ICA

No No No No

CTX_MF_SHADOWING_CHOICE Yes Yes Yes  

CTX_MF_SILENT_DSNFILE (see note 1) (see note 1)    

CTX_MF_USER_NAME Administrator   Administrator  

CTX_MF_XML_CHOICE Separate Separate Share Share

Property A B C D

CTX_MF_XML_PORT_NUMBER 180 180 80 80

Note 1. Add this row to the transform because it is not available in the default Windows Installer package used for mps.msi: CTX_MF_SILENT_DSNFILE=\\fileserver\image\TestSQL.DSN

Note 2. Properties for the database password are not included. If the database has a password , add this row to the transform (if the database has a blank password, do not add the password property): CTX_INDIRECT_JOIN_PASSWORD=Password

Performing an Unattended Installation with an Answer File

You can perform an unattended installation of XenApp by creating an answer file to respond to XenApp Setup prompts. A sample answer file is provided, with instructions for setup options.

You can also use the answer file to generate a Windows Installer command line with the silent option. This command line results from running the XenApp unattended installation.

To perform an unattended installation with an answer file:

1. Copy the sample answer file (UnattendedTemplate.txt in the Support\Install directory on the installation media) to another location.

2. The file includes definitions and possible values for each entry. Using a text editor, enter values for entries you want to set, then save the file.

3. At a command prompt, type the following, where path-to-mps.msi is the full path to your XenApp installation, and answer_file.txt is the name of the text file you created and edited in the previous steps.

UnattendedInstall.exe <path-to-mps.msi> <answer_file.txt> [MSIPROPERTY1=”VALUE1”] ... [MSIPROPERTYN=“VALUEN”]

Note: Passwords are not stored in the answer file; they must be provided on the command line when you invoke UnattendedInstall.exe. The sample file contains password command-line options.

The following example command includes the ODBC password.c:\XenApp\UnattendedInstall.exe "c:\Setup\MPS.msi"c:\cps\x32ORCL10-1.txt CTX_ODBC_PASSWORD="password"CTX_MF_ADD_LOCAL_ADMIN=YesThe following example command includes the indirect join password.c:\XenApp\UnattendedInstall.exe "c:\Setup\MPS.msi"c:\cps\x32Access-2All.txtCTX_INDIRECT_JOIN_PASSWORD="password"CTX_MF_ADD_LOCAL_ADMIN=Yes

For property descriptions, see XenApp Windows Installer Properties Reference .

XenApp Windows Installer Properties Reference

Updated: 2009-10-16

For custom XenApp installations, XenApp Setup properties are used with Windows Installer (msiexec) commands and transforms.

Some values, such as passwords, may be case-sensitive.

When performing an unattended install (UnattendedInstall.exe), use Setup properties in the command line to specify user credentials; these are not included in the XenApp answer file. You can also use the command line to specify other Setup properties, such as installation directories.

When using Setup properties in a command line as part of an unattended installation, enclose values that include spaces in quotation marks (""). If you use quotation marks when running Setup properties in the command line, set them explicitly by prefacing them with the escape character (\). For example,

use INSTALLDIR=\"C:\Program Files\Citrix\" instead ofINSTALLDIR="C:\Program Files\Citrix".

Setup properties for XenApp features, technologies, and plug-ins are described, when available, in their documentation.

See the licensing documentation for Windows Installer commands for Citrix Licensing.

The management consoles have their own .msi files; they are not specified using Windows Setup properties as part of XenApp installation. For more information, see Custom Installations of the XenApp Management Consoles.

XenApp Setup Properties for Create Farm and Join Farm The following table indicates the properties used for the Create Farm and Join Farm installations. For an Unattended Installation, values are provided with a different syntax from Windows Installer

commands; equivalent parameters are provided in the table. Unless otherwise noted, the property is supported on XenApp 5 for Windows Server 2003 and XenApp 5 for

Windows Server 2008 installations. The property descriptions indicate valid and default values.

Property Create Farm

Join Farm

Unattended Installation Equivalent

CTX_ADDLOCAL X X  

CTX_CONFIGMGR_USER X X  

CTX_CONFIGMGR_USER_PASSWORD X X  

CTX_CPSVC_SERVICE_USER_NAME X X  

CTX_CPSVC_SERVICE_USER_PASSWORD X X  

CTX_IGNORE_MCM * X X  

CTX_IMA_PROTECTION_ENABLE X X ** EncryptionEnable

CTX_MALOO_SERVICE_USER X X  

CTX_MALOO_SERVICE_USER_PASSWORD X X  

CTX_MF_ADD_ANON_USERS X X  

CTX_MF_ADD_LOCAL_ADMIN X    

CTX_MF_CREATE_FARM_DB_CHOICE X X DirectConnect

CTX_MF_CREATE_REMOTE_DESKTOP_USERS X X  

CTX_MF_DOMAIN_NAME X   FarmAdministratorDomain

CTX_MF_ENABLE_VIRTUAL_SCRIPTS X X EnableVirtualScripts

CTX_MF_FARM_SELECTION X X CreateFarm

CTX_MF_INDIRECT_JOIN_DOMAIN_NAME   X DomainName

CTX_MF_INDIRECT_JOIN_PASSWORD   X  

CTX_MF_INDIRECT_JOIN_USER_NAME   X UserName

CTX_MF_JOIN_FARM_DB_CHOICE   X DirectConnect

CTX_MF_JOIN_FARM_SERVER_NAME   X IndirectServerName

CTX_MF_JOIN_FARM_SERVER_PORT   X IndirectServerPort

CTX_MF_LIC_CHOICE_FOR_CREATE X   LicenseServerChoice

CTX_MF_LIC_CHOICE_FOR_JOIN_OR_UPGRADE   X LicenseServerChoice

CTX_MF_LICENSE_SERVER_NAME X X LicenseServerName

Property Create Farm

Join Farm

Unattended Installation Equivalent

CTX_MF_LICENSE_SERVER_PORT X X LicenseServerPort

CTX_MF_LICENSE_SERVER_PORT_DEFAULT X X LicenseServerPortDefault

CTX_MF_LOCAL_DATABASE X X LocalDBType

CTX_MF_MSDE_INSTANCE_NAME X X InstanceName

CTX_MF_NEW_FARM_NAME X   FarmName

CTX_MF_ODBC_DRIVER X X  

CTX_MF_ODBC_PASSWORD X X  

CTX_MF_ODBC_USER_NAME X X UserName

CTX_MF_ONLY_LAUNCH_PUBLISHED_APPS X X  

CTX_MF_SERVER_TYPE X   ServerType

CTX_MF_SHADOW_PROHIBIT_NO_LOGGING X   ProhibitLoggingOff

CTX_MF_SHADOW_PROHIBIT_NO_NOTIFICATION X   ProhibitNotificationOff

CTX_MF_SHADOW_PROHIBIT_REMOTE_ICA X   ProhibitRemoteControl

CTX_MF_SHADOWING_CHOICE X   AllowShadowing

CTX_MF_SILENT_DSNFILE   X DSNFilePath

CTX_MF_USER_NAME X   FarmAdministratorUsername

CTX_MF_XML_CHOICE X   ExtendIIS

CTX_MF_XML_PORT_NUMBER X   DedicatedPortNumber

CTX_MF_ZONE_NAME X X ZoneName

CTX_PROTECT_KEY_PATH   X KeyPath

CTX_PROTECT_KEY_TYPE X X KeyType

CTX_PROTECT_NEW_KEY_PATH X   NewKeyPath

CTX_RDP_DISABLE_PROMPT_FOR_PASSWORD X   DisableRDPPromptForPassword

CTX_REMOVE_WI_TURNKEY * X X  

CTX_SERV_MALOO_LOGON * X X  

CTX_SERV_PRINTER_LOGON * X X  

CTX_USE_EXISTING_JRE * X X  

INSTALLDIR X X  

REBOOT X X  

REINSTALLMODE X X  

* This property is valid only on XenApp for Windows Server 2003 installations.

** This property is valid when creating a farm with a XenApp 5 for Windows Server 2003 installation. It is valid when creating or joining a farm with a XenApp 5 for Windows Server 2008 installation.

CTX_ADDLOCAL

Updated: 2009-08-31

Specifies one or more XenApp features to install. The features must be installed locally. Separate multiple values with commas. (This property is similar to the Windows Installer ADDLOCAL property.)

For XenApp 5 for Windows Server 2008 installations, this property does not provide values for installing the Access Management Console or XenApp Advanced Configuration. For XenApp 5 for Windows Server 2003 installations, this property does not provide a value for installing XenApp Advanced Configuration.

Valid values See tables below for valid values in XenApp 5 for Windows Server 2008 and XenApp 5 for Windows Server 2003 installations.

Default value Blank

Installation type Create Farm, Join Farm

The following table lists valid values for XenApp for Windows Server 2008 installations.

  Description

Blank (default)

All Installs all XenApp features and components

CTX_MF_MetaFrame_Core Installs only the XenApp core server software

CTX_MF_LM Installs the Load Manager

WMI Installs the XenApp Provider

CTX_MF_IMA_Core Installs the Citrix Independent Management Architecture service

CTX_MF_CTXCPU Installs the Citrix CPU Utilization Management feature

CTX_MF_CTXSFO Installs the Memory Optimization Management feature

CSS_SS Installs support for application streamingCaution: Do not specify CSS_SS value if you have an Advanced Edition license. Specifying this property can cause issues after Setup when applying hotfixes.

The following table lists valid values for XenApp for Windows Server 2003 installations.Important:

For readability, the table contains spaces between multiple values. When entering multiple values, do not use spaces.

@Core is a placeholder and should not actually be used in the command.

Value(s) Description

Blank (default)

All Installs all XenApp features and components

MetaFrame_XP, CTX_MF_MetaFrame_Core, CTX_MF_IMA_Core, CTX_MF_ICA_Shell_Editor, CTX_SMA, CTX_MF_CTXCPU, CTX_MF_CTXSFO

Installs only the core server software, required for any configuration (referred to below as @Core)

PN, PN_ENGINE Installs the full Program Neighborhood client as the passthrough client (referred to below as PN)

PN_AGENT, PN_ENGINE Installs the Program Neighborhood Agent as the passthrough client

CTX_MF_CMC, CTX_MF_IM_Plugin, CTX_MF_RM_Plugin

Installs the Advanced Configuration (referred to below as @CMC)

CTX_MF_IM_Service Installs the Installation Manager installer service

Value(s) Description

CTX_MF_IM_Packager Installs the Installation Manager packager

CTX_MF_IM, CTX_MF_IM_Service, CTX_MF_IM_Packager

Installs all Installation Manager components (referred to below as @IM)

CTX_MF_RM Installs the Resource Manager

@Core, CTX_MF_LM, WMI, @CMC, PN, @IM, CTX_MF_RM, CTX_MF_ASCII

Installs all default Enterprise Edition components

@Core, CTX_MF_LM, @CMC, PN Installs all default Advanced Edition components

CTX_CONFIGMGR_USER

Defines the account for Configuration Manager for the Web Interface Service. If this property is not specified, the service is installed with the default local user account (Ctx_ConfigMgr). You can change this to run under a different account by using this property with CTX_CONFIGMGR_USER_PASSWORD.

To specify a domain account for a service, log on to the server on which you are running Setup as a domain administrator of the domain on which you want to run the server.

To specify another account to use for Setup, specify the following privileges when you create the account: Log on as a service(SeServiceLogonRight) and Log on as a batch job (LogonAsBatch). Without these privileges, the Configuration Manager for the Web Interface Service service will not start.

Format Domain\Username

Valid values User defined

Default value Ctx_ConfigMgr

Installation type

Create Farm, Join Farm

CTX_CONFIGMGR_USER_PASSWORD

Specifies the password for the Configuration Manager for the Web Interface Service. Use with CTX_CONFIGMGR_USER.

Valid values User defined

Installation type

Create Farm, Join Farm

CTX_CPSVC_SERVICE_USER_NAME

Specifies a different user account for the Citrix Print Manager Service. If this property is not specified, the service is installed under the account ctx_cpsvcuser. To change the account, specify this property with a value representing the account you already created, and specify the password with CTX_CPSVC_SERVICE_USER_PASSWORD.

To specify a domain account for a service, log on to the server on which you are running Setup as a domain administrator of the domain on which you want to run the server.

To specify another account to use for Setup, specify the following privileges when you create the account: Log on as a service(SeServiceLogonRight) and Log on as a batch job (LogonAsBatch). Without these privileges, the Citrix Print Manager Service will not start.

Note: The Citrix Print Manager Service now uses the ctx_cpsvcuser account instead of the Ctx_SmaUser account, which the service used in Presentation Server 4.0.

Format Domain\Username

Valid values User defined

Default value ctx_cpsvcuser

Installation type

Create Farm, Join Farm

CTX_CPSVC_SERVICE_USER_PASSWORDSpecifies the password for the Citrix Print Manager Service.

Specifying this property without specifying CTX_CPSVC_SERVICE_USER_NAME installs the service under the default account (ctx_cpsvcuser) and changes the password.

Specifying this property with CTX_CPSVC_SERVICE_USER_NAME changes the user name and password for this account.

Valid values User defined

Installation type

Create Farm, Join Farm

CTX_IGNORE_MCMNote: This property is valid only on XenApp 5 for Windows Server 2003 installations.

This XenApp release is not compatible with Conferencing Manager 2.0. If you upgrade to this XenApp version before upgrading Conferencing Manager, Conferencing Manager fails on this server. Therefore, upgrade Conferencing Manager before upgrading to this version of XenApp. The latest version of Conferencing Manager is available on the installation media.

If the installer detects Conferencing Manager 2.0 on the server, an error message appears. When you set this property value to Yes, the installer ignores the error message and continues the installation.

Valid values Yes

No

Default value No

Installation type

Create Farm, Join Farm

CTX_IMA_PROTECTION_ENABLE

Enables or disables IMA encryption.

Valid values 1 - enables IMA encryption; use with CTX_PROTECT_KEY_TYPE

0 - disables IMA encryption

Default value 0

Installation type XenApp 5 for Windows Server 2003: Create Farm

XenApp 5 for Windows Server 2003: Create Farm, Join Farm

CTX_MALOO_SERVICE_USER

Specifies a different user account for the CPU Utilization Mgmt/CPU Rebalancer service. If this property is not specified, the service is installed under the ctx_cpuuser account. To change the account, specify this property with a value representing the account you already created, and specify the password with CTX_MALOO_SERVICE_USER_PASSWORD.

This service is only installed on servers with multiple processors.

To specify a domain account for a service, log on to the server on which you are running Setup as a domain administrator of the domain on which you want to run the server.

To specify another account to use for Setup, specify the following privileges when you create the account: Log on as a service(SeServiceLogonRight), Log on as a batch job (LogonAsBatch), Debug programs (SeDebugPrivilege), and Increase scheduling priority(SeIncrementBasePriorityPrivilege). Without these privileges, the CPU Utilization Mgmt/CPU Rebalancer service will not start.

Format Domain\Username

Valid values User defined

Default value ctx_cpuuser

Installation type

Create Farm, Join Farm

CTX_MALOO_SERVICE_USER_PASSWORDSpecifies the password for the Citrix CPU Utilization Mgmt/CPU Rebalancer service.

Specifying this property without specifying CTX_MALOO_SERVICE_USER installs the service using the default value for the CTX_MALOO_SERVICE_USER property (ctx_cpuuser) as the user name, and changes the password.

Specifying this property with CTX_MALOO_SERVICE_USER changes the user name and password for this account.

Valid values User defined

Installation type

Create Farm, Join Farm

CTX_MF_ADD_ANON_USERS

Specifies whether or not anonymous users can connect remotely.

Valid values Yes

o If CTX_MF_CREATE_REMOTE_DESKTOP_USERS is set to “CopyUsers” or “DoNothing,” anonymous users are added to the Remote Desktop Users group in Windows Server

o If CTX_MF_CREATE_REMOTE_DESKTOP_USERS is set to “AddEveryone,” this property is ignored because the Remote Desktop Users group is configured so that every user in the Users group is also a remote desktop user

No - prohibits anonymous connections to XenApp

Default value Yes

Installation type Create Farm, Join Farm

CTX_MF_ADD_LOCAL_ADMIN

Enables or disables the creation of Citrix administrator accounts for all user accounts in the local Administrators group.

Valid values Yes

No

Default value No

Installation type

Create Farm

CTX_MF_CREATE_FARM_DB_CHOICE

Specifies whether the database is a local database stored on the first server in the farm or an enterprise (third-party) database stored on a separate server.

Valid values Local — Microsoft Access or Microsoft SQL Server Express. (Use with CTX_MF_LOCAL_DATABASEand, if using Microsoft SQL Server Express, CTX_MF_MSDE_INSTANCE_NAME.)

Third Party — Microsoft SQL Server, Oracle, or IBM DB2. (Use with CTX_MF_ODBC_USER_NAMEand CTX_MF_ODBC_PASSWORD.)

Default value Local

Installation type Create Farm, Join Farm

CTX_MF_CREATE_REMOTE_DESKTOP_USERS

Determines whether or not to add users to the Windows Remote Desktop Users group if the accounts are already created on the system. Users must be members of the Remote Desktop Users group to log on remotely to a Windows Server system.

Setting this property has no effect if the Remote Desktop Users group already has members.

Note: This property takes precedence over CTX_MF_ADD_ANON_USERS. If this property is set to “AddEveryone” and CTX_MF_ADD_ANON_USERS is set to “No,” anonymous connections to XenApp are enabled on this server.

Valid values AddEveryone — Adds the Authenticated Users group to the Remote Desktop Users group. All current members of the Users group are allowed to log on remotely to the server, and whenever you add a user to the Users group, XenApp automatically adds the user to Remote Desktop Users group.

CopyUsers — Copies all current users from the Users group to the Remote Desktop Users group. After Setup, any user accounts you add must be added manually to the Remote Desktop Users group.

DoNothing — Does not add any users to the Remote Desktop Users group. No users will be allowed to log on remotely to the server until you add users to the Remote Desktop Users group in Windows Server.

Default value CopyUsers

Installation type Create Farm, Join Farm

CTX_MF_DOMAIN_NAME

Specifies the domain name for the first Citrix administrator account you create in the farm.

Valid values User defined

Default value DomainName

Installation type

Create Farm

CTX_MF_ENABLE_VIRTUAL_SCRIPTS

Updated: 2009-09-25

Enables or disables port sharing with IIS during Setup. This property directs XenApp Setup to create the virtual scripts directory, which is required for IIS.

If you are running a silent installation and this property is not set to “Yes” or “1” and the XML port on the server is shared with IIS (for example, if you are installing the Web Interface on the same server as XenApp), Setup fails and the following error message is added to the installation log file:

“ERROR: SetIISScriptsDir - Could not get the scripts path because the Virtual Scripts directory in not enabled in IIS or the property CTX_MF_ENABLE_VIRTUAL_SCRIPTS is not set to Yes.”

If the property is defined, the silent installation continues with no error.

Valid values Yes or 1 — Creates the virtual scripts directory if it does not already exist. Setup does not prompt you to create the virtual scripts directory, even if you are running Setup in wizard-based mode.

Not defined, 0, or No — Does not create the virtual scripts directory if it does not already exist. You are prompted during Setup to create the virtual scripts directory.

Default value Not defined

Installation type Create Farm, Join Farm

CTX_MF_FARM_SELECTION

Specifies whether you are creating a new server farm or joining an existing farm. If this server is joining an existing farm, you must also set CTX_MF_JOIN_FARM_DB_CHOICE.

Valid values Create

Join

Default value Create

Installation type

Create Farm, Join Farm

CTX_MF_INDIRECT_JOIN_DOMAIN_NAME

Specifies the domain name of a user account that has full administrative rights in XenApp. Use this property if you are joining a farm that uses a Microsoft Access or Microsoft SQL Server Express database stored locally on the first server in the farm (indirect connection).

Valid values Any domain in which the user account has full administrative rights on the XenApp farm

Default value DomainName

Installation type Join Farm

CTX_MF_INDIRECT_JOIN_PASSWORD

Specifies the password for a user account that has full administrative rights in XenApp. Use this property if you are joining a farm that uses a Microsoft Access or Microsoft SQL Server Express database stored locally on the first server in the farm (indirect access).

Valid values Password for the user name specified in CTX_MF_INDIRECT_JOIN_USER_NAME

Default value “” (null)

Installation type Join Farm

CTX_MF_INDIRECT_JOIN_USER_NAME

Specifies the user name for an account that has full administrative rights in XenApp. Use this property if you are joining a farm that uses a Microsoft Access or Microsoft SQL Server Express database stored locally on the first server in the farm (indirect connection).

Valid values Any user account that has full administrative rights on the XenApp farm (ideally, the same account used to create the farm)

Default value Administrator

Installation type Join Farm

CTX_MF_JOIN_FARM_DB_CHOICE

Specifies whether the existing farm connects directly or indirectly to the data store.

Valid values Direct — Set this value if you are using a Microsoft SQL, Oracle, or IBM DB2 database stored on a separate, dedicated database server.

Indirect — Set this value if you are using a Microsoft Access or Microsoft SQL Server Express database stored locally on the first server in the farm on which you installed XenApp.

Default value Direct

Installation type Join Farm

TX_MF_JOIN_FARM_SERVER_NAME

Specifies the name of the first server in the farm that you want to join.

Valid values The name of a server hosting the Microsoft Access or Microsoft SQL Server Express database as the data store

Default value ServerName

Installation type Join Farm

CTX_MF_JOIN_FARM_SERVER_PORT

Specifies the IMA communication port number used to communicate with the farm data store. This property applies if you are using a Microsoft Access or Microsoft SQL Server Express database stored locally on the first server in the farm on which you installed XenApp.

Valid values User defined

Default value 2512

Installation type

Join Farm

CTX_MF_LIC_CHOICE_FOR_CREATE

Configures the server to point to an existing Citrix License Server when creating a farm. If set to “Point,” ensure thatCTX_MF_LICENSE_SERVER_NAME points to a valid license server. If you plan to install the license server after installing XenApp, set CTX_MF_LIC_CHOICE_FOR_CREATE to “DontKnow.”

Note: You can also configure the server to point to the license server after running Setup.

Valid values Point

DontKnow

Default value Point

Installation type

Create Farm

CTX_MF_LIC_CHOICE_FOR_JOIN_OR_UPGRADEConfigures XenApp to point to an existing Citrix License Server.

If set to “Point”, ensure that CTX_MF_LICENSE_SERVER_NAME points to a valid license server.

If set to “UseFarmSettings,” ensure that the existing server farm is configured to use a license server.

 Set this property to "DontKnow" if you plan to install the license server after installing XenApp.

Note: You can also configure XenApp to point to the license server after running Setup.

Valid values Point

UseFarmSettings

DontKnow

Default value UseFarmSettings

Installation type

Join Farm

CTX_MF_LICENSE_SERVER_NAMESpecifies the license server the XenApp server uses. This applies only:

When performing a new installation when joining an existing server farm and CTX_MF_LIC_CHOICE_FOR_JOIN_OR_UPGRADE is set to “Point”

When performing a new installation while creating a new server farm and CTX_MF_LIC_CHOICE_FOR_CREATE is set to “Point”

Valid values User defined

Default value localhost

Installation type

Create Farm, Join Farm

CTX_MF_LICENSE_SERVER_PORT

Specifies a different port number (other than the default 27000) to use when communicating with the Citrix License Server. The value must match the port number configured on the license server. Use with CTX_MF_LICENSE_SEVER_PORT_DEFAULT set to “” (null).

Valid values An integer representing the port number through which the license server listens for requests

Default value 27000

Installation type Create Farm, Join Farm

CTX_MF_LICENSE_SERVER_PORT_DEFAULT

Controls whether XenApp communicates with the license server through the license server default port (27000).

Valid values 1 — XenApp uses the default port number, 27000

“” (null) — XenApp uses the value of CTX_MF_LICENSE_SERVER_PORT as the port number when communicating with the Citrix License Server

Default value 1

Installation type Create Farm, Join Farm

CTX_MF_LOCAL_DATABASE

Specifies the type of local database for the farm data store.

Valid values Access

SQL (for Microsoft SQL Server Express)

Default value Access

Installation type

Create Farm, Join Farm

CTX_MF_MSDE_INSTANCE_NAME

If you install the Microsoft SQL Server Express database using the batch file SetupSqlExpressForCPS.cmd, the default instance name is CITRIX_METAFRAME. However, if you defined a different instance name, use this property to specify that name. That is, use this property if you modified the instance name in the batch file or did not install Microsoft SQL Server Express using the batch file.

Valid values User defined

Default value CITRIX_METAFRAME

Installation type

Create Farm, Join Farm

CTX_MF_NEW_FARM_NAME

Specifies the name of the new farm. (If you are joining a farm, use CTX_MF_JOIN_FARM_SERVER_NAME.)

Valid values User defined

Default value NewFarmName

Installation type

Create Farm

CTX_MF_ODBC_DRIVER

Specifies the ODBC driver name for the database hosting the farm data store. Use when joining a farm directly.

Valid values The ODBC driver name such as “SQL Server”, “Oracle in OraClient11g_home1”, or “IBM DB2 ODBC DRIVER - DB2COPY1”

Default value “” (null)

Installation type Create Farm, Join Farm

CTX_MF_ODBC_PASSWORD

Specifies the password for a directly connected database that stores the farm data store. Use with MF_ODBC_USER_NAME.

Valid values User defined

Default value Password

Installation type

Create Farm, Join Farm

CTX_MF_ODBC_USER_NAME

Specifies the user name for a directly connected database that stores the farm data store. Use with CTX_MF_ODBC_PASSWORD.

Valid values User defined

Default value UserName

Installation type

Create Farm, Join Farm

CTX_MF_ONLY_LAUNCH_PUBLISHED_APPS

By default, XenApp prohibits non-administrative users from connecting to the published desktops and the desktop of the servers hosting XenApp. When this property is set to either “Yes” or “” (null), users can only connect to published applications. This setting is a server setting and not farm wide. To allow users to connect to some server desktops but not all, change this property value for those servers.

Valid values Yes — users cannot connect to published desktops or server desktops with

clients

No — users can connect to published desktops or server desktops with clients

“” (null) — users cannot connect to published desktops or server desktops with clients

Note: If set to a value other than Yes or No:

For XenApp 5 for Windows Server 2008 installations, this security enhancement is enabled

For XenApp 5 for WIndows Server 2003 installations, this security enhancement is enabled for clean installs, but disabled for upgrades

Default value “” (null)

Installation type Create Farm, Join Farm

CTX_MF_SERVER_TYPE

Updated: 2009-09-22

Specifies the edition of XenApp to be installed.

Valid values P — Platinum Edition

E — Enterprise Edition

A — Advanced Edition

Default value XenApp 5 Feature Pack 2 for Windows Server 2003 and XenApp 5 for Windows Server 2008: none

Important: Because there is no edition type set as the default, Setup fails if you do not set this property or leave it as “” (null)

XenApp 5 for Windows Server 2003: P

Installation type Create Farm

CTX_MF_SHADOW_PROHIBIT_NO_LOGGING

Prohibits or allows shadow connections without logging.

Valid values Yes — prohibit

No — allow

Default value No

Installation type

Create Farm

CTX_MF_SHADOW_PROHIBIT_NO_NOTIFICATION

Prohibits or allows shadowing connections without user notification.

Valid values Yes — prohibit

No — allow

Default value No

Installation type

Create Farm

CTX_MF_SHADOW_PROHIBIT_REMOTE_ICA

Prohibits or allows remote control of mouse and keyboard in shadowed sessions.

Valid values Yes — prohibit

No — allow

Default value No

Installation type

Create Farm

TX_MF_SHADOWING_CHOICE

Enables or disables session shadowing.

Important: If you turn session shadowing off when you install XenApp, you cannot enable it later through user policies or connection configuration.

Valid values Yes — turn it on

No — turn it off

Default value Yes

Installation type

Create Farm

CTX_MF_SILENT_DSNFILE

Specifies the path to the Data Source Name (DSN) file used to connect to the data store when the database is Oracle, SQL, or DB2. During a wizard-based installation, Setup creates the DSN file for you. For a custom installation, you must create the DSN file and use this property to specify its location.

Valid values Complete path to the DSN file

Default value “” (null)

Installation type

Join Farm

CTX_MF_USER_NAME

Specifies the user name for the first Citrix administrator account you create in the farm.

Valid values User defined

Default value “UserName”

Installation type

Create Farm

CTX_MF_XML_CHOICE

Specifies whether Microsoft Internet Information Services (IIS) and the Citrix XML Service share the same port on this server or use separate ports. If you do not want IIS and the Citrix XML Service to share the same port, set the Citrix XML Service port number usingCTX_MF_XML_PORT_NUMBER.

Valid values Share — share with IIS

Separate — use separate port, set in CTX_MF_XML_PORT_NUMBER

Default value Share

Installation type Create Farm

CTX_MF_XML_PORT_NUMBER

Port number the Citrix XML Service will use (when you do not want the Citrix XML Service and IIS to share ports).

Valid values User defined

Default value 80

Installation type

Create Farm

TX_MF_ZONE_NAME

Specifies the name of the zone to which the server belongs. For a Create Farm Setup, this property specifies the name of the first zone in the farm. For a Join Farm Setup, this property specifies the name of the zone where you want to add the server.

Valid values Not applicable

Default value XenApp 5 for Windows Server 2008: Default Zone

XenApp for Windows Server 2003: None; the default value is generated programmatically, based on the server subnet address

Installation type Create Farm, Join Farm

CTX_PROTECT_KEY_PATH

Specifies where a valid encryption key file is stored. Use this property with CTX_PROTECT_KEY_TYPE with a value of “file.” Failure to set both key properties correctly causes XenApp Setup to not activate the encryption settings for the current server.

Valid values The full path where an encryption key file is stored

Default value “” (null)

Installation type

Join Farm

TX_PROTECT_KEY_TYPE

Specifies how the IMA encryption key is provided.

Valid values file — Provides a path to the location where the key file resides. Use withCTX_PROTECT_KEY_PATH.

generate — Provides a writable location where the key file is stored after Setup generates a new encryption key. Use with CTX_PROTECT_NEW_KEY_PATH.

 existing — Indicates a key is already loaded on the computer; Setup will not attempt to replace the existing key with a new key from the file.

Default value file

Installation type Create Farm, Join Farm

CTX_PROTECT_NEW_KEY_PATH

Specifies the location of the writable folder where you want the IMA encryption key file created. If the folder is not writable, Setup fails. Use this property with CTX_PROTECT_KEY_TYPE containing a value of “generate.” Failure to set both properties correctly causes XenApp Setup not to activate the encryption settings for the current server.

Valid values The full path where an encryption key file will be created

Default value “” (null)

Installation type

Create Farm

CTX_RDP_DISABLE_PROMPT_FOR_PASSWORD

Setting this property to “Yes” changes the security setting on the server so that passwords from users of Microsoft Remote Desktop Web Connection software are not required. Users must still enter credentials when logging on to the Web Interface, but can launch applications without further prompts for credentials by the server.

Valid values Yes

No

Default value No

Installation type

Create Farm

CTX_REMOVE_WI_TURNKEYNote: This property is valid only on XenApp 5 for Windows Server 2003 installations.

When upgrading from earlier versions of Presentation Server that include the Web Interface, you must upgrade the Web Interface before upgrading Presentation Server; otherwise, the Web Interface may be removed from the server. Set this property to Yes if you do not object to the removal of the Web Interface from the server.

Valid values Yes

No

Default value No

Installation type

Create Farm, Join Farm

CTX_SERV_MALOO_LOGONNote: This property is valid only on XenApp 5 for Windows Server 2003 installations.

Defines the Citrix CPU Utilization Mgmt/CPU Rebalancer Service as the CPU user rather than using the build in accounts created by XenApp.

Format USERID:PASSWORD:DOMAIN/MACHINENAME

Default value ctx_cpuuser

Installation type

Create Farm, Join Farm

CTX_SERV_PRINTER_LOGONNote: This property is valid only on XenApp 5 for Windows Server 2003 installations.

Defines the Citrix Print Manager Service as the printer user rather than the built in accounts created by XenApp.

Format USERID:PASSWORD:DOMAIN/MACHINENAME

Default value ctx_cpsvcuser

Installation type

Create Farm, Join Farm

CTX_USE_EXISTING_JRENote: This property is valid only on XenApp 5 for Windows Server 2003 installations.

Instructs the installer to accept the JRE version currently installed on the computer.

Valid values Yes

No

Default value No

Installation type

Create Farm, Join Farm

INSTALLDIR

Target location for the installation.

Valid values User defined

Default value %Program Files%\Citrix

Installation type

Create Farm, Join Farm

REBOOT

Specifies whether you restart a server manually or are prompted for the server to be restarted.

Note: XenApp requires that you reboot the server after running Setup.

Valid values Force — forces restart to occur; no further prompts are displayed

Suppress — forces restart to not occur by default; a prompt appears if action is necessary

ReallySuppress — forces restart to not occur; no prompts appear

Default value Force

Installation type Create Farm, Join Farm

REINSTALLMODESpecifies the type of reinstall to perform. Options are case-insensitive and order-independent.Important: Citrix recommends that you do not modify this property.

Valid values p — install missing files

o — replace older versioned or missing files

c — replace corrupt files (checksum validation)

e — replace same versioned or missing files

d — replace files of differing versions

a — replace all files regardless of version

u — replace user registry settings

m — replace registry settings on the server

s — replace shortcuts

v — replace the cached .msi package with the package currently being installed

Default value oums

Installation type Create Farm, Join Farm

In XenApp for Windows Server 2008 installations, this property performs the same function as the Repair function in Control Panel > Programs and Features.

XenApp Windows Setup Properties Script Examples

Create Farm Sample Windows Installer Command Script

This sample script creates a farm using a local database (Microsoft Access) with port sharing, IMA encryption, and shadowing enabled.

msiexec.exe /i MPS.msi /qb- /l*v C:\mps.log CTX_MF_SERVER_TYPE="P"

INSTALLDIR="C:\XenApp\" CTX_MF_FARM_SELECTION="Create"CTX_MF_CREATE_FARM_DB_CHOICE="Local" CTX_LOCAL_DATABASE="Access"CTX_MF_NEW_FARM_NAME="NewFarmName" CTX_MF_XML_CHOICE="Share"CTX_MF_USER_NAME="Administrator" CTX_MF_DOMAIN_NAME="DomainName"CTX_MF_LIC_CHOICE_FOR_CREATE="Point"CTX_MF_LICENSE_SERVER_NAME="LicenseServerName"CTX_MF_LICENSE_SERVER_PORT_DEFAULT="1"CTX_MF_LICENSE_SERVER_PORT="27000" CTX_IMA_PROTECTION_ENABLE="1"CTX_PROTECT_KEY_TYPE="generate"CTX_PROTECT_NEW_KEY_PATH="C:\KeyFile.key"CTX_MF_SHADOWING_CHOICE="Yes"CTX_MF_SHADOW_PROHIBIT_NO_NOTIFICATION="No"CTX_MF_SHADOW_PROHIBIT_REMOTE_ICA="No"CTX_MF_CREATE_REMOTE_DESKTOP_USERS="AddEveryone"CTX_MF_ADD_ANON_USERS="Yes" CTX_MF_ENABLE_VIRTUAL_SCRIPTS="Yes"CTX_MF_ADD_LOCAL_ADMIN="Yes" CTX_MF_ONLY_LAUNCH_PUBLISHED_APPS="No"

Join Farm Sample Windows Installer Command Script

This sample script joins a farm whose data store is hosted on a third-party, or enterprise, database (SQL Server). The farm has IMA encryption and shadowing enabled.

msiexec /i MPS.msi /qb- /l*v C:\mps.log CTX_MF_SERVER_TYPE="E"INSTALLDIR="C:\XenApp\" CTX_MF_FARM_SELECTION="Join"CTX_MF_CREATE_FARM_DB_CHOICE="Thirdparty"CTX_MF_JOIN_FARM_DB_CHOICE="Direct"CTX_MF_ODBC_USER_NAME="DomainName\UserName"CTX_ODBC_PASSWORD="****" CTX_MF_ODBC_RE_ENTERED_PASSWORD="****"CTX_MF_SILENT_DSNFILE="C:\SQLWin.dsn"CTX_MF_SELECTED_DRIVER_NAME="SQL Server"CTX_MF_XML_CHOICE="Separate" CTX_MF_XML_PORT_NUMBER="8080"CTX_MF_LIC_CHOICE_FOR_JOIN_OR_UPGRADE="UseFarmSettings"CTX_IMA_PROTECTION_ENABLE="1" CTX_PROTECT_KEY_TYPE="file"CTX_PROTECT_KEY_PATH="C:\KeyFile.key" CTX_MF_SHADOWING_CHOICE="Yes"CTX_MF_SHADOW_PROHIBIT_NO_NOTIFICATION="No"CTX_MF_SHADOW_PROHIBIT_NO_LOGGING="No"CTX_MF_SHADOW_PROHIBIT_REMOTE_ICA="No"CTX_MF_CREATE_REMOTE_DESKTOP_USERS="CopyUsers"

Citrix Licensing Sample Windows Installer Command Script

This sample script installs Citrix Licensing.

msiexec.exe /i ctx_licensing.msiCTX_LICENSING_INSTALLDIR="C:\program files\citrix\"CTX_LIC_FILE_PATH="C:\program files\citrix\licensing\my files\"CTX_WEB_SERVER="IIS" CTX_LICENSE_SERVER_PORT="23456"CTX_VENDOR_DAEMON_PORT="65432" /l*v "C:\Lic.log" /qb-

Web Interface Sample Windows Installer Command Script

This sample script installs the Web Interface.

WebInterface.exe -q -v %systemdrive%\WI.log