This morning I moved from users from one AD org unit to another, which resulted in their "dn" attribute changing. One of those users is a manager for other subordinate users, and that user's dn value is retrieved by an adapter Join transform on the subordinate users, and mapped into their "manager" field in AD via their locker records.
After the change was made, the manager's connector and adapter record updated with the new dn field value, but the updated value did not flow through to the subordinate users' "manager" field in the locker. The link which should be responsible for this is only configured for Change Polling. When I ran a Baseline Sync, however, the subordinate users' manager fields did update in the locker.
I haven't tried to replicate this problem, but I do not believe it to be typical behaviour.
Customer support service by UserEcho