Exchange Server 2010 Introduction to

Supporting Administration
Calendaring

Jonathan Runyon
Exchange 2010 Content BRE
Microsoft
1 1/1/2009 Microsoft Confidential - For Internal Use Only
Lesson 1: Exchange 2010 Calendaring Overview
Lesson 1: Exchange 2010 Calendaring Overview
After completing this lesson you will be able to:
Describe the challenges administrators faced when
managing calendaring features in previous versions of
Exchange.
Understand the how these challenges have been
addressed by the new calendaring features of Exchange
2010.
Calendaring in Previous Versions of Exchange
Calendar Resiliency
Prone to issues
user mismanagement
3rd party applications
Calendar Troubleshooting
Investigation difficult, time consuming
Gathering data requires coordination
User may not understand bad habits that cause issues
Calendar Management
Simple management limited to administrators
Resource mailbox calendar management limited to one
management workflow
Exchange 2010 Calendaring Improvements
Calendar Repair
Common calendar issues are detected and repaired
Calendar Diagnostics
Gather diagnostic information directly from mailbox without user
participation
Calendar Management
New workflows/interfaces for managing user and resource mailbox
calendars
Lesson Review
Previous versions of Exchange presented certain
challenges for managing and troubleshooting calendar
issues.
Exchange 2010 introduces new concepts and tools that
make calendars more resilient and easy to maintain for
both end-users and administrators.
Lesson 2: Exchange 2010 Calendaring Repair
Calendar Repair
Focus of Calendar Repair
Calendar Repair Assistant
Focus of Calendar Repair

Correct issues in the calendar of a user to avoid:

the user missing a meeting
having an unreliable calendaring experience
Focus of Calendar Repair (continued)
Failure Definition What it causes
Missing From A calendar item that should exist in a person’s calendar is missing.  People missing
Calendar Examples: meetings
(a) User1’s calendar indicates that he is invited to a meeting organized by User2, but
User2’s calendar does not have the corresponding item.
(b) User2’s calendar item indicates that User1 Accepted (or Tentatively Accepted) her
invitation, but User1 does not have the meeting in his calendar.

Wrong Time Organizer and attendee items have mismatched start and end times or locations. People missing
or Location Trivial mismatches are identified and not counted. meetings

Wrong Tracking information in the organizer’s item does not match information in the attendee’s Unreliable experience
Tracking Info calendar item.
Examples:
(a) User4’s item indicates that he Accepted a meeting organized by User3, but the
tracking information for User4 in User3’s item displays None.
(b) User6 has a meeting invitation from User5, but User5 is not aware that User6 is an
attendee (because User6 is not listed explicitly or as a member of a Distribution List).

Duplicated Multiple calendar items representing the same meeting are present. Unreliable experience
Each calendar item has a unique identifier. If e.g. 3 items have the same ID, we say that 1
item has duplicates. In a calendar, duplicates may show side by side or at different times
(if one of them is updated but the other is not).

Can’t open Calendar item that can’t be opened. Unreliable experience

Items are opened with XSO (Exchange calendar business logic layer), which is a bit less
forgiving to errors than OLK.
Repair Principles
Non-intrusiveness to the user
Repair information logged for analysis
Configurable repair options
Organizer item is the master copy
Repairs items on server where found
Stateless repair rules
“Local” information on attendee item preserved
Recoverable deletion of items
Repair obeys meeting update rules
Re-creating items considers private information on
organizer’s item – no message body or attachments
Calendar Repair Assistant
Runs on all Exchange 2010 Mailbox role servers
Repairs calendar items for mailboxes on the mailbox server
Built as a time based Mailbox Assistant
Similar to the Messaging Records Management (MRM)
assistant
Main processing component is the CalendarValidator
Performs a series of checks on each calendar item that it finds in
the Calendar folder
Takes action only if the test confirms there is a result that requires
further action
CRA maintains a text log for each mailbox, records any
actions taken to repair a calendar item
Errors are not recorded in these logs, instead handled by
Application Event log
Calendar Repair Assistant Components
Calendar Properties
Calendar Repair Tests
CalendarValidator Checks
Repair Update Message
Inconsistencies Repair
Calendar Repair Log
Calendar Properties considered by CRA
These properties are consistent to the calendar item:
GlobalObjectId (unique identifier)
CleanGlobalObjectId (unique identifier, recurring item)
OwnerAppointmentId
InternetMessageID
These properties can be different, as set by organizer or as
set by attendee:
Subject
Location
StartTime
EndTime
Calendar Repair Tests
For any given meeting, there is:
An organizer
One or more attendees
These are considered counterparts of the meeting
CRA tests a user’s calendar item
Depending on the test, CRA must access Calendar folder in the
counterpart(s) mailbox and test their copy of the item as well
Counterpart’s mailbox may be in same database, on a different
server, or on a server in different AD site
Inconsistencies detectable by CRA are in either two
categories:
Organizer’s data about one (or more) attendee’s presence
mismatching the attendees' data
Attendee’s data about meeting is mismatching organizer's data
Comparison Tests

