Article ID: 255589
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Metadirectory Services 2.1
This article was previously published under Q255589
SYMPTOMS
The connector space common name is not synchronized with the connected directory and metaverse common names.
For example, when you use the Account Joiner to join an unconnected connector space object to a metaverse object, if you search the metaverse (by common name), you may not receive the hits you expect because the common name attribute has not been populated in the connector space.
CAUSE
This issue occurs because the attribute assignment rules for the common name have not been implemented in the connector space construction template. The common name attribute is not assigned to the connector space record in the connector space construction template (zcDsiAliasThingConstruction) by default.
RESOLUTION
To resolve this issue, upgrade to MMS 2.2.
To work around this issue, ensure that the following assignments are made in the connector space construction template (zcDsiAliasThingConstruction):
$cs.cn = $cd.cn
This workaround sets the common name attribute of the connector space object to the connected directory's common name attribute.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Metadirectory Services 2.1.
Additional query words: Zoomit Via MA zscript genlogs
Keywords: kbbug KB255589
