Microsoft KB Archive/246833

From BetaArchive Wiki
Knowledge Base

XADM: Directory Exchange Agent Sends an Add Transaction Instead of a Modify Transaction

Article ID: 246833

Article Last Modified on 7/18/2007


  • Microsoft Exchange Server 5.5 Standard Edition
  • Microsoft Exchange Server 5.5 Service Pack 1
  • Microsoft Exchange Server 5.5 Service Pack 2
  • Microsoft Exchange Server 5.5 Service Pack 3

This article was previously published under Q246833


In a mixed Exchange Server and Microsoft Mail (MS Mail) environment where the Exchange Server computer is configured as the directory synchronization server, if you modify the network or postoffice portion of the MS Mail address of a custom recipient, an add transaction may be sent to the MS Mail environment instead of a modify transaction.


This issue can occur because the address-type comparison checks to determine if the new entry and the record in the Directory Exchange Agent (DXA) mapping table are from the same NET/PO combination. If the entry is not the same, then an add transaction is sent for the new entry. If the NET/PO combination does match, a modify transaction is sent.


To work around this issue, delete the custom recipient and recreate it. When you need to modify multiple addresses, export the custom recipients to a .csv file. Delete the existing custom recipients and allow a full directory synchronization cycle to finish. Then re-import the modified custom recipients and allow another directory synchronization cycle to finish.


This behavior is by design.

Additional query words: Dirsync gal

Keywords: kbprb KB246833