Calendar Repair Assistant

Hello rstevenson ,

It is best to disable the Calendar Repair Assistant to avoid issues during mail migrations and enable it once the mail migrations have completed.   We have a few knowledgebase articles below on this subject.

https://support.quest.com/on-demand-migration/kb/4376081/odm-your-meeting-was-found-to-be-out-of-date-and-has-been-automatically-updated

https://support.quest.com/on-demand-migration/kb/4286933/inconsistencies-caused-by-cra

Thanks,

Doug

From what I’ve seen, the Calendar Repair Assistant (CRA) usually runs in the background and tries to fix mismatches between the organizer’s and attendee’s calendars. If a meeting exists on one side but not the other, CRA may recreate or update it automatically. If you’re seeing unexpected meeting updates or items reappearing, it’s often because a meeting was deleted instead of being declined, so CRA assumes it was removed by mistake and restores it. In migration scenarios some admins temporarily disable CRA with PowerShell to avoid these conflicts and then enable it again later.

From what I’ve seen, the Calendar Repair Assistant (CRA) usually runs in the background and tries to fix mismatches between the organizer’s and attendee’s calendars. If a meeting exists on one side but not the other, CRA may recreate or update it automatically. If you’re seeing unexpected meeting updates or items reappearing, it’s often because a meeting was deleted instead of being declined, so CRA assumes it was removed by mistake and restores it. In migration scenarios some admins temporarily disable CRA with PowerShell to avoid these conflicts and then enable it again later.