AD rename is considered as update, will not apply the provisioing rule

Question

Hi all,
I'm trying to rename my existing accounts in AD to arrange  them in different OU depending on departments.
I configured my environment to have both data flow for dn as persestant flow and initial only for dn value,
for new users created in the forum, the provisioing occur in the right way with the correct ou location, but for existing accounts it considers the dn change as an update and the system tries to flow the value to the dn attribute in the
AD account, when reimporting the error msg appears as "exported-chagnge-not-imported"
any ideas will greatly help!
thanks

Answer 1

I have just done a sanity check in my lab environment.
All, I can tell you is, that it should work as explained.
Your best bet is probably to create a repro of my scenario and to compare it with what you have.
Here is the synchronization rule I've been using:
 As you can see, I'm using the description attribute to make a move decision.
If description is "Test", I'm moving the object to a different OU.
Moving the object to a different OU is correctly indicated as Rename:
This is also what the synchronization statistics reports:
I hope this helps...
Cheers,
Markus
Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation