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

Applies to: Forefront Identity Manager 2010 R2


A hotfix rollup package (build 4.1.2548.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2. The hotfix rollup package resolves the issues and adds the features that are described in the "More Information" section. Additionally, this hotfix rollup contains all servicing fixes that were released since the release of FIM 2010 R2.


Hotfix rollup information

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

Microsoft Support

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, 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.

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, visit 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.

Component update packages

The following files are available for download from the Microsoft Download Center:
ComponentFile name
FIM 2010 R2 Add-ins and ExtensionsFIMAddinsExtensions_xnn_KB2750671.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 PackFIMAddinsExtensionsLP_xnn_KB2750671.msp

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

Note Versions of this file are available for x86-based and x64-based versions of FIM 2010.
FIM 2010 R2 Certificate Management ClientFIMCMClient_xnn_KB2750671.msp

Note Versions of this file are available for x86-based and x64-based versions of FIM 2010.
FIM 2010 R2 Service and PortalFIMService_x64_KB2750671.msp
FIM 2010 R2 Service Portal Language PackFIMServiceLP_x64_KB2750671.msp
FIM 2010 R2 Synchronization Service FIMSyncService_x64_KB2750671.msp
FIM 2010 R2 Certificate Management Bulk Issuance ClientFIMCMBulkClient_x86_KB2750671.msp


To apply this hotfix, you must have FIM 2010 R2 (build 4.1.2273.0) installed.

Restart requirement

You must restart the computer after you apply the FIM 2010 R2 Add-ins and Extensions component. Additionally, you may have to restart the server components.

Replacement Information

This update replaces the following update:
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 nameFile sizeDateTime

More Information

Known issues in this update

After you install this update, 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.
    • Make sure that you open the text editor by using the Run as Administrator option so that Windows will let you save the changes.
    • If you do not open the text editor by using the Run as Administrator option, and if the UserAccountControl option is enabled, Windows will not let the file be saved to the \bin folder.
  3. Find the <runtime> section in the MIIServer.exe.config file, and then replace the content of the <dependentAssembly> section with the following:
    <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="" newVersion="" />
    <bindingRedirect oldVersion="" newVersion="" />
    <bindingRedirect oldVersion="" newVersion="" />
    <bindingRedirect oldVersion="" newVersion="" />
  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.

More information

Included in this hotfix package is a new version of the Microsoft.MetadirectoryServicesEx.dll file (also known as the interface DLL). This new version is If you have MA extensions for ECMA1/XMA, ECMA 2.0, or rules extensions, you might have to take additional actions for these extensions to continue working. This is because your DLL will have references to an earlier version (4.0.x.0). There are three files that have binding redirect information. They are used as follows:
  • MIIServer.exe.config: All ECMA1 and ECMA2.0 management agents and all rules extensions that are running in-process
  • Mmsscrpt.exe.config: All rules extensions that are running out-of-process
  • Dllhost.exe.config: All ECMA1 and ECMA2.0 management agents that are running out-of-process

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


This hotfix addresses an issue in which the digital signature on files that are produced and signed by Microsoft will expire prematurely, as described in Microsoft Security Advisory 2749655.

FIM Synchronization Service

Issue 1
When you use the IIF function in an outbound synchronization rule, the function can evaluate the result to "Null." For example, this may occur when a value in the metaverse is removed from an object. In this situation, it is expected that the attribute value in the target connector space is also deleted because the contributed attribute value is "Null."
Issue 2
When you pass the LoginAccountSID property to the ExchangeUtils:CreateMailbox method, administrator permissions are required in Active Directory Domain Services.

FIM Service

New feature
When the FIM password reset activity does not connect to Active Directory, the Windows Management Instrumentation (WMI) components return a code. The code explains the reason for this failure.

FIM Reporting

When you perform the "Transform.Common" job when FIM 2010 is operating under a heavy load, the job fails because of a time-out. The time-out occurs when the computer processes the TransformEntityRelatesToEntityFact module.

Common Component (Microsoft.MetadirectoryServicesEx.dll)

Hotfix rollup build 4.1.2515.2 changes information in the Microsoft.MetadirectoryServicesEx.dll assembly file but does not change the file version number. Therefore, the file version numbers are mismatched when you try to update the file from version 4.1.2273.0 to version 4.1.2515.0.

When this issue occurs, you may experience the following symptoms:
  • You cannot load and run a custom management agent.
  • You cannot create a new FIM service management agent.
  • After you apply this hotfix rollup, the version of the Microsoft.MetadirectoryServicesEx.dll assembly file is
  • The Microsoft.MetadirectoryServicesEx.dll assembly file is included in both the FIM Synchronization service and the FIM Service setup files.


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