XFOR: DXA Doesn't Export New Recipients Container During Dirsync

• Microsoft Exchange Server, versions 4.0 and 5.0

SYMPTOMS

After you add a new recipients container to the list of Exported Containers for either a Dirsync Requester object or Remote Dirsync Requester object, some names in the new recipients container may not be sent in the next directory synchronization (dirsync) cycle as expected.

CAUSE

The Microsoft Exchange Directory Synchronization service (DXA) did not always handle this properly.

Every object within a Microsoft Exchange Directory has a USN-Changed value. This value is updated every time that the object is modified. The USN- Changed value is what the DXA uses to determine if an object that it is synchronizing with Microsoft Mail for PC Networks has changed since the last dirsync cycle.

When a new recipients container is added to the list of Exported Containers, the DXA should look for all objects with a USN-Changed value greater than zero within that new recipients container and send those objects out as dirsync transactions. Due to a logic error in the DXA, the DXA was treating the new recipients container as if it had always been in the list of export containers.

WORKAROUND

DXA Is Acting as Dirsync Server

If the DXA is acting as the dirsync server, each remote dirsync requester must request a full import from the DXA. This can be accomplished by performing either of the following two procedures.

Procedure 1 - Use the Admin.exe Utility:

1. Start the Microsoft Mail for PC Networks Admin.exe utility against the Requester postoffice that is now expecting the new recipients container.

2. Select Config, Dirsync, Requester, Import, and YES.

Procedure 2 - Use the Exchange Administrator Program:

1. Start the Microsoft Exchange Administrator program.

2. Highlight the Remote Requester object, open the File menu, and click Properties.

3. On the General tab, select the Export on Next Cycle checkbox.

DXA Is Acting as a Dirsync Requester

1. Start the Microsoft Exchange Administrator program.

2. Highlight the Remote Requester object, open the File menu, and click Properties.

3. On the General tab, select the Export on Next Cycle checkbox.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server, version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

Keywords          : kbbug4.00 kbbug5.00 kbfix5.00.sp2 XFOR
Version           : WinNT:4.0,5.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbfix