Product Documentation

Preparing to Install and Configure XenApp

Oct 09, 2015

Review the XenApp Readme for late-breaking issues.

You must be in the local Administrators group to install and configure the XenApp software. (Elevating your privilege to local administrator through User Account Control is not a substitute for Administrators group membership.)

Important: Do not install XenApp on a domain controller. Citrix does not support installing XenApp on a domain controller.

To ensure availability of the features and functionality of XenApp for Windows Server 2008 R2 to your users, install the most recent version of any plug-ins you use.

When installing roles or role components other than XenApp server, see the role documentation for details about information requested during installation and configuration.

Important: Do not join servers running XenApp 6 for Windows Server 2008 R2 to a deployment with servers running previous versions of XenApp.
Note: To prepare XenApp for server imaging and provisioning, you can use the XenApp Server Configuration Tool included on the XenApp 6 for Windows Server 2008 R2 installation media. However, the preparation process is streamlined and more effective if you use the updated XenApp Server Configuration Tool, which you can install on the server with CTX124981. If you install the updated XenApp Server Configuration Tool after you install XenApp, you must use the same user account that was used to install XenApp.

Before Installing XenApp

  • Review the installation process (wizard-based or command-line) to learn what information you must provide.
  • Review the system requirements for the XenApp server and for other roles you plan to install.
    • Wizard-based installations include automatic installation of prerequisite software and required Windows roles.
    • For command-line installations, you must install the prerequisite software and Windows roles before initiating XenApp installation. You can deploy prerequisites with PowerShell cmdlets, the Microsoft ServerManagerCmd.exe command, or the Microsoft Deployment Image Servicing and Management (DISM) tool.
  • Ensure the Microsoft Windows Server has the latest Microsoft hotfixes and that the operating system clock has the correct time.
  • Prepare for Windows Multilingual User Interface (MUI) support, if needed.
  • Important: By default, the XenApp server installation process creates install logs in the user's temporary directory (%TEMP%). On Windows Server 2008 R2 servers, the session's temporary directory is deleted by default when the server restarts. If you encounter problems during installation or want to preserve those log files, use one of the following options:
    • Copy the logs from the %TEMP% location to a safe place before the server restarts.
    • Before installing the XenApp server role, change your local computer policy to prevent deletion of the temporary directories.
      1. Go to Start > Run, then type gpedit.msc.
      2. Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders.
      3. Verify that Do not delete temp folder upon exit is set.
      4. Restart the server.
    • For a command-line installation, use the /logfile:path option to specify an installation log file in a different directory.

Before Configuring XenApp

  • Review the configuration process (wizard-based or command-line) to learn what information you must provide.
  • During configuration, you specify the database to be used for the XenApp farm data store: Microsoft SQL Server Express, Microsoft SQL Server, or Oracle. See CTX114501 for supported versions.
    • If you use a Microsoft SQL Server Express database, XenApp configuration installs it automatically.
    • If you use a Microsoft SQL Server or Oracle database, install and configure the database before initiating XenApp configuration. (For an Oracle database, this includes installing an Oracle client on the XenApp server and restarting the server.)
  • If you use a Microsoft SQL Server or Oracle database for the farm data store, and use command-line XenApp configuration, create a Data Source Name (DSN) file before configuring XenApp. (A wizard-based configuration creates the DSN file for you.) Each server in the farm must have the DSN file. You can create the file and copy it to other servers, or put it on a network share, provided you remove the value for any workstation-specific information (such as the Oracle WSID). Use the /DsnFile:dsn_file option to specify the file location on the XenApp configuration command line.
  • If you plan to use the Configuration Logging feature and encrypt the data being logged, you must load the encryption key on servers that join the farm after configuring XenApp but before restarting the server.