Exchange 2010 Calendar Repair Tool

  • Article

Merhabalar

Exchange 2010'la birlikte, genellikle mobil cihazlarla kullanim oldugunda yasanan Calendar'lardaki bozulma-silinme-kaybolma problemlerini minimuma indiren Calendar Repair Tool kullanima sunuluyor. Konuyla ilgili detayli bilgi su sekilde :

Understanding Calendar Repair in Exchange 2010

The Calendar Repair Assistant (CRA) is a configurable, mailbox assistant that runs within the Microsoft Exchange Mailbox Assistants service on servers running Microsoft Exchange Server 2010 with the Mailbox server role installed. CRA automatically detects and corrects inconsistencies that occur for single and recurring meeting items for mailboxes homed on that Mailbox server so that recipients won't miss meeting announcements or have unreliable meeting information.

The Calendar Repair Assistant performs the following functions:

  1. Detects inconsistencies.
    CRA uses the organizer copy as a master copy for all meeting items, and it assumes that the organizer's calendar item is the correct copy. CRA then compares the attendee's calendar item with the organizer's calendar item for inconsistencies. The only exception to this rule is when CRA compares the attendee and organizer response status. In that case, CRA assumes that the attendee's response status is the correct one, and updates the organizer's tracking information.
  2. Determines client intent.
    CRA determines if the inconsistency was intentionally introduced by attendees using their calendar client, such as Outlook. Only if CRA is sure that the attendee did not introduce the inconsistency, will it then correct the problem. If CRA is not sure that the inconsistency was intentional, it will perform no further action.
  3. Corrects inconsistencies.
    CRA corrects inconsistencies on the server on which it runs. However, CRA will read from other Exchange 2010 Mailbox servers to compare the organizer's calendar item. CRA doesn't overwrite the recipient's calendar information; it merges the information so that no data is lost. In addition, the repair update messages are moved to the recipient's Deleted Items folder.
  4. Sends a calendar repair update message if a correction was made.
    Calendar repair update messages are sent to user's whose calendar items were updated by CRA. When CRA sends a update message, it places the message in the user's Deleted Items folder instead of sending the message to the user's inbox. This allows CRA to send a record to the user's mailbox without causing user confusion. If the user is experiencing calendar inconsistencies, their Exchange administrator can advise them to look in their Deleted Items folder for troubleshooting purposes. CRA only sends repair update messages if the issue is fixed.

Conflict Detection and Correction

This section describes the scenarios in which CRA detects and corrects issues.

  • Attendee's calendar is missing an item or recurring meeting request CRA detects that the attendee has accepted the organizer's meeting request or recurring meeting request, but the meeting items are not on the attendee's calendar. CRA checks the database version of the attendee and finds that the attendee intentionally deleted the item without sending a response. If CRA can't determine that the meeting item was intentionally deleted by the attendee, the meeting request is re-created. If CRA determines that the change was intentional, it will perform no further action on the calendar item.
  • Attendee's calendar is missing an occurrence or exception CRA detects that an attendee is missing an occurrence or exception within a recurring meeting series. CRA checks the meeting master if a deleted exception exists and sees that the attendee intentionally deleted the meeting request without sending a response. If CRA can't determine that the meeting item was intentionally deleted by the attendee, the meeting request is re-created. If CRA determines that he change was intentional, it will perform no further action on the calendar item.
  • Attendee's calendar item tracking status doesn't match the organizer's tracking status CRA detects that attendees' response status for the meeting doesn't match the status on the organizer's calendar item. In this case, the organizer's tracking status is updated with the status on the attendee's calendar item.
  • Attendee isn't on the organizer's attendees list CRA detects that attendees have the meeting on their calendars, but the organizer doesn't have those attendees listed in the attendee list. CRA adds the attendees to the organizer's list of attendees.
  • Attendee's recurring meeting doesn't match the organizer's recurring meeting CRA detects that the attendee is on some of the organizer's recurring meetings and the attendee's recurrence pattern doesn't match the organizer's recurrence pattern. CRA replaces the attendee's recurrence pattern with the organizer's recurrence pattern.
  • Attendee's meeting location doesn't match the organizer's meeting location CRA detects that the location of the attendee's meeting doesn't match the location recorded in the organizer's calendar item. If the attendee intentionally changed the meeting location, CRA doesn't make any changes. If CRA can't determine that the location was intentionally changed by the attendee, the attendee's calendar item is appended with the meeting location on the organizer's calendar item.
  • Attendee's start/end time doesn't match the organizer's start/end time CRA detects that the attendee's start and/or end time is different from that of the organizer's. If CRA determines that the attendee intentionally changed the time, then the time is not changed. If CRA determines that the mismatch was unintentional, then the start time and/or end time is changed if either time differentiates more than 2 hours from the organizer's start or end time.
  • Organizer or attendees have multiple calendar meetings that appear the same CRA detects that the organizer or attendee has multiple meetings that have the same MAPI property identifier LIL_GLOBAL_OBJID. CRA compares all of the duplicates and performs the following steps to correct the inconsistency:
    1. CRA checks the sequence numbers of all of the duplicates. If one duplicate has the highest sequence number, that duplicate is kept, and the other meetings are deleted.
    2. If CRA couldn't determine which item to keep based upon the sequence number, it checks the OwnerCriticalChangeTime property. If one of the duplicates is the most recent copy, it keeps that duplicate item, and the other meeting items are deleted.
    3. If CRA couldn't determine which item to keep based upon the most recent copy, it checks the LastModifiedTime property. If one of the duplicates has the last modified time, CRA keeps that duplicate item, and the other meeting items are deleted.
    4. If CRA couldn't determine which item to keep based upon the last modified time, it keeps the first calendar item returned by the database when querying for duplicate meetings, and the other items are deleted.
  • Organizer is missing a calendar item CRA detects that an attendee has a single meeting on his or her calendar, but the organizer does not have this item on the calendar. CRA checks if the organizer intentionally deleted the meeting. If the organizer intentionally deleted the meeting, CRA sends a cancellation to the attendee. If the organizer's intent can't be determined, then no cancellation is sent.