# A hotfix rollup package (build 4.1.3419.0) is available for Forefront Identity Manager 2010 R2 ## 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 section in the MIIServer.exe.config file, and then replace the content of the section with the following: `