During a project, when a two way synchronization is enabled, both source and target objects service attributes are populated. Therefore, if the attributes are already populated on the source object, this could be an indication that the object was previously matched.
This also could be caused by source domain participating in a previous migration project, and post migration cleanup did no occur, leaving AD objects stamped with stamped attributes from the old project.
Verify the domain pair settings, Skip Objects.
If domain pair is set to skip disabled account (for example), and source account is disabled, then it cannot be migrated.
Same location, Object Matching, Service Attributes.
Select objects class on source and target and note which attributes are currently selected as auxiliary and matching service attributes.
Clear the service attributes on the source object and migrate it again.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center