Introduction

A hotfix rollup package (build 4.1.3599.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2 Service Pack 1 (SP1). 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.

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:

http://support.microsoft.com/contactus/?ws=supportNote 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, rule extensions and custom management agents (MAs) that are based on Extensible MA (ECMA1 or ECMA 2.0) may not run and may generate a run status of "stopped-extension-dll-load." This issue occurs when you run such rule extensions or custom management agents after you change the configuration file (.config) for one of the following processes:

  • MIIServer.exe

  • Mmsscrpt.exe

  • Dllhost.exe

For example, assume that you edited the MIIServer.exe.config file to change the default batch size for processing sync entries for the FIM Service management agent.

To avoid deleting your previous changes in this situation, the synchronization engine installer for this update does not replace the configuration file. Because the configuration file is not replaced, entries that are required by this update are not present in the files, and the synchronization engine does not load any rule extension DLL files 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 rule 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, 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 SP1 (build 4.1.3419.0 or a later build) installed.

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

Restart requirement

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

Replacement information

This update replaces the following updates:

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

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 name

File version

File size

Date

Time

Platform

Accessmanagementconnector.msi

Not Applicable

671,744

19-Aug-2014

06:59

Not Applicable

Bholdanalytics 5.0.2724.0_release.msi

Not Applicable

2,703,360

19-Aug-2014

06:46

Not Applicable

Bholdattestation 5.0.2724.0_release.msi

Not Applicable

3,207,168

19-Aug-2014

07:38

Not Applicable

Bholdcore 5.0.2724.0_release.msi

Not Applicable

5,009,408

19-Aug-2014

06:34

Not Applicable

Bholdfimintegration 5.0.2724.0_release.msi

Not Applicable

3,534,848

19-Aug-2014

07:12

Not Applicable

Bholdmodelgenerator 5.0.2724.0_release.msi

Not Applicable

3,252,224

19-Aug-2014

07:51

Not Applicable

Bholdreporting 5.0.2724.0_release.msi

Not Applicable

1,990,656

19-Aug-2014

07:25

Not Applicable

Fimaddinsextensionslp_x64_kb2980295.msp

Not Applicable

3,921,920

27-Aug-2014

00:14

Not Applicable

Fimaddinsextensionslp_x86_kb2980295.msp

Not Applicable

1,595,904

27-Aug-2014

00:07

Not Applicable

Fimaddinsextensions_x64_kb2980295.msp

Not Applicable

5,208,064

27-Aug-2014

00:14

Not Applicable

Fimaddinsextensions_x86_kb2980295.msp

Not Applicable

4,662,784

27-Aug-2014

00:07

Not Applicable

Fimcmbulkclient_x86_kb2980295.msp

Not Applicable

9,097,728

27-Aug-2014

00:07

Not Applicable

Fimcmclient_x64_kb2980295.msp

Not Applicable

5,565,440

27-Aug-2014

00:14

Not Applicable

Fimcmclient_x86_kb2980295.msp

Not Applicable

5,198,848

27-Aug-2014

00:07

Not Applicable

Fimcm_x64_kb2980295.msp

Not Applicable

33,480,704

27-Aug-2014

00:15

Not Applicable

Fimcm_x86_kb2980295.msp

Not Applicable

33,094,656

27-Aug-2014

00:07

Not Applicable

Fimservicelp_x64_kb2980295.msp

Not Applicable

12,237,824

27-Aug-2014

00:14

Not Applicable

Fimservice_x64_kb2980295.msp

Not Applicable

31,314,432

27-Aug-2014

00:14

Not Applicable

Fimsyncservice_x64_kb2980295.msp

Not Applicable

36,231,680

27-Aug-2014

00:15

Not 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.

FIM service and portals

Issue 1

This hotfix updates the FIM Password Reset and Password Registration Portal with additional UI changes that apply to customers who are customizing these portals in compliance with Section 508 of the U.S. Federal Rehabilitation Act.

Symptoms include the following:

  • On the "Your current Password" page, the Password text box is labeled incorrectly.

  • On the "Register your Answers" page, none of the text boxes are labeled correctly.

  • The following image has no alt tag:

    <img src="images/wait_animationa.gif" />

  • When a validation error is encountered for the form fields on the "Your Current Password" and "Register Your Answers" pages, there is a message that's displayed to the user. However, there is no indication to Assistive Technology that this message has appeared, no shift of focus, and the graphic that indicates an error to visual users is inaccessible. Therefore, it's not apparent that this is an error message because it is displayed only as flat text.

  • The customized logo and text in the title is inaccessible to Assistive Technology.


Changes after the fix is applied:

  • Assistant Technology now fully reads all pages in the SSPR portal, and the user is informed if an error occurs.

  • The banners in Password Reset and Registration portals now have a tooltip.


Issue 2

When you configure a UocDropDownList control in a Resource Control Display Configuration with string values, the list of values in the control are not displayed in alphabetical order.

This fix adds the Sorted property to the UocDropDownList control. When the Sorted property is set to True, the items are sorted in alphabetical order.

Example:

<my:Control my:Name="EmployeeType" my:TypeName="UocDropDownList" my:Caption="{Binding Source=schema, Path=EmployeeType.DisplayName}" my:Description="{Binding Source=schema, Path=EmployeeType.Description}" my:RightsLevel="{Binding Source=rights, Path=EmployeeType}">
<my:Properties>
<my:Property my:Name="Sorted" my:Value="True"/>
<my:Property my:Name="Required" my:Value="{Binding Source=schema, Path=EmployeeType.Required}"/>
<my:Property my:Name="ValuePath" my:Value="Value"/>
<my:Property my:Name="CaptionPath" my:Value="Caption"/>
<my:Property my:Name="HintPath" my:Value="Hint"/>
<my:Property my:Name="ItemSource" my:Value="{Binding Source=schema, Path=EmployeeType.LocalizedAllowedValues}"/>
<my:Property my:Name="SelectedValue" my:Value="{Binding Source=object, Path=EmployeeType, Mode=TwoWay}"/>
</my:Properties>
</my:Control>

Issue 3

In the FIM Identity Management Portal that has the language pack installed, the display names of approval objects are not completely translated.

Be aware that 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, and it is not affected by client browser locale. To change the language that's 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.

BHOLD

Issue 1

Users who are in inherited supervisor roles for operational units (OUs) may not have supervisor roles in subordinate OUs.

Issue 2

Roles that are directly assigned to a user are also listed under the inherited roles node.

Issue 3

When multiple attribute-based authorization (ABA) rules that are specified in BHOLD Core assign permissions to a user, and the user's attributes change and are synched in from BHOLD FIM Provisioning Access Management Connector, the user may not receive all of his or her permissions.

Issue 4

In the BHOLD Analytics module, the impact operation is not available after a ruleset that includes a filter with a restrictive type is set. After this fix is applied, pressing the Impact button displays the impact of the rules.

Issue 5

The following error message may be logged in the Application log on a computer where BHOLD Core is installed:

Error when executing 'EXEC ProcessQueueCommand30RoleBiased' \n\n Reason System.Data.OleDb.OleDbException: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.
at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)
at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()
at BHOLD.B1ServiceLibrary.Queue.ConnectorQueueDal.RetrieveQueueEntries(Int32 applicationId) in d:\Builds\52\5\Sources\imp\src\Access Management\Core\B1ServiceBC\Queue\ConnectorQueueDal.cs:line 122'

