MIM 2016 SP2 upgrade from Forefront Identity or Microsoft Identity Manager

Organizations can upgrade to Microsoft Identity Manager 2016 SP2 from earlier versions of Microsoft Identity Manager or Forefront Identity Manager. Each section of this article covers a supported upgrade path.

There are several upgrade options available. If you're already running MIM 2016, and do not need to refresh the underlying platform (Windows Server, SQL, SharePoint, SCSM DW) or run MIM services using group managed service accounts, and you do not use MIM Language Packs then the easiest option will be in-place upgrade / hotfix (.msp) installation. Otherwise, the full installation is recommended.

Important

Check updated Software prerequisites section before installing MIM 2016 SP2

Upgrade from FIM 2010 R2 SP1 or later FIM builds

Note

The minimal supported version of Forefront Identity Manager that can be directly upgraded to MIM 2016 SP2 is FIM 2010 R2 SP1 (build 4.1.3419.0). Direct upgrade to MIM 2016 SP2 from earlier versions of FIM is not supported. If you're running FIM builds earlier than 4.1.3419.0 then you have to upgrade to FIM 2010 R2 SP1 prior to upgrading to MIM 2016 SP2.

  1. Option 1: Full installation using existing databases
    1. Make a backup copy of your FIMSynchronizationService and FIMService databases.
    2. Export all FIM Service RCDC objects and RCDC resource strings you made changes to.
    3. Export Synchronization Service encryption keys.
    4. Backup miisserver.exe.config, Synchronization Server 'Extensions' folder, Microsoft.ResourceManagement.Service.exe.config as MIM installer might overwrite custom changes made to config files.
    5. Uninstall all FIM components, including Language Packs (to be uninstalled first).
    6. Optional: Move FIM databases to another SQL server. It is recommended to create SQL aliases on MIM servers and use these aliases instead of real SQL server name to ease MIM DBs migration in future.
    7. Install MIM 2016 SP2 from the .iso installation media on the same or on another server following MIM deployment guide, choose to use existing databases when prompted, provide previously exported Synchronization Service encryption keys.
    8. Review miisserver.exe.config and Microsoft.ResourceManagement.Service.exe.config files for missing .net redirects or any custom sections you added.
    9. Install MIM 2016 SP2 Language Packs if needed.
    10. Re-submit customizations to RCDC objects and RCDC resource strings and localizations if needed.
    11. Upgrade FIM Add-ons and Password Reset clients, provide new MIM Service server name if MIM Service server name changed.

Upgrade from previous MIM 2016 builds

  1. Make a backup copy of your FIMSynchronizationService and FIMService databases.
  2. Export all custom FIM Service localizations made to RCDC objects and RCDC resource strings.
  3. Export Synchronization Service encryption keys.
  4. Backup miisserver.exe.config, Synchronization Server 'Extensions' folder, Microsoft.ResourceManagement.Service.exe.config as MIM installer might overwrite custom changes made to config files.
  5. Uninstall MIM Language Packs if used.
  6. Stop MIM services.
  7. Option 1: In-place upgrade - hotfix installation
    1. Apply MIM 2016 SP2 Synchronization Service hotfix
    2. Apply MIM 2016 SP2 Service hotfix
    3. Review miisserver.exe.config and Microsoft.ResourceManagement.Service.exe.config files for missing .net redirects or any custom sections that must be added.
    4. Install MIM 2016 SP2 Language Packs if needed.
    5. Re-submit customizations to RCDC objects and RCDC resource strings and localizations if needed.
    6. Upgrade MIM 2016 Add-ons and Password Reset clients.
  8. Option 2: Full installation using existing databases
    1. Uninstall all MIM components.
    2. Optional: Move FIM databases to another SQL server. It is recommended to create SQL aliases on MIM servers and use these aliases instead of real SQL server name to ease MIM DBs migration in future.
    3. Install MIM 2016 SP2 from the .iso installation media on the same or on another server following MIM deployment guide, choose to use existing databases when prompted, provide previously exported Synchronization Service encryption keys.
    4. Review miisserver.exe.config and Microsoft.ResourceManagement.Service.exe.config files for missing .net redirects or any custom sections that must be added.
    5. Install MIM 2016 SP2 Language Packs if needed.
    6. Re-submit customizations to RCDC objects and RCDC resource strings and localizations if needed.
    7. Upgrade MIM 2016 Add-ons and Password Reset clients, provide new MIM Service server name if MIM Service server name changed.

Note

Language Packs updates after MIM 2016 SP2 will be distributed as hotfixes (.msp files), eliminating the need to uninstall/reinstall Language Packs.

More detailed information about the upgrade and databases backup procedures could be found in the Upgrade to FIM 2010 R2 article, that is applicable to any FIM or MIM upgrade process.