A hotfix rollup package (build 4.0.3733.2) is available for Forefront Identity Manager 2010

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

Microsoft Update Catalog

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: 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.

Component update packages

The following table contains the component update packages that are included in the download from Microsoft Support.

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 (.config) for one of the following processes:

• MIIServer.exe
• Mmsscrpt.exe
• Dllhost.exe

For example, assume that you edit the MIIServer.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 does not replace the configuration file in order to avoid deleting your previous changes. Because the configuration file is not replaced, entries that are required by this update are not present in the files, and the synchronization engine does not load any rules extension DLL files 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.
   • 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.
3. Find the <runtime> section in the MIIServer.exe.config file, and then replace the contents 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

4. Save the changes to the file.
5. Find the Mmsscrpt.exe.config file in the same directory and the Dllhost.exe.config in the parent directory. Repeat steps 1–4 for these two files.
   
   Note You might not have a file that's 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 as "Dllhost.exe.config."
   
6. Restart the Forefront Identity Manager Synchronization Service (FIMSynchronizationService).
7. Verify that the rules extensions and custom management agents now work as expected.

Microsoft.MetadirectoryServicesEx.dll

This hotfix package includes an updated version of the Microsoft.MetadirectoryServicesEx.dll file (also known as the interface DLL). This interface DLL file is updated from the original release version and is now version 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 to make sure that these extensions continue to work. 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, and 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

Prerequisites

To apply this update, you must have Forefront Identity Manager 2010 build 4.0.2592.0 or a later build installed.

Restart requirement

You must restart the computer after you apply this update. Additionally, you may have to restart the server components.

Replacement information

This update replaces the following updates:

File information

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.

Issues that are fixed or features that are added in this update

This update fixes the following issue that was not previously documented in the Microsoft Knowledge Base.

FIM Synchronization Service

Issue 1

If a multivalued attribute is exported and then changed directly in the target system, the change is not evaluated during delta synchronization. For example, this issue occurs in the following scenario when the Active Directory Management Agent is used:

1. A change to proxyAddresses is exported to the Active Directory for User1.
2. A second change is made to proxyAddresses directly in Active Directory outside the synchronization service.
3. A Delta Import run profile is run to confirm the exported changes.

The next delta sync will not process the change.