Update Rollup 2 (build 4.0.3606.2) is available for Forefront Identity Manager 2010

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, visit 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 available for download from Microsoft Support.

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 the FIM 2010 Add-ins and Extensions component. Additionally, you may have to restart the server components.

Registry information

To use one or more of the hotfixes in this update, you may have to change the registry. The following issues and features may require a registry change.

Replacement information

This update replaces the following updates:

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

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.

Issue 1

After you install Update Rollup 2, rules extensions and custom management agents that are based on the Extensible MA (ECMA) may not run, with a run status of "stopped-extension-dll-load." This issue occurs when you run such rules extensions or custom MAs and you had previously changed the configuration file for MIISServer.exe. For example, you might have edited the 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 in order to avoid deleting your previous changes. Because the configuration file is not replaced, entries that are required by Update Rollup 2 will not be present in the file, and the Sync Engine will not load any rules extension .dlls when it runs a Full Import or Delta Sync run profile.

To correct 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 Visual Studio.

   • Make sure that you open the text editor by using the Run as Administrator option so Windows will let you save the changes.

   • If you do not open the text editor by using the Run as Administrator option and the UserAccountControl option is enabled, Windows will not let the file be saved to the \bin folder.

3. Make the following change in the file.
   
   Current text:

   <bindingRedirect oldVersion="3.3.0.0" newVersion="4.0.0.0" />

   
   Updated text:

   <bindingRedirect oldVersion="3.3.0.0" newVersion="4.0.1.0" />

4. Insert the following line directly under the line that you changed in step 3:

   <bindingRedirect oldVersion="4.0.0.0" newVersion="4.0.1.0" />

5. Locate the following line:

   <startup useLegacyV2RuntimeActivationPolicy="true">

6. Insert the following line directly under the line that you located in step 5:

   <supportedRuntime version="v4.0.30319"></supportedRuntime>

7. Make sure that the startup section resembles the following (ordering is important):

   <startup useLegacyV2RuntimeActivationPolicy="true">
     <supportedRuntime version="v4.0.30319"></supportedRuntime>
     <supportedRuntime version="v2.0.50727"></supportedRuntime>
   </startup>

8. Save the changes to the file.

9. Restart the Forefront Identity Manager Synchronization Service (FIMSynchronizationService).

10. Verify that the rules extensions and custom management agents now work as expected.

More information

Together with Update Rollup 2, we included a new version of Microsoft.MetadirectoryServicesEx.dll (a.k.a. interface DLL). This is version 4.0.1.0. If you have MA extensions for ECMA1/XMA 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 version 4.0.0.0 (the older version). If your Management Agent is 64-bit and is running in-proc, the binding redirects in Miiserver.exe.config will be sufficient, and you do not have to take any further action. If your Management Agent is running out-of-proc, either as 32-bit or as 64-bit, you have to take one of the following actions:

• Recompile your Management Agent Extension, and reference the new 4.0.1.0 version of the interface DLL.

• Copy Miiserver.exe.config to the folder %Program Files%\Microsoft Forefront Identity Manager\2010\Synchronization Service, and then rename it as "Dllhost.exe.configwo."

The important section in this config file is the binding redirect. This allows processes that are running out-of-proc to find the new version of the interface DLL. If rules extensions are not working together with Update Rollup 2, verify that the Mmsscrpt.exe.config file in the bin folder has the same binding redirect statements that are described for Miiserver.exe.config in this Microsoft Knowledge Base article. These statements would be missing only if the config file was changed outside the setup process.

Schema

FIM Synchronization Service

Sets and query

FIM Service MA

FIM Service

Outlook add-in

Declarative provisioning