6 Appendix A: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs.

  • Microsoft Exchange Server 2003

  • Microsoft Exchange Server 2007

  • Microsoft Exchange Server 2010

  • Microsoft Exchange Server 2013

  • Microsoft Exchange Server 2016

  • Microsoft Office Outlook 2003

  • Microsoft Office Outlook 2007

  • Microsoft Outlook 2010

  • Microsoft Outlook 2013

  • Microsoft Outlook 2016

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.2: The following additional properties can be set on items described by the Appointment and Meeting Object Protocol for backward compatibility with Office Outlook 2003. These properties are not used by Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016: PidLidRequiredAttendees ([MS-OXPROPS] section 2.229), PidLidOptionalAttendees ([MS-OXPROPS] section 2.194), PidLidResourceAttendees ([MS-OXPROPS] section 2.230), PidLidDelegateMail ([MS-OXPROPS] section 2.92), PidLidTimeZone (section 2.2.5.6), PidLidStartRecurrenceDate ([MS-OXPROPS] section 2.303), PidLidStartRecurrenceTime ([MS-OXPROPS] section 2.304), PidLidEndRecurrenceDate ([MS-OXPROPS] section 2.115), PidLidEndRecurrenceTime ([MS-OXPROPS] section 2.116), PidLidDayInterval ([MS-OXPROPS] section 2.90), PidLidWeekInterval ([MS-OXPROPS] section 2.352), PidLidMonthInterval ([MS-OXPROPS] section 2.172), PidLidYearInterval ([MS-OXPROPS] section 2.362), PidLidMonthOfYearMask ([MS-OXPROPS] section 2.174), and PidLidRecurrenceType (section 2.2.1.45).

<2> Section 2.2.1.2:  Exchange 2003, Exchange 2007, Exchange 2010, Office Outlook 2003, Office Outlook 2007, and Outlook 2010 do not support the olWorkingElsewhere value. Office Outlook 2003, Office Outlook 2007, and Outlook 2010 interpret the olWorkingElsewhere value as olFree.

<3> Section 2.2.1.5: For compatibility with Office Outlook 2003, the PidTagStartDate property (section 2.2.1.30) needs to be set, and when set, it has to be equal to the value of the PidLidAppointmentStartWhole property ([MS-OXPROPS] section 2.29).

<4> Section 2.2.1.6: For compatibility with Office Outlook 2003, the PidTagEndDate property (section 2.2.1.31) needs to be set, and when set, it has to be equal to the value of the PidLidAppointmentEndWhole property ([MS-OXPROPS] section 2.14).

<5> Section 2.2.1.7: Exchange 2003 ignores the PidLidAppointmentDuration property ([MS-OXPROPS] section 2.11) and always computes the length of the event from the difference between the value of the PidLidAppointmentEndWhole property (section 2.2.1.6) and the value of the PidLidAppointmentStartWhole property (section 2.2.1.5).

<6> Section 2.2.1.8: If no value is specified in the PidNameKeywords property ([MS-OXCMSG] section 2.2.1.17), Office Outlook 2003 displays the Calendar object in the color specified by the PidLidAppointmentColor property (section 2.2.1.50).

<7> Section 2.2.1.13: Exchange 2003 does not read or write the PidLidIsRecurring property ([MS-OXPROPS] section 2.156).

<8> Section 2.2.1.25: Office Outlook 2003 instead uses the following properties to track unsendable attendees:

PidLidNonSendableTo (section 2.2.1.19 )

PidLidNonSendableCc (section 2.2.1.20)

PidLidNonSendableBcc (section 2.2.1.21)

PidLidNonSendToTrackStatus (section 2.2.1.22)

PidLidNonSendCcTrackStatus (section 2.2.1.23)

PidLidNonSendBccTrackStatus (section 2.2.1.24)

<9> Section 2.2.1.29: When a Meeting object is created, Office Outlook 2003, Office Outlook 2007, Microsoft Outlook 2010, Outlook 2013, and Outlook 2016 set the value of the PidTagOwnerAppointmentId property ([MS-OXPROPS] section 2.847) to the number of minutes between the start time and midnight, January 1, 1601. When trying to find a Meeting object, Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 sort the table according to the PidTagOwnerAppointmentId property, thus allowing increased performance in the search.

