If you use multiple client access URLs for different network ranges, you must edit the network ranges so the end user connects to the correct client access URL and port number. If these settings are not updated, the Horizon Client will not launch.


  1. Log in to the VMware Identity Manager console.
  2. Review your network ranges and create new ones, if required.
    1. Click the Identity & Access Management > Policies tab.
    2. Click Network Ranges.
    3. Review the network ranges and click Add Network Range to add new ranges, if required.
  3. Click the Catalog > Virtual Apps tab, then click Virtual Apps Settings.
  4. Select Network Settings.
  5. Select the network range to configure.
    The View CPA federation section appears only if you integrated pod federations. This section lists the global launch URLs you specified for the pod federations. The View Pod section lists all the View pods that have the Sync Local Entitlements option selected.
  6. In the View CPA federation section, for the global launch URL, specify the fully-qualified domain name of the server to which to direct launch requests for global entitlements that come from this network range. This is typically the global load balancer URL of the View pod federation deployment.

    For example: lb.example.com

    The global launch URL is used to launch globally-entitled resources.

  7. In the View Pod section, for each pod, specify the fully-qualified domain name of the server to which to direct launch requests for local entitlements that come from this network range. You can specify a Horizon Connection Server instance, a load balancer, or a security server. For example, if you are editing a range that provides internal access, you would specify the internal load balancer for the pod.

    For example: lb.example.com

    The client access URL is used to launch locally-entitled resources from the pod.

    Note: For information about the Wrap Artifact in JWT and Audience in JWT options, see Launching Horizon Resources Through Validating Gateways.
  8. Verify that each network range in your environment contains a client access URL.
    Important: If you miss a network range, end users who launch through that network range might have problems.