Update informationA supported update is available from Microsoft Support. We recommend that all customers apply this update to their production systems.
Microsoft SupportIf 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 updateFIM 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:
In this case, 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 will not be present in the files, and 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:
- Make a backup copy of the MIIServer.exe.config file.
- Open the MIIServer.exe.config file in a text editor or in Microsoft Visual Studio.
- Find the <runtime> section in the MIIServer.exe.config file, and then replace the content of the <dependentAssembly> section with the following:
<assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="188.8.131.52-184.108.40.206" newVersion="220.127.116.11" />
- Save the changes to the file.
- Find the Mmsscrpt.exe.config file in the same directory and the Dllhost.exe.config in the parent directory. Repeat steps 1 through 4 for these two files.
- Restart the Forefront Identity Manager Synchronization Service (FIMSynchronizationService).
- Verify that the rules extensions and custom management agents now work as expected.
If you install FIM Reporting on a new server that has Microsoft System Center 2012 Service Manager Service Pack 1 installed, follow these steps:
- Install the FIM 2010 R2 SP1 FIMService component. To do this, click to clear the Reporting check box.
- Install this hotfix rollup to upgrade the FIM Service to build 4.1.3510.0.
- 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 the FIM Service and Portal, you must re-enable reporting. To do this in the FIM Identity Management Portal, follow these steps:
- On the Administration menu, click All Resources.
- Under All Resources, click System Configuration Settings.
- Click the System Configuration Settings object, and then open the Properties of this object.
- Click Extended Attributes, and then click to select the Reporting Logging Enabled check box.
- Click OK, and then click Submit to save the change.
Assigned role reflecting in inherited roles
When a role is assigned to a user, the assigned role is displayed in the user interface in the user’s inherited roles. However, the roles are not actually inherited.
Conflicting attribute-based authorization (ABA) role is assigned when the "End Date" field is changed
When you try to update the End Date value for a user who has a conflicting ABA inherited role, the role is directly assigned to that user without an ABA Check validation.
Cardinality for permission and roles to users
Cardinality functionality behavior is slightly different in the new build compared with the Service Pack 1 (SP1) build.
- SP1 build: If the max #Of Users field is set to 2, and if you try to assign a role or permission to a third user, the warning message "Role/User cardinality exceeded" is displayed. After you change the cardinality settings to 3, for example, you can assign the role to the third user.
- This hotfix build: For the third user, a warning message is not displayed. But, you can still add the role. However, the role becomes disabled. After you change the cardinality settings to 3, the role is enabled for the third user.
PrerequisitesTo apply this update, you must have Service Pack 1 for Forefront Identity Manager 2010 R2 (build 4.1.3114.0 or a later build) installed.
Before you install this update to the BHOLD Suite components, the old version of BHOLD must be uninstalled.
File informationThe 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||06-Mar-2014||06:47||Not Applicable|
|Bholdanalytics 5.0.2521.0_release.msi||Not Applicable||2,703,360||06-Mar-2014||06:36||Not Applicable|
|Bholdattestation 5.0.2521.0_release.msi||Not Applicable||3,198,976||06-Mar-2014||07:25||Not Applicable|
|Bholdcore 5.0.2521.0_release.msi||Not Applicable||5,009,408||06-Mar-2014||06:23||Not Applicable|
|Bholdfimintegration 5.0.2521.0_release.msi||Not Applicable||3,530,752||06-Mar-2014||07:00||Not Applicable|
|Bholdmodelgenerator 5.0.2521.0_release.msi||Not Applicable||3,256,320||06-Mar-2014||07:37||Not Applicable|
|Bholdreporting 5.0.2521.0_release.msi||Not Applicable||1,990,656||06-Mar-2014||07:12||Not Applicable|
|Fimaddinsextensionslp_x64_kb2934816.msp||Not Applicable||3,928,064||22-Feb-2014||03:20||Not Applicable|
|Fimaddinsextensionslp_x86_kb2934816.msp||Not Applicable||1,593,344||22-Feb-2014||03:15||Not Applicable|
|Fimaddinsextensions_x64_kb2934816.msp||Not Applicable||5,206,016||22-Feb-2014||03:20||Not Applicable|
|Fimaddinsextensions_x86_kb2934816.msp||Not Applicable||4,661,248||22-Feb-2014||03:15||Not Applicable|
|Fimcmbulkclient_x86_kb2934816.msp||Not Applicable||9,091,584||22-Feb-2014||03:15||Not Applicable|
|Fimcmclient_x64_kb2934816.msp||Not Applicable||5,607,424||22-Feb-2014||03:20||Not Applicable|
|Fimcmclient_x86_kb2934816.msp||Not Applicable||5,198,848||22-Feb-2014||03:15||Not Applicable|
|Fimcm_x64_kb2934816.msp||Not Applicable||31,694,848||22-Feb-2014||03:20||Not Applicable|
|Fimcm_x86_kb2934816.msp||Not Applicable||31,408,128||22-Feb-2014||03:15||Not Applicable|
|Fimservicelp_x64_kb2934816.msp||Not Applicable||12,140,544||22-Feb-2014||03:20||Not Applicable|
|Fimservice_x64_kb2934816.msp||Not Applicable||31,088,640||22-Feb-2014||03:20||Not Applicable|
|Fimsyncservice_x64_kb2934816.msp||Not Applicable||36,061,184||22-Feb-2014||03:20||Not Applicable|
Issues that are fixed or features that are added in this updateThis update fixes the following issues or adds the following features that were not previously documented in the Microsoft Knowledge Base.
FIM Service and Portal
Issue 1If a FIMService instance loses connection to the FIMService database, it can may stop processing FIM Service MA export requests. This results in failed FIM Service MA exports with a run status of "stopped-server." Additionally, the following exception is logged in the Forefront Identity Manager event log:
Issue 2You use a multivalue attribute in a dynamic set. This dynamic set is used in a Transition Out management policy rule. If two or more elements are removed from the attribute in a single request, and if of the elements triggers the Transition-Out MPR, the request fails, and you receive the following exception:
Issue 3When an export run in the FIM Service MA includes updates to the Filter attribute of multiple dynamic groups, a "failed-modification-via-web-services" exception can be returned. When you review the details of the exception that is returned, you see that an SQL Deadlock occurred.
FIM Synchronization Service
Issue 1In the Active Directory management agent, changes to a multivalue attribute such as proxyAddresses are not synchronized to the metaverse in the following scenario:
- A change to proxyAddresses is exported to the Active Directory for User1.
- A second change is made to proxyAddresses outside the synchronization service.
- A Delta Import run profile is run to confirm the exported changes.
Issue 2If an exception is thrown by the management agent's password extension during password synchronization, the password interface at which the exception was thrown is discarded. This can cause high processor usage on the computer that is hosting the FIM Synchronization Service when the computer processes password synchronization to multiple management agents.
After you apply this update, exceptions of type PasswordPolicyException and PasswordIllFormedException no longer discard the password interface. This enables the interface to be reused for another password operation to the connected data source.
If a regular expression policy rule is applied for an ABA role, all applied ABA roles are stuck in the pending state for the users and are never assigned.
Issue 2If a user has an ABA role, and if you try to change a user attribute that is not related to the ABA role, all ABA roles are again marked for policy validation. Additionally, assigned permissions are removed and assigned back.
Issue 3When you have more than 500 permissions in BHOLD and search permissions on the Supervised Permissions tab of Default Supervisor Role, no results are returned, and you are returned to the previous page.
Issue 4When you configure an attribute-based role assignment for a role and then you try to click the Show Impact link in the policies section of a role, you receive the following error message:
Issue 5The SP1 build does not let you re-create a permission that was removed from BHOLD earlier.
Issue 6When you try to change and save a user without changing the end date, you receive the following error message:
Issue 7When you try to move an organization unit in the BHOLD Core Portal, you receive the following warning message:
Issue 8The "User by Role" report cannot be generated after the limit of 50,000 users is reached. Additionally, you receive an "Out of memory" exception.
Issue 9In the BHOLD Self-Service Portal, the role information screen under the Role Requests-Current Roles tab displays no role descriptions or permission details.
Issue 10When you log on as a typical end-user in the BHOLD Service Portal, the "My Roles" screen is displayed as an empty page even though the user is assigned with both "active" and "proposed" roles.
Issue 11The BHOLD - Access Management agent cannot perform full imports because of an SQL time-out issue that occurs when there is a load of more than 50,000 to 100,000 users.
Issue 12BHOLD cannot add permissions to a user by using the BHOLD Connector after these permissions are denied.
Issue 13When a steward in the BHOLD Attestation portal has multiple resources to attest and is working on approving or denying permissions for one user, other permissions for a different user are changed in the user interface.
Article ID: 2934816 - Last Review: 11 Apr 2014 - Revision: 1