Hotfix rollup package (build 4.1.3671.0) for Forefront Identity Manager 2010 R2

Introduction
A hotfix rollup package (build 4.1.3671.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2. This rollup package resolves the issues and adds the features that are described in the "More Information" section.

Update information

A supported update is available from Microsoft Support. We recommend that all customers apply this update to their production systems.

Microsoft Support

If this update is available for download from Microsoft Support, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Additionally, you can obtain the update from Microsoft Update or from Microsoft Update Catalog.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Known issues in this update

Synchronization Service
After this update is installed, rules extensions and custom management agents (MAs) that are based on Extensible MA (ECMA1 or ECMA 2.0) may not run, and they may produce a run status of "stopped-extension-dll-load." This issue occurs when you run such rules extensions or custom MAs after you change the configuration file (.config) for one of the following processes: 
  • MIIServer.exe
  • Mmsscrpt.exe
  • Dllhost.exe
For example, this issue may occur when you edit the MIIServer.exe.config file to change the default batch size for processing sync entries for the FIM Service MA.

In this situation, the synchronization engine installer for this update does not replace the configuration file in order to avoid deleting your previous changes. Because the configuration file is not replaced, entries that are required by this update will not be present in the files, and the synchronization engine will not load any rules extension DLLs when the engine runs a Full Import or Delta Sync run profile.

To resolve this issue, follow these steps:
  1. Make a backup copy of the MIIServer.exe.config file.
  2. Open the MIIServer.exe.config file in a text editor or in Microsoft Visual Studio.
  3. Find the <runtime> section in the MIIServer.exe.config file, and then replace the content of the <dependentAssembly> section with the following:

    <dependentAssembly><assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />        <bindingRedirect oldVersion="3.3.0.0-4.1.3.0" newVersion="4.1.4.0" /></dependentAssembly>
  4. Save the changes to the file.
  5. Find the Mmsscrpt.exe.config file in the same directory and the Dllhost.exe.config file in the parent directory. Repeat steps 1–4 for these two files.
  6. Restart the Forefront Identity Manager Synchronization Service (FIMSynchronizationService).
  7. Verify that the rules extensions and custom management agents now work as expected.

FIM Reporting
If you install FIM Reporting on a new server that has System Center 2012 Service Manager Service Pack 1 installed, follow these steps:
  1. Install the FIM 2010 R2 SP1 FIMService component. To do this, clear the Reporting check box.
  2. Install this hotfix rollup to upgrade the FIM Service to build 4.1.3671.0.
  3. Run the change-mode installation for the FIM Service, and then add Reporting.

If reporting is enabled and the change-mode installation is run for FIM Service and Portal, you must be re-enable reporting. To do this in the FIM Identity Management Portal, follow these steps:
  1. On the Administration menu, click All Resources.
  2. Under All Resources, click System Configuration Settings.
  3. Click the System Configuration Settings object, and then open the Properties of this object.
  4. Click Extended Attributes, and then select the Reporting Logging Enabled check box.
  5. Click OK, and then click Submit to save the changes.

Prerequisites

To apply this update, you must have Forefront Identity Manager 2010 R2 (build 4.1.3419.0 or a later build) installed.

For BHOLD deployments, you must have hotfix rollup package 2934816 (build 4.1.3510.0) installed to apply this update.

Restart requirement

You must restart the computer after you apply the Add-ins and Extensions (Fimaddinsextensions_xnn_kb3092178.msp) package. You may also have to restart the server components.

Registry information

To use one or more of the hotfixes in this update, you must edit the registry.

Replacement information

This update replaces update 3054196 (build 4.1.3646.0) for Forefront Identity Manager 2010 R2.

File information

Hotfix release build numbers
Forefront Identity Manager 4.1.3671.0 
BHOLD 5.0.3176.0 
Access Management Connector 5.0.3176.0 

File attributes
The global version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File nameFile versionFile sizeDateTimePlatform
Accessmanagementconnector.msiNot Applicable671,74402-Sep-201507:20Not Applicable
Bholdanalytics 5.0.3176.0_release.msiNot Applicable2,707,45602-Sep-201507:09Not Applicable
Bholdattestation 5.0.3176.0_release.msiNot Applicable3,293,18402-Sep-201508:01Not Applicable
Bholdcore 5.0.3176.0_release.msiNot Applicable5,029,88802-Sep-201506:29Not Applicable
Bholdfimintegration 5.0.3176.0_release.msiNot Applicable3,543,04002-Sep-201507:34Not Applicable
Bholdmodelgenerator 5.0.3176.0_release.msiNot Applicable3,268,60802-Sep-201508:14Not Applicable
Bholdreporting 5.0.3176.0_release.msiNot Applicable1,998,84802-Sep-201507:47Not Applicable
Fimaddinsextensionslp_x64_kb3092178.mspNot Applicable3,959,29616-Sep-201514:17Not Applicable
Fimaddinsextensionslp_x86_kb3092178.mspNot Applicable1,622,01616-Sep-201514:12Not Applicable
Fimaddinsextensions_x64_kb3092178.mspNot Applicable5,234,17616-Sep-201514:17Not Applicable
Fimaddinsextensions_x86_kb3092178.mspNot Applicable4,685,82416-Sep-201514:12Not Applicable
Fimcmbulkclient_x86_kb3092178.mspNot Applicable9,164,28816-Sep-201514:12Not Applicable
Fimcmclient_x64_kb3092178.mspNot Applicable5,619,71216-Sep-201514:17Not Applicable
Fimcmclient_x86_kb3092178.mspNot Applicable5,235,71216-Sep-201514:12Not Applicable
Fimcm_x64_kb3092178.mspNot Applicable33,739,77616-Sep-201514:17Not Applicable
Fimcm_x86_kb3092178.mspNot Applicable33,312,76816-Sep-201514:12Not Applicable
Fimservicelp_x64_kb3092178.mspNot Applicable12,647,42416-Sep-201514:17Not Applicable
Fimservice_x64_kb3092178.mspNot Applicable31,865,34416-Sep-201514:17Not Applicable
Fimsyncservice_x64_kb3092178.mspNot Applicable36,420,09616-Sep-201514:17Not Applicable


More information

Issues that are fixed or features that are added in this update

This update also fixes the following issues or adds the following features that were not previously documented in the Microsoft Knowledge Base.

FIM add-ins and extensions

Issue 1
This hotfix addresses an issue in the password reset window that occurs on displays that have high DPI settings when the Windows display sizing of items is set to a custom size, such as 200% or more.

FIM Certificate Management

Issue 1
If you try to enroll a smart card that has the correct profile selected (and the correct adminKey), but the user PIN does not correspond to the smart card PIN policy, you receive the following error message:

The card cannot be accessed because the wrong PIN was presented.


FIM Synchronization Service

Issue 1
When you configure an ECMA2 run profile, you receive the following exception:

Value of ‘10’ is not a valid value


Issue 2
The Sync Engine reports a staging error during delta import when the Generic LDAP connector detects the renaming of the distinguished name for an object.

Issue 3
During the export run DN modification of a user, an object is deleted from a group membership in Oracle Directory Enterprise Edition (ODSEE) instead of changing the DN LDAP.

Issue 4
When you try to select an OU that contains more than 4,000 sub-OUs on the Directory Partitions tab, you receive the following error message:

The administrative size limit on the server was exceeded.


Issue 5
When you perform an Export, CS Search, or CS Deletion during ECMA2 Export Only, the MA displays the following error message:

The image or delta doesn't have an anchor.


Issue 6
The Sync Service stops responding because of high CPU usage when you stop a run profile for the ECMA connector.

Issue 7
When you have characters in the SMTP address that are unsupported by Exchange Server, a GALSync Export operation stops, and you receive an ma-extension error. This triggers a provisioning loop that causes object duplication.

FIM Portal

Issue 1
This hotfix addresses an issue in the FIM Portal that affects sorting a customized list view that's based on the columns specified in the ColumnsToDisplay field.

Issue 2
This hotfix updates HTML elements and attributes in the password registration portal and the FIM Portal.

Issue 3
The object picker does not search objects that contain special characters in their file names.

Issue 4
This hotfix updates the translation into Russian of the user interface strings that relate to “Password Reset AuthN Workflow” activity.

Issue 5
This hotfix addresses an issue that affects the Leave and Remove Member buttons when the group resource type is customized.

Issue 6
This hotfix adds a new search scope (All Groups) to enable searching for and joining groups if the user does not know whether the group is a security group or a distribution list.

FIM Service

Issue 1
This hotfix addresses an issue in which broker service conversations are not closed after an export from FIM Sync to the FIM Service database.

Issue 2
When there are too many negative conditions in the Group Criteria, the SQL & FIM service stop running.

Issue 3
SET filter definitions are unsuccessful during save after you upgrade to version 4.1.3634.0.

Issue 4
When you use the CustomExpression option, the Concatenate operator is replaced with the "+" character. This triggers an error when it saves.

Issue 5
This hotfix addresses an issue that affects FIM Service database stored procedures. Specifically, deadlocks might occur in approval workflows. This issue occurs particularly in deployments with complex or general Set definitions such as sets matching "/*" instead of with specific resource types.

BHOLD

Issue 1
There's an inconsistency between the Permission name and the value if an attribute changes. After Export\Import\Export flow in FIM Sync, BHOLD receives duplicates of a renamed group and retains the original group in the database.

References
Learn about the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3092178 - Last Review: 01/20/2016 02:08:00 - Revision: 2.0

  • kbqfe kbsurveynew kbautohotfix kbhotfixserver kbfix kbexpertiseinter kbbug KB3092178
Feedback