Product Documentation

Install using the graphical interface

Jun 04, 2013
Use the graphical interface to:
  • Install one or more core components: Delivery Controller, Citrix Studio, Citrix Director, License Server, and StoreFront.
  • Install additional core components to extend your deployment. For example, installing Studio on a separate system allows you to manage a deployment remotely.
  • Install a Virtual Delivery Agent (VDA) on a master image or on a virtual or physical machine. For Remote PC Access deployments, Citrix recommends using your existing Electronic Software Distribution (ESD) methods by leveraging the VDA installer's command line interface.
  • Customize a VDA by updating Controller addresses, port numbers, and Windows Firewall port exceptions.
  • Install a Universal Print Server, which provisions network session printers. (The Controller already has the Universal Print Server functionality; you need only install the Universal Print Server on the print servers in your environment.)

To launch the installer graphical interface

  1. Download the product package and unzip it. Optionally, burn a DVD of the ISO file.
  2. Log on to the server where you are installing the components, using a local administrator account.
  3. Insert the DVD in the drive or mount the ISO file. If the installer does not launch automatically, double-click the AutoSelect application.

To install core components using the graphical interface

Use this procedure to install a Delivery Controller, and optionally, other core components.
  1. Launch the installer.
  2. After clicking Start, select Delivery Controller.
  3. Accept the license agreement.
  4. On the Core Components page:
    • By default, components are installed in C:\Program Files\Citrix. Click Change to specify a different location.
    • By default, all components are selected. Clear the checkboxes of the components you do not want to install on this server.
  5. On the Features page:
    • (Appears only when you are installing a Controller.) The Microsoft SQL Server 2012 Express feature is enabled by default, and that database software will be installed. If you plan to use a supported SQL Server version on another server, clear the checkbox. If you are not installing the Controller, you might be asked to specify the address of an existing Controller that the components you are installing can communicate with. If SQL Server is already installed on this server, this option does not appear.
    • (Appears only when you are installing Director.) The Windows Remote Assistance feature is always installed when you install Director; you enable or disable the feature on this page. Windows Remote Assistance lets administrators and support personnel help with common IT issues.
  6. The Firewall page lists the ports used by each component being installed. You can print this list. By default, these ports are opened automatically if the Windows Firewall Service is running, even if the firewall is not enabled. If you use a third-party firewall or no firewall, or you prefer to open the ports manually after installation, select Manually.
    Component Port number
    Controller TCP 80, 443
    Director TCP 80, 443
    License Server TCP 7279, 8082, 8083, 27000
    StoreFront TCP 80, 443

    For complete port information, see CTX101810.

  7. The Summary page lists the information you provided on previous pages, plus the prerequisites that will be installed automatically. After you verify the information and click Install, the display indicates installation progress. If a component does not install successfully, the process stops and an error message appears. Components that installed successfully are retained; you do not need to reinstall them.

    If you installed Studio, it starts automatically by default after the installation completes. You can disable this option. (If you install core components on a non-domain-joined server, you cannot create a Site, so the option to start Studio is not available.)

To install additional components using the graphical interface

  1. Launch the installer.
  2. After clicking Start, select the component you want to install from the entries in the Extend Deployment column. Follow the wizard.

If you install an additional Controller, you must add it to the Site; see To add a Controller.

To install a VDA using the graphical interface

