This page describes the high-level steps that you must perform to decommission an existing Horizon 8 deployment. You might decommission a deployment to prepare for a clean installation of Horizon 8, or to remove Horizon 8 components from your system infrastructure completely.
Complete the following tasks in the specific order listed. How many of the tasks you need to complete depends on which components of Horizon 8 you have in your deployment.
-
Complete the steps to delete automated pools and farms.
- In Omnissa Horizon Console, delete all automated desktop pools, application pools, and farms. Allow time for the replicated desktops to be deleted. See Desktops and Applications in the Horizon 8 documentation.
- In vCenter Server, delete any remaining instant-clone artifacts such as replicas. See VMware vSphere Documentation.
- In vCenter Server, delete all golden image virtual machines (VMs) if you no longer require them. See VMware vSphere Documentation.
-
Complete the steps to delete manual pools and farms.
- In Horizon Console, delete all manual desktop pools, application pools, and farms. See Desktops and Applications in the Horizon 8 documentation.
- In Horizon Console, remove any registered machines. See Desktops and Applications in the Horizon 8 documentation.
- In vCenter Server, delete all VMs previously used in a manual desktop pool or manual farm. See VMware vSphere Documentation.
-
If the deployment is part of a Cloud Pod Architecture federation, remove it from the federation. See Cloud Pod Architecture in Horizon 8.
-
Disconnect the deployment from Omnissa Horizon Cloud Service, if applicable.
- Shut down the Omnissa Horizon Edge Gateway or Horizon Cloud Connector.
- Remove the Horizon Edge Gateway or Horizon Cloud Connector from vCenter Server. For more information, see Using Horizon Cloud Service - next-gen or Horizon Cloud Service - First-Gen Administration Guide.
-
Complete the steps to uninstall Omnissa Horizon Connection Server instances.
- Revoke any Certificate Authority (CA-signed) certificates used for Horizon Connection Server instances. You may keep wildcard certificates if you use them in other environments.
- Remove all Horizon Connection Server instances from Omnissa Unified Access Gateway. See the Unified Access Gateway Documentation.
- Remove all Horizon Connection Server instances from Omnissa Workspace ONE. See the Omnissa Workspace ONE Documentation.
- Remove each Horizon Connection Server instance and each Active Directory Lightweight Directory Services (AD LDS) instance individually. See "Removing the Entry for a Horizon Connection Server Instance Using the -S Option" in the Administration guide in the Horizon 8 documentation.
- Remove all Horizon Connection Server instances from any RSA or RADIUS servers that you have configured for authentication.
- Delete all Horizon Connection Server log files if you no longer require them.
-
Complete the steps to uninstall Enrollment Server instances.
- Revoke any enrollment agent certificates issued to Enrollment Server instances.
- Remove each Enrollment Server instance from any Active Directory groups used to grant permission to certificate templates.
- Remove each Enrollment Server instance from your system environment. See "Commands for Managing Enrollment Servers" in the Administration guide in the Horizon 8 documentation.
-
Remove any Horizon 8-related objects from Active Directory.
- Delete any Horizon 8 accounts from Active Directory, unless you plan to reuse them in a new installation or in another environment. These accounts include:
- Computer accounts for deleted VMs previously used in desktop pools and farms
- User accounts created for the purposes of domain bind and instant-clone domain join
- User account created for the purpose of adding vCenter Server to the deployment
- Delete any Organizational Units (OUs) that you created in Active Directory to store Horizon 8-related computer or user accounts.
- Remove any Horizon 8-related groups from the Remote Desktop Users group in the Restricted Groups policy. See Configure the Restricted Groups Policy.
- Remove all Horizon 8 GPO templates from your Active Directory domains.
- Delete any Horizon 8 accounts from Active Directory, unless you plan to reuse them in a new installation or in another environment. These accounts include:
-
Remove any firewall rules for Horizon 8 that you have configured on your network.
-
If you have integrated Horizon 8 with a Syslog server or a Microsoft SQL Server, Oracle, or PostgreSQL event database and do not require that server or database for future auditing, you can delete it. You can also delete any event data stored on the file system if no longer required.
Note: Do not reuse a VM after uninstalling a Horizon Connection Server instance from it. Install any new Horizon Connection Server instance on a new VM that has never hosted a prior Horizon Connection Server instance.
Was this page helpful?