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

Applies to: Microsoft Forefront Identity Manager 2010 R2 Service Pack 1

Introduction


A hotfix rollup package (build 4.1.3627.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2 Service Pack 1 (SP1). The build number for BHOLD components that are included in this release is 5.0.2959.0. This hotfix rollup resolves some issues and adds some features that are described in the "More Information" section.

Update information

A supported update is available from Microsoft Support. We recommend that all customers apply this update to their production systems.

Microsoft Support

If this update is available for download from Microsoft Support, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Additionally, you can obtain the update from Microsoft Update or from Microsoft Update Catalog.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Known issues in this update

Synchronization Service

After this update is installed, rules extensions and custom management agents (MAs) that are based on Extensible MA (ECMA1 or ECMA 2.0) may not run and may produce a run status of "stopped-extension-dll-load." This issue occurs when you run such rules extensions or custom MAs after you change the configuration file (.config) for one of the following processes:
  • MIIServer.exe
  • Mmsscrpt.exe
  • Dllhost.exe
For example, assume that you edit the MIIServer.exe.config file to change the default batch size for processing sync entries for the FIM Service MA.
In this situation, the synchronization engine installer for this update intentionally does not replace the configuration file to avoid deleting your previous changes. Because the configuration file is not replaced, entries that are required by this update are not present in the files. Therefore, the synchronization engine will not load any rules extension DLLs when the engine runs a Full Import or Delta Sync run profile.

To resolve this issue, follow these steps:
  1. Make a backup copy of the MIIServer.exe.config file.
  2. Open the MIIServer.exe.config file in a text editor or in Microsoft Visual Studio.
  3. Find the <runtime> section in the MIIServer.exe.config file, and then replace the contents of the <dependentAssembly> section with the following:

    <dependentAssembly>
    <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="3.3.0.0-4.1.3.0" newVersion="4.1.4.0" />
    </dependentAssembly

  4. Save the changes to the file.
  5. Find the Mmsscrpt.exe.config file in the same directory and the Dllhost.exe.config in the parent directory. Repeat steps 1–4 for these two files.
  6. Restart the Forefront Identity Manager Synchronization Service (FIMSynchronizationService).
  7. Verify that the rules extensions and custom management agents now work as expected.

FIM Reporting

If you install FIM Reporting on a new server that has Microsoft System Center 2012 Service Manager SP1 installed, follow these steps:
  1. Install the FIM 2010 R2 SP1 FIMService component. To do this, click to clear the Reporting check box.
  2. Install this hotfix rollup to upgrade the FIM Service to build 4.1.3599.0.
  3. Run the change-mode installation for the FIM Service, and then add Reporting.

If reporting is enabled and the change-mode installation is run for FIM Service and Portal, you must be re-enable reporting. To do this in the FIM Identity Management Portal, follow these steps:
  1. On the Administration menu, click All Resources.
  2. Under All Resources, click System Configuration Settings.
  3. Click the System Configuration Settings object, and then open the Properties of this object.
  4. Click Extended Attributes, and then select the Reporting Logging Enabled check box.
  5. Click OK, and then click Submit to save the change.

Prerequisites

To apply this update, you must have Forefront Identity Manager 2010 R2 (build 4.1.3419.0 or a later build) installed.

For BHOLD deployments, you must have hotfix rollup package 2934816 (build 4.3.3510.0) installed to apply this update.

Restart requirement

You must restart the computer after you apply the Add-ins and Extensions (Fimaddinsextensions_xnn_kb3022704.msp) package. Additionally, you may have to restart the server components.

Replacement information

This update replaces the following updates:
3011057 A hotfix rollup (build 4.1.3613.0) is available for Forefront Identity Manager 2010 R2 SP1

2980295 A hotfix rollup (build 4.1.3599.0) is available for Forefront Identity Manager 2010 R2

2969673 A hotfix rollup (build 4.1.3559.0) is available for Forefront Identity Manager 2010 R2

2934816 A hotfix rollup package (build 4.1.3510.0) is available for Forefront Identity Manager 2010 R2

File information

Hotfix release build numbers
Forefront Identity Manager 4.1.3627.0
BHOLD 5.0.2959.0
Access Management Connector 5.0.2959.0

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.

File nameFile versionFile sizeDateTimePlatform
Accessmanagementconnector.msiNot Applicable671,74420-Feb-201507:50Not Applicable
Bholdanalytics 5.0.2959.0_release.msiNot Applicable2,699,26420-Feb-201507:35Not Applicable
Bholdattestation 5.0.2959.0_release.msiNot Applicable3,207,16820-Feb-201508:33Not Applicable
Bholdcore 5.0.2959.0_release.msiNot Applicable5,013,50420-Feb-201507:22Not Applicable
Bholdfimintegration 5.0.2959.0_release.msiNot Applicable3,530,75220-Feb-201508:05Not Applicable
Bholdmodelgenerator 5.0.2959.0_release.msiNot Applicable3,248,12820-Feb-201508:47Not Applicable
Bholdreporting 5.0.2959.0_release.msiNot Applicable1,994,75220-Feb-201508:19Not Applicable
Fimaddinsextensionslp_x64_kb3022704.mspNot Applicable3,916,80017-Feb-201502:23Not Applicable
Fimaddinsextensionslp_x86_kb3022704.mspNot Applicable1,596,41617-Feb-201502:15Not Applicable
Fimaddinsextensions_x64_kb3022704.mspNot Applicable5,206,52817-Feb-201502:23Not Applicable
Fimaddinsextensions_x86_kb3022704.mspNot Applicable4,662,78417-Feb-201502:15Not Applicable
Fimcmbulkclient_x86_kb3022704.mspNot Applicable9,097,72817-Feb-201502:15Not Applicable
Fimcmclient_x64_kb3022704.mspNot Applicable5,570,04817-Feb-201502:23Not Applicable
Fimcmclient_x86_kb3022704.mspNot Applicable5,192,70417-Feb-201502:15Not Applicable
Fimcm_x64_kb3022704.mspNot Applicable33,493,50417-Feb-201502:23Not Applicable
Fimcm_x86_kb3022704.mspNot Applicable33,104,38417-Feb-201502:15Not Applicable
Fimservicelp_x64_kb3022704.mspNot Applicable12,251,64817-Feb-201502:23Not Applicable
Fimservice_x64_kb3022704.mspNot Applicable31,272,96017-Feb-201502:23Not Applicable
Fimsyncservice_x64_kb3022704.mspNot Applicable36,211,20017-Feb-201502:23Not Applicable


More Information


Issues that are fixed or features that are added in this update

This update fixes the following issues or adds the following features that were not previously documented in the Microsoft Knowledge Base.

BHOLD integration with the FIM Identity Management Portal and language packs

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.

BHOLD Reporting

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.

BHOLD Model Generator

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.

FIM Service and Identity Management Portal

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.

Certificate Management

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:

Object cannot be cast from DBNull to other types.
Technical Details
Type: System.InvalidCastException
Source: mscorlib
Stack Trace: at System.DBNull.System.IConvertible.ToDateTime(IFormatProvider provider)
at System.Convert.ToDateTime(Object value, IFormatProvider provider)
at Microsoft.Clm.DataAccess.Certificates.CalculateCertificateStatus(CertificateDataSet certData)
at Microsoft.Clm.BusinessLayer.Profiles.GetProfilesByStatus(Guid userUuid, ProfileStatus status)
at Microsoft.Clm.Web.UserDetail.LoadIntoInterface()
at Microsoft.Clm.Web.UserDetail.Page_Load(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)


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:

The card cannot be accessed because the wrong PIN was presented.

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

Processing error: Invalid smart card. This card may only be reused for the user and profile template for which the card is assigned. Please retire the card first before enrolling for a different user or profile template.

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.

Synchronization Service

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:

The image or delta doesn't have an anchor.

References


Learn about the terminology that Microsoft uses to describe software updates.