License preservation and license regeneration

Last Updated : Jun 10, 2026 |
  • If you perform VMware OVA to VMware OVA upgrade of System Manager by using Solution Deployment Manager Client, the system retains the licenses. However, you must backup or export the licenses from the older System Manager server.

    If you are upgrading other applications by using System Manager Solution Deployment Manager, then Solution Deployment Manager retains the license file. However, if you are upgrading the application to a major release, install the new license file for those applications after the upgrade.

    For example, if you are upgrading System Manager and other applications to Release 10.1, Solution Deployment Manager retains the license file, but these license will not be valid. Therefore, install the new license file.

  • If you use the CLI procedure to upgrade System Manager to Release 10.2.x, the system does not retain the System Manager WebLM licenses that are installed on the old System Manager server. This will impact each product that is using the licenses from System Manager WebLM. During or after the upgrade, those prodFor more information about parauct might go in the license grace period mode or license error mode. To remediate this, after the upgrade, regenerate the licenses by using the new host ID. Ensure that all your Avaya License Activation Codes (LACs) for your system are available that is under contract with ‘Upgrade Advantage’ entitlement. Also, check that your account at Avaya PLDS website https://plds.avaya.com/ is functional to regenerate the license keys.

    Ensure to backup or export the System Manager license keys from the older System Manager server.