February 28, 2012
Before blindly applying this update it is critical that you read the release notes, as XMA’s or ECMA’s may not run after the update. If you changed the MIISServer.exe.config file to tweak the FIM MA performance the update won’t replace your file. So you have to make some updates to it by hand. This is documented in the release notes.
There are lots of fixes, my most favorite is that they have rolled back the change I mentioned [ranted about] in a previous blog post: What the %_ is the deal with wildcards in FIM Queries in the latest hotfix?
My next favorite new feature and this one alone will get a separate blog entry, is the release of the ECMA 2.0 (information available on the beta and RC of the ECMA 2.0 here).
A few sync engine crash issues have been fixed.
Support for writing rules extensions in .NET 4.
Update to the update: Do not run the stored procedure mentioned below, it can result in incorrect set query results.
Update: The KB article was updated today and the item dealing with this stored procedure mentioned below has been removed. You should know that this stored procedure is intended to solve a specific performance problem and should only be implemented with guidance from PSS. You should also know that running it is a one-way trip i.e. the only way to undo it is to restore the FIMService database from backup.
Another key item that once more underscores the need to read the release notes, is a fix for the FIM Service dealing with large criteria based sets and groups. In order to take advantage of this performance enhancement it is necessary to run a stored procedure (EXECUTE [fim].[EnableSetPartitioningAndTabularFunctions]) by hand. Based on the name I expect that this procedure is doing some table partitioning, more on that when I get a chance to take a look. (Please see the update above)