Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Allow vRealize Suite and vCloud Suite customer to mix old and new versions license keys (67163)

Last Updated: 6/9/2020Categories: InformationalTotal Views: 5279Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Details

This article provides information on vRealize Suite and vCloud Suite to mix old and new versions license keys.

Solution

If you use VMware vRealize Suite (any edition), either as a standalone VMware offering or as part of the VMware vCloud Suite software bundle, the following terms apply:

You may use the 2018 edition and 2019 edition license keys to activate and use the software components in the VMware vRealize Suite bundle as described in this paragraph. You may selectively upgrade some software components in the VMware vRealize Suite bundle to newer versions while keeping other software components at old versions. Newer versions of the software components may require a 2019 edition license key while old versions of the software components may require a 2018 edition license key. You may use the 2018 edition license key to use old versions of the software components that have not been upgraded and the 2019 license key to use new versions of the software components that have been upgraded. If you use a 2019 edition license key to access and use a software component in the VMware vRealize Suite bundle, you must not use the 2018 edition license key for that software component. As a reminder, the 2018 edition license key can be applied to vRealize Suite 2019 products, but the 2019 edition license cannot be applied to vRealize Suite 2018 products.

For example, if you have licensed one hundred (100) Portable License Units of VMware vRealize Suite to be deployed on a per Processor basis, you may deploy one hundred (100) Processors in an environment with VMware vSphere and use the following:

VMware vRealize Automation version 7.5 included in VMware vRealize Suite 2018.

The license key provided with VMware vRealize Suite 2018 to use VMware vRealize Automation version 7.5.

VMware vRealize Operations version 8.0 included in VMware vRealize Suite 2019.

The license key provided with VMware vRealize Suite 2019 to use VMware vRealize Operations version 8.0.

The software components and license keys described in (1) – (4) above on the 100 Processors of VMware vRealize Suite that have been deployed in an environment with VMware vSphere.

Before you upgrade and accept the 2019 version on customerconnect.vmware.com, you need to document your previous license key outside of the portal to manually use the 2018 license key where needed.

Certain features of VMware vRealize Suite and VMware vCloud Suite may not be available if you upgrade certain software components in VMware vRealize Suite and VMware vCloud Suite to newer versions while keeping other software components at old versions. For example, integration features between VMware vRealize Operations and VMware vRealize Automation in the vRealize Suite may not be available if the integration requires that the all software licenses and software components are the same version.

Please refer to the below instructions on how to use vRealize Suite Lifecycle Manager to deploy products with different licenses.

Using vRealize Lifecycle Manager (to be referred as LCM hence forth in this doc) to deploy products with different licenses

Prerequisites:

Relevant license keys should be added to locker from LCM UI in prior to their use. This is an optional requirement since there is option to add a new license key during product deployment itself.

If Customer Connect account has the license key and LCM can connect to Customer Connect (with or without a proxy), then upon registering the Customer Connect account in LCM, all the license keys belonging to that account shall be auto saved in locker.
Note: If multiple Customer Connect accounts are added then collection of all the license keys shall be stored in locker with unique entry for each license key, i.e. if account ‘A’ & account ‘B’ both has a common license entry then locker shall store them against any one of the account to avoid duplicate entry. Download of a license key shall be skipped from Customer Connect only if it is already added in LCM.

Procedure

While creating new environment in LCM or while performing organic growth with a new product deployment, we need to arrive at the step where a license needs to be selected. The name of this step in the wizard is ‘License’.

If locker does not have the license entries already, then users can always add from this step by clicking the ADD button.

Selecting license keys for the deployment can be done with the following 3 easy steps:

Click on the select button as shown below. This shall open a pop-up with listing of the keys present in LCM locker which are eligible for the products & versions selected for deployment.

Select all/probable license keys which may fit for the deployment. A short cut approach is to select all the keys.

Once the keys are selected, they will be listed in the table as shown below. At this moment they are not set for the deployment. For that we need click the button with label ‘Validate Association’ to complete the process.

This process automatically associates a license with appropriate products. If multiple choices are available, then user is asked to choose one of the possible entries as shown below.

Once validation is done and licenses are applied to all products (which are getting deployed), the final table will look like following image.

Notes:

While adding or selecting licenses, there is no restriction imposed on the types of license used. Hence the license keys being used here can be either vRealize Suite License, or standalone product licenses. LCM will not prevent users unless the license has expired already.

License validation assures association with each of the products that is considered for deployment. Hence the option the provide license keys from under the product advanced property has been removed. All license selection and association with products, must be done form the license stage only.

The license validation does not ensure availability of functionality/feature in a product based on the selected key. Hence user needs to take a conscious decision while selecting a license key. Depending on the products and the desired inter-product configuration, the appropriate license key should be selected.

Related Information

Do not use LCM directly if you are using VMware Cloud Foundation. Use SDDC Manager to upgrade any components to versions supported by Cloud Foundation.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant