[VMC on AWS] Decommission a vCenter Cloud Gateway

Products

• VMware Cloud on AWS

Issue/Introduction

To provide the steps to unlink and remove the vCenter Cloud Gateway.

Symptoms:
The vCenter Cloud Gateway is no longer needed and is being removed.

Resolution

Before removing the vCenter Cloud Gateway, the VMware Cloud on AWS vCenter needs to be unlinked:

1. Log into the vCenter Cloud Gateway.
2. Navigate to the "Linked Domains" page. (Menu -> Administration -> Hybrid Cloud -> Linked Domains)
3. Under the name of the linked domain, click "Unlink". A dialog box will appear to confirm the unlinking. Note: All currently active sessions will be logged out. 
4. Click "OK." When the unlinking is complete, you are prompted to log out. 
5. Click "OK" to log out. 
6. The SSO domain is now unlinked and the removal of the vCenter Cloud Gateway can begin. 

After unlinking from the VMware Cloud on AWS vCenter is successful, properly unregister the vCenter Cloud Gateway from the on-premise vSphere environment: https://kb.vmware.com/s/article/2106736 
Note: The vCenter Cloud Gateway may not show as a node in the on-premise vSphere environment. If it does not show as a node, run the above VMware KB as a precaution to prevent any Inventory Service or Lookup Service errors. 

Once the vCenter Cloud Gateway has been unlinked and unregistered, the appliance can be removed from the inventory. 

Additional Information

Unlink a Cloud SDDC: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center.doc/GUID-880B6F21-7A8C-486B-9AD7-EC14753055D6.html
Using the 'cmsso' command to unregister vCenter Server from Single Sign-On: https://kb.vmware.com/s/article/2106736

Impact/Risks:
When you unlink the VMware Cloud on AWS vCenter from the vCenter Cloud Gateway, users can not use their on-premise credentials to log into the VMware Cloud on AWS vCenter any longer.