<10> Section 2.2.1.41: Office Outlook 2003 does not support the PidLidAppointmentTimeZoneDefinitionRecur property ([MS-OXPROPS] section 2.33).

<11> Section 2.2.1.44: Office Outlook 2003 and Office Outlook 2007 use the start time when calculating whether exceptions overlap.

<12> Section 2.2.1.44.1: This value can be read by Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 but is not used.

<13> Section 2.2.1.44.1: This value can be read by Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 but is not used.

<14> Section 2.2.1.44.1: Office Outlook 2003 and Office Outlook 2007 always write a default value of 0x0000000A for the OccurrenceCount field when the recurrence pattern has no end date.

<15> Section 2.2.1.44.3: The Reserved field is not present in Office Outlook 2003 or Office Outlook 2007.

<16> Section 2.2.1.44.5: Office Outlook 2003 uses version 0x00003008.

<17> Section 2.2.1.47: Office Outlook 2003 does not set the PidLidLinkedTaskItems property ([MS-OXPROPS] section 2.158).

<18> Section 2.2.1.51: Office Outlook 2003 reads and writes the properties in this section.

<19> Section 2.2.1.51.5:  The PidLidAllowExternalCheck property ([MS-OXPROPS] section 2.6) is used for interoperability with Microsoft NetMeeting.

<20> Section 2.2.1.51.5:  Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, and Exchange 2016 do not require that the PidLidAllowExternalCheck property ([MS-OXPROPS] section 2.6) be set on a Calendar object.

<21> Section 2.2.2.2: Exchange 2003 includes only the seCoerceToInbox and seOpenForCtxMenu flags. Without all the flags, the client user interface will not always behave as expected when a Calendar object is moved, deleted, or copied or when a context menu is displayed for the object.

<22> Section 2.2.4.10.1:  Office Outlook 2003 and Office Outlook 2007 use these reserved flags for internal information that does not affect the Appointment and Meeting Object Protocol. A server or client does not need to read these flags but needs to leave the values unchanged if they are set.

<23> Section 2.2.4.10.1:  Office Outlook 2003 and Office Outlook 2007 use these reserved flags for internal information that does not affect the Appointment and Meeting Object Protocol. A server or client does not need to read these flags but needs to leave the values unchanged if they are set.

<24> Section 2.2.4.10.1:  Office Outlook 2003 and Office Outlook 2007 use these reserved flags for internal information that does not affect the Appointment and Meeting Object Protocol. A server or client does not need to read these flags but needs to leave the values unchanged if they are set.

<25> Section 2.2.5.2: If the value of the PidLidAttendeeCriticalChange property is not specified, Exchange 2003 will use the last modified time as this value.

<26> Section 2.2.5.3: Exchange 2003 does not read or write the PidLidWhere property.

<27> Section 2.2.6.2: Office Outlook 2003 does not read or write the PidLidChangeHighlight property ([MS-OXPROPS] section 2.51).

<28> Section 2.2.6.3: Office Outlook 2003 reads and writes the PidLidForwardInstance property ([MS-OXPROPS] section 2.138).

<29> Section 2.2.6.7: Office Outlook 2003 does not read or write the PidLidOldLocation property ([MS-OXPROPS] section 2.189).

<30> Section 2.2.6.8: Office Outlook 2003 does not read or write the PidLidOldWhenStartWhole property ([MS-OXPROPS] section 2.192).

<31> Section 2.2.6.9: Office Outlook 2003 does not support the PidLidOldWhenEndWhole property ([MS-OXPROPS] section 2.191).

<32> Section 2.2.6.12: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, and Exchange 2016 do not add downlevel text.

<33> Section 2.2.10.1.6: Office Outlook 2003 and Office Outlook 2007 do not write the value for the PidTagExceptionReplaceTime property ([MS-OXPROPS] section 2.676).

<34> Section 3.1.4.3: Office Outlook 2003 does not set the PidLidAppointmentStateFlags property (section 2.2.1.10).

<35> Section 3.1.4.3: Office Outlook 2003 and Office Outlook 2007 sometimes do not copy the recipient list. If the RecipientRow structures ([MS-OXCDATA] section 2.8.3) from a Meeting object are not copied, the resulting snapshot will not show who was invited to the meeting at the time the copy was made.

