A mistake was made and some of objects were matched that should not have been.
Now, DSA still continues to match the objects in the same manner as before, even though matching rules should be prohibiting this.
Seems that the DSA has all previous matchings cached somewhere and simply refers to that cache rather than enumerating the source and target AD and looking for the correct objects.
What needs to be done to get this resolved?
This has been found to be a product bug.
WORKAROUND 1:
DSA is using the cached data first when matching objects so one needs to delete the cache.
Delete everything (or copy away) what can be found under the folder:
C:\Program Files\Quest Software\Migration Manager\DSA\CONFIGS\Cache (default location).
But it is very important also to clean up the old matching first, the following KB article contains instructions:
Click Here
If not cleaned up properly the objects might still be mismatched by old attributes mentioned in the SOL32553.
WORKAROUND 2:
This issue does not arise when synchronization is configured to be a two-way synchronization.
Knowing this synchronization can be configured as two-way synchronization.
For example in target domain an empty OU can be created and selected as synchronization scope. It has been confirmed that in this case the synchronization will work as expected and will never use the cache. This approach can be especially interesting in environments where this issue occurs constantly (such environments are very rare).
Important: modifying the synchronization scope from one-way to two-way synchronization will require a full resynchronization.
STATUS:
Waiting for fix in a future release of Migration Manager.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center