Condition Test for Organizer Test For Attendee

Missing item Whenever an attendee responded as either accepted Whenever the organizers item is not in the
or tentatively, and the meeting is missing from the organizers calendar anymore and the attendee
attendees calendar. has a non-cancelled item in their calendar.

Corrupt item When processing a calendar item, the item can’t be Same
opened

Duplicate item Whenever there are 2 or more items that have the Same
same GOID.

Wrong time/location None - The organizer’s items is always considered Whenever the attendee’s location string does
correct. not contain the organizers location.
Whenever the times are outside the 2 hour
boundary allowance, or if there is zero overlap.

Wrong tracking status Whenever the tracking status on the organizers item None - Does not apply because the attendee
is different than on the attendee’s item, and the item includes no tracking information.
organizer has a value of accepted, tentative, or
declined.
(i.e., the user responded once before, but for some
reason did not continue to inform the organizer of
their intent).
CalendarValidator Checks
Check Name
CanValidateOwnerCheck
ValidateStoreObjectCheck
UserExistsCheck
MeetingExistenceCheck
MeetingCancellationCheck
TimeZoneMatchCheck
MeetingPropertiesMatchCheck
RecurrenceBlobsConsistentCheck
RecurrencesMatchCheck
DeletedOccurrencesMatchCheck
AttendeeOnListCheck
CorrectResponseCheck
ModifiedOccurrencesMatchCheck
Description
Checks whether the counterpart user can be validated or not.
Calls Validate() on the base calendar item.
Checks whether the counterpart user can be found or not.
Checks whether the item can be found in the owner's calendar or not.
Checks to make sure that the meeting cancellations statuses match.
Checks to make sure that the attendee has correct recurring time zone
information with the organizer.
Checks to make sure that the attendee has the correct critical properties
for the meeting.
Checks to make sure that the recurrence blobs are internally consistent.
Checks to make sure that the attendee has the correct recurrence
pattern.
Checks to make sure that the attendee has correct deleted occurrences.
Checks to make sure that the attendee is listed on the organizer's list of
attendees.
Checks to make sure that the organizer has the correct response recorded
for the attendee.
Checks to make sure that the attendee has correct exceptions.
Repair Update Message (RUM)
CRA does not take action directly on counterpart’s
calendar items
Instead, uses specialized meeting message called Repair Update
Message (RUM)
Utilizes existing calendaring logic to synchronize the inconsistent
calendar items
Message types:
Organizer inconsistent – Response sent to attendee(s)
Attendee inconsistent – Request sent on behalf of organizer
Calendar Assistant performs the required process on the
RUM and makes the items consistent again
Multiple repair actions can be sent in a single message
Sample RUMs

One or more problems with your meeting were detected and fixed.
One or more problems with your meeting were detected and fixed.
Problem(s) Fixed:

• Start Time
• End Time
• Location
Sent by Microsoft Exchange Server 2010

This meeting has been canceled by the organizer.

