A hotfix rollup package (build 3.3.1051.2) is available for Microsoft Identity Lifecycle Manager 2007 Feature Pack 1. This hotfix rollup package resolves the following problems:
Attributes from disconnectors take precedence over attributes from connectors.
There are many scenarios in which this problem occurs. For example, consider the following scenario:
Management agents X and Y both contribute values for an object’s attribute.
The currently synchronized attribute value in the metaverse is from management agent X.
The object is deprovisioned from management agent X. The object becomes a disconnector for that management agent.
In this scenario, the value that is contributed by management agent X is preserved. However, the current value in the metaverse should be the one that is contributed by management agent Y.
A multi-single-mismatch error occurs in a delta import operation from a SunOne management agent.
Note This problem occurs when the following conditions are true:
A user ID is changed in the SunOne directory.
The change involves only a change from uppercase to lowercase characters or vice versa in the user ID.
When you try to synchronize multivalued attributes, the synchronization results differ. The results depend on whether the attributes are indexed in the metaverse. After you run delta synchronizations, a non-indexed multivalued attribute keeps existing values on the metaverse on replace operations instead of deleting those values. For example, if the multivalued attribute has two values, and if one value is deleted in the data source and is replaced by a different value, the metaverse has all three values in the attribute after an import and delta synchronization.
When you try to move an object on a SunOne Directory Server from a container that is discovered by an Identity Lifecycle Manager (ILM) SunOne management agent to one that is not discovered by ILM, you receive a "stopped-parsing" error message in a delta import operation.
When you run a full import operation from a SunOne Directory Server management agent or an IBM Directory Server management agent, the same Lightweight Directory Access Protocol (LDAP) query is sent to the data source repeatedly. This problem occurs if there are more than 7,000 objects being imported.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Identity Lifecycle Manager 2007 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
To apply this hotfix, you must have Identity Lifecycle Manager 2007 Feature Pack 1 installed on the computer.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix 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.
Back to the top
