A Horizon Cloud Pod is configured using the Horizon Administration console for each Pod that will be a member. In this section, we will create a Cloud Pod consisting of two Horizon pods.
All Connection Servers within a Cloud Pod must have unique names, even if they are in different domains. Additionally, do not reboot or restart any services on Connection Servers while creating a Cloud Pod.
The following procedure outlines how to create a Cloud Pod:
- Log on to the Horizon Administration console of the intended first member of the Cloud Pod using an AD account that has administrative permissions within Horizon.
- Open the View Configuration | Cloud Pod Architecture window within the console.
- Click on the Initialize the Cloud Pod Architecture feature link to open the Initialize window, as shown in the following screenshot. Click OK to proceed, and monitor the status window that will be displayed:
- When the Cloud Pod feature has finished configuring, click OK in the Reload window to reload the console and refresh the View Configuration | Cloud Pod Architecture window, as shown in the following screenshot:
- Log on to the Horizon Administration console of the intended second member of the Cloud Pod using an AD account that has administrative permissions within Horizon, and open the View Configuration | Cloud Pod Architecture window within the console.
- Click the Join the Pod Federation link to open the Join window shown in the following screenshot. Provide the details for the Connection Server used in the previous steps, give the user name and password for an account with administrative permissions within Horizon, and then click OK to join the Pod Federation. Monitor the status window that will be displayed:
- When the Cloud Pod feature has finished configuring, click OK in the Reload window to reload the console and refresh the View Configuration | Cloud Pod Architecture window, as shown in the following screenshot:
- Repeat steps 5 through 7 as needed to add additional pods to the Cloud Pod.
- Once finished, open the Horizon Administration console Dashboard and expand the Remote Pods section under System Health, as shown in the following screenshot. The status of all other pods in the Cloud Pod will be displayed here to make it easier to quickly identify whether there are issues that require further investigation:
The Horizon Cloud Pod is now configured, although we have not yet defined our Horizon sites. Horizon sites allow us to prioritize which Horizon pool a user is directed to, while retaining the ability to use any available resources within the Cloud Pod. The purpose and configuration of Horizon sites is described in the next section.