Issue 6

When the FIM Integration module is being used, and the BHOLD self-service features are incorporated into the FIM portal, some column headings may appear to be truncated.

Issue 7

In BHOLD Attestation, the notification template editor toolbar buttons are not displayed correctly.

Issue 8

When you apply this hotfix, BHOLD Attestation notification email messages contain a URL that requires one fewer click by the end-user in order to navigate to the page to perform the attestation.

Issue 9

This hotfix adds a UserUpdate function to the BHOLD Core scripting web service.

FIM Synchronization Service

Issue 1

Starting with build 4.1.3508.0, audit log files on Export run profile steps do not include reference attribute values.

Certificate management

Issue 1

Assume that a certificate is enrolled by using certificate template CT1 in profile template PT1, and then CT1 is replaced by another certificate template. If CT1 is removed, the certificate is revoked, and no new certificate is created from PT1. Additionally, later renewals of the certificate fail and a cryptic error message is returned.

With the profile template model, you cannot avoid this issue. Removal of the certificate template was done for a reason, and the system cannot arbitrarily determine whether the user can still enroll for the certificate by using that template.

The system now returns a user-friendly message, telling you to enroll instead of renew. This change makes sure that the certificate templates that are currently available in the profile template are used. Additionally, this action is logged on the FIM Certificate Manager server's log file with all the necessary information.

Feature 1

Existing users in the FIM Certificate Management database, who have associated profiles and certificates, cannot be migrated to a different Active Directory user.

This new functionality is exposed through the clmutil.exe command prompt utility.

CLMUtil takes as input the original user's UUID and the current user's UUID. Records in the following tables are updated to the new UUID: profiles, certificates, and smart cards. Additionally, the UserNameCache table is updated if this is necessary, attaching the user name to the new UUID.

Command syntax:

ClmUtil -migrateuser -oldUserId "oldUserUuid" -newUserId "newUserUuid"
Description:

Migrate a user's profile, certificate and smart cards records - from a user who has an old uuid to new uuid.

Example:

ClmUtil -migrateuser -oldUserId 11111111-2222-3333-4444-d602b49480b0 -newUserId 11111111-2222-3333-4444-2c68e64bba93

References

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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×