• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 19 subscribers
  • Views 3190 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

What is the impact to the destination environment

rwilso
over 6 years ago

I am trying to understand if there is an impact on the Migration and Sync components, especially on the destination domain, if we decided to include additional target objects in a separate OU structure as part of our migration and also if we also want to include a new OU structure that contains Contact Objects only that we now want to sync to our destination domain -  would I expect QMM to require an entire re-sync to start?

Parents
  • 0 over 6 years ago

    Any changes to the DirSync scope will require a full Sync, further to add the sync will only match objects and their attributes that were migrated during a migration session.  Does that help?

  • 0 over 6 years ago in reply to Enrico Mancini

    Enrico, I think it answers.  Would the same full sync need to happen if I only wanted to Sync contacts over to a destination forest?

  • 0 over 6 years ago in reply to rwilso

    Explain your migration process and how the contacts were created in the target originally.

  • 0 over 6 years ago in reply to Enrico Mancini

    Objects for migration have been created as disable objects, until the time we actually give the account to the user.  However it appears that a OU structure that is hosting Contact objects in our source, which are created by a separate import process, now also need to be sync'd to the target.   Currently someone decided to duplicate the same import process in our target.  What would make sense is to have QMM manage the contacts from source to target.  

Reply
  • 0 over 6 years ago in reply to Enrico Mancini

    Objects for migration have been created as disable objects, until the time we actually give the account to the user.  However it appears that a OU structure that is hosting Contact objects in our source, which are created by a separate import process, now also need to be sync'd to the target.   Currently someone decided to duplicate the same import process in our target.  What would make sense is to have QMM manage the contacts from source to target.  

Children