<36> Section 3.1.4.3: Office Outlook 2003 does not set the PidLidResponseStatus property (section 2.2.1.11).

<37> Section 3.1.4.3: Office Outlook 2003 does not set the PidTagSubjectPrefix property ([MS-OXCMSG] section 2.2.1.9).

<38> Section 3.1.4.5: Office Outlook 2003 prompts the user with an option to delete without sending a cancellation.

<39> Section 3.1.4.7.1.1: Outlook 2013 and Outlook 2016 do not support direct booking. By default, Outlook 2010 does not use direct booking, but it can be set up to use it.

<40> Section 3.1.4.7.1.1: Office Outlook 2003 and Office Outlook 2007 attempt direct booking only for Resource objects.

<41> Section 3.1.4.7.2: Office Outlook 2003 does not support the calendar options dictionary.

<42> Section 3.1.4.7.2.1: Office Outlook 2003 does not skip automatic creation of the Meeting object based on the values of these properties.

<43> Section 3.1.4.7.2.2: If the PidLidReminderSet property ([MS-OXORMDR] section 2.2.1.1) is set to FALSE, Outlook 2010, Outlook 2013, and Outlook 2016 change the value of the PidLidReminderSet property to TRUE, set the PidLidReminderDelta property ([MS-OXORMDR] section 2.2.1.3) to its default value (as defined by the client), and recalculate the PidLidReminderSignalTime property ([MS-OXORMDR] section 2.2.1.2) regardless of the value of the PidLidAppointmentSubType property (section 2.2.1.9).

<44> Section 3.1.4.7.2.2:  Office Outlook 2003 does not set the PidLidAppointmentReplyName property (section 2.2.4.5).

<45> Section 3.1.4.7.2.2: Office Outlook 2003 does not copy the RecipientRow structures, as described in [MS-OXCDATA] section 2.8.3, of the PidLidAppointmentUnsendableRecipients property (section 2.2.1.25) of the Meeting Request object to the RecipientRow structures of the Meeting object.

<46> Section 3.1.4.7.2.2: Office Outlook 2003 and Office Outlook 2007 do not copy the busy status for the exception.

<47> Section 3.1.4.7.2.2:  Office Outlook 2003 and Office Outlook 2007 do not set the PidLidServerProcessed property (section 2.2.5.4).

<48> Section 3.1.4.7.2.3: Office Outlook 2003 automatically sends Meeting Response objects if the PidLidServerProcessed property (section 2.2.5.4) is set.

<49> Section 3.1.4.7.2.3: Office Outlook 2003 and Office Outlook 2007 do not set the PidLidServerProcessingActions property (section 2.2.5.5).

<50> Section 3.1.4.7.3: Office Outlook 2003 does not set the PidLidOldWhenStartWhole (section 2.2.6.8) and PidLidOldWhenEndWhole (section 2.2.6.9) properties.

<51> Section 3.1.4.7.3.1: Office Outlook 2003 sets the value of the PidLidMeetingType property (section 2.2.6.5) to mtgFull regardless of the change made.

<52> Section 3.1.4.7.3.2: Office Outlook 2003 always clears responses whenever any update is sent out.

<53> Section 3.1.4.7.3.4: Office Outlook 2003 does not treat an attendee that has been marked sendable as a new attendee.

<54> Section 3.1.4.7.3.4: Office Outlook 2003 does not set the PidLidAppointmentUnsendableRecipients property (section 2.2.1.25) as specified.

<55> Section 3.1.4.7.3.5: Office Outlook 2003 does not send a Meeting Cancellation object for the exception to each attendee included in the recurring series that is not included in the exception.

<56> Section 3.1.4.7.3.5: Office Outlook 2003 does not send out cancelations to exceptions when the recurrence pattern has changed.

<57> Section 3.1.4.7.4: Office Outlook 2003 does not support the calendar options dictionary.

<58> Section 3.1.4.7.4.1: Office Outlook 2003 does not skip automatic updating of the Meeting object based on the values of the PidLidServerProcessed (section 2.2.5.4) and the PidLidServerProcessingActions (section 2.2.5.5) properties.

<59> Section 3.1.4.7.4.2: Office Outlook 2003 re-creates the exception regardless of whether these properties are set.

