Month: July 2018

FIM to MIM 2016 Upgrade of Reporting

/ Ike Ugochuku

I have got to throw my views here about the MIM Reporting upgrade.

For most FIM environments, there is a 30 day tombstone on requests else your DB will grow at an alarming rate. So requests are stored externally via the FIM reporting feature. To be more product specific, FIM data is stored in the SCSM Data warehouse. For an upgrade to MIM 2016 and SCSM 2016 we are looking at

First an SCSM upgrade to SCSM 2016 and then a MIM upgrade.

Anyone who has done the MIM reporting installation will tell you it is quite a voluminous and  delicate setup process. You miss one minor step and you have to redo the whole thing again. Of course 90% of this work is in setting up the SCSM infrastructure. The SCSM upgrade is no different.

My recommendation

  1. Install SCSM 2016 with Datawarehouse
  2. Upgrade FIM to MIM 2016
  3. Add MIM reporting. Run Initial sync, let that complete and then run incremental sync.

What about your archived data in the FIM Datawarehouse? You can keep the server as a historical DB and access it via SQL reporting service.

MIM Reporting Installation

First, you cannot install MIM Reporting by itself on a server. You must have MIM Portal also on the same server. MIM Reporting is not a website (like SSPR), the setup will install new resource objects in the port add some tables to the MIMService DB and copy over files. So sits on the Portal.

So lets say you want your SCSM Service manager to be on a separate server and then your MIM reporting on a different server do this.

Server1 – SCSM Service manager

  1. Install SCSM pre-reqs
  2. Install SCSM Service Manager

Server2 – MIM Portal and MIM Reporting

  1. Install SharePoint 2016 or SP2013
  2. Install MIM Portal
  3. Install SCSM pre-reqs
  4. Install SCSM Console only
  5. Install MIM Reporting, during setup wizard, put “Server1” as SCSM/MIM Reporting server.