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:
<dependentAssembly>
<assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="3.3.0.0" newVersion="4.0.2.0" />
<bindingRedirect oldVersion="4.0.0.0" newVersion="4.0.2.0" />
<bindingRedirect oldVersion="4.0.1.0" newVersion="4.0.2.0" />
</dependentAssembly>
- Save the changes to the file.
- 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.
More informationIncluded in this hotfix package is a new version of the Microsoft.MetadirectoryServicesEx.dll file (also known as the interface DLL). This new version is 4.0.2.0. 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
General
Issue
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
Issue
The DB2 Management Agent cannot connect to a DB2 server that is running on an IBM iSeries v6 server or a later version.