<60> Section 3.1.4.7.4.2: Office Outlook 2003 does not copy the PidLidLocation property (section 2.2.1.4), the PidLidAppointmentStartWhole property (section 2.2.1.5), or the PidLidAppointmentEndWhole property (section 2.2.1.6) onto the Meeting Update object.

<61> Section 3.1.4.7.4.2: Office Outlook 2003 performs these actions regardless of whether the cpsCopiedOldProperties bit is set on the PidLidServerProcessingActions property (section 2.2.5.5).

<62> Section 3.1.4.7.4.2: Office Outlook 2003 overwrites private values of the PidTagSensitivity property ([MS-OXCMSG] section 2.2.1.13).

<63> Section 3.1.4.7.4.2: Office Outlook 2003 resets the value of the PidLidResponseStatus property (section 2.2.1.11) to "respNotResponded" (0x00000005) regardless of whether the Meeting Update object contains a significant change.

<64> Section 3.1.4.7.5: Office Outlook 2003 and Office Outlook 2007 set the value of the PidLidMeetingType property (section 2.2.6.5) to 0x00000000.

<65> Section 3.1.4.7.5: Office Outlook 2003 does not copy the RecipientRow structures ([MS-OXCDATA] section 2.8.3) to the PidLidAppointmentUnsendableRecipients property (section 2.2.1.25) of the new object.

<66> Section 3.1.4.7.5.1: Office Outlook 2003 does not forward exceptions to a recurring series.

<67> Section 3.1.4.8.4: Office Outlook 2003 allows an organizer to send a response to their own meeting, but only if the asfReceived bit is not set on the PidLidAppointmentStateFlags property (section 2.2.1.10).

<68> Section 3.1.4.8.4: Office Outlook 2003 and Office Outlook 2007 also write the following properties, which are not used by Office Outlook 2003 or Office Outlook 2007: PidLidInternetAccountName ([MS-OXOMSG] section 2.2.1.62) and PidLidInternetAccountStamp ([MS-OXOMSG] section 2.2.1.63).

<69> Section 3.1.4.8.4: Office Outlook 2003 and Office Outlook 2007 also write the following properties when the Meeting Response object represents a recurring series. These properties are not used by Office Outlook 2003 or Office Outlook 2007: PidLidRequiredAttendees ([MS-OXPROPS] section 2.229), PidLidOptionalAttendees ([MS-OXPROPS] section 2.194), PidLidResourceAttendees ([MS-OXPROPS] section 2.230), PidLidDelegateMail ([MS-OXPROPS] section 2.92), PidLidTimeZone (section 2.2.5.6), PidLidStartRecurrenceDate ([MS-OXPROPS] section 2.303), PidLidStartRecurrenceTime ([MS-OXPROPS] section 2.304), PidLidEndRecurrenceDate ([MS-OXPROPS] section 2.115), PidLidEndRecurrenceTime ([MS-OXPROPS] section 2.116), PidLidDayInterval ([MS-OXPROPS] section 2.90), PidLidWeekInterval ([MS-OXPROPS] section 2.352), PidLidMonthInterval ([MS-OXPROPS] section 2.172), PidLidYearInterval ([MS-OXPROPS] section 2.362), PidLidMonthOfYearMask ([MS-OXPROPS] section 2.174), PidLidRecurrenceType (section 2.2.1.45).

<70> Section 3.1.4.8.5: Office Outlook 2003 does not support the calendar options dictionary.

<71> Section 3.1.4.8.5.1: Office Outlook 2003 will process the response regardless of the value of the PidLidServerProcessingActions property (section 2.2.5.5).

<72> Section 3.1.4.8.5.1: When processing a Meeting Response object that represents an exception to a recurring appointment, Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 ignore the cpsUpdatedCalItem bit and still record the response.

<73> Section 3.1.4.8.5.2: Office Outlook 2007 does not set the PidLidPromptSendUpdate (section 2.2.7.8) property.

<74> Section 3.1.4.8.5.2: Office Outlook 2003 and Office Outlook 2007 do not verify that the attendee exists on an out-of-date Meeting Response object.

<75> Section 3.1.4.8.5.2: Office Outlook 2003 and Office Outlook 2007 compare the two time values rounded down to the nearest minute so that if an attendee responds twice within the same minute, both responses will be seen as having been sent at the same time.

