Article ID: 2877254
A hotfix rollup package (build 4.1.3469.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2. This hotfix rollup package resolves some issues and adds some features 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:
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 updateSynchronization 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:
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:
If you install FIM Reporting on a new server that has Microsoft System Center Service Manager 2012 Service Pack 1 installed, follow these steps:
If reporting is enabled and the change-mode installation is run for FIM Service and Portal, you must re-enable reporting. To do this in the FIM Identity Management Portal, 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_kb2877254.msp) package. Additionally, you may have to restart the server components.
Replacement informationThis update replaces the following updates:
(http://support.microsoft.com/kb/2870703/ )A hotfix rollup package (build 4.1.3461.0) is available for Forefront Identity Manager 2010 R2
(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 or features that are added in this updateThis update fixes the following issues or adds the following features that were not previously documented in the Microsoft Knowledge Base.
Issue 1In some rare scenarios in which the Exchange server FIM Service tries to poll approval response email messages, an "ErrorInternalServerTransientError" error is returned. In these scenarios, the FIM Service throws an exception.
After you apply this update, you can configure a retry by setting the following values in the configuration file:
FIM Synchronization Service
Issue 1An Active Directory Management Agent runs an export run profile that is configured to also log an audit file. When there are child objects such as Active Sync devices on the user, the export fails.
Issue 2When an ECMA2 Connector runs an export run profile that is configured to also log an audit file, no objects are exported.
Issue 3FIM synchronization cannot deprovision computer objects in Active Directory when there are other child objects, such as printers and file share objects, present on the computer object.
Issue 4In ECMA2, when the NoAddAndDeleteConfirmation capability is set and an exception is thrown during object export, the exception is processed incorrectly. Additionally, failed objects are marked incorrectly as successful.
Issue 5When an additional object type is added to an already configured ECMA2 Connector, an "Object Reference Not Set" exception is thrown.
Issue 6When you try to stop a running ECMA2 Connector from the user interface (UI), the Sync Engine may crash.
Issue 7A Delete-Add that is sent as a Replace in ECMA2 requires the anchor to be returned from the Connector. This causes issues with the Windows Azure Active Directory Connector when the object is deleted and reprovisioned.
Issue 8When you use an attribute Replace during export to remove the last value from a multivalued attribute, an attribute Replace without values is sent to the Connector. This causes a "The server encountered an unexpected error in the synchronization engine" error to be thrown when the Windows Azure Active Directory Connector is used. After you apply this update, the new behavior is to send this as an attribute Delete to the Connector.
Issue 9When the Set-MIISADMAConfiguration cmdlet is used in a multidomain environment, a corrupted configuration may occur.
Issue 10In build 4.1.3461.0
(http://support.microsoft.com/kb/2870703/ ), a regression occurs that causes import-only attribute flows not to be honored by the UI.
See the terminology
(http://support.microsoft.com/kb/824684/ )Microsoft uses to describe software updates.
Contact us for more help
Connect with Answer Desk for expert help.