This meeting has been canceled by the organizer. To see the original contents of
the meeting, view the item in your calendar.
Sent by Microsoft Exchange Server 2010
Additional RUM behavior
A meeting response is only sent when:
The response status on the attendee’s item does not match the
tracking info on the organizer’s item
The organizer has requested meeting responses
The attendee has actually sent a response to the meeting request
CRA is dependent on Transport Service for delivering
RUMs, and Calendar Attendant for processing RUMs
Inconsistencies Repair Actions
Inconsistency Description
Attendee Missing Meeting Attendee does not have the meeting for
which they have an Accept or Tentative
response.
Attendee Not In Organizers Attendee has a calendar item for which
Attendee List the organizer does not have that user in
the attendee list.
Organizer time properties StartTime/ EndTime, are not anywhere
don’t match within the allowed 2 hour window.
Attendee’s location The attendee’s value for location does
property is not similar to not contain anything of the organizer’s
organizer’s location.
Recurrence pattern check Pattern, type, etc  values do not match
Failed
Exceptions check Failed The list of occurrences/exceptions don’t
match
Actions to take / Heuristics
Create the attendee item with critical
values from the organizer; no body or
attachments copied
 Add the user to the recipient list with
the response status and response time of
attendee.
Is not added if DL expansion failed for a
DL.
Change the attendee’s value to be equal
to organizer’s values / create the largest
overlap fitting the 2 hour allowance.
Prefix the organizer’s original value
Copy the organizer’s values for type,
pattern, interval, etc.
Merge the modified occurrences
Intersect the deleted occurrences (i.e.
have as few deletes as are in both)
Inconsistencies Repair Action (continued)
Inconsistency Description
Incorrect Response The organizer has a response from the
attendee, but it does not match what is
found in the attendee’s calendar.
Organizer Missing Organizer does not have a meeting or
Meeting canceled meeting exists for which an
attendee has an accepted meeting.
Duplicates Detected Two items with the same GOID were
found. Future updates will only be
applied to 1 item.
Actions to take / Heuristics
Update Organizer tracking info with attendee
response + response time if attendee is on the
attendee list.
Mark attendee item as canceled and timeslot as
free
Detect the older items as oldest update sequence
number and /or oldest last_modification time
and/or oldest OwnerCriticalChangeTime
If oldest determination is not possible, pick the
first one as the newest one and delete the older
items.

Version Data Missing Sequencenumber, If missing from an attendee item, copy from the
LastSequencenumber, organizer, and copy all values (i.e.
OwnerCriticalChangeTime missing UpdateCalendarItem)
from the item. If missing from organizer, then open attendee
mailboxes, get the highest numbers, add OFFSET of
100 and set the version information.

Version Data Sequencenumber, Copy newest data to the attendee data

Out-of-sync OwnerCriticalChangeTime don’t match If organizer is older than attendee, then copy
highest number, and  set the version information
Scenario 1: Changes to an attendee’s calendar item to adjust to the organizer’s item
Time and Location.

Case: Attendee wrong location

CRA validates user’s Calendar
On some calendar items it detects that organizer has a different
location for meetings than attendee(s)
CRA corrects and resets location information on attendee(s) items to
location value of organizer item
Case: Attendee wrong time
CRA validates a user’s Calendar
On some items where user is an attendee it detects that organizers
item is a different time (and possibly day)
CRA handles case where there is an overlapping of time in case
attendees adjust a prolonged meeting from an organizer to reflect their
attendance requirement (the CRA applies heuristics that define
overlapping intervals)
The CRA moves the item to the time of the organizer
Scenario 2: Organizer calendar item or organizer is missing

The CRA validates a user’s Calendar

On some items where user is an attendee it detects that
the organizer doesn’t have the item in their Calendar
CRA marks the attendee calendar item as canceled and
free
Scenario 3: Attendee’s calendar item missing with positive response

The CRA validates a user’s Calendar

On some items where the user is an organizer it detects
that some attendees responded with accept or tentative,
but the item is not in their Calendar anymore
The CRA creates the meeting in the attendee’s Calendar
and generates an RUM
Scenario 4: Consistent attendee status
The CRA validates a user’s Calendar
On some items where the user is an organizer it detects
that the response status in the attendee item doesn’t
match the tracking information in the organizers calendar
item
The CRA corrects the organizers tracking status
information for the item
Scenario 5: Consistent organizers attendee list

