A hotfix rollup package (build 4.0.3644.2) is available for Microsoft Forefront Identity Manager (FIM) 2010. This hotfix rollup package resolves the issues and adds the features that are described in the "More Information" section.
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:
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the issues that are described in this article. Apply this hotfix only to systems that are experiencing the issues that are 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:
To apply this update, you must have Forefront Identity Manager 2010 build 4.0.2592.0 or a later build installed.
You must restart the computer after you apply this update. Additionally, you may have to restart the server components.
This update replaces the following updates:
2737503 A hotfix rollup package (build 4.0.3627.2) is available for Forefront Identity Manager 2010
2688078 A hotfix rollup package (build 4.0.3617.2) is available for Forefront Identity Manager 2010
2635086 Update Rollup 2 (build 4.0.3606.2) is available for Forefront Identity Manager 2010
2520954 A hotfix rollup package (build 4.0.3594.2) is available for Forefront Identity Manager 2010
2502631 A hotfix rollup package (build 4.0.3576.2) is available for Forefront Identity Manager 2010
2417774 A hotfix rollup package (build 4.0.3573.2) is available for Forefront Identity Manager 2010
2272389 A hotfix rollup package (build 4.0.3558.2) is available for Microsoft Forefront Identity Manager (FIM) 2010
2028634 A hotfix rollup package (build 4.0.3547.2) is available for Microsoft Forefront Identity Manager (FIM) 2010
978864 Update Package 1 for Microsoft Forefront Identity Manager (FIM) 2010
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.
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:
Make a backup copy of the MIIServer.exe.config file.
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.
Find the <runtime> section in the MIIServer.exe.config file. Replace the content of the <dependentAssembly> section with the following:
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.
Note You might not have a file that is named Dllhost.exe.config in the parent directory. It is needed only for ECMA1 and ECMA 2.0 management agents that are running out-of-process. If you are running management agents in this mode, copy the MIIServer.exe.config file to the parent folder (..\Synchronization Service), and then rename it "Dllhost.exe.config."
Restart the Forefront Identity Manager Synchronization Service (FIMSynchronizationService).
Verify that the rules extensions and custom management agents now work as expected.
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 126.96.36.199. 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 by 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
The DB2 Management Agent cannot connect to a DB2 server that is running on an IBM iSeries v6 server or a later version.
When the FIM password reset activity does not connect to the Active Directory, the WMI components returns a code. The code explains the reason for this failure.
Common Component (Microsoft.MetadirectoryServicesEx.dll)
Hotfix rollup build 4.0.3644.2 changed the version number of the Microsoft.MetadirectoryServicesEx.dll assembly file to 188.8.131.52. Then, hotfix rollup build 4.0.3617.2 made additional changes to the assembly file but did not change the file version number. Therefore, the file version numbers are mismatched when you try to update the file from version 4.0.3606.2 to later hotfix rollup builds.
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.
Note This assembly file is included in both the FIM Synchronization service and the FIM Service setup files.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.