Skip to content

Multi-Region Cloud Access Manager Deployment

Teradici Cloud Access Manager enables you to deploy remote workstations, with pre-created Cloud Access Connectors and a pre-defined Virtual Network, in multiple Azure regions. This allows users to be closer to their remote workstations which reduces latency and provides a better connection and user experience.

The image below outlines the relationship between subnets, vnets and resource groups across a multi-region deployment:

Alt Text

Deploying a Cloud Access Connector in a New Region

The following steps outline the procedure for deploying a Cloud Access Connector in a new Azure region. For more information on the Cloud Access Connector, see Cloud Access Connector. Prior to deploying a Cloud Access Connector you need to create a new Virtual Network in a new Resource Group in the desired region. Create three subnets for this Virtual Network as desired. Teradici recommends the following subnets:

  • GatewaySubnet for the Application Gateway.
  • ConnectorSubnet for the Cloud Access Connector.
  • RemoteWorkstationSubnet for the Remote Workstations.

Application Gateway Subnet

The GatewaySubnet can only contain application gateways.

Once you have created a Virtual Network in the desired region, you can deploy a Cloud Access Connector:

  1. The DC/DNS needs to be reachable from the new Virtual Network via vnet peering or VPN. Peer or VPN the new Virtual Network to the original Virtual Network.
  2. Peer or VPN the original Virtual Network to the new Virtual Network. You must carry this out in both directions.
  3. Set the DNS for the Virtual Network to be the DC/DNS's IP address. Once the networks are connected you can setup DNS.
  4. Deploy a new Cloud Access Connector using the Azure cloud shell script, see Deploying Cloud Access Manager with Azure Cloud Shell.
  5. When you are prompted to select a Cloud Access Manager deployment to modify or upgrade, select the deployment that is connected to the DC/DNS.
  6. Enter Yes when prompted to enable external access to the connector.
  7. Enter Yes when prompted to deploy in a new region.
  8. Select the new Virtual Network as the VNet for the deployment.
  9. Select a Subnet for the Cloud Access Connector [ConnectorSubnet].
  10. Select a Subnet for the Application Gateway [GatewaySubnet].
  11. Continue and complete the deployment.

Deploying a Remote Workstation in a New Region

The following steps outline the procedure for deploying a remote workstation in a new Azure region, based on the Cloud Access Connector you created and deployed above:

  1. Log into the Cloud Access Manager management interface. With Cloud Access Manager it is possible to manage all remote workstaions from any management interface in any region. For more information on the Cloud Access Manager management interface, see Signing into the Cloud Access Manager Management Interface.
  2. Navigate to the Workstation Configuration tab and select the template for the remote workstation you are going to deploy.
  3. Save this template as a new template.
  4. In the same ARM Template Parameter File, set the value of the "subnetID" parameter as the subnet where you wish to deploy the remote workstation. This subnet must exist in the new region where the new Virtual Network was created. The "subnetID" parameter will be in the form of:

"/subscriptions/<subscription>/resourceGroups/<vnet-resource-group>/providers/Microsoft.Network/virtualNetworks/<new-region-vnet>/subnets/<remote-workstation-subnet>"

  • <subscription> is your subscription ID.
  • <vnet-resource-group> is the resource group name where the new region's Virtual Network is placed.
  • <new-region-vnet> is the name of the new region's Virtual Network.
  • <remote-workstation-subnet> is the name of the subnet where remote workstations are deployed.

Alt Text 5. In the new template's ARM Template Parameter File, set the value of the "location" parameter. The "location" parameter has to be set to the region the new vnet has been provisioned to in step 4:

Alt Text 6. Save the ARM Template Parameter File.

-RW Resource Group

All remote workstations will still be deployed into the *-RW resource group. For more information on the resource groups created with Cloud Access Manager, see Azure Resource Groups.