The CRA validates a user’s Calendar.

On some items where the user is an attendee it detects
that the user is not listed as an attendee in the Organizers
item
CRA puts this user into the attendee list on the organizer’s
item
Scenario 6: Repairing duplicate items

The CRA validates a user’s Calendar

It detects that some of the calendar items have the same
GOID (they might be at the same or different times)
User is the organizer or an attendee on those items
CRA gets all duplicates and does following in order:
1. Update sequence number: if one of the dupes has the highest,
this is kept and the other ones are deleted
2. OwnerCriticalChangeTime: if one of the dupes is the most
recent, this is kept and the other ones are deleted
3. LastModifiedTime: if one of the dupes is the last modified, this is
kept and the other ones are deleted
4. Keep the first item returned by the store, and delete the others
Scenario 7: Recurrent meetings considerations

Case: Recurrence pattern mismatch

CRA validates a user’s Calendar
User is an attendee on some recurrent meetings where the recurrence
pattern information doesn’t match the organizers recurrence pattern
CRA replaces the recurrence pattern with the pattern from the
organizer’s calendar item. This also deletes all exceptions for the series.
Case: Attendee exceptions mismatches
CRA validates a user’s Calendar
User is an attendee on some recurrent meetings where the organizer’s
copy mismatches some exceptions (this is fixing recurrence blob
attachment table inconsistencies)
CRA checks organizer’s exceptions and takes action:
For delete exceptions: The attendees’ exception that still exists is marked as
canceled and free.
For other exceptions: The attendee’s exceptions are checked and if there is
no delete of the exception it is added back to the attendee’s calendar with
only the critical properties.
Large meeting handling
Based on DL expansion cost demands
Individual attendees on the meeting are always processed
(validated/fixed)
Each DL is expanded up to a limit of 200 and repair happens for
those 200 attendees
Repair of Missing Items
Current client workflow allows an attendee to delete previously accepted
meeting without sending response to organizer
The organizer still expects the attendee to show up to the meeting, but
because the attendee does not have the meeting on the calendar, the
attendee misses the meeting
This is perceived by both the attendee and the organizer as the calendar
not being reliable
The CRA detects the case where an attendee previously accepted a
meeting and sent a response, but the meeting is missing from the
attendee’s calendar
The meeting is re-created with a clear indicator in the meeting body why
it was put back on the attendee’s calendar and the expected action from
the attendee
The CRA re-creates the meeting if the attendee continues to delete it,
until the attendee sends a response to the organizer
The CRA allows a customer to opt-out of this repair option, but repair is
enabled by default when the CRA is enabled
Repair of Missing Items - Details
Detection of missing item state
CRA checks if attendee has corresponding meeting item based on
GOID
If item is not found and organizer’s ResponseStatus for attendee is
Accepted or Tentative Accepted, then missing item state is raised
for this attendee
Repair of missing item state
To re-create missing meeting, a RUM full update is sent from
organizer to attendee
Calendar Attendant re-creates meeting as Tentative Accepted in
attendee calendar
Missing Item body text
RUM sent for missing item state has a special text body, indicating
that item was re-created because organizer had a positive
response and item was missing from attendee’s calendar
Missing Item RUM
Controlling missing item re-creation

Re-creation of missing item is a repair option

administrator can set on a mailbox server as part of
calendar repair configuration
Missing item repair is enabled by default
To disable repair administrator would use Set-Mailbox
cmdlet with CalendarRepairMissingItemFixDisabled
parameter set to $True as shown in this example:

[PS] C:\>Set-MailboxServer -Identity <Server

Name> -CalendarRepairMissingItemFixDisabled
$True
Preserving Attendee Changes
It is possible for attendees to customize certain properties
of meetings (change highlights)
If a property was changed, special logic is applied to
preserve the current value when applicable:
Property Change highlights Keep attendee’s value if
Body BodyProps Update is a RUM
StartTime MapiStartTime Original value set by organizer remains the same and the attendee’s
value falls within 2-hour tolerance.

EndTime MapiEndTime Same as above

