scheduling full sync by DSA

No. There is not. The only way to trigger a full sync while in delta is for the source DC to be changed. That will trigger a full resync dynamically because the USN are different.

If you would let the DSA create the objects, there would have been the same problem. You would still not have mailboxes created without changing a MBRedir source attribute.

Really you should not be adding mailboxes into the scope of the dir sync as the migration runs. All users and groups in the should be mail/mailbox enabled in the target when you migrated the first mailbox. This is to fully populate the GAL and allow the delegates and permissions and other tasks to work with a full map. Without this mapping alot of functionality with have less then a full map to wotk with and some translation functionality will be lost.

So you are really painted into a corner with your non standard configuration using two directory sync products in concert and the limitation you customer has placed on you.

To automate this, FIM needs to change the source object post creation in the target. Or you could stop adding source users into the scope of the sync period, and that would solve the issue once and for all.

No. There is not. The only way to trigger a full sync while in delta is for the source DC to be changed. That will trigger a full resync dynamically because the USN are different.

If you would let the DSA create the objects, there would have been the same problem. You would still not have mailboxes created without changing a MBRedir source attribute.

Really you should not be adding mailboxes into the scope of the dir sync as the migration runs. All users and groups in the should be mail/mailbox enabled in the target when you migrated the first mailbox. This is to fully populate the GAL and allow the delegates and permissions and other tasks to work with a full map. Without this mapping alot of functionality with have less then a full map to wotk with and some translation functionality will be lost.

So you are really painted into a corner with your non standard configuration using two directory sync products in concert and the limitation you customer has placed on you.

To automate this, FIM needs to change the source object post creation in the target. Or you could stop adding source users into the scope of the sync period, and that would solve the issue once and for all.