• State Verified Answer
  • Locked Locked
  • Replies 13 replies
  • Subscribers 20 subscribers
  • Views 11120 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

scheduling full sync by DSA

sekandari
over 6 years ago

Hello,

the goal is to start a full sync by DSA for example every 2 hours. Best way will be to create a windows schedule job. Is there an powershell cmdlet or any command to start a Re-Syn (full sync)?

MMEX 8.14 is in use without MMAD licenses.

Thanks,

Soheil

Parents
  • 0 over 6 years ago
    The situation is most difficult. As I told, it takes time to describe the whole configuration. There is another option, which could solve the timing problem in our case. If we use different EA in source for FIM and DirSync, we could create target object for matching before we move source object to the sync. For example EA8 for FIM and EA9 for DSA. Source Admin has to set first EA8. Then two hours later set EA9 and later set EA13.

    Just a little bit more about the configuration in our environment:
    I agree with the idea to get GAL full before migration of the first mailbox. Mailbox enabled users in target will not work, because we have to migrate 8 Exchange organization parallel. And each of 8 has more than one Exchange Server in up to 5,6, or 7 in other trees, which we are not allowed to connect to their Domain Controllers in first migration step. Instead of one by one Exchange org. we have to migrate only Mailboxes on first Exchange Server in each 8 Exchange Organization. Unresolved links are daily business, but this is another problem.
Reply
  • 0 over 6 years ago
    The situation is most difficult. As I told, it takes time to describe the whole configuration. There is another option, which could solve the timing problem in our case. If we use different EA in source for FIM and DirSync, we could create target object for matching before we move source object to the sync. For example EA8 for FIM and EA9 for DSA. Source Admin has to set first EA8. Then two hours later set EA9 and later set EA13.

    Just a little bit more about the configuration in our environment:
    I agree with the idea to get GAL full before migration of the first mailbox. Mailbox enabled users in target will not work, because we have to migrate 8 Exchange organization parallel. And each of 8 has more than one Exchange Server in up to 5,6, or 7 in other trees, which we are not allowed to connect to their Domain Controllers in first migration step. Instead of one by one Exchange org. we have to migrate only Mailboxes on first Exchange Server in each 8 Exchange Organization. Unresolved links are daily business, but this is another problem.
Children
No Data