Subject Subject Update is a RUM
Location Location Attendee’s value contains organizer’s value
Free/Busy N/A Update is informational or the Update is a RUM
Reminder N/A Already preserved for both info and full updates
Categories N/A Already preserved for both info and full updates
Calendar Repair Log
Repair results recorded into a log file on the user’s mailbox
server
Contains
Information to indicate to the administrator what got fixed
Sufficient information to locate the meeting in case needed
Naming Convention
CRA + <current date/time: YYYYMMDDHH>-<sequence>.<user>.LOG

CRA writes logs to the <Exchange installation

path>\Logging\Calendar Repair Assistant folder
Using Set-MailboxServer cmdlet administrator can control:
log file location
maximum size of log file directory before oldest logs are removed
age limit for log files
Calendar Repair Log (continued)
Contains the following specific information:
Specific information about the meeting, including the Meeting
Subject, MeetingType, StartTime, EndTime, and Organizer
Attendee(s) that is being checked for inconsistencies
Consistency Checks that are being performed and the results of
each check
Any detected inconsistencies
Details on the RUM that is a result of the inconsistency(ies)
CRA log file contains information in XML format
Lesson 3: Calendar Diagnostics
Lesson 3: Calendar Diagnostics
Calendar Diagnostic LoggingRetrieving the Logs for
Analysis
Analyzing Calendar Diagnostics Logs
Calendar Diagnostic Logging Basics: Snapshots

Snapshots provide a history of the item

Uses Exchange 2010 Copy-on-Write functionality to save
a copy of a calendar item before any changes are made
Allows the retrieval of the state of any item as it was at any
point in time, as well as calculating the effective changes
that happened to the item as the result of each transaction
Snapshots are made for all calendar items including
appointments, meetings and meeting messages
Meeting messages include meeting requests, responses,
cancellations and forward notifications
Calendar Diagnostic Logging Basics: Metadata
Metadata is added to a calendar item as a property entry to
allow for a more detailed diagnosis of the causes of any
change
When a change is made to a calendar item, a snapshot is
made first to persists the current metadata
Metadata can be classified as three types:
Basic Context who did what in general terms. This is any relevant
information about who did the change and what the general
change was (create, update, delete). It includes, but is not limited to,
user, machine, application, and so on.
Historic Context when it was done. The logs maintain historical
record of when the change occurred while maintaining other
important historical data like Creation time.
Operation Context details on how it was done. The operation
context contains information about what was done to the calendar
item as part of the XSO processing sequence.
Log Storage

Calendar item snapshots are saved in the root folder of the

mailbox dumpster
In Exchange 2010 this is the Recoverable Items folder,
which is in the Non-IPM Subtree of the mailbox and is
hidden from client view
The dumpster has been redesigned for Exchange 2010 and
includes special logic for handling calendar item snapshots
so they are retained for 90 days before being
automatically purged from the dumpster
logic used to maintain snapshot copies
On Create operation:
Specific calendaring logging metadata is added as a set of
properties on the item in the IPM Subtree
On Update operation:
Specific calendaring logging metadata is added as a set of
properties on the item in the IPM Subtree.
This overwrites the original set when the item was created, but
Copy-On-Write already made a snapshot copy of the item to the
Dumpster, including the previous calendaring logging metadata
On Delete operations:
Item is saved to the dumpster with the current calendar logging
metadata
An additional snapshot copy of the item is saved to the Dumpster
with the Delete operation calendaring logging metadata added
Logging Recurring Meetings

Log entries for recurring exceptions are not any different

from the ones for single instance meetings
Whenever there is a change in an exception, there is a log
entry for that exception and a log for the corresponding
master
As in other cases, the snapshot includes only a subset of
the item’s content
The exception attachment and any other kind of
attachment are not included
What Triggers Logging

User actions that trigger calendar diagnostic logging can

