none
Why MIM Reporting SQL jobs exist, if MIM Reporting is not deployed? RRS feed

  • Question

  • Hi,

    Have just deployed MIM Sync and MIM Service/Portal. Definitely did not deploy MIM Reporting.

    Why does the MIM installer deploy these jobs if they are not required?

    - FIM_CheckAndUpdateReportingJobStatusJob    
    - FIM_TerminateStuckRequestsJob
    - FIM_ScheduleReportingIncrementalSynchronizationJob    
    - FIM_TruncateExportLogJob

    Thanks.

    Friday, April 29, 2016 4:44 AM

Answers

  • To install FIM Service, you have to have sysadmin rights on SQL, after setup is completed, they are not needed. As FIM Reporting can be considered as a feature of FIMService, it can be enabled without the need of sysadmin rights.

    That's why FIMService is "ready" for Reporting even if this option wasn't selected.

    That's the same reason why you can see msidmReportingJob objects in MIM without installing Reporting and PAM navigation links without PAM installed.


    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    • Marked as answer by Shim Kwan Sunday, May 1, 2016 10:09 PM
    Friday, April 29, 2016 11:39 AM

All replies

  • To install FIM Service, you have to have sysadmin rights on SQL, after setup is completed, they are not needed. As FIM Reporting can be considered as a feature of FIMService, it can be enabled without the need of sysadmin rights.

    That's why FIMService is "ready" for Reporting even if this option wasn't selected.

    That's the same reason why you can see msidmReportingJob objects in MIM without installing Reporting and PAM navigation links without PAM installed.


    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    • Marked as answer by Shim Kwan Sunday, May 1, 2016 10:09 PM
    Friday, April 29, 2016 11:39 AM
  • Thank you Dominik.
    Sunday, May 1, 2016 10:09 PM