You run the pod deployment wizard to deploy the components that together make up a pod and its gateway configurations. The pod's connector component pairs with Horizon Cloud so that you can use your Microsoft Azure capacity with Horizon Cloud.

The deployer uses the information you provide in each step of the wizard to determine how to configure the pod. After you provide the requested information in a particular step, proceed to the next step by clicking Next.
Caution: The IP addresses mentioned in these steps are examples. You should use the address ranges that meet your organization's needs. For each step that mentions an IP address range, substitute ones that are applicable for your organization.

Prerequisites

Before you start the pod deployment wizard, verify that you have the required items. The items you need to provide in the wizard vary according to the pod configuration options you want. For the prerequisites, see Prerequisites for Running the Pod Deployment Wizard.

Pod configuration options include:

  • Selecting existing subnets that you create in advance or having the pod deployer automatically create the subnets
  • Selecting whether to enable high availability for the pod. If you deploy the pod without high availability enabled, you can later edit the pod to enable it.
  • Having the deployment process create a VMware Workspace ONE® Access™ tenant.
  • Deploying with an external or internal Unified Access Gateway configuration, or deploying with both. If you deploy with only one type of gateway configuration, you can later edit the pod to add the other, non-configured type.
    If you deploy with the Unified Access Gateway configuration as... You can later edit the pod to add...
    External Internal
    Internal External
    None One or the other or both at the same time
  • Deploying with an external Unified Access Gateway configuration in its own VNet, separate from the pod's VNet.
  • Deploying with an external Unified Access Gateway configuration in its own subscription, separate from the pod's subscription. Because VNets do not span subscriptions, this option is a special scenario of the separate VNet case — when the external gateway is deployed using its own subscription, it also means it is in its own VNet.
  • Which SKU to use for the Microsoft Azure Load Balancer for the external and internal gateway configurations. The choices are the Standard Azure Load Balancer SKU or the Basic Azure Load Balancer SKU. For a comparison of the two SKUs, see the Microsoft Azure documentation topic Load Balancer SKU comparison.
  • Deploying with the option for RADIUS two-factor authentication configured on the pod's gateway configurations. If you deploy without RADIUS settings configured on the pod's gateway configurations, you can later edit the pod to add the other, non-configured type.
  • For an external Unified Access Gateway configuration, you can optionally select to not have a public IP address on the configuration's load balancer. If you select the wizard option to not have a public IP address on the load balancer, you must specify in the wizard an IP value that you have mapped to an FQDN in your DNS server. That FQDN is the one that will be used in your end users' Horizon clients for PCoIP connections to this gateway. In the deployment process, the deployer will configure that IP address in the Unified Access Gateway's Horizon configuration settings. In the Unified Access Gateway documentation, this IP value is referred to as the PCoIP External URL. Even though the Unified Access Gateway documentation refers to it as a URL, the entered value must be an IP address. You map this IP address to an FQDN in your DNS, which is the FQDN used in your end users' Horizon clients to establish their PCoIP sessions with the pod's external Unified Access Gateway configuration.
    Caution: You cannot later edit the deployed pod to change this IP address setting for the external gateway's load balancer. Therefore, ensure that you input the public IP address in the deployment wizard that matches your DNS mapping with the FQDN, and the FQDN matches the one in the certificate that you upload in the deployment wizard.