You can upgrade from earlier versions of VMware Identity Manager to the latest version if you conform to vRealize Suite Lifecycle Manager supported form-factor. Otherwise, the upgrade has to be performed outside vRealize Suite Lifecycle Manager. After an upgrade, you can reimport VMware Identity Manager by triggering the inventory sync in vRealize Suite Lifecycle Manager. For more information, refer to the Installing vRealize Automation with vRealize Suite Lifecycle Manager Easy Installer for vRealize Automation and VMware Identity Manager documentation.

  • If the installation, upgrade, or scale out request of VMware Identity Manager is IN PROGRESS or FAILED state in vRealize Suite Lifecycle Manager, ensure that you do not remediate the cluster.
  • If VMware Identity Manager is clustered through vRealize Suite Lifecycle Manager, then it is recommended to use the Power ON and Power OFF option for a scenario which involves bringing down the cluster, such as reboot and shut down.
  • VMware Identity Manager version 3.3.4 is backward compatible with Windows connectors of previous versions.
  • When you deploy VMware Identity Manager with vRealize Suite Lifecycle Manager, do not change the VMware Identity Manager hostname. For more information, refer to the VMware Identity Manager documentation.


  • In a clustered environment, ensure that the Postgres Cluster Health Status is healthy by selecting the Trigger Cluster Health for your product in the Environments page. After your request is complete, you can view the notifications for your product and verify if your status is healthy. If your status is unhealthy, you can use Power ON to remediate your cluster, prior to an upgrade. For the 8.4 release, the remediate button is available in your product card in the Environments page.
  • Verify that you have taken a snapshot of VMware Identity Manager nodes.
  • Verify that you have your product binaries mapped. For more information, see Configure Product Binaries.
  • For a clustered VMware Identity Manager upgrade, ensure that you disable all the stand-by nodes in the load-balancer so that the traffic is not routed to the stand-by nodes, and then enable the stand-by nodes after the upgrade is complete.


  1. On the Lifecycle Operations page, click Manage Environment.
  2. Navigate to the Global Environment instance.
  3. Click View Details > Upgrade..
  4. Under the Product details section, you can select the following repository type.
    Option Description
    Repository URL When you select this option, you can manually add the local upgrade file location in the Lifecycle virtual appliance.
    vRealize Suite Lifecycle Repository When you select this option, you can enter the upgrade path available after mapping the binaries through vRealize Suite Lifecycle Manager.
    Note: For VMware Identity Manager version 3.3.4, the only option available is vRealize Suite Lifecycle Repository The other options, Repository URL and VMware Repository are not available.
    VMware Repository Select this option and select the version. The upgrade is performed using the online source.
  5. Click and run the pre-check.
  6. Click Submit.