Removing Cloud-Connected Horizon Pods from Use with Horizon Cloud

The business reasons for cloud-connecting a Horizon pod to Horizon Cloud range from the simple use case of using a subscription license with that pod to leveraging all the cloud-hosted services that are supported for use with cloud-connected Horizon pods. If you no longer have a need for those use cases, you can remove, or disconnect, the cloud-connected pod from use with Horizon Cloud by using the Remove button on the console's Capacity page. When disconnected from Horizon Cloud, that pod is no longer cloud-connected and you can no longer use a subscription license or use cloud-hosted services with that pod.

Tip: In addition to the Remove action on the Capacity page, the pod's details page has a Disconnect action that gives the same result.

Prerequisites

Remove the pod from any assignments in which that pod is involved. See Edit a Multi-Cloud Assignment in Your Horizon Cloud Tenant Environment.

If an on-premises Horizon pod is offline or unavailable when you complete these steps and the system completes its activities to disconnect the pod, the system cannot communicate with the pod's Connection Server to clear out the appropriate cloud-management-related properties in the Horizon global database. This property informs the Horizon Connection Server that the pod is in-use with Horizon Cloud. In this situation, after performing the steps here, you must also manually edit the Horizon global database to clear out the cloud-management-related properties.

Procedure

1. On the Capacity page, select the pod that you want to remove from use with Horizon Cloud.

2. Click Remove.

   A notification message appears in the following cases:

   • If the pod is included in one or more assignments, a message appears stating that you cannot disconnect the pod. You must first disassociate the pod from any assignments before trying to remove it.
   • If the pod is offline or unavailable, a message alerts you that the pod will still retain its cloud-managed property in the Horizon global database after the disconnection process. You can specify whether to proceed with or cancel the process.

Results

If you proceed with the disconnection process, the pod is disconnected from Horizon Cloud, and the pod's name disappears from the pages in the administrative console.

What to do next

If you saw a notification message that the pod was offline or unavailable during the disconnection process, manually edit the Horizon global database to clear out the pod's cloud-managed properties. See Clear the Cloud-Managed Properties from a Horizon Pod that was Offline During the Process to Disconnect it from Horizon Cloud.