<76> Section 3.1.4.8.5.2: Office Outlook 2003 and Office Outlook 2007 round the time value from the PidLidAttendeeCriticalChange property (section 2.2.5.2) down to the nearest minute before setting the value in the PidTagRecipientTrackStatusTime property (section 2.2.4.10.3).

<77> Section 3.1.4.8.5.2: Office Outlook 2003 and Office Outlook 2007 allow the user to decide whether to delete empty responses.

<78> Section 3.1.4.9.1.1: Office Outlook 2003 does not send cancellations to unsendable attendees.

<79> Section 3.1.4.9.1.2: Office Outlook 2007 does not send out cancellations for deleted exceptions when sending out a cancellation for a recurring series.

<80> Section 3.1.4.9.1.2: Office Outlook 2007 sends Meeting Cancellation objects to exceptions when sending a Meeting Cancellation object to a recurring series to a Partial Attendee List, but Office Outlook 2003 does not.

<81> Section 3.1.4.9.2: Office Outlook 2003 does not support the calendar options dictionary.

<82> Section 3.1.4.9.2.1: Office Outlook 2003 does not skip automatic updating of the Meeting object based on the PidLidServerProcessed (section 2.2.5.4) and PidLidServerProcessingActions (section 2.2.5.5) properties.

<83> Section 3.1.4.9.2.1: Office Outlook 2003 and Office Outlook 2007 re-create the Exception object.

<84> Section 3.1.4.9.2.1: Office Outlook 2003 and Office Outlook 2007 re-create the Meeting object.

<85> Section 3.1.4.9.2.2: Office Outlook 2003 and Office Outlook 2007 both set the PidTagProcessed property (section 2.2.5.7).

<86> Section 3.1.4.10.1:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release version of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release version of Outlook 2013 do not support the X-ServerApplication header and the Connect request type. The X-ServerApplication header and the Connect request type were introduced in Microsoft Exchange Server 2013 Service Pack 1 (SP1) and Microsoft Outlook 2013 Service Pack 1 (SP1).

<87> Section 3.1.4.10.1: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 also write the following properties, which are not read by Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016: PidLidInternetAccountName ([MS-OXOMSG] section 2.2.1.62) and PidLidInternetAccountStamp ([MS-OXOMSG] section 2.2.1.63).

<88> Section 3.1.4.10.1: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 also write the following properties when the Meeting Response object represents a recurring series. These are not read by Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016: PidLidRequiredAttendees ([MS-OXPROPS] section 2.229), PidLidOptionalAttendees ([MS-OXPROPS] section 2.194), PidLidResourceAttendees ([MS-OXPROPS] section 2.230), PidLidDelegateMail ([MS-OXPROPS] section 2.92), PidLidTimeZone (section 2.2.5.6), PidLidStartRecurrenceDate ([MS-OXPROPS] section 2.303), PidLidStartRecurrenceTime ([MS-OXPROPS] section 2.304), PidLidEndRecurrenceDate ([MS-OXPROPS] section 2.115), PidLidEndRecurrenceTime ([MS-OXPROPS] section 2.116), PidLidDayInterval ([MS-OXPROPS] section 2.90), PidLidWeekInterval ([MS-OXPROPS] section 2.352), PidLidMonthInterval ([MS-OXPROPS] section 2.172), PidLidYearInterval ([MS-OXPROPS] section 2.362), PidLidMonthOfYearMask ([MS-OXPROPS] section 2.174), and PidLidRecurrenceType (section 2.2.1.45).

<89> Section 3.1.4.10.2: Office Outlook 2003 does not support the calendar options dictionary.

<90> Section 3.1.5.4: When sending a Meeting Update object for an exception to a recurring series, Office Outlook 2003 does not increment the sequence number for the exception.

<91> Section 3.1.5.5.1:  Office Outlook 2003 and Office Outlook 2007 do not interpret data in this manner.

<92> Section 3.1.5.5.2:  Office Outlook 2003 and Office Outlook 2007 do not interpret data in this manner.

<93> Section 3.1.5.6: Office Outlook 2003 does not support the PidTagScheduleInfoDelegatorWantsInfo property ([MS-OXODLGT] section 2.2.2.2.2).

<94> Section 3.1.5.6: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 do not set the cpsDelegatorWantsCopy bit of the PidLidServerProcessingActions property (section 2.2.5.5).

Show: