Create a Site

May 11, 2018

A Site is the name you give to a product deployment. It comprises the Delivery Controllers and the other core components, VDAs, virtual resource connections (if used), plus the machine catalogs and Delivery Groups you create and manage. A Site does not necessarily correspond to a geographical location, although it can. You create the Site after you install the components and before creating machine catalogs and Delivery Groups.

Prepare

Decide which type of Site you will create:

  • Application and desktop delivery Site - When you choose to create an application and desktop delivery Site, you can further choose to create a full deployment Site (recommended) or a empty Site. (Empty Sites are only partially configured, and are usually created by advanced users.)
  • Remote PC Access Site - Allows designated users to remotely access their office PCs through a secure connection. If you will use the Remote PC Access Wake on LAN feature, complete the tasks described in Configuration Manager and Remote PC Access Wake on LAN.

If you create an application and desktop delivery deployment now, you can add a Remote PC Access deployment later. Conversely, if you create a Remote PC Access deployment now, you can add a full deployment later.

Database: Site creation includes creating the Site Configuration database. Make sure the SQL Server software is installed before you create a Site.

To create the database, you must be a local administrator and a domain user. You must also either have SQL Server permissions, or you can generate scripts to give to your database administrator to run. See the Database permissions table below for details. If your Studio user credentials do not include these permissions, you are prompted for SQL Server user credentials.

Scripts: If your database server is locked down and you do not have the required SQL Server permissions, the Site creation wizard can generate two database scripts: one that sets up the database and the other to use in a mirroring environment. After you request script generation, you give the generated scripts to your database administrator (or someone with required SQL Server permissions) to run on the database server, and the mirrored database, if needed. After the script is executed and the database is successfully created, you can finish creating the Site.

Licenses: Consider if you will use the 30-day free trial license that allows you to add license files later, or if you will use existing licenses. You can add or download license files from within the Site creation wizard.

Configure your virtualization resource (host) environment.

If you use XenServer:

  • See the XenServer documentation.
  • You must provide the credentials for a VM Power Admin or higher-level user.
  • Citrix recommends using HTTPS to secure communications with XenServer. To use HTTPS, you must replace the default SSL certificate that was installed on XenServer with a certificate from a trusted authority; see CTX128656.
  • You can configure high availability if it is enabled on the XenServer.  Citrix recommends that you select all servers in the pool to allow communication with XenServer if the pool master fails.  It can be selected from “Edit High Availablity” of added host.
  • You can also select a GPU type and group, or passthrough, if the XenServer supports vGPU. The display indicates if the selection has dedicated GPU resources.

If you use VMware, see that product’s documentation and Prepare the virtualization environment: VMware.

If you are using Hyper-V, see that product’s documentation and Prepare the virtualization environment: Microsoft System Center Virtual Machine Manager.

Decide if you will use Machine Creation Services (MCS) or other tools to create VMs on the virtualization resources.

Decide if you will use shared or local storage. Shared storage is available through the network. If you use shared storage, you can enable the use of IntelliCache to reduce load on the storage device. For information, see Use IntelliCache for XenServer connections.

Decide if you will use Personal vDisks and whether they will use shared or local storage. Personal vDisks can use the same or different storage as the VMs. (LTSR: Not supported)

If you installed product components in a cloud environment, you will need the API key and secret key values when configuring the first connection. You can export the key file containing those values from AWS or CloudPlatform, and then import them into the Site creation wizard.

When you create a Site for a cloud deployment, you will also need the region, availability zone, VPC name, subnet addresses, domain name, security group names, and credentials you configured in AWS.

Decide if you will use App-V publishing, and configure those resources, if needed.

Good to know:

  • When you create a Remote PC Access Site:
    • A machine catalog named Remote PC Access Machines, and a Delivery Group named Remote PC Access Desktops are automatically created.
    • You must specify users or user groups; there is no default action that automatically adds all users.
    • You can enable the Wake on LAN feature (power management) and specify the Microsoft System Center Configuration Manager (ConfigMgr) address and credentials, plus a connection name.
  • The user who creates a Site becomes a Full Administrator; for more information, see Delegated Administration.
  • When an empty database is created, it has default attributes except:
    • The collation sequence is set to 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. (When a database is created manually, any collation sequence can be used, provided it is case-sensitive, accent-sensitive, and kanatype-sensitive; the collation sequence name typically ends with _CI_AS_KS.)
    • The recovery mode is set to Simple. For use as a mirrored database, change the recovery mode to Full.
  • When you create the Site Configuration Database, it also stores configuration changes recorded by the Configuration Logging Service, plus trend and performance data that is used by the Monitoring Service and displayed by Citrix Director. If you use those features and store more than seven days of data, Citrix recommends that you specify different locations for the Configuration Logging Database and the Monitoring Database (known as the secondary databases) after you create a Site.
  • When naming the Monitoring Database, or a Site Configuration Database that includes the Monitoring Database, using a name that includes spaces causes errors when the database is accessed. For more information, see to CTX200325.

At the end of the Site creation wizard, you are asked if you want to participate in the Citrix Customer Experience Improvement Program. When you join this program, anonymous statistics and usage information is sent to Citrix; see About the Citrix Customer Experience Improvement Program for more information.

Database permissions

Operation

Purpose

Server role

Database role

Create a database

Create a suitable empty database

dbcreator

Create a schema

Create all service-specific schemas and add the first Controller to the Site

securityadmin*

db_owner

Add a Controller

Add a Controller (other than the first) to the Site

securityadmin*

db_owner

Add a Controller (mirror server)

Add a Controller login to the database server currently in the mirror role of a mirrored database

securityadmin*

Update a schema

Apply schema updates or hotfixes

db_owner

Create

Start Studio, if it is not already open. After you choose to create a Site from the center pane, specify the following:

  • The type of Site and the Site name.
  • Database information. If you chose during Controller installation to have the default SQL Server Express database installed, some information is already provided. If you use a database server that is installed on a different server, enter the database address, using one of the following forms:
    • ServerName
    • ServerName\InstanceName
    • ServerName,PortNumber

After you click Next and are alerted that the services could not connect to a database, indicate that you want Studio to create it. If you do not have permission to edit the database, use Generate database script. The scripts must be run before you can finish creating the Site.

  • License Server address in the form name:[port], where name is a Fully Qualified Domain Name (FQDN), NetBIOS, or IP address; FQDN is the recommended format. If you omit the port number, the default is 27000. You cannot proceed until a successful connection is made to the license server.
  • (Remote PC Access Sites only.) Power management information, including ConfigMgr connection information.
  • Connection information to your virtualization resource and storage information. If you are not using a resource, or if you will use Studio to manage user desktops hosted on dedicated blade PCs, select the connection type None.
  • App-V management and App-V publishing server information.
  • (Remote PC Access Sites only.) User and machine accounts information.
    • User information. Click Add Users. Select users and user groups, and then click Add users.
    • Machine accounts information. Click Add machine accounts. Select machine accounts, and then click Add machine accounts. Click Add OUs. Select the domain and Organizational Units, and indicate if items in subfolders should be included. Click Add OUs.

Test a Site configuration

You can view an HTML report of the site test results. To run the tests:

  1. From Studio, click the Studio (<site-name>) entry at the top of the left pane.
  2. In the center pane, click Test site.

Create a Site