The goal of this article is to provide an overview of the available builds for FIM as well as a short overview of the new features they introduce.
Note: This change involves an extensive upgrade to the sync database. This upgrade can take lots of time, depending on your hardware. A progress bar is displayed during the database upgrade.
A new Connector (formerly Management Agent) development framework that is named Extensible Connectivity Management Agent 2.0 (ECMA2.0) is included. This is listed as a new entry in the Management Agent
The FIM Synchronization Service now supports running the Microsoft .NET Framework 4 extension code. This can be used both in rules extension and for Management Agents such as the ECMA 262 language specification
version 2.0. The FIM Synchronization Service will auto detect the latest version of the .NET Framework on the server. If it is needed, you can disable the .NET Framework 4 by removing it from the Runtime section in the Miiserver.exe.config file.
Hotfix rollup 2520954 removed support for using the following characters as SQL wildcard characters in queries, in dynamic group filters, and in set filters.
The functionality of some existing customer deployments may use these characters as wildcard characters. This update reverts the earlier change.
IMPORTANT: FIM 2010 Update Rollup 2 (build 4.0.3606.2) contains a feature that is intended to improve Query
performance in the case of certain complex queries. This “tabular functions” feature is turned off by default. The product team has discovered an issue in this feature that could return incorrect query results when the query includes at least two statements
and the same attribute is referenced in the statements. We strongly advise customers NOT to turn on the Set Partition feature.
Fixed issues in the Sync Engine (ECMA 2.0, ECMA 1.0 and organizational unit provisioning related)
Fixed issues in setup (database upgrade & change/remove installation related)
Fixed issues in the Sync Engine
Fixed issues in the FIM Service MA (.net 4.0 bug, additional logging for FIM MA exceptions)
Fixed DB2 MA issue when connecting to a server that is running on an IBM iSeries V6 server or a later.
When the FIM password reset activity does not connect to the Active Directory, the WMI components now return an error code.
Fixed .NET version numbers in Microsoft.MetadirectoryServicesEx.dll as changes occurred in build 4.0.3617.2, but the version number was not incremented.
Fixed Exchange configuration options on the Active Directory Management Agent
After installing 4.0.3576.2 you may find your FIM MA exports start failing with a "The request does not conform to the expected request message format of the protocol" exception ... and if you do, chances are you have been using a different service account identity for your FIM MA to that which you specified when you installed the FIM Service. If you get to this point you will need to (a) find out the service account you should be using (HKLM->System->CurrentControlSet->services->FIMService->SynchronizationAccount) and (b) change the FIM MA identity back to this value.
If you then find that you are getting a "Failed to connect to the specified database or Forefront Identity Manager Service. Please check the specified database location, service host address, and account information" error thrown, the problem is database connectivity. Your case might be different, but mine is a lab environment where the FIM Sync Service is also a DC ... I followed the advice of this article - crosbysite.blogspot.com/.../fim-service-management-agent-creation.html - and added the service account to the domain builtin administrators group and I was good again (not that this is a sensible production configuration!).
Correction to my post a few minutes ago ... the problem is indirectly database access, but what I meant to say is that the error is because of missing local logon rights for the FIM MA account.
I would like to get info in the hotfix released notes for Windows 2008 R2 SP1 support, and regarding OS pacth support after SP1
Build 4.0.3594.2 is out: support.microsoft.com/.../en-us
-export the current time on the server to the HTTPPasswordChangeDate field during the password set operation.
-Honor the Active Directory Management Agent (AD MA) the preferred domain controller list when passwords are exported.Feature 3
-Adds the ability to filter objects before they are imported into the AD MA connector space.
-Adds new options to the Storechk.exe tool to enable it to remove orphaned rule fragments that are associated with an MA.
Update Rollup 2 (build 4.0.3606.2) (support.microsoft.com/.../2635086) is out.
RSS feed is not updated yet :(
Please, be aware of the following issue: social.technet.microsoft.com/.../fc8c75bf-65af-453c-9dd7-4bd7557be968