Introduction

A hotfix rollup package (build 4.1.3419.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2. This hotfix rollup package resolves some issues that are described in the "More Information" section. Additionally, this update contains all servicing fixes that were made since the release of FIM 2010 R2 hotfix build 4.1.2515.0.

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 following Microsoft websites:

Microsoft Update

http://update.microsoft.com

Microsoft Update Catalog

http://catalog.update.microsoft.com/v7/site/Home.aspx

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:

http://support.microsoft.com/contactus/?ws=supportNote 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.

Component update packages

The following table contains the component update packages that are included in the download from Microsoft Support.

Component

File name

FIM 2010 R2 Add-ins and Extensions

FIMAddinsExtensions_xnn_KB2814853.msp

Note Versions of this file are available for x86-based and x64-based versions of FIM 2010.

FIM 2010 R2 Add-ins and Extensions Language Pack

FIMAddinsExtensionsLP_xnn_KB2814853.msp

Note Versions of this file are available for x86-based and x64-based versions of FIM 2010.



FIM 2010 R2 Certificate Management

FIMCM_xnn_KB2814853.msp

Note Versions of this file are available for x86-based and x64-based versions of FIM 2010.

FIM 2010 R2 Certificate Management Client

FIMCMClient_xnn_KB2814853.msp

Note Versions of this file are available for x86-based and x64-based versions of FIM 2010.

FIM 2010 R2 Service and Portal

FIMService_x64_KB2814853.msp

FIM 2010 R2 Service Portal Language Pack

FIMServiceLP_x64_KB2814853.msp

FIM 2010 R2 Synchronization Service

FIMSyncService_x64_KB2814853.msp

FIM 2010 R2 Certificate Management Bulk Issuance Client

FIMCMBulkClient_x86_KB2814853.msp

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 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 for MIISServer.exe, Mmsscrpt.exe.config, or Dllhost.exe.config. For example, you edited the MIISServer.exe.config file to 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" newVersion="4.1.0.0" />
    <bindingRedirect oldVersion="4.0.0.0" newVersion="4.1.0.0" />
    <bindingRedirect oldVersion="4.0.1.0" newVersion="4.1.0.0" />
    <bindingRedirect oldVersion="4.0.2.0" newVersion="4.1.0.0" />
    <bindingRedirect oldVersion="4.0.3.0" newVersion="4.1.0.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.


Prerequisites

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

Restart requirement

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

Replacement information

This update replaces the following updates:

2772429 Service Pack 1 (build 4.1.3114.0) is available for Forefront Identity Manager 2010 R2

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

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

File information

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

Platform

Fimaddinsextensionslp_x64_kb2814853.msp

Not applicable

3,861,504

15-Feb-2013

07:49

Not applicable

Fimaddinsextensionslp_x86_kb2814853.msp

Not applicable

1,554,432

15-Feb-2013

07:43

Not applicable

Fimaddinsextensions_x64_kb2814853.msp

Not applicable

4,638,208

15-Feb-2013

07:49

Not applicable

Fimaddinsextensions_x86_kb2814853.msp

Not applicable

4,174,336

15-Feb-2013

07:43

Not applicable

Fimcmbulkclient_x86_kb2814853.msp

Not applicable

8,537,088

15-Feb-2013

07:43

Not applicable

Fimcmclient_x64_kb2814853.msp

Not applicable

4,734,464

15-Feb-2013

07:49

Not applicable

Fimcmclient_x86_kb2814853.msp

Not applicable

4,375,040

15-Feb-2013

07:43

Not applicable

Fimcm_x64_kb2814853.msp

Not applicable

28,323,840

15-Feb-2013

07:49

Not applicable

Fimcm_x86_kb2814853.msp

Not applicable

27,951,104

15-Feb-2013

07:43

Not applicable

Fimservicelp_x64_kb2814853.msp

Not applicable

11,494,400

15-Feb-2013

07:49

Not applicable

Fimservice_x64_kb2814853.msp

Not applicable

25,949,696

15-Feb-2013

07:49

Not applicable

Fimsyncservice_x64_kb2814853.msp

Not applicable

34,639,360

15-Feb-2013

07:49

Not applicable



More Information

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

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

FIM Synchronization service

Issue 1

In some cases, the Exchange configuration options on the Active Directory Management Agent do not appear. These options will now always be visible even if Exchange is not detected in the source directory.

Issue 2

When Exchange post-processing PowerShell cmdlets are run during export on the Active Directory Management Agent, the host process can stop for many reasons. In this case, the Active Directory Management Agent continues the export but does not try to run the Exchange cmdlets. With the changed behavior in this fix, the export run is now stopped so that the process can be restarted from where it ended.

Issue 3

The Synchronization service crashes in certain scenarios when references to newly created objects are exported into ECMA2 Connector (also known as "reference retry").

Issue 4

An ECMA1/XMA with call-based export crashes the Synchronization service. This problem occurs in some scenarios in which the following conditions are true:

  • Reference attributes are constantly rejected by the target directory.

  • The Synchronization service is trying to determine which value is causing the problem. It does this by┬átrying to export a multivalued reference attribute as several individual changes (known as "fourth pass reference retry").



Issue 5

A full import might be stuck at the "Completing-Obsoletions" stage if the obsoletion of an object cascades into the obsoletion of related objects.

FIM service and portal

Issue 1

If a user who has access to advanced pages for a group (typically, an administrator) made a change to the object in this view, the group would contain invalid members. If the user was trying to delete the group, the system would be in a state in which no additional requests could be processed.



References

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Need more help?

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

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×