Note: Follow these instructions when installing a Virtual Delivery Agent on Windows 7, Windows 8, Windows Server 2008 R2, or Windows Server 2012 operating systems. For information about installing an earlier Virtual Desktop Agent on Windows XP or Windows Vista systems, see Install an earlier Virtual Desktop Agent on Windows XP or Windows Vista.
On the host or machine where you are installing the VDA:
  1. Launch the installer.
  2. After clicking Start, click the VDA entry. The installer automatically detects your operating system and offers only the VDA type supported on that system: Virtual Delivery Agent for Windows Server OS or Virtual Delivery Agent for Windows Desktop OS.
  3. On the Environment page, choose whether you want to build a master image that will be used to create other machines (default) or you want users to connect to an existing machine.
  4. When installing a VDA for Windows Desktop OS, choose whether to install the VDA for HDX 3D Pro. The HDX 3D Pro feature delivers desktops and applications that perform best with a GPU for hardware acceleration. By default, this option is disabled. For more information, see the HDX 3D Pro documentation.
  5. On the Core Components page:
    • By default, components are installed in C:\Program Files\Citrix. Click Change to specify a different location.
    • By default, Citrix Receiver for Windows (CitrixReceiver.exe) is installed. To disable that installation, clear the checkbox.
  6. On the Delivery Controller page, choose one of the following methods for specifying the location of installed Controllers:
    • Manually, by typing the Fully Qualified Domain Name (FQDN) of a Controller, then clicking Add. Although you can specify a Controller that is not currently in the domain, a VDA can connect only to a Controller in the domain. Also, you can test the connection only for Controllers in the domain.
    • Using Active Directory, if the Controllers are in the domain.
    • Allow Machine Creation Services to specify the Controllers.
    • Later, by rerunning the installer, using Citrix policies, setting registry values, or by using Active Directory OUs.

    Citrix Group Policy settings that specify Controller locations override settings provided during installation.

    After you initially specify the Controller location, you can use the auto-update feature to update VDAs when additional Controllers are installed. See Manage your Delivery Controller environment.

  7. On the Features page, select the features you want to enable:
    Feature Description
    Optimize performance Enables or disables optimization for VDAs running in a VM on a hypervisor. VM optimization includes disabling offline files, disabling background defragmentation, and reducing event log size. For more information about the optimization tool, see CTX125874. For Remote PC Access, do not enable this option. Default = enabled.
    Use Windows Remote Assistance Enables or disables Windows Remote Assistance for use with Director. When this feature is enabled, Windows automatically opens TCP port 3389 in the firewall (even if you choose to open firewall ports manually on the next wizard page). Default = enabled.
    Use Real-Time Audio Transport for audio Enables or disables use of UDP for audio packets. Enabling this feature can improve audio performance. Default = enabled.
    Personal vDisk (Appears only when you are installing a VDA for Windows Desktop OS on a VM.) Enables or disables the use of Personal vDisks with a master image. For more information, see Manage Personal vDisks. Default = disabled.
  8. The Firewall page lists the ports used to communicate with the Controller and the features you enabled on the previous page. You can print this list. By default, these ports are opened automatically if the Windows Firewall Service is running, even if the firewall is not enabled. If you use a third-party firewall or no firewall, or you prefer to open the ports manually after installation, select Manually.
    Component or feature Port number
    Controller
    • For communication between user devices and virtual desktops, configure inbound TCP on ports 1494 and 2598 as port exceptions. For security, Citrix recommends that you do not use these registered ports for anything other than the ICA protocol and the Common Gateway Protocol.
    • For communication between Controllers and virtual desktops, configure inbound port 80 as a port exception.

    TCP 80, 1494, 2598, 8008

    Windows Remote Assistance

    TCP 3389. Windows opens this port automatically if the feature is enabled on the previous page, even if you choose Manually on this page.

    Real-Time Audio Transport

    UDP 16500-16509

    For complete port information, see CTX101810.

  9. The Summary page lists your selections, plus the prerequisites that will be installed automatically. You are also advised if a restart will be needed; you are prompted for confirmation before the installer initiates the restart. After you verify the information and click Install, the display indicates installation progress.

    If a component does not install successfully, the process stops and an error message appears. Components that installed successfully are retained; you do not need to reinstall them.

  10. After a successful installation, the machine restarts automatically when you click Finish. Although you can prevent this automatic restart by clearing the checkbox, the VDA will not be fully available for use until after a restart.

To customize a VDA using the graphical interface

  1. From the Windows feature for removing or changing programs, select Citrix Virtual Delivery Agent 7.0, then right-click and select Change.
  2. Select Customize Virtual Delivery Agent Settings. The graphical installer launches.
  3. Use the wizard to change:
    • Controller addresses.
    • TCP/IP port used to register with the Controller (default = 80).
    • Whether to automatically configure the Windows Firewall port exceptions.
  4. The Summary page lists the choices you made, and advises if a restart is required.

To install the Universal Print Server using the graphical interface

  1. Launch the installer.
  2. After clicking Start, select Universal Print Server, and then follow the wizard.

The installer adds the Windows Print Server role service.