Skip to main content
Version: Omada Identity on-premises 15.0.x Long-term support (LTS)

Upgrade guides

warning

Support for Microsoft Identity Manager (MIM) in Omada Identity 15.x is deprecated and ends on October 31, 2027. If you use MIM Sync for provisioning, migrate to the Omada Provisioning Service by that date.

Omada Identity 15.x does not support Microsoft Identity Manager 2016 SP3. For details, see the release notes.

Planning the upgrade​

Follow the correct upgrade path. Each upgrade procedure lists the applicable source versions in its title or description.

  • To upgrade to v15 LTS, you can upgrade from Omada Identity 15.0.5 or earlier, including version 14.0.16, or from an earlier v15 LTS patch. Use the Upgrade to v15 LTS guide and the installation files for the latest patch.
  • To upgrade to Omada Identity 16.0.0, the minimum required version is Omada Identity 15.0.5 or 15.0.6.

Make sure you copy your PswEncryptionKey.

Handling installed hotfixes and changed files​

During an upgrade, the installer overwrites versioned files, such as .dll files and ODW SSIS packages. Any previously installed hotfixes that modify these files are also overwritten.

The installer does not automatically overwrite non-versioned files, such as .js files and web.config, that were changed by a hotfix or edited manually. Before upgrading, remove these files from the installation folder or restore the original versions. After the upgrade, reapply any manual changes you need.

Note on changesets​

If you recorded changesets before the upgrade, download them from the source environment before upgrading it. To transfer the changesets:

  1. Download all changesets from the source environment before upgrading it.
  2. Import them into each target environment while it is still running the original version.
  3. Upgrade the target environment only after importing the changesets.
info

Moving changesets between different versions is not supported. Although the system may not report an error, importing changesets between different versions can lead to unexpected results.

Important

To use the Access Request or Approvals feature, install the Extend Access package.

Completing OPS jobs​

Before upgrading, make sure that no OPS jobs are pending. Stop the RoPE service and wait for any running OPS jobs to complete.

After upgrading, commit the settings to OPS from the system onboarding page for one of the onboarded systems.

Stopping services and creating backups​

  1. Make sure you have the service account information and credentials available.
  2. Stop all running Omada Identity services and any scheduled SSIS import jobs. In IIS, stop all Omada-related application pools and websites. Stop the following services:
    • Omada Identity Suite Timer Service.
    • Omada Provisioning Service.
    • Omada Role and Policy Engine Service.
  3. Stop the Omada Identity Enterprise Server portal.
  4. Back up the Omada Provisioning Service installation folder.
  5. Back up the Omada Role and Policy Engine installation folder.
  6. Back up all Omada Identity databases. The default database names are:
    • OIS.
    • ES Audit database.
    • Omada Source System Data DB.
    • Omada Data Warehouse.
    • Omada Data Warehouse Master.
    • Omada Data Warehouse Staging.
    • Provisioning Service.
    • RoPE.

Select an upgrade guide to upgrade your Omada Identity solution to the desired version: