To resolve the issue, it's important to review possible scenarios, depending on the direction of migration/synchronization sessions.
1. When QMM is trying to create an object in the domain pair in the target domain, and another object with the same name already exists, it's easy to resolve such issue by creating a simple migration session and utilizing a TXT importfile, which will specify source samAccountName and different target attributes, like samAccountName, Name, DisplayName, that are unique.
2. However, when there's a 2way migration and object creation should be done in the source domain, it's not possible to use a migration session. For migration session like this, the same domain pair in reverse fashion should be created and such configuration is unsupported.
So to successfully create a user account in the source domain by dirsync, target user account should be renamed, so its attributes like name, displayName and cn are unique.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center