|
Article ID: 2889529 - View products that this article applies to. On This PageIntroductionA hotfix rollup package (build 4.1.3479.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=support 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.
(http://support.microsoft.com/contactus/?ws=support)
Component update packagesThe following table contains the component update packages that are included in the download from Microsoft Support.Collapse this table
Known issues in this updateSynchronization ServiceAfter 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:
FIM Reporting If you install FIM Reporting on a new server that has 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 be 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_kb2889529.msp) package. Additionally, you may have to restart the server components.Replacement informationThis update replaces the following updates:2877254
(http://support.microsoft.com/kb/2877254/
)
A hotfix rollup package (build 4.1.3469.0) is available for Forefront Identity Manager 2010 R22870703
(http://support.microsoft.com/kb/2870703/
)
A hotfix rollup package (build 4.1.3461.0) is available for Forefront Identity Manager 2010 R22849119
(http://support.microsoft.com/kb/2849119/
)
A hotfix rollup package (build 4.1.3451.0) is available for Forefront Identity Manager 2010 R22832389
(http://support.microsoft.com/kb/2832389/
)
A hotfix rollup package (build 4.1.3441.0) is available for Forefront Identity Manager 2010 R22814853
(http://support.microsoft.com/kb/2814853/
)
A hotfix rollup package (build 4.1.3419.0) is available for Forefront Identity Manager 2010 R22772429
(http://support.microsoft.com/kb/2772429/
)
Service Pack 1 (build 4.1.3114.0) is available for Forefront Identity Manager 2010 R22750671
(http://support.microsoft.com/kb/2750671/
)
A hotfix rollup package (build 4.1.2548.0) is available for Forefront Identity Manager 2010 R22734159
(http://support.microsoft.com/kb/2734159/
)
A hotfix rollup package (build 4.1.2515.0) is available for Forefront Identity Manager 2010 R2File 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 table
More informationIssues that are fixed in this updateThis update fixes the following issues that were not previously documented in the Microsoft Knowledge Base.FIM ServiceIssue 1When you have very long XPath queries in the FIM Service, CPU usage may increase. This causes a decrease in performance.FIM Synchronization ServiceIssue 1The Synchronization Service may leak memory when you use an ECMA2 connector.Issue 2When an existing ECMA2 connector is updated when a server configuration is moved between servers, the update is unsuccessful. This problem occurs when the connector requires access to encrypted parameters, such as a password, to complete the operation.Issue 3When an import is confirmed, a staging error may occur in rare cases. When this problem occurs, you receive the following error message:Cannot insert duplicate key row in object 'dbo.mms_cs_link' Issue 4If during a full import on the Active Directory management agent there is a reference on an organizational unit (OU) to an OU two levels down, the sync engine will crash.Issue 5When you select the option to abandon the key set in the Synchronization Service Key Management Utility, the operation may be unsuccessful. Additionally, you receive the following error message:Value is not in the expected range. BHOLD suiteIssue 1The processing of BHOLD Queue entries takes a longer time than expected to finish after an earlier hotfix is applied.Issue 2You cannot add a permission for a user by using the BHOLD connector if the permission was ever denied for the user.Issue 3The removal of permissions from a personal role (prefixed with PR-) does not trigger the removal of those permissions from the user.ReferencesSee the terminology
(http://support.microsoft.com/kb/824684/
)
Microsoft uses to describe software updates.PropertiesArticle ID: 2889529 - Last Review: November 27, 2013 - Revision: 2.0
|
|

