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.
Decide which type of Site you will create:
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.
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.
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:
If you use VMware, see that product's documentation and Manage virtual machines with VMware.
If you are using Hyper-V, see that product's documentation and Manage virtual machines with 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 about IntelliCache, see Use IntelliCache.
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. For more information, see Personal vDisks.
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. For more information, see Microsoft Application Virtualization.
Good to know:
|Database type||What to enter||With this database configuration|
|Standalone or mirror||servername||The default instance is used and SQL Server uses the default port.|
|servername\INSTANCENAME||A named instance is used and SQL Server uses the default port.|
|servername,port-number||The default instance is used and SQL Server uses a custom port. (The comma is required.)|
|Other||cluster-name||A clustered database.|
|availability-group-listener||An AlwaysOn database.|
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.