REF: E14 Mailbox Role – Part 2 – Address List & Calendar Repair

-

 

先提 Address List 看起來沒有什麼新的


Understanding Calendar Repair

The Calendar Repair Assistant (CRA) is a configurable, time-based mailbox assistant that runs within the Microsoft Exchange Mailbox Assistants service on Exchange 2010 mailbox servers. CRA automatically detects and corrects inconsistencies that occur for single and recurring meeting items for mailboxes that are homed on that mailbox server so that recipients will not miss meetings or have unreliable meeting information.

 

Conflict Detection and Correction

CRA uses the organizer copy as 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 items for inconsistencies. The only exception to this rule is when CRA compares the attendees' and organizer's response status. In that case, CRA assumes that the attendee's response status is the correct one and updates the organizer's tracking information. CRA corrects inconsistencies by sending special repair update messages to the mailbox of either the attendee of the organizer.

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.

 

[PS] C:\Windows\system32>Get-Mailbox -identity bqt.e14user1 | fl -property calendarrepairdisabled

CalendarRepairDisabled : False

image

 

CRA detects and corrects the following issues:
  • Attendee's calendar item has the wrong time   The organizer and the attendees have different times or dates for the meeting. CRA changes the meeting time on the attendees' calendar items to the time that is on the organizer's calendar item.
  • Attendee's calendar item has the wrong location   The organizer and the attendees have different locations for the meeting. CRA corrects and merges the location information on the attendees' calendar items to the location that is on the organizer's calendar item.
  • Attendee's calendar item is missing   CRA detects that some attendees have responded to the organizer's meeting request with Accept or Tentative and the item is no longer on the attendee's calendar. CRA will re-create the meeting in the attendees' calendars with the response status on the organizer's 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 organizers attendees list   CRA detects that attendees have the meeting on their calendars, but the organizer does not have those attendees listed in their attendee list. CRA adds the attendees to the organizers list of attendees.

     

    CRA will not add the attendees to the organizer's list of attendees from meetings sent to large distribution groups with more than 200 members. 


    image

  • 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.
  • 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:
    • 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.
    • If CRA could not 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.
    • 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.
    • If CRA couldn't determine which item to keep based upon the last modified time, it will keep the first calendar item that is returned by the database when querying for duplicate meetings and delete the other items.
  • Organizer's calendar item is missing   CRA detects that the attendee has a meeting on their calendar but the organizer doesn't have the meeting item any more. CRA marks the attendee's meeting as Cancelled and the attendee's free/busy status is now Free.

 

Calendar Repair Log

Every time CRA changes a calendar item on a user's mailbox, it writes to a log file. The output of the log file doesn't reveal personal data, such as the body of the message or attachments. The log only contains the minimum information to identify the meeting that was repaired and what repair actions happened to the meeting. One repair log is created for every mailbox each time CRA runs. By default, calendar repair logging is enabled.

The calendar repair log is configurable for a server and can be turned on or off for a server or user. For more information, see Managing Calendar Repair.

The default calendar repair log path is <Exchange Installation Path>\v14\Logging\Calendar Repair Assistant.

The log files are created with the following naming convention:

CRAYYYYMMDDHH-X.<alias>.log

  • CRA   Calendar repair assistant prefix.
  • YYYY   Year
  • MM   Month
  • DD   Day
  • HH   Hour
  • X   Instance
  • Alias   Mailbox alias
  • Log   File extension

[PS] C:\Windows\system32>Set-MailboxServer -Identity bqt-e14mbs1 -CalendarRepairLogPath "c:\CRA_Log"

image


Configure Calendar Repair Assistant Settings

You can use the following Set-MailboxServer cmdlet parameters to configure CRA settings:

  • CalendarRepairIntervalEndWindow   Use this parameter to specify how far into the future you want CRA to look for calendar errors. The default value is 30 days.
  • CalendarRepairMissingItemFixDisabled   Use this parameter to disable CRA from fixing missing items. By default, CRA fixes missing calendar items on attendee's calendars. If an attendee is missing a calendar item, the item will be re-created.
  • CalendarRepairSchedule   Use this parameter to configure a schedule for when CRA will run. By default, a schedule for CRA isn't configured. If you don't specify a schedule, CRA won't run. If CRA doesn't finish processing the mailboxes on the server during the time that you've scheduled, it automatically resumes processing where it left off the next time it runs.

 

[PS] C:\Windows\system32>Get-MailboxServer -Identity bqt-e14cas1 | fl

RunspaceId                                    : 9e68a44f-3db0-4427-a6f8-8875707fe7a0
Name                                          : BQT-E14CAS1
CalendarRepairSchedule                        : {}

[PS] C:\Windows\system32>Set-MailboxServer -Identity bqt-e14cas1 -CalendarRepairSchedule "Monday.1:00 AM-Friday.11:50 PM"

[PS] C:\Windows\system32>get-MailboxServer -Identity bqt-e14cas1 | fl -property CalendarRepairSchedule

CalendarRepairSchedule : {星期一.上午 01:00-星期五.下午 11:45}

 

Restart MS Exchange Mailbox Assistants service

image

<?xml version="1.0" encoding="utf-8"?>
<CalendarRepairLog SchemaVersion="3.00" MailboxUser="BQT.E14User1" ServerVersion="Version 14.0 (Build 639.0)" RangeStart="11/16/2009 03:30:00" RangeEnd="12/16/2009 03:30:00">
  <Meetings />
</CalendarRepairLog>



Blog Extended Reading

More Information & Reference

1. Understanding Address Lists
2. Understanding Calendar Repair
3. Configure Calendar Repair Assistant Settings
4. Configure Calendar Repair Log Settings

image

Comments

Post a Comment

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c79921331         Last attempt @ 2013-12-19 17:
Read more

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Section EnableSerializationDataSigning -Parameters @("Enabled=true&qu
Read more

E14–Bulk Create Mail Contact & Set-Contact

-
Image
  http://community.office365.com/en-us/w/exchange/579.aspx     Get-Contact | Export-Csv c:\temp\contact.csv Get-MailContact | Export-Csv c:\temp\Mailcontact.csv   [PS] Import-Csv .\Contact_Source.csv | % {New-MailContact -Name $_.Name -DisplayName $_.DisplayName -ExternalEmailAddress $_.ExternalEmailAddress -Alias $_.Alias -PrimarySmtpAddress $_.PrimarySMTPAddress -OrganizationalUnit "Contacts" -WhatIf }   [PS] >$Contacts = Import-Csv .\Contact_final.csv [PS] >$Contacts | foreach {Set-Contact $_.Name -Company $_.Company -Department $_.Department -Office $_.Office -Phone $_.Phone }
Read more