A hotfix rollup package (build 4.1.3766.0) is available for Forefront Identity Manager 2010 R2

Introduction

A hotfix rollup package (build 4.1.3766.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2.

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

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

FIM Certificate Management

  • A smart card search takes 3.5 minutes on an idle server. Additionally, the search never ends if the server is stressed.

  • The Duplicate Revocation Settings policy is replaced because some users could not set it.

  • There is a redundant space in the "Profile Summary" string on the Request Complete page for some languages.

FIM Synchronization Service

  • In a metaverse search and when you view the object, there is a Last Modified field. But when you sort that field, it sorts as a generic text field instead of as a date field.

  • Error messages (such as Event ID 6313) are logged in the event log. Additionally, performance counters don't work.

  • The Sync Service crashes when you run a Full Synchronization process that has Equal Precedence set for attributes that exist in IAF or EAF.

  • When an incorrect page size (either less than the minimum or more than the maximum) is used for the run profile of the ECMA2 management agent, the size value quietly changes to the minimum or the maximum after you click Finish.

  • An error message from the Management Agent cannot be parsed if it contains some special symbols. Therefore, the error message doesn't appear in the error list as expected, and a non-informative error window appears.

  • You receive a "Reference to undeclared entity 'qt'" error message when you run the history process and the history text contains the "greater than" symbol (>).

  • Under certain conditions, the file selection dialog box does not appear on the MA configuration wizard pages.

  • A "MEMORY_ALLOCATION_FAILURE" error occurs in the Performance Monitoring tool when the performance data .dll file cannot open the process.

FIM Portal

  • Multivalued labels are displayed incorrectly in a single line in the UI.

FIM Service

  • During an Export process between the Synchronization and FIM Service, the msidmCompositeType request may fail if some multivalued string attribute value is changed in the scope of the Export session. This behavior affects performance.

  • In SharePoint Server 2013 and later versions, if you change a workflow or update an email template by using the FIM Portal, the version is automatically updated to 4.0.0.0. This causes a system error message during processing.

BHOLD

  • When you add a user to an organizational unit (OU) that has some incompatible permissions in the OUs role, all the incompatible permissions are assigned.

  • Some issues are fixed for attribute-based authorization (ABA) roles that are assigned to a user when the roles have incompatible permissions.

  • When you use the Access Management Connector to provision new OUs with a parent OU, all the parent OU roles are inherited but are also disabled.

  • An error occurs in BHOLD during installation in Internet Information Services (IIS) 10.

  • If two or more roles assigned to a user who has the same permissions as the roles, and the roles use the endDate attribute, you cannot extract a user permission that has the latest date.

  • An email alias is truncated if it is longer than 30 characters.

Known issues

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 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, in the MIIServer.exe.config file, you change the default batch size for processing sync entries for the FIM Service MA.

In this case, the synchronization engine installer for this update intentionally does not replace the configuration file 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 in the parent directory. Repeat steps 1 through 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 Microsoft 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.3766.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. In 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 dialog box 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 change.

Update information

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

This update is available from the Microsoft Download Center:

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

For information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

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 of the BHOLD FIM Integration, Access Management Connector or Reporting modules, you must have hotfix rollup package 2934816 (build 4.3.3510.0) or a later build installed on your FIM servers before you apply this update to the BHOLD modules.
 

Restart requirement

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

Replacement information

This update replaces update 2934816 (build 4.1.3510.0) for Forefront Identity Manager 2010 R2.
 

File information

Hotfix release build numbers

Forefront Identity Manager

4.1.3766.0

BHOLD

5.0.3468.0

Access Management Connector

5.0.3468.0

 

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 name

File version

File size

Date

Time

Accessmanagementconnector.msi

Not Applicable

598,016

03-Jul-2016

06:48

Bholdanalytics 5.0.3468.0_release.msi

Not Applicable

2,740,224

03-Jul-2016

06:38

Bholdattestation 5.0.3468.0_release.msi

Not Applicable

3,317,760

03-Jul-2016

07:23

Bholdcore 5.0.3468.0_release.msi

Not Applicable

5,058,560

03-Jul-2016

06:27

Bholdfimintegration 5.0.3468.0_release.msi

Not Applicable

3,571,712

03-Jul-2016

07:00

Bholdmodelgenerator 5.0.3468.0_release.msi

Not Applicable

3,289,088

03-Jul-2016

07:35

Bholdreporting 5.0.3468.0_release.msi

Not Applicable

2,031,616

03-Jul-2016

07:11

Fimaddinsextensionslp_x64_kb3171318.msp

Not Applicable

3,937,280

29-Jun-2016

15:27

Fimaddinsextensionslp_x86_kb3171318.msp

Not Applicable

1,606,656

29-Jun-2016

15:16

Fimaddinsextensions_x64_kb3171318.msp

Not Applicable

5,212,672

29-Jun-2016

15:27

Fimaddinsextensions_x86_kb3171318.msp

Not Applicable

4,661,248

29-Jun-2016

15:17

Fimcmbulkclient_x86_kb3171318.msp

Not Applicable

9,130,496

29-Jun-2016

15:17

Fimcmclient_x64_kb3171318.msp

Not Applicable

5,575,168

29-Jun-2016

15:27

Fimcmclient_x86_kb3171318.msp

Not Applicable

5,201,920

29-Jun-2016

15:17

Fimcm_x64_kb3171318.msp

Not Applicable

33,662,464

29-Jun-2016

15:28

Fimcm_x86_kb3171318.msp

Not Applicable

33,250,304

29-Jun-2016

15:17

Fimservicelp_x64_kb3171318.msp

Not Applicable

12,224,512

29-Jun-2016

15:27

Fimservice_x64_kb3171318.msp

Not Applicable

31,534,080

29-Jun-2016

15:28

Fimsyncservice_x64_kb3171318.msp

Not Applicable

36,344,832

29-Jun-2016

15:28

References

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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×