Jorge's Quest For Knowledge!

All You Need To Know About Identity And Security On-Premises And In The Cloud. It's Just Like An Addiction, The More You Have, The More You Want To Have!

(2013-10-17) A Hotfix Rollup Package (Build 4.1.3479.0) Is Available for Forefront Identity Manager 2010 R2

Posted by Jorge on 2013-10-17


Microsoft released a new hotfix for FIM 2010 R2 with build 4.1.3479.0. What it fixes can be found in this blog post. For additional or detailed info see MS-KBQ2889529

Issues that are fixed or features that are added in this update
FIM Service
Issue 1

When you have very long XPath queries in the FIM Service, CPU usage may increase. This causes a decrease in performance

FIM Synchronization Service
Issue 1

The Synchronization Service may leak memory when you use an ECMA2 connector.

Issue 2

When an existing ECMA2 connector is updated when a server configuration is moved between servers, the update is unsuccessful. This problem occurs when the connector requires access to encrypted parameters, such as a password, to complete the operation.

Issue 3

When an import is confirmed, a staging error may occur in rare cases. When this problem occurs, you receive the following error message:

Cannot insert duplicate key row in object ‘dbo.mms_cs_link’

Issue 4

If during a full import on the Active Directory management agent there is a reference on an organizational unit (OU) to an OU two levels down, the sync engine will crash.

Issue 5

When you select the option to abandon the key set in the Synchronization Service Key Management Utility, the operation may be unsuccessful. Additionally, you receive the following error message:

Value is not in the expected range

BHOLD Suite
Issue 1

The processing of BHOLD Queue entries takes a longer time than expected to finish after an earlier hotfix is applied.

Issue 2

You cannot add a permission for a user by using the BHOLD connector if the permission was ever denied for the user.

Issue 3

The removal of permissions from a personal role (prefixed with PR-) does not trigger the removal of those permissions from the user.

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER:
https://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
#########
http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: