After Broadcom's acquisition of VMware, our shared goal is to focus and invest in on-premises products as published in earlier blog posts by Krish Prasad and Rick Walsworth. 

vSphere+ customers who have connected their vCenter servers to the Cloud Console are encouraged to migrate from SaaS to on-premises deployments to benefit from our product investments and roadmap.

This article helps vSphere+ customers disconnect their vCenter Servers and apply their license keys.

To support customers to remove vSphere+ capabilities in brownfield deployments and move vSphere environment to termed license mode.

The proposed solution is to disconnect the vCenter from the GW/Cloud and remove the subscription so that the customer can apply license keys. А vCenter API is available for this.

Note:

• If the vCenter is disconnected, no GW changes are required.
• If the vCenter isn't subscribed, so no vCenter changes are necessary either.
• Please ensure that you take downtime of all the VCs that are part of a single gateway instance & run the script on all of them to apply licenses.

Steps:

1. Obtain the necessary license keys for virtual infrastructure licensing after unsubscribing. (The system will transition into an unlicensed state, and to avert any potential side effects, the process of applying the license keys must remain streamlined. Therefore, it is advised that the customer possesses the keys in advance.).

Note: The keys will be available on the Broadcom Support Portal under "My Entitlements".

2. Prepare for maintenance and possible downtime.

• Once the script is executed, the system will transition into an unlicensed state, and to avert any potential side effects, the process of applying license keys must remain streamlined. Therefore, it is advised that the customer possesses the keys in advance.
• Ensure we have a snapshot of the vCenter Server.
• If the vCenter Server is part of ELM, take offline snapshot of all the vCenter Servers part of the setup.
• This script, once executed will license the VC and ESXi hosts with evaluation licenses valid for 60 days. However, it is advised that you run the script and assign the term licenses in one go.

3. Power off the GW to sever the connection from GW to vCenter. This will prevent automatic re-subscription from the GW.
4. Download the attached delete-subscription.sh file from the attachments section of the iKB.

• Upload the script on the vCenter Server, preferably in /tmp
• Make the script executable chmod +x delete-subscription.sh.
• Execute the script: ./delete-subscription.sh
• Note:  You may receive an error when you try to run the script:
  bash:  ./delete-subscription.sh: /bin/bash^M: bad interpreter: No such file or directory
  This error is caused by DOS carriage returns added to the script when copying from a Windows-based text editor.  To resolve this problem, run the following command and rerun the script:
  
  sed -i -e 's/\r$//' delete-subscription.sh

5. Execute the application of license keys to all assets within the virtual environment from the vCenter H5C UI.

The assignment of the new licenses should happen in this order:

• Assign license to vCenter.
• Assign licenses to all ESXi hosts.
• Assign licenses to vSAN
• Reconnect those that were disconnected during this process

6. Delete the GW VM. Do not power it back on.

7. Script will only remove the subscription of vCenter Server with vSphere+. We will need to manually remove all the CloudGateway service accounts (with prefix: CloudServicesGateway) from vCenter Server.

• Login to vCenter Server UI using administrator SSO credentials.
• Navigate to Administration > Users and Groups > Select domain "local SSO".
• Filter Users with CloudServicesGateway prefix and delete the user accounts.

Please Note:

• Customers running on vSphere 7.x will need to downgrade their new licenses received as they are issued as version 8.x.
• Ensure that the newly received license keys are assigned to the VCs & ESXi hosts at the earliest as once the temp license expires, the hosts will get disconnected from the vCenter.

Workaround:
In case of failure, follow below steps,

1. Power on the cloud gateway and validate that the VCs are in connected state on cloud portal.
2. In case VC goes down, power off the VCs and revert the snapshot of all the linked VCs and power them back on and re-validate the connection.