DSP: AD2AD: AD Objects did not get deleted in the target after the source objects was moved from (B297511)

Issue

AD Objects did not get deleted in the target after the source objects was moved from one domain to another

DirSync will always maintain full Synchronization between source and target forest as long as the objects are created by DirSync.  When objects are being removed from the Source Domain, DirSync will remove the synced objects in the target as well during profile sync.  However, when object was moved from one source domain to another domain in the same forest, DirSync will not remove the target object even though the object in the source is now outside of the sync profile scope.

Cause

DirSync looks at the Deleted Object Container in AD to determine if the object was removed from the Active Directory.  If the object was moved from one domain to another domain in the same forest, this object does not considered to be deleted.  Hence DirSync will not find this object in the Delete Object Container in order to remove the synced object in the target forest.

Solution

Remove the source object first then recreate them in the desire target domain in the source. 

In the event where delete the source object is not a valid option, we recommend client to contact Binary Tree Product Support for assistance to determine if a work around can be provided.