Jorge's Quest For Knowledge!

All About Identity And Security On-Premises And In The Cloud – It's Just Like An Addiction, The More You Have, The More You Want To Have!

(2017-05-11) Updating MIM 2016 With Patches After Fresh MIM 2016 (SP1) Install

Posted by Jorge on 2017-05-11


Somewhere in September 2016 Microsoft released MIM 2016 SP1 (see this blog post). That was MIM 2016 with SP1 included (build 4.4.1237.0) and which could be installed freshly. However, if you were running MIM 2016 RTM (4.3.1935.0) (with or without patches 4.3.2064.0, or 4.3.2195.0, or 4.3.2266.0) you could not apply this MIM 2016 SP1 (build 4.4.1237.0) as it was not an update package for RTM, but rather a new installation package. To still install MIM 2016 SP1 (build 4.4.1237.0) you had to first uninstall MIM 2016 RTM and then install MIM 2016 SP1 (build 4.4.1237.0) and reuse existing DBs. That procedure is explained here. In November 2016 I blogged about 2 different SP1 packages here. The build 4.4.1302.0 is explained here. Since then Microsoft released a newer build 4.4.1459.0 to replace the build 4.4.1302.0. The build 4.4.1459.0 is explained here.

If you are running MIM 2016, you will be able to install either build 4.4.1302.0 or build 4.4.1459.0.

However, if you are running MIM 2016 SP1, because you performed a fresh install you will NOT be able to install either build 4.4.1302.0 or build 4.4.1459.0.

If you want to install build 4.4.1302.0 and/or build 4.4.1459.0 you will have to perform the following actions:

  • Do NOT make any changes
  • Backup ALL FIM related databases in SQL Server
  • Create a backup copy of the contents of the folder “C:\Program Files\Microsoft Forefront Identity Manager\2010”
  • Uninstall the MIM 2016 SP1 server components
  • Install the MIM 2016 RTM (4.3.1935.0) and reuse the databases
  • DO NOT try to apply the patches 4.3.2064.0, or 4.3.2195.0, or 4.3.2266.0 as that will break your database. In that latter case you will need to restore the DB from backup
  • Apply the patch with build 4.4.1302.0 (this may be skipped if you want to install the newest patch mentioned next)
  • Apply the patch with build 4.4.1459.0
  • Check the different settings in the WEB.CONFIGs by comparing them with the backup copy. Apply any configuration differences you find
  • If applicable also check the mfasettings.xml
  • Done!

I do not when, but I think/hope Microsoft will create patches that can be applied to both SP1 packages.

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER:
https://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
#########
http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: