Set up resource locations

Setting up a resource location begins with the following tasks:

  • Set up your host environment (hypervisor or cloud service).
  • Set up your Active Directory domain.

About resource locations

If you’re not familiar with resource locations, review this information.

What’s in a resource location Resource locations contain the resources required to deliver applications and desktops to users. You manage those items from Citrix Cloud and the Studio console. Typically, resources include:

  • Active Directory domain controller
  • Hypervisors or cloud services, known as hosts
  • Virtual Delivery Agents (VDAs)
  • Citrix Gateway (optional): To enable secure external access to the applications and desktops offered to users, add a Citrix Gateway VPX appliance to the resource location and set up Citrix Gateway (formerly NetScaler Gateway). For a proof-of-concept deployment that requires only internal access, you can use the cloud-hosted StoreFront that comes with Citrix Cloud.
  • Citrix StoreFront servers (optional)

To communicate with Citrix Cloud, every resource location must contain a Citrix Cloud Connector. At least two Cloud Connectors per resource location is recommended, for availability.

A resource location is considered a zone in a Citrix Virtual Apps and Desktops service environment.

Where to place resource locations A resource location can be anywhere you need it: in a public cloud, private cloud, or an on-premises datacenter. You can set up multiple resource locations to meet your company’s specific needs. Planning where to place a resource location can depend on:

  • Proximity to users
  • Proximity to data
  • Scale requirements
  • Security attributes

For example, a resource location in your head office’s data center might serve users that must be close to the data. Another resource location in a public cloud might serve global users. Or, resource locations in branch offices might provide applications that are best served near the branch workers. Finally, restricted applications might be placed in a separate resource location, restricting visibility to other resources and users without having to adjust other resource locations.

Host requirements

The hypervisor or cloud service where you provision VMs that deliver apps or desktops to users might have unique permission or setup requirements.

  • If the hypervisor or cloud service requires virtual networks or other items, follow the guidance in its documentation.
  • Create the appropriate virtual private cloud (VPC) or virtual networks for the machines you’ll add to your resource location, if needed. For example, when using AWS, set up a VPC with public and private subnets.
  • Create the appropriate rules to secure inbound and outbound internet traffic, as well as traffic between machines in the virtual network. For example, when using AWS, ensure the VPC’s security group has the appropriate rules configured so that machines in the VPC are accessible only to the IP addresses you specify

Review the article for the host type you’re using.

Active Directory

Provision a Windows server, install Active Directory Domain Services, and promote it to a domain controller. For guidance, see the Microsoft Active Directory documentation.

  • You must have at least one domain controller running Active Directory Domain Services.
  • Do not install any Citrix components on a domain controller.
  • Do not use a forward slash (/) when specifying Organizational Unit names in Studio.

For technical details, see:

Add a resource location in Citrix Cloud

To add a resource location:

  1. Sign in to Citrix Cloud.
  2. In the upper left menu, select Resource Locations.
  3. If you have not already installed a Citrix Cloud Connector, you are prompted to download one. Follow the guidance in Install Cloud Connectors.
  4. After you’ve installed a Cloud Connector (preferably at least two), back in the Citrix Cloud console, enter a name for the resource location and then click Save.

Where to go next

Install Cloud Connectors

To review the entire configuration process, see Install and configure.