Upgrading Appliance Virtualization Platform or VMware-based System Manager Release 8.1.x or 10.1.x to Release 10.2.x running on VMWare by using the Solution Deployment Manager client

Last Updated : Jun 10, 2026 |

About this task

Use the procedure to upgrade System Manager to Release 10.2.x from:

  • Release 8.1.x running on Appliance Virtualization Platform, VMware, orAvaya Solutions Platform R5.1.x.

  • Release 10.1.x running on VMware or Avaya Solutions Platform R5.1.x.

Solution Deployment Manager is not supported for Avaya Solutions Platform R6.0.x

Note:

  • If you are upgrading System Manager Release 8.1.x or 10.1.x to Release 10.2.x by using the Solution Deployment Manager client then the license files are retained. However, you need to install the license file for System Manager Release 10.2.

    For more information, see License preservation and license regeneration.

  • From Release 10.1 and later, Appliance Virtualization Platform is no longer available. Therefore, if System Manager Release 8.1.x and earlier is on the Appliance Virtualization Platform host, then migrate Appliance Virtualization Platform to Avaya Solutions Platform 130 Release 6.0 before upgrading System Manager to Release 10.2. Migration of Appliance Virtualization Platform is supported from Avaya Solutions Platform 120 (Dell PowerEdge R640).

Before you begin

  • Install Solution Deployment Manager Client.

    For information, see Installing the Solution Deployment Manager client on your computer.

  • Add a location.

    For information, see Adding a location.

  • Add the required host.

    For information about adding the host, see Managing the platform.

    Important:

    • If the application is running on the ESXi version that is not supported with Release 10.2, then first upgrade the ESXi to a supported ESXi version.

      For information about the supported ESXi version, see Supported ESXi version.

      For information about upgrading ESXi, see the VMware product documentation.

    • If ESXi is managed by vCenter, ensure that the vCenter version is same or higher than the ESXi version.

    • If the application is running on the server that is not supported with Release 10.2.x, then deploy Avaya Solutions Platform 130.

      For information about supported servers, see Supported servers for Avaya Aura applications.

  • Select the System Manager 8.1.x or 10.1.x virtual machine and click More Actions > Re-establish connection to establish the trust.

    For more information, see Re-establishing trust for Solution Deployment Manager elements.

  • Obtain the System Manager software. See Software details of System Manager

Procedure

  1. To start the Solution Deployment Manager client, click Start > All Programs > Avaya > Avaya SDM Client or the SDM icon (Icon to open the Solution Deployment Manager client dashboard) on the desktop.
  2. Click Application Management.
  3. In the lower pane, click Upgrade Management.
  4. Select the System Manager 8.1.x or 10.1.x virtual machine.
  5. Click Upgrade.
  6. In Platform FQDN, select the required host.

    If the System Manager system prompts for the certificate, accept the certificate. When you accept the certificate, the system displays the following message: Certificate added successfully in trust store.

  7. Optional Select the datastore on the host.

    If more than one datastore is available, select the datastore.

    If the host is part of a VMware cluster, the system displays the following message:

    Host is in a cluster. Therefore, capacity details of CPU and memory are unavailable! Ensure that the host resource requirements are met before any action.

    For information about resource details, see Supported footprints of System Manager on VMware.

  8. Click Next.
  9. On the OVA tab, click one of the following:

    • URL, in OVA File, type the absolute path of the same local windows computer or the http URL accessible from the same local windows computer of the System Manager OVA file, and click Submit.

    • S/W Library, in File Name, select the System Manager OVA file from the drop-down list.

      To use the S/W Library option, the OVA file must be present in the local software library directory that is defined during the Solution Deployment Manager client installation. The system displays the directory name when the S/W Library option is selected.

    • Browse, select the required OVA file from your local computer, and click Submit File.

    • Browse from Datastore

      For information about upgrading System Manager using the Pre-staging feature, see Upgrading System Manager from Release 7.x, 8.x, or 10.1.x to Release 10.2.x by using the Pre-staging feature of Solution Deployment Manager Client.

      For information about the Pre-staging feature, see Using the Solution Deployment Manager client.

      This option is applicable only for System Manager Release 10.1 and later.

    When you select the OVA, the system:

    • Displays the CPU, memory, and other parameters in the Capacity Details section.

    • Disables the Flexi Footprint field.

  10. To upload the data migration utility file, click the Data Migration tab, and click one of the following:

    • URL, and type the absolute path of the same local windows computer or the http URL accessible from the same local windows computer of the latest data migration utility file.

    • S/W Library, and select the latest data migration utility file from the drop-down list.

      The data migration utility file must be present in the local software library directory.

    • Browse, and select the latest data migration utility file from your local computer, and click Submit File.

  11. To upload the latest service or feature pack, select the Service or Feature Pack tab, and click one of the following:

    • URL, and type the absolute path of the same local windows computer or the http URL accessible from the same local windows computer of the latest service or feature pack.

    • S/W Library, and select the latest service or feature pack from the drop-down list.

    • Browse, and select the latest service or feature pack from your local computer, and click Submit File.

  12. Click Next.
  13. In the Config Parameters section, provide the required details.
    Note:

    Use the same Management FQDN and Time Zone as configured on the old System Manager.

    For information, see Upgrade Management field descriptions.

  14. In the Network Parameters section, select the required Public and Out of Band Management network interface details.
  15. Click Upgrade and accept the license terms.

    The system takes the backup, shuts down the existing virtual machine (VM), deploys the OVA file, and restores the data on the new virtual machine.

  16. To view the status, in the Upgrade Status column, click Status Details.

    The complete process takes about 100–150 minutes depending on the data on System Manager.

    Note:

    The upgrade process might involve multiple reboots during data migration. If you have selected the checkbox Require Encryption Pass-Phrase at Boot-Time, you must monitor the VM console for reboots and enter the Encryption Pass-Phrase promptly.

    If you fail to enter the Encryption Pass-Phrase timely, the upgrade process may timeout and fail. If this happens, restart the upgrade process.

  17. Do one of the following:

    • If the upgrade is successfully completed, do the following:

      1. Verify that the new System Manager virtual machine is functional.

        For more information, see Verifying the functionality of System Manager.

      2. If you upgraded System Manager on a different host, refresh both hosts in Solution Deployment Manager.

        The system deletes the old virtual machine.

      3. Click Commit.

        The system deletes the old virtual machine.

        If you already performed the Commit operation or manually deleted the older VM (For example, <vm_name>_old) after successful upgrade on host itself. In these cases, if you re-attempt the Commit operation then Solution Deployment Manager displays the warning message Unable to find <vm_name>_old on the Commit status page.

    • If the upgrade fails or you want to revert to the old system, then do the following:

      1. If you upgraded System Manager on a different host, refresh both hosts in Solution Deployment Manager.

      2. Click Rollback.

        The system deletes the newly created virtual machine and starts the old virtual machine.

      3. Again refresh both the host to get the latest virtual machine information.

Next Steps

Install the valid license file for System Manager Release 10.2.x.