Professional Documents
Culture Documents
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.
Before you build a XenApp farm, read about XenApp deployment planning, and complete the preparation tasks.
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.
The information that follows is based on using the wizard-based installation. Generally, the sequence and
explanations also apply to custom installations.
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.
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.)
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 Installs the tool that manages printing, policies, load manager, and
Configuration or Presentation Server Console 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 Installs the agent for Resource Manager powered by EdgeSight.
by default)
If you select Citrix Licensing, see the Citrix Licensing documentation. For Web Interface and EdgeSight installation
information, see their respective documentation.
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.
Click Disk Cost to display the amount of disk space required by the selected components.
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.
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.
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.
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 The XML Service and IIS use the same port for communications.
Services(default) 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.
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,
This topic provides information about the tasks in Join Farm Setup that differ from Create Farm Setup.
On the Create or Join a Server Farm page, select Join an existing farm. The Join a Server Farm page appears.
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.
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.
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 Strategy
There 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.
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.
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.
Changes to Setup
These 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.
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.
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.
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.
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.
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.
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.
See the Custom XenApp Installation topics for more information about using Windows Installer packages and
unattended installations.
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.
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.
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.
After imaging your servers, join these servers to your farm by using the CHFARM command.
To clone a server
This 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.
o 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.
o Delete the value for HKLM\SOFTWARE\Wow6432Node\Citrix\IMA\ServerHost. This key is in
HKLM\SOFTWARE\Citrix\IMA\ServerHost on XenApp, 32-bit edition.
b. Delete the contents of database local persistent cache files.
o Delete the contents of the Local Host Cache in C:\Program Files (x86)\Citrix\Independent
Management Architecture\imalhc.mdb by running dsmaint recreaterade.
o 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.
o 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.
c. 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.
d. 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.
e. Create an image of this installation using Citrix Provisioning services, Citrix XenServer, or third-party
imaging software.
f. Deploy this image to other servers using the tools provided by the imaging software.
g. To begin initializing the cloned image, restart the server where the image was deployed.
h. Using a system preparation utility or the imaging software, assigned the cloned image a new computer
name.
i. 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.
j. 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.)
o Using a text editor, open the CtxSta.config file in C:\Program Files (x86)\Citrix\System32.
o 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.)
o Enter the STA ID in the UID field in the CtxSta.config file. (For example, UID=STA020068554D01.)
k. In the Windows Services panel:
o Set the Startup type for Citrix Independent Management Architecture and the Citrix MFCOM
service to Automatic.
o Start the Citrix Independent Management Architecture service.
o Start the Citrix MFCOM service.
o 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.
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 Setup
When 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 Installation
After 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.
Key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
Type REG_SZ
Name Logging
Value data voicewarmup
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.”
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.log
The following table lists several common options for the msiexec command.
Option Syntax
Install or configure a product msiexec /i {package|ProductCode}
Option Syntax
Uninstall a product msiexec /x {package|ProductCode}
Set a logging level (use with Install or msiexec /L [i][w][e][a][r][u][c][m][p][v][+][!] LogFile
Uninstall option)
To include the v option in a log file using the wildcard flag, type /L*v.
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.
Sample Transforms
Sample 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_Serv License_Serv License_Server License_Serv
er er er
CTX_MF_LOCAL_DATABASE SQLEXPRESS
CTX_MF_MSDE_INSTANCE_NAME CITRIX_METAFRA
ME
CTX_MF_NEW_FARM_NAME Farm- FarmAccess
ThirdParty
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_LOGGIN No No No Yes
G
CTX_MF_SHADOW_PROHIBIT_NO_NOTIFIC Yes Yes No No
ATION
CTX_MF_SHADOW_PROHIBIT_REMOTE_IC No No No No
A
CTX_MF_SHADOWING_CHOICE Yes Yes Yes
Property A B C D
CTX_MF_SILENT_DSNFILE (see note 1) (see note 1)
CTX_MF_USER_NAME Administrator Administrator
CTX_MF_XML_CHOICE Separate Separate Share Share
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
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.
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.
** 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 streaming
Caution: 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, Installs only the core server software, required for any
CTX_MF_IMA_Core, CTX_MF_ICA_Shell_Editor, configuration (referred to below as @Core)
CTX_SMA, CTX_MF_CTXCPU, CTX_MF_CTXSFO
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
Value(s) Description
CTX_MF_CMC, CTX_MF_IM_Plugin, Installs the Advanced Configuration (referred to below as
CTX_MF_RM_Plugin @CMC)
CTX_MF_IM_Service Installs the Installation Manager installer service
CTX_MF_IM_Packager Installs the Installation Manager packager
CTX_MF_IM, CTX_MF_IM_Service, Installs all Installation Manager components (referred to
CTX_MF_IM_Packager below as @IM)
CTX_MF_RM Installs the Resource Manager
@Core, CTX_MF_LM, WMI, @CMC, PN, @IM, Installs all default Enterprise Edition components
CTX_MF_RM, CTX_MF_ASCII
@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 Create Farm, Join Farm
type
CTX_CONFIGMGR_USER_PASSWORD
Specifies the password for the Configuration Manager for the Web Interface Service. Use with
CTX_CONFIGMGR_USER.
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 Create Farm, Join Farm
type
CTX_CPSVC_SERVICE_USER_PASSWORD
Specifies 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 Create Farm, Join Farm
type
CTX_IGNORE_MCM
Note: 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.
Default value No
Installation Create Farm, Join Farm
type
CTX_IMA_PROTECTION_ENABLE
Enables or 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.
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 Create Farm, Join Farm
type
CTX_MALOO_SERVICE_USER_PASSWORD
Specifies 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 Create Farm, Join Farm
type
CTX_MF_ADD_ANON_USERS
Specifies whether or not anonymous users can connect remotely.
Default value No
Installation Create Farm
type
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.)
Setting this property has no effect if the Remote Desktop Users group already has members.
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.
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.”
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.
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 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.
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.
Note: You can also configure the server to point to the license server after running Setup.
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).
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 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.
Updated: 2009-09-22
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
Default value No
Installation Create Farm
type
CTX_MF_SHADOW_PROHIBIT_NO_NOTIFICATION
Prohibits or allows shadowing connections without user notification.
Default value No
Installation Create Farm
type
CTX_MF_SHADOW_PROHIBIT_REMOTE_ICA
Prohibits or allows remote control of mouse and keyboard in shadowed sessions.
Default value No
Installation Create Farm
type
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
Valid values The full path where an encryption key file is stored
Default value “” (null)
Installation Join Farm
type
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.
Valid values The full path where an encryption key file will be
created
Default value “” (null)
Installation Create Farm
type
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.
Default value No
Installation Create Farm
type
CTX_REMOVE_WI_TURNKEY
Note: 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.
Default value No
Installation Create Farm, Join Farm
type
CTX_SERV_MALOO_LOGON
Note: 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 Create Farm, Join Farm
type
CTX_SERV_PRINTER_LOGON
Note: 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 Create Farm, Join Farm
type
CTX_USE_EXISTING_JRE
Note: 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 Create Farm, Join Farm
type
INSTALLDIR
Target location for the installation.
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
In XenApp for Windows Server 2008 installations, this property performs the same function as the Repair function
in Control Panel > Programs and Features.