be found in the table on Page 28.
Examples:
Create new appointment
Create new meeting
Create new re-occurring meeting
Retrieving the Logs for Analysis
The Get-CalendarDiagnosticLog cmdlet is used to retrieve
calendar diagnostic logs from a user’s mailbox and then store
them in a file system folder to allow for further analysis
The task searches the specified mailbox using a query based on
the specified subject of an appointment or meeting
The task returns all calendar items and snapshots that match the
search criteria and is not limited to searching only the dumpster
folder
If the search criteria matches more than one calendar item with
the same subject, the task retrieves items for all matches.
The file system location where retrieved calendar items are
written can be specified as part of the command, or it can be
read from the LogLocation registry value in the following
location:
HKLM\SOFTWARE\Microsoft\ExchangeServer\v14\CalendarLogs
Workflow Example

Administrator for Contoso receives a report of a possibly

corrupt recurring meeting from user “ITPro01”, confirms
meeting subject is “Weekly Staff Meeting”
Administrator decides to gather diagnostic logging for the
meeting from ITPro01’s mailbox for further analysis
Administrator executes the following command:
Get-CalendarDiagnosticLog -Identity itpro01 -Subject
“Weekly Staff Meeting”
The task makes a connection to itpro01’s mailbox to search
for calendar items matching the subject specified. M
The task creates a subfolder to contain the items that were
retrieved
To examine the retrieved logs Outlook is used to open each
item as message
Analyzing Calendar Diagnostics Logs
Lesson 4: Managing Calendaring
Managing Calendaring with EMS
Calendar Management Commands
Associated Calendaring Commands
Calendar Management Commands
Get-MailboxCalendarConfiguration
Set-MailboxCalendarConfiguration
Get-CalendarProcessing
Set-CalendarProcessing
Get-MailboxCalendarFolder
Set-MailboxCalendarFolder
Get-CalendarNotification
Set-CalendarNotification
Get-CalendarDiagnosticLog
Get-MailboxCalendarConfiguration
Use to show the calendar settings for a specified mailbox
These calendar settings define a user’s work days, working hours, work time
zone and reminder settings

[PS] C:\>Get-MailboxCalendarConfiguration -Identity itpro01 | Format-

List
 
RunspaceId : 4d317f4f-2549-4c81-bac9-e78610dd8829
WorkDays : Weekdays
WorkingHoursStartTime : 08:00:00
WorkingHoursEndTime : 17:00:00
WorkingHoursTimeZone : Pacific Standard Time
WeekStartDay : Sunday
ShowWeekNumbers : False
TimeIncrement : ThirtyMinutes
RemindersEnabled : True
ReminderSoundEnabled : True
DefaultReminderTime : 00:15:00
Identity : itpro01
IsValid : True
Set-MailboxCalendarConfiguration
Use to apply calendar settings for users using Microsoft
Office Outlook Web App calendars.
This affects how the user's calendar looks and how
reminders work in Outlook Web App. This also affects
settings that define how meeting invitations, responses,
and notifications are sent to the user.
[PS] C:\>Set-MailboxCalendarConfiguration -Identity itpro01
-WorkingHoursStartTime 09:00:00 -WorkingHoursEndTime 18:00:00
-WorkingHoursTimeZone "Central Standard Time"
Get-CalendarProcessing
Use to retrieve the calendar related processing
configuration on the target mailbox
The configuration information is used by the Calendar
Attendant and the Resource Booking Assistant for
processing calendar meeting items

[PS] C:\>Get-CalendarProcessing -Identity itpro01

Identity AutomateProcessing
-------- ------------------
contoso.com/ITPros/itpro one AutoUpdate
Set-CalendarProcessing
Use to modify calendar-related processing configuration
properties for the target mailbox, which include Calendar
Attendant, resource booking assistant, and calendar
configuration

[PS] C:\>Set-CalendarProcessing -Identity user22

-AutomateProcessing None

[PS] C:\>Set-CalendarProcessing -Identity room01

-AutomateProcessing AutoAccept -AllBookInPolicy $true
-ScheduleOnlyDuringWorkHours $True

[PS] C:\>Set-CalendarProcessing -Identity room02

-AutomateProcessing AutoAccept -AllBookInPolicy $False
-AllRequestInPolicy $True -ResourceDelegates user21
Get-MailboxCalendarFolder
Use to retrieve the publishing or sharing settings for a specified mailbox
calendar folder
Includes the calendar folder name, whether the folder is currently published or
shared, the start and end range of calendar days published, the level of details
published for the calendar, whether the published URL of the calendar can be
searched on the Web, and the published URL for the calendar

