Product Documentation

Plan

Mar 17, 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

These are the 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 three databases:
    • Site database
    • Configuration logging database
    • Monitoring database

    Because the configuration logging and monitoring databases' characteristics are different than the site database, Citrix recommends that you change the location of those two databases after site creation completes.

    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 XenDesktop 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 for XenDesktop. Do not install either 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.