Support-Release (MIM2016): Microsoft Identity Manager 2016 SP1 hotfix (4.4.1459.0) Released

All,

We have released our latest hotfix for MIM 2016 SP1.  This is build 4.4.1459.

• Support for SQL 2016 Always On Availability Groups: https://blogs.technet.microsoft.com/iamsupport/2017/03/22/microsoft-identity-manager-2016-sp14-4-1459-0-or-later-support-for-sql-2016-always-on-availability-groups/
• SSPR with Web Application Proxy: https://blogs.technet.microsoft.com/iamsupport/2017/03/27/using-microsoft-identity-manager-2016-sp1-portal-self-service-password-reset-with-web-application-proxy/
• Support for SCSM 2016 Reporting: https://blogs.technet.microsoft.com/iamsupport/2017/03/27/microsoft-identity-manager-2016-sp1-portal-4-4-1459-0-or-later-support-for-scsm-2016-reporting/
• Support for FIMService Dynamic Logging: https://blogs.technet.microsoft.com/iamsupport/2017/03/27/microsoft-identity-manager-2016-sp1-portal-4-4-1459-0-or-later-support-for-fimservice-dynamic-logging/
• Support for CustomObject (ExplicitMember) Membership Management: https://blogs.technet.microsoft.com/iamsupport/2017/03/27/microsoft-identity-manager-2016-sp1-portal-4-4-1459-0-or-later-support-for-customobject-explicitmember-membership-management/
• Approval Justification Blog: https://blogs.technet.microsoft.com/iamsupport/2017/03/27/microsoft-identity-manager-2016-sp1-portal-4-4-1459-0-or-later-approval-justification-entry-enhancement/
• Updated Support Platforms: /en-us/microsoft-identity-manager/plan-design/microsoft-identity-manager-2016-supported-platforms
• Certificate Manager Modern Application: https://www.microsoft.com/en-us/download/details.aspx?id=54954
• Microsoft KB Article: https://support.microsoft.com/en-us/help/4012498/hotfix-rollup-package-build-4-4-1459-0-is-available-for-microsoft-iden
• Download: https://www.microsoft.com/en-us/download/details.aspx?id=54952

NOTE: You must be at 4.4.1302.0 prior to installing this fix.  If you are at 4.4.1237.0, you will need to uninstall and install 4.4.1302.0.   For more information, review: https://blogs.technet.microsoft.com/iamsupport/2016/11/08/microsoft-identity-manager-2016-service-pack-1-update-package/

Comments

• Anonymous
  April 19, 2017
  Hello Team,is there a solution for a BAIL error in MIM 2016, when running multiple run profiles at the same time?Kind regards,Peter
  • Anonymous
    April 19, 2017
    Peter, I would ask, which run profiles are you running at the same time and what is the bail error? You might be better suited to open a support case on that one. From a support standpoint, it is supported to stagger the start of Import Run Profiles, or stagger the start of Export Run Profiles. It is not supported to run multiple synchronization run profiles at the same time. There should only ever be one synchronization profile running at any given time. We can find more information about Run Profiles here on the Run Profile Resource Wiki: https://social.technet.microsoft.com/wiki/contents/articles/12529.miisilmfim-2010-run-profiles-resource-wiki.aspxFind more information on Optimizing Run Profiles here: https://blogs.technet.microsoft.com/iamsupport/2015/08/27/info-run-profile-optimization/
    • Anonymous
      April 19, 2017
      It's the 0x8023063d BAIL error, which is thrown when running multiple sync profiles. (Only Sync).It's not a 'bug', although a bail error, as it is explicitly mentioned by Hotfix 4.3.2195.0.1I've documented it at: https://social.technet.microsoft.com/wiki/contents/articles/37758.mim-2016-troubleshooting-unable-to-run-the-management-agent-error-0x8023063d.aspxIt would be nice to update the 2015 post with the new built-in MIM behaviour to avoid any confusion.
• Anonymous
  May 31, 2017
  The comment has been removed
  • Anonymous
    May 31, 2017
    MikeAtUniBZ, if you could obtain a Windows Installer verbose log and send it to me, I will be glad to take a look. timmac@microsoft.com
• Anonymous
  July 28, 2017
  Can this hotfix deploy in a load balanced setting where multiple MIM 2016 Portal & Service instances sharing to the same database for improvement performance and HA?
  • Anonymous
    August 01, 2017
    Yes. This hotfix can be deployed to all of the MIM Service and Portal Servers.We do recommend that you stop the FIM Service on all the Service and Portal machines prior to executing the installation/upgrade.Keep in mind, that the service is started after the install is complete. So you will have to stop it after each successful install.
• Anonymous
  August 30, 2017
  Hi Tim,I configured MIM CM 2016 and everything works fine MIM CM client is able to send request to CA and its rejecting by policy module and we found that CRL is unavailable for Agent account. Later we upgraded the system to MIM CM 2016 SP1, CM client and CA to same version. I am getting a strange error while requesting any certificate from CM portal. Portal UI error: Error connecting to certificate authority: [CA Name] Description: This is in SubscriberEnrollExecute.aspx, page header: Installing certificates and page status is Executing enrollment... Server Event Log error:Event ID: 4104 message: [CA Name] is offlinetrace logs: No errors I am seeing, but its invoking the below method and everything is authenticated."2017-08-29 21:25:05.14 -05" "Microsoft.Clm.BusinessLayer.RequestExecution" "Void CheckCertificateAuthorityAvailable(Microsoft.Clm.Common.AD.UserProfile)" Check that all CAs are available for profile template: Virtual Smart CardAny idea about this error.
  • Anonymous
    August 30, 2017
    I have not seen that error. I would recommend to open a support case and let us do some investigation.
    • Anonymous
      August 31, 2017
      Raghu, Check out this blog. I think this will help you out.https://blogs.technet.microsoft.com/iamsupport/2017/05/17/support-tipcm-fimmim-certificate-management-cm-and-certificate-management-agent-cmagent-certificate-issued-by-a-foreign-certification-authority-ca/