Change in Objectclass Value Does Not Trigger Attribute Flow (279279)



The information in this article applies to:

  • Microsoft Metadirectory Services 2.1
  • Microsoft Metadirectory Services 2.2

This article was previously published under Q279279

SUMMARY

A change in the value of the object of a connected directory objectclass attribute is insufficient to cause the flow of attribute values into the metaverse even though the appropriate attribute flow rules may exist.

MORE INFORMATION

This behavior occurs because a trigger is required within Microsoft Metadirectory Services (MMS) to initiate the flow of any attribute into the metadirectory. Typically, the fact that a valid attribute flow rule exists coupled with a change in value in the connected directory will cause the new attribute value to flow into the metaverse. The objectclass attribute is the sole exception. Therefore, the following items are required for the objectclass values to flow into the metaverse:
  • At least one other attribute must be properly configured to flow.
  • That attribute must be coincidentally changed in the connected directory.

Modification Type:MinorLast Reviewed:1/25/2006
Keywords:kbenv kbinfo KB279279