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 don't 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 don't see your language, it's because a hotfix isn't available for that language.
PrerequisitesTo apply this update, you must have the Microsoft .NET Framework 4.0 installed and also one of the following:
- FIM Synchronization Service build 4.1.3461.0 (KB 2870703 ) or a later version
- MIM Synchronization Service
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||Path|
Issues that are fixedThis hotfix rollup fixes the following issues that were not previously documented in the Microsoft Knowledge Base.
Issue 1You rename a distinguished name (DN) and then export it. When you import the object, two entries are displayed with different case styles (lowercase and mixed case) during the "confirming import" process.
Issue 2During a delta import, no entries are present if the partition name contains white-space characters.
Issue 3If a value in an attribute is the same as the name of another attribute, you receive the following error message:
Issue 4A delta import does not correctly parse base64-encoded characters if it contains a double colon (::).
Issue 5A change in case does not work for values in a multivalued attribute.
Issue 6A change in case does not work if a multivalued attribute is used to create the relative distinguished name (also known as RDN) attribute.
Issue 7If the attribute that makes up the relative distinguished name isn't changed at the same time that you rename the DN, you receive an MA-extension error.
Issue 8If an attribute has a long value during delta import, the whole value isn't read.
Features that are added
Feature 1If a directory does not support pagination but can return all objects in one stream, the Connector can now paginate internally to the sync engine.
Feature 2Delta import performance is improved when the changelog mechanism is used.
Article ID: 3078617 - Last Review: Sep 24, 2015 - Revision: 1