Article ID: 2870703 - View products that this article applies to.
A hotfix rollup package (build 4.1.3461.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.
Update informationA supported update is available from Microsoft Support. We recommend that all customers apply this update to their production systems.
Microsoft SupportIf 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 packagesThe following table contains the component update packages that are included in the download from Microsoft Support.
Collapse this tableExpand this table
Known issues in this updateFIM 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 MIIServer.exe, Mmsscrpt.exe.config, or Dllhost.exe.config.
For example, you edit the MIIServer.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. This is done to avoid deleting your previous changes. Because the configuration file is not replaced, entries that are required by this update are not present in the files, and the synchronization engine does 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:
If you install FIM Reporting on a new server that has System Center Service Manager 2012 Service Pack 1 installed, follow these steps:
PrerequisitesTo apply this update, you must have Forefront Identity Manager 2010 R2 (build 4.1.2273.0 or a later build) installed.
Restart requirementYou must restart the computer after you apply the Add-ins and Extensions (Fimaddinsextensions_xnn_kb2870703.msp) package. Additionally, you may have to restart the server components.
Replacement informationThis update replaces the following updates:
(http://support.microsoft.com/kb/2849119/ )A hotfix rollup package (build 4.1.3451.0) is available for Forefront Identity Manager 2010 R2
(http://support.microsoft.com/kb/2832389/ )A hotfix rollup package (build 4.1.3441.0) is available for Forefront Identity Manager 2010 R2
(http://support.microsoft.com/kb/2814853/ )A hotfix rollup package (build 4.1.3419.0) is available for Forefront Identity Manager 2010 R2
(http://support.microsoft.com/kb/2772429/ )Service Pack 1 (build 4.1.3114.0) is available for Forefront Identity Manager 2010 R2
(http://support.microsoft.com/kb/2750671/ )A hotfix rollup package (build 4.1.2548.0) is available for Forefront Identity Manager 2010 R2
(http://support.microsoft.com/kb/2734159/ )A hotfix rollup package (build 4.1.2515.0) is available for Forefront Identity Manager 2010 R2
File informationThe 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.
Collapse this tableExpand this table
Issues that are fixed in this updateThis update fixes the following issues that were not previously documented in the Microsoft Knowledge Base.
FIM BHOLD Suite
Issue 1When you create custom attributes in the BHOLD Core module that are linked to the Permission object type, an import of these permissions into the Metaverse (MV) does not synchronize the attribute values of the custom attributes.
To resolve this issue, run the SQL script in the BHOLD KB2870703.txt file that is contained in this hotfix rollup package against the B1 database.
FIM Synchronization Service
Issue 1When the FIM Service Management Agent runs an export run profile that is configured to also log an audit file, no objects are exported to FIM Service.
Issue 2The FIM Synchronization Service leaks memory during export when an ECMA2 Connector is used.
Issue 3It takes a long time to save a new ECMA2 Connector that has a large schema.
Issue 4ECMA2 Connectors that run in 32-bit mode cannot refresh the schema. This includes the Domino Connector as provided by Microsoft.
Issue 5When you use the ECMA2 distinguished name (DN) capability that is not set as an anchor, the old DN is not present in the export entry if the DN is changed to a new value.
Changed behavior: The DN property always contains the old DN, and the new DN exists as an attribute update.
Issue 6When you edit an existing ECMA2 Connector, you may receive the following error message in some scenarios:
Object reference not set to an instance of an object.
See the terminology Microsoft uses to describe software updates