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 updateSynchronization 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 situation, the synchronization engine installer for this update does not replace the configuration file. This is done intentionally 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.
- Locate 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.
- Locate the Mmsscrpt.exe.config file in the same directory as the MIIServer.exe.config file, and locate the Dllhost.exe.config file 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.
PrerequisitesTo apply this update, you must have Microsoft Identity Manager 2016 (build 4.3.1935.0 or a later build) installed.
Restart requirementYou must restart the computer after you apply the Add-ins and Extensions (Fimaddinsextensions_xnn_kb3092179.msp) package. Additionally, you may have to restart the server components.
Registry informationTo use one or more of the hotfixes in this update, you must change the registry.
Replacement informationThis update does not replace any previously released update because this is the first update for Microsoft Identity Manager 2016.
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 size||Date||Time|
Issues that are fixed or added in this updateThis update fixes the following issues or adds the following features that were not previously documented in the Microsoft Knowledge Base.
MIM add-ins and extensions
Issue 1This hotfix addresses an issue that affects the password reset window and that occurs on monitors that have high DPI settings when the Windows display sizing of items is set to a custom size, such as 200 percent or more.
Issue 1You try to enroll a smart card by having the correct profile selected (with correct adminKey). However, the user PIN doesn't correspond to the smart card PIN policy. In this situation, you receive the following error message:
Issue 2MIM Configuration Manager Reporting doesn't show smart card settings correctly. Settings are shown only for the Pkcs11 smartcard provider and not for baseCSP.
Issue 3All policies in the MIM Configuration Manager allows for changes to "Revocation Settings" only for all certificates together. In this fix, a new page is added (CertificateTemplateRevocationSettings) to show "revocation settings" for the selected certificate. Changes to ProfilePolicyrevocationSettingsPage are also made to show all certificates of the profile.
MIM Synchronization Service
Issue 1When you configure an ECMA2 run profile, you receive a “Value of ‘10’ is not a valid value” error message.
Issue 2The Sync Engine reports a staging-error during delta import when the Generic LDAP connector detects the renaming of an object distinguished name.
Issue 3When a rename, or a distinguishedName change, of a user is exported to Oracle Directory Enterprise Edition (ODSEE), that user is removed from group memberships. You expect that the membership reference to the renamed object will be updated, instead.
Issue 4When unsupported characters are entered in the SMTP address, MIM Sync cannot correctly provision the object into GALSync MA. In this situation, the object fails and throws an error. This problem also causes the object to be duplicated.
Issue 5ECMA2 Export only MA displays an "Image or delta doesn't have an anchor" error message when you perform an Export, CS Search, or CS Deletion.
Issue 6The Sync Service stops responding when you stop a run profile for the ECMA connector.
Issue 7The Active Directory MA interprets objects that are restored in the directory as deleted.
Issue 8If you call Set-MIISECMA2Configuration to set the configuration for the SharePoint connector (Microsoft.IdentityManagement.Connector.Sharepoint.dll, version 4.3.836.0), the call fails silently but the verbose output says that the operation was successful.
Issue 9The Set-MIISADMAConfiguration cmdlet supports only a single partition and a single container. In this update, the following changes are made to the parameters of this cmdlet.
The -Partitions parameter allows one or more partitions to be specified in the Active Directory MA.
- The -Partitions parameter can apply single or multiple containers by using the ";" delimiter.
- If the -Partitions parameter is absent, the Set-MIISADMAConfiguration cmdlet behaves in the same manner as it did prior to this update.
Example command that uses the -Partitions parameter:
This parameter is updated to allow one or more containers to be specified together with the -Parameters parameter. It uses the following rules:
- If the –Partitions parameter is present, parameter –Container can now apply to single or multiple containers by using the ";" delimiter.
- If –Container is absent or no container are given for the partition, all the containers of this partition are selected.
- If –Partitions is absent, the MIISADMAConfiguration cmdlet behaves in the same manner as it did prior to this update, and –Container can accept only a single container.
Example command that uses the -Partitions and -Container parameters:
Issue 1This hotfix addresses an issue in the MIM Portal that affects the sorting of a customized list view based on the columns that are specified in the ColumnsToDisplay property.
Issue 2This hotfix updates HTML elements and attributes in the password registration portal and MIM Portal.
Issue 3The object picker does not search objects that have special characters in their name.
Issue 4This hotfix updates the translation of the user interface strings that relate to the “Password Reset AuthN Workflow” activity into Russian.
Issue 5This hotfix addresses an issue that affects the Leave Member and Remove Member buttons when the group resource type is customized.
Issue 6This hotfix adds a new search scope that is named "All Groups" to enable searching for and joining groups if the user does not know whether the group is a security group or a distribution list.
Issue 7Specific culture localization settings for Spanish and French revert to English.
Issue 8When you update an integer attribute value on the Extended Attributes tab of an object in the MIM Portal, the value is limited to a 32-bit integer. This issue occurs even though the same attribute allows 64-bit integer values if it is updated outside the Portal .
Issue 9Resource Control Display Configuration (RCDC) does not allow a default tab to be configured.
In this hotfix, the UOCInitialTabName parameter is added to the URL so that an object loads together with its associated RCDC.
The current RCDC users page has four tabs: General, Work Info, Contact Info, Summary.
If you open the corresponding XML, you find XML code that resembles the following:
If you provide the following code for an RCDC users page, the Work Info tab automatically opens:
Or, if you provide the following code for a default administrators page, the Work Info page automatically opens:
MIM Password Registration Portal
Issue 1On the Question and Answer page, the initial scroll position is incorrect and prevents users from seeing the initial question.
Issue 2When you update the Password Reset AuthN Workflow: QA gate, the Message to user that describes uniqueness and answer text constraints field is not updated as expected in the Self-Service Password Reset (SSPR) UI.
Issue 1Broker service conversations are closed after a sync export to the MIM Service database.
Issue 2A custom expression that includes Concatenate() is replaced by a plus sign (+) and generates an error when it is saved.
Issue 3This hotfix addresses an issue that affects the MIM Service database stored procedures in which deadlocks might occur in approval workflows. In particular, deadlocks might occur in deployments that have complex or general Set definitions (for example, sets that match "/*" instead of specific resource types).
Issue 1An inconsistency can occur between the Permission name and attribute changes that occur during an export, import, and subsequent export process in MIM Sync. In this case, BHOLD receives duplicates of a renamed group and maintains the original group in the database.
Issue 2The Attestation Campaign Portal has an incorrectly worded title that displays campaign progress.
Article ID: 3092179 - Last Review: 29 Feb 2016 - Revision: 1