• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 94 subscribers
  • Views 5086 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The updated CN value being rollback by Synchronization (system user)

xd
over 8 years ago

As requested CN has to be lower case across the domains, and the template ensures the value being converted to lower case. But after applying the template and CN value converted to lower case, the system user "Synchronization" immediately changes CN value back to the value before (See screen). This is v7.1.1. What could the root cause be to trigger the Synchronization user doing rollback? 

Your suggestion and guidance are appreciated.

  • 0 over 8 years ago
    If the Synchronization user changed these attributes, a sync has occured as only the synchronization engine is using that user.
     
    Some more questions:
    • What type of object are we looking at?
    • Did you check the jobqueue after applying the templates? Did any processes have been generated that might trigger a sync of these objects
  • 0 over 8 years ago
    The object is ADS user object. I monitored the job queue right after the template applied but did not find an y processes fired in the job queue.
    Only an account in 1IM behaves like that. I guess it might be created incorrectly.
    Could something else trigger Synchronization user?
    Thanks,
    Jeffrey
  • 0 over 8 years ago
    Did you check the synchronization journals if an operation took place that you might have missed?
     
    Additional step to help you to get to the bottom of this:
     
    • Check the object in AD if the cn is in upper-case. If not, check if you do have a custom sync configuration that is doing some conversion to upper-case (not likely).
    • You could turn on the debug log in Object Browser to check if a process would be generated during your execute templates. You do not have to change the globallog.config to do that. Just turn on the debug log in the operations log window of Object Browser prior to your execute template. (see screenshot)