[PS] C:\>Get-MailboxCalendarFolder itpro01:\Calendar

RunspaceId : 4d317f4f-2549-4c81-bac9-e78610dd8829
Identity : contoso.com/ITPros/itpro one:\Calendar
PublishEnabled : True
PublishDateRangeFrom : OneMonth
PublishDateRangeTo : Whole
DetailLevel : LimitedDetails
SearchableUrlEnabled : False
PublishedCalendarUrl :
IsValid : True
Set-MailboxCalendarFolder
Use to configure publishing or sharing settings on a
calendar folder of a specified mailbox. The calendar folder
can be configured as follows:
Whether the calendar folder is enabled for publishing
Range of start and end calendar days to publish
Level of detail to publish for the calendar
Whether the published URL of the calendar is enabled for search
on the Web
Published URL to display for the calendar

[PS] C:\>Set-MailboxCalendarFolder -Identity room01:\Calendar

-DetailLevel FullDetails -PublishDateRangeFrom OneMonth
-PublishDateRangeTo ThreeMonths
Get-CalendarNotification
Use to return a list of all calendar notification settings for a user
The cmdlet retrieves and then displays the rules used to trigger the
calendar agenda notification, reminder notification, or update
notification

[PS] C:\>Get-CalendarNotification -Identity itpro01

 
RunspaceId : 4d317f4f-2549-4c81-bac9-
e78610dd8829
Identity : contoso.com/ITPros/itpro one
CalendarUpdateNotification : False
NextDays : 1
CalendarUpdateSendDuringWorkHour : False
MeetingReminderNotification : False
MeetingReminderSendDuringWorkHour : False
DailyAgendaNotification : False
DailyAgendaNotificationSendTime : 08:00:00
MailboxOwnerId : contoso.com/ITPros/itpro one
IsValid : True
Set-CalendarNotification
Use to set text message notifications for calendar events
for a user
The cmdlet makes it possible to modify the rules that
trigger the calendar agenda notification, reminder
notification, or update notification text messages to be
sent to the specified user
[PS] C:\>Set-CalendarNotification -Identity itpro01
-CalendarUpdateNotification $true -MeetingReminderNotification
$true -MeetingReminderSendDuringWorkHour $true

[PS] C:\>Set-CalendarNotification -Identity contoso\itpro03

-DailyAgendaNotification $true -NextDays 3
Get-CalendarDiagnosticLog
Use to gather all data for a given calendar item based on
subject, and place the information in a specified file system
folder

[PS] C:\>Get-CalendarDiagnosticLog -Identity itpro01

-Subject "weekly staff meeting" -LogLocation
"C:\calendarlogs\"
Associated Calendaring Commands
Get-Mailbox
Set-Mailbox
Get-MailboxServer
Set-MailboxServer
Get-Mailbox
Used to view the calendar configuration
information for a mailbox

[PS] C:\>Get-Mailbox -Identity itpro01 | Format-List name,

calendar*

Name : itpro one

CalendarRepairDisabled : False
CalendarVersionStoreDisabled : False
Set-Mailbox
Used with the CalendarRepairDisabled parameter to
specify that mailbox won't have its calendar items repaired
by Calendar Repair Assistant
The two possible values for this parameter are $true or
$false (default)

[PS] C:\>Set-Mailbox -Identity itpro02

-CalendarRepairDisabled $true -CalendarVersionStoreDisabled
$true
Get-MailboxServer
Used to view configuration information that is related
to mailbox calendar processing on a mailbox server

[PS] C:\>Get-MailboxServer -Identity conseamb1 | Format-List name, *calendar*

