XADM: Directory Export Sends Out the OBJ-DIST-NAME Instead of the Directory Name

ID: Q215533

The information in this article applies to:

SYMPTOMS

Directory Export sometimes does not use the directory name object attribute as the directory name when performing a directory export. Instead, Directory Export may construct the directory name from the OBJ-DIST-NAME object attribute using the last common name field as the directory. Normally this would be fine, as the last common name and the directory name are usually the same. But if a customer deletes and recreates a mailbox changing the case of the directory name, then the directory name object attribute and the last common name of the OBJ-DIST-NAME will be different. This can cause problems when performing a dirsync operation with third-party e-mail servers.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

Component: Administrator Program

File name Version
Dapi.dll 5.5.2541.0



NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.

Additional query words: 


Keywords          : 
Version           : winnt:5.5
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: August 3, 1999