Issue
DirSync was not able to process Password copy as it did not detect any password changes in the source. Instead the below message was observed in the log:
Skipping Password Sync, No Changed Password Found
Cause
This can happen when AD Replication in the source did not update the change password in a timely manner. Hence, DirSync will not detect the change so that Password will be synced during the delta sync process.
Resolution
To work around this issue, we can force an AD Replication on the source so that DirSync can pick up the changes.
The 2nd option is to force DirSync to process Password copy for all objects, this would require direct access to the SQL Server.
Please contact Binary Tree Product Support for guidance.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center