• State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 17 subscribers
  • Views 8266 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

Mailbox deleted or simply overwritten?

rich_stevenson
over 7 years ago

MMEX 8.13, legacy agents, Exchange 2010 in source and target

I have a mailbox user matching in both source and target

I have the ForbidDelMailbox set to 0.

I need some clarification on what actually happens when the tool, cal or mail sync, sees the existing target mailbox.

Does it actually delete the mailbox and re-create it, or is it overwriting it?

Parents
  • 0 over 7 years ago
    Correct, but in this case the mailbox exists in the target first. Then I let the DSA run, then calendar sync. So it deletes the existing mailbox for the same reasons stated in that article, and re-creates it. But it appears to be saving those attributes and applying them to the new mailbox. Customer is just looking for confirmation on that as I also thought it was a full-on delete.
Reply
  • 0 over 7 years ago
    Correct, but in this case the mailbox exists in the target first. Then I let the DSA run, then calendar sync. So it deletes the existing mailbox for the same reasons stated in that article, and re-creates it. But it appears to be saving those attributes and applying them to the new mailbox. Customer is just looking for confirmation on that as I also thought it was a full-on delete.
Children
No Data