

Horizon Cloud Service Next-gen Initial Onboarding.

Click in the to view the detail health and status of the gateways respectively. Repeat the same for another gateway as well.ġ1. > in gateway column, point the mouse cursor on top of one of the and verify Name/IP Address/ Status/Detail. Verify Unified Access Gateway health and status. If pod has HA enabled, you should see 2 green circles.ġ0. Note: You can see only one green circle in Pod Manager column because my pod is deployed without high availability. Navigate to > select the pod from drop down to which you have enabled the infrastructure monitoring feature > click in the in pod manager column to view the health and status in detail. Under the section, Unified Access Gateway (UAG) and pod manager status is shown as. In Horizon Universal console, navigate to > confirm the Horizon Edge Appliance configuration detail i.e. The status becomes once the configuration is completed.Ĩ. This means the Edge VM itself is deployed successfully but the configuration is still in progress.ħ. Once the Edge VM is deployed, the status gets changed like below. Make sure that the Edge VM deployment has been initiated. Select the pod on which you need to activate the feature > accept the terms and conditions >. You can see the status of Horizon Infrastructure Monitoring as. Select in Horizon Infrastructure Monitoring section.ģ. Navigate to > and confirm you have completed the VMware Cloud Service Platform onboarding. If you haven`t completed the CSP onboarding, please refer to step#1-6 (only) of this link for the procedure of CPS onboarding.Ģ. The CSP onboarding is already completed on this pod. This post is based on Horizon Cloud on Azure deployment. This IP range is used for underlying Kubernetes networking on the appliance.

The Microsoft Azure Subscription that hosts the Horizon Cloud on Azure pod must accommodate the requirements of the Horizon Edge Virtual Appliance.Active Directory bind has to be completed the the pod.The pod has to be onboarded to VMware Cloud Services Platform (CSP) aka Enterprise federation or integrated it with Workspace ONE.The pod must be running manifest 2298.0 or later.
