Product Documentation


May 03, 2015

This release allows you to grow your deployment at a rate that best suits your organization. You can start with a simple default configuration, which you release to additional user groups at a later time. It is important to think about your deployment in terms of user needs and focus your pilot on the users who will see the most immediate benefit.

If you are not ready to transition your users to virtual desktops, you can start with a Remote PC Access deployment that enables them to access their office PCs and take advantage of Citrix HDX features, and then add traditional virtual desktops and application deployments later.

Essential elements

The Delivery Controller, Studio, Director, License Server, and StoreFront can be installed on the same server or on different servers. For example, to manage your deployment remotely, you can install Studio on a different system than the server where you installed the Controller.
  • Controller
  • Studio
  • Director
  • License Server — For further information on licensing, see: Licensing.
  • Storefront
  • The database — By default, during site creation, Studio creates a database on the server where you install the Controller; this database contains:
    • Site database
    • Configuration logging database
    • Monitoring database

    Citrix recommends that you change the location of the configuration logging and monitoring databases after you create the site.

    Important: You can choose to use a database on a separate server. If you intend using an external database created manually, not created using Studio, ensure your database administrator uses the following collation setting when creating the database: Latin1_General_100_CI_AS_KS (where Latin1_General varies depending on the country; for example Japanese_100_CI_AS_KS). If this collation setting is not specified during database creation, subsequent creation of the service schemas within the database will fail, and an error similar to "<service>: schema requires a case-insensitive database" appears (where <service> is the name of the service whose schema is being created).
  • A domain controller running Active Directory. Active Directory is required. Do not install XenApp, XenDesktop, or the SQL Server database on a domain controller.

    Consider the potential implications of the domain name you select. Avoid domain names that may be used elsewhere. For example, the string 'client' is also used to access client drive mapping.

  • VMs or physical computers hosting the desktops you want to deliver to your users. You install the Virtual Desktop Agent on these machines to manage communications and broker connections.
  • User devices running the appropriate client to enable your users to access desktops.

Example deployments

Two examples of typical deployments are:
  • Distributed components configuration
  • Multiple site configuration

Distributed components configuration

You can distribute the components of your deployment among a greater number of servers, or provide greater scalability and failover by increasing the number of controllers in your site. You can install the management consoles on separate computers to enable you to manage your deployment remotely. A distributed deployment is necessary for an infrastructure based on remote access through NetScaler Gateway (formerly called Access Gateway).

Figure 1. A distributed components configuration

For more information about Citrix NetScaler Gateway for secure remote access, see the product-specific documentation.

Multiple site configuration

If you have multiple regional sites, for example one in Europe and one in the US, you can use Citrix NetScaler to direct user connections to the most appropriate site and StoreFront to deliver desktops and applications to users.

In the following example, a site was created in two data centers. Having two sites globally, rather than just one, minimizes the amount of unnecessary WAN traffic. You can use StoreFront to aggregate resources from multiple sites to provide users with a single point of access with NetScaler. Citrix NetScaler accelerates application performance, load balances servers, increases security, and optimizes the user experience. In this example, two NetScalers are used to provide a high availability configuration. The NetScalers are configured for Global Server Load Balancing and positioned in the DMZ to provide a multi-site, fault-tolerant solution. For more information on highly available multi-site configurations with StoreFront, see Set up highly available multi-site store configurations.

A separate Studio console is required to manage each site; sites cannot be managed as a single entity. You can use Director to support users across sites.

Figure 2. A configuration consisting of multiple regional sites and data centers