Hotfix rollup (build 4.1.3627.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2 Service Pack 1

Hotfix release build numbers

File attributes

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

When a customer has installed the FIM Portal, BHOLD FIM Integration, and FIM language packs, a user who views a localized FIM Portal page sees the page revert to English after going to a BHOLD Self-Service page.

Issue 1

When a customer who uses BHOLD Reporting removes a filter from a report, successive reports continue to generate a report as if the filter was not removed.

Issue 1

When you use the BHOLD Model Generator for role mining, and the Retain existing model check box is not selected, an exception may be reported when the BHOLD Model Generator loads files again.

Issue 2

When you use the BHOLD Model Generator for role mining, an exception may be reported when you create membership roles and proposed roles.

Issue 3

When you use the BHOLD Model Generator for role mining, if the user who's running Model Generator does not exist in BHOLD, then attribute roles and ownership roles may not be created.

Issue 4

When the BHOLD Model Generator is run by a different user than who ran it previously or who installed BHOLD Core, and the Retain existing model check box is not selected, an exception may be reported.

Issue 1

When multiple FIM Service computers are deployed, authentication workflow instances for SSPR requests that time out may remain in the Authenticating state indefinitely.

Issue 2

When you set or edit custom integer-valued attributes through the FIM Portal Extended attributes tab of an object, "Particular value is not supported" error message may be displayed for integer values that are greater than 2147483647.

Issue 1

The FIM Certificate Management website incorrectly sends a request to the domain to look up the IdentityOneTimePasswordsRole+ FIM CM internal role.

Issue 2

When you select a user in the FIM CM Portal to manage a smart card, the following exception is triggered:

Issue 3

FIM CM orphans smart cards in the FIMCertificateManagement database if initial enrollment for the smart card is tried under the incorrect profile template. This returns the following exception:

When you repeatedly try to enroll the smart card with the correct profile template, you receive the following error message:

Note After you apply this update rollup, when the wrong profile template fails with the "wrong PIN" exception, the following symptoms occur:

• An incorrect administrator key is detected.

• The smart card object in the database is moved to a retired state, without following the retire policy.

• The user receives a message that states that the operation failed, probably because an incorrect profile template selection, and alternative profile templates are suggested.

Issue 4

Expired or revoked logon certificates are no longer removed from smart card upon renewal in FIM CM.

This update adds functionality to remove certificates from smart cards on certificate expiration or revocation. This is a new option available in the Profile Template General Options settings page.

Issue 1

When the Active Directory global address list (GALSync) management agent is used against an Active Directory forest that hosts Exchange Server 2013, the GALSync solution does not generate the correct value for the msExchVersion attribute.

Issue 2

In a test environment, if there is no available connected data source for a particular kind of management agent, import audit trail files and export audit trail files are sometimes used to test the synchronization service solution functionality. When you use the FIM synchronization engine, this may trigger unexpected results.

The import and export operations seem to work, but on import, the run statistics show a delete and add for each object that's exported to the drop file. Additionally, there are no objects left in the connectorspace.

This behavior occurs because the connectorspace object does not have the anchor value in the hologram as expected. Therefore, the connectorspace object is deleted and is intended to be replaced by the matching object that's being imported. Additionally, the import add operation fails. The following workaround can be used in most scenarios.

Workaround

Important Before you use this workaround, make sure that you have a current backup of the FIMSynchronizationService database.

The steps and SQL script that are documented in this workaround assume that you use a value from the metaverse object to populate the anchor value of new connectorspace objects during provisioning. If the management agent relies on the connected data source to create and provide anchor values for new objects, the provisioning code or synchronization rule may have to be temporarily changed to use a value from the metaverse to support this workaround.

This workaround is provided for a management agent with export and import run profiles configured as follows:

• Export run profile that's configured to create an audit trail file and stop the run

• Import run profile configured to resume from audit trail file

To use this workaround, follow these steps:

1. Run the export run profile.

2. Run the script to update the FIMSynchronizationService database.

3. Run the import run profile.

Sample script

The sample script that's provided here is not intended for use in a production environment and is only meant to address the specific scenario that's documented in this article in a development or test environment.

Before you run this SQL script, it must be changed to replace the management agent identifier (cs.ma_id). If a metaverse attribute other than UID must be used, the script must also be updated to replace all instances of "mv.uid" with the fieldname of the attribute to be used.

/*
 Fix anchor field in CS table for "broken" connectors after export to log file only
 Note:
 "mv.uid" should be fixed with valid field in MV table used as anchor
 "cs.ma_id = '2F2516F6-AD5B-4CFA-9F2B-AA4385D1879E'" should be fixed with valid id of target MA
 in CS table.
*/

update [FIMSynchronizationService].[dbo].[mms_connectorspace]
set [anchor] = cast(reverse(cast(len(mv.uid)*2 as binary(4))) as binary(4))+cast(mv.uid as varbinary(800))
from [FIMSynchronizationService].[dbo].[mms_connectorspace] cs
 join [FIMSynchronizationService].[dbo].[mms_csmv_link] l
  on cs.object_id = l.cs_object_id 
 join [FIMSynchronizationService].[dbo].[mms_metaverse] mv
  on mv.object_id = l.mv_object_id
where cs.ma_id = '2F2516F6-AD5B-4CFA-9F2B-AA4385D1879E' and cs.[anchor] is NULL

Issue 3

When you perform an export run for ECMA 2.0 Export Only MA, you receive the following error message: