Forefront Identity Manager 2010 R2 build 4.1.3613.0 released

  • Article

Today, Tuesday November 25th, saw Microsoft release a new hotfix rollup package (build 4.1.3613.0) for Forefront Identity Manager 2010 R2.  The official documentation for this build can be found on the Microsoft support website under knowledgebase (KB) article 3011057.  Download link is here.  This build supersedes 4.1.3559.0. The hotfix contains a number of updates:

  • BHOLD Attestation – 1 update
  • BHOLD Core – 1 update
  • BHOLD Core and FIM Provisioning – 3 updates
  • FIM Certificate Management – 2 updates
  • FIM Clients – 1 update
  • FIM Service and IdentityManagement Portal – 2 updates
  • FIM Synchronization Service – 3 updates
  • PCNS – 1 update

Full details of the update, duplicated from the KB for posterity, follow.  Hit the KB for the known issues and other details.

BHOLD Attestation

Issue 1

Symptoms:

  • When a steward is added to an in-progress campaign, the steward receives the “New entries for Steward” email.

Changes after the fix:

  • When a steward is added to an in-progress campaign, the steward receives the “Instance Start” email.

BHOLD Core

Issue 1

Symptoms:

  • When a user has conflicting ABA roles, and the user’s “EndDate” field is changed through the BHOLD Core UI, the user may be assigned an incorrect role.

Changes after the fix:

  • Changing the user’s “EndDate” field does not affect any other ABA role attributes.

BHOLD Core and FIM provisioning

Issue 1

When you use the Access Management Connector, and an import is performed immediately following an export that caused ABA role membership changes, the import may indicate that users have fewer permissions than are assigned by either their previous or new role memberships. After you install this fix:

  • If an import is performed immediately following an export that caused ABA role membership changes, the import indicates that users have the permissions assigned by either their previous or new role memberships. After queue processing is completed, the import indicates that users have the permissions that are assigned by their new role memberships.

Issue 2

In some deployments, deletion of multiple groups through the Access Management Connector is not successful if there are two or more pending exports. After you install the fix:

  • The deletion of multiple groups through the Access Management Connector is successful.

Issue 3

In some deployments, export of changes through the Access Management Connector to OU objects that specify a new parent OU do not take effect. After you install the fix:

  • A Parent OU can be changed from root to any other OU through the Access Management Connector.

FIM Certificate Management

Issue 1

Online certificate updates are failing because of a constraint violation.

Issue 2

The FIM Certificate Management (CM) exit module does not honour the CT_FLAG_DONOTPERSISTINDB flag on a certificate. This may cause many certificates to be written to the FIM CM database. This, in turn, causes performance issues. After you install this fix:

  • The FIM CM exit module honours the CT_FLAG_DONOTPERSISTINDB flag on certificates, and those certificates are not written to the FIM CM database.

FIM Clients (Portal, Outlook, Windows logon)

Issue 1

After you install the FIM Windows logon extension, and then you (or a user) try to log on to the computer through a remote desktop, you must enter your credentials two times. After you apply the fix, remote desktop logons work as expected.

FIM Service and IdentityManagement Portal

Issue 1

Some text that is displayed in the FIM Portal and added to email templates always uses the English language. For example, this issue occurs in the Display Name of Approval objects. After you install the fix:

  • The string translation for objects that are created by the FIM Service in the FIM Service database is performed according to the FIM Service account locale that was in effect when the object was created. Note that this functionality is not affected by the client browser locale.

To change the language that is used for string translation to a setting other than English, log on to each computer where the FIM Service is installed as the FIM Service account, and then set the locale for this account through Control Panel.

Issue 2

Creating synchronization rules in the FIM IdentityManagement Portal fails to load connected system object types in the External System Resource Type drop-down list. This behavior may occur if the size of the connector instance definition (ma-data) is larger than the 14 MB default WCF message size limit in the ResourceManagementClient configuration. This size is configured by using the maxReceivedMessageSizeInBytes property of the ResourceManagementClient. Before you apply this fix:

  • maxReceivedMessageSizeInBytes values that are configured in the web.config for the IdentityManagement Portal are ignored in favor of the default setting.

After you apply this fix:

  • The maxReceivedMessageSizeInBytes setting is applied.

Note that this setting is case-sensitive. For more information about this setting, go to the following Microsoft website: Registry keys and configuration file settings in FIM 2010

FIM Synchronization Service

Issue 1

The Synchronization Service crashes during an Export run profile run on a SQL Server management agent.

Issue 2

When you run a Delta Import on the FIM Service management agent, the MIIServer.exe process terminates with a CLR_EXCEPTION_SYSTEM.APPDOMAINUNLOADEDEXCEPTION exception. After you install this fix, the race condition that triggers this exception no longer occurs.

Issue 3

If a synchronization rule uses the NULL() function in an incoming attribute flow rule, returning NULL() is seen as a value instead of being blank, and attribute precedence does not continue to the next precedent incoming attribute flow. After you apply this fix, attribute flow precedence on incoming attribute flow rules that use the NULL() function works as expected.

Password Change Notification Service (PCNS)

Issue 1

The following error message is logged:

  • 6914 The connection from a password notification source failed because it is not a Domain Controller service account.

After you install this fix, adding a backslash character to a domain name causes the function to return the domain controller Security Identifier (SID) instead of an empty user SID.