Name : CONSEAMB1
CalendarRepairSchedule : {Mon.8:00 AM-Mon.6:00 PM, Tue.8:00
AM-Tue.6:00 PM, Wed.8:00 AM-Wed.6:0
0 PM, Thu.8:00 AM-Thu.6:00 PM, Fri.
8:00 AM-Fri.6:00 PM, Sat.8:00 AM-Sa
t.6:00 PM}
CalendarRepairMissingItemFixDisabled : False
CalendarRepairLogEnabled : True
CalendarRepairLogSubjectLoggingEnabled : True
CalendarRepairLogPath : C:\Program Files\Microsoft\Exchange
Server\V14\Logging\Calendar Repair
Assistant
CalendarRepairIntervalEndWindow : 30
CalendarRepairLogFileAgeLimit : 00:00:00
CalendarRepairLogDirectorySizeLimit : unlimited
Set-MailboxServer
Used to configure mailbox server settings for
calendar processing.

[PS] C:\>Set-MailboxServer -Identity conseamb2

-CalendarRepairLogPath “D:\Logging\Calendar Repair
Assistant" -CalendarRepairLogDirectorySizeLimit 100MB
-CalendarRepairSchedule 1.22:00-1.23:00, 2.22:00-
2.23:00, 3.22:00-3.23:00, 4.22:00-4.23:00, 5.22:00-
5.23:00, 6.22:00-6.23:00, 7.22:00-7.23:00
Use the EMC to Configure User Mailbox Calendar
Processing

Use Calendar Settings Tab on Mailbox Properties to

modify the Calendar Attendant settings for the selected
mailbox
Use the EMC to Configure Resource Mailbox Calendar Processing

Resource General Tab

Use to configure general settings for the resource mailbox
Resource Policy Tab
Use to specify under which conditions the resource mailbox
automatically accepts requests
Resource Information Tab
Use to specify the meeting information that appears in the
resource's calendar
Resource In-Policy Requests Tab
Use to specify users who are allowed to submit requests within the
resource policy's configuration
Resource Out-of-Policy Requests Tab
Use to specify the users who are allowed to submit out-of-policy
requests
Managing User Mailbox Calendars with ECP
Settings – Calendar Tab
Appearance Slab
Use to control how the calendar appears
Reminders Slab
Use to control how reminders behave
Automatic Processing Slab
Use to control how the Calendar Attendant processes calendar items
Text Message Notifications Slab
Use to control how calendar notifications are sent as text messages to
the mailbox owner
Calendar Troubleshooting Slab
Use to gather all diagnostic data for a given calendar item based on
subject, and then place the information in a pre-configured file system
folder specified in the LogLocation value in following registry key on
the CAS server that is providing ECP
Managing Resource Mailbox Calendars with ECP
Settings – Resource Tabs
Scheduling Options Slab
Use to control the calendar processing behavior for a Resource
mailbox
Scheduling Permissions Slab
Use to control who can submit meeting requests for the resource
Response Message Slab
Use to specify that an additional message be included when
responding to meeting requests
Watch This: Managing User Calendars
 Questions

71 1/1/2009 Microsoft Confidential - For Internal Use Only

 © 2009 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Microsoft Confidential - For Internal Use Only

Conditions and Terms of Use
Microsoft Confidential - For Internal Use Only

This training package content is proprietary and confidential, and is intended only for users described in the training materials. Content and
information designated for limited distribution is provided to you under a Non-Disclosure Agreement and cannot be distributed. Copying or
disclosing all or any portion of the content and/or information included in such packages is strictly prohibited.
The contents of this package are for informational and training purposes only and are provided "as is" without warranty of any kind, whether
express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and non-
infringement.
Training package content, including URLs and other Internet Web site references, is subject to change without notice. Because Microsoft
must respond to changing market conditions, the content should not be interpreted to be a commitment on the part of Microsoft, and
Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Unless otherwise noted, the companies,
organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association
with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.

Copyright and Trademarks

© 2009 Microsoft Corporation. All rights reserved.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this
document. Except as expressly provided in written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this
document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic,
mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
For more information, see “Use of Microsoft Copyrighted Content “at http://www.microsoft.com/about/legal/permissions/.
Microsoft®, Internet Explorer, and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries. Microsoft products mentioned herein may be either registered trademarks or trademarks of Microsoft Corporation in
the United States and/or other countries. All other trademarks are property of their respective owners.