Downgrade the vRealize Automation license
After running a vRealize Automation Enterprise license for some time I tried to downgrade the license on the vRealize Automation appliance to the Advanced version. This resulted in the error message ‘Unable to downgrade the existing license edition‘. This can also happen when you try to change the vRealize Automation evaluation license to a vCloud Suite license.
To downgrade the vRealize Automation license you need to follow the steps described below.
NOTE: Before you start, create a back-up/snapshot of the existing database or complete appliance. This procedure involves modifications of the databases which can permanently damage the databases.
Remove existing license from SQL database
To remove the vRealize Automation license, go to the IaaS database server and perform the following steps:
- Run this query to backup existing license keys to a new table:
SELECT * INTO dbo.LicenseKeys_backup FROM dbo.LicenseKeys - Run this query to remove the license keys:
DELETE FROM dbo.LicenseKeys WHERE SerialNumber IN (‘1st license key’, ‘2nd license key’)
NOTE: Replace the first license key and second license key with actual license keys and keep the quotes and parentheses. - If you require to restore the license keys you have removed, run this query:
INSERT INTO LicenseKeys (SerialNumber) SELECT SerialNumber FROM LicenseKeys_backup WHERE NOT EXISTS (SELECT SerialNumber FROM LicenseKeys WHERE SerialNumber = LicenseKeys_backup.SerialNumber).
Remove existing license from vPostgres database
- First stop the vRealize Automation service on the appliance with the following command:
# /etc/init.d/vcac-server stop - Connect to the vRealize Automation database with the following command:
# /opt/vmware/vpostgres/current/bin/psql vcac vcac
Syntax: psql [database][user] - List all database tables by using the sql shell with the command \d;
- Check the availability of the embeddedlicenseentry table;
- Remove all license information from the embeddedlicenseentry table with the following command in the sql shell:
vcac=> delete from embeddedlicenseentry - Exit the sql shell with the following command:
vcac=> \q - Now you can start the vRealize Automation Service again with the command:
# /etc/init.d/vcac-server start - Now you can enter the new license in the vRealize Automation appliance and IaaS Server.
Other articles in the series vRealize Automation:
- Infoblox & vRealize Automation, Setup IPAM endpoint
- Infoblox & vRealize Automation, Install Infoblox IPAM plugin
- Setup provisioning of vCloud Air workloads
- Setup a vCloud Air Endpoint in vRealize Automation
- Setup Postgres database high availability for vRealize Automation
- Setup vRealize Automation Cost profiles & currency
- Speed up vRealize Automation life cycle updates
- Configure vRealize Automation not to delete virtual machines
- Track infrastructure changes with vRealize Automation Data Collection
- MS SQL high availability support for vRealize Automation
- Setup the vRealize Automation prerequisites for IaaS
- vRealize Automation: How to …
- Downgrade the vRealize Automation license
- vRealize Automation 7 – New Architecture & Installation
- vRealize Automation 7 – Improved Authentication
- vRealize Automation 7 – Converged Blueprints
- vRealize Automation 7 – LifeCycle Extensibility
- How to transfer vRealize Automation payload to Orchestrator
- Automation is not difficult with vRealize Automation 7
- vRA custom host name using Orchestrator and Event Broker
- How to deliver Database-as-a-Service with vRealize Automation
- Prepare Windows for vRA software deployment
- Missing endpoints after upgrading to vRealize Automation 7.3
- How to run Containers as a Service – Part 1
- How to run Containers as a Service – Part 2
- Infoblox & vRealize Automation, IP Address Management (IPAM) made easy
- How to run Containers as a Service – Secure Docker communications
- Create a new database user using vRealize Automation XaaS
- Infoblox & vRealize Automation, Infoblox NIOS setup
- Infoblox & vRealize Automation, vRA setup
- vRealize Automation failed requests monitoring
- vRealize Automation 7.2 released
- How to specify a deployment target when using vRealize Automation
- vRealize Suite just became a lot easier with Lifecycle Manager
- LAMP Stacks made easy with VMware and Puppet
- How to: Deploy vRealize Automation 8
- Create Custom Names with vRealize Automation 8
- Kubernetes as a Service
Related Posts:
Tags In
Erik Scholten
Related Posts
2 Comments
Leave a Reply Cancel reply
You must be logged in to post a comment.
Hi ERIK, Is this method still valid for vRA 7.0?
Yes, I’ve tested this on vRA 7 for this article