Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1 Major Initial Availability. 4/25/2008 0.2 Revised and updated property names and other technical content. 6/27/2008 1.0 Major Initial Release. 8/6/2008 1.0.1 Editorial Revised and edited technical content. 9/3/2008 1.0.2 Editorial Updated references. 12/3/2008 1.0.3 Editorial Revised and edited technical content. 12/2/2009 1.0.4 Editorial Revised and edited technical content. 4/10/2009 2.0 Updated technical content and applicable product releases. 7/15/2009 3.0 Major Revised and edited for technical content. 11/4/2009 3.1.0 Minor Updated the technical content. 2/10/2010 3.2.0 Minor Updated the technical content. 5/5/2010 3.3.0 Minor Updated the technical content.
8/4/2010 4.0 Major Significantly changed the technical content. 11/3/2010 4.1 Minor Clarified the meaning of the technical content. 3/18/2011 4.1 None No changes to the meaning, language, and formatting of the technical content. 8/5/2011 5.0 Major Significantly changed the technical content. 10/7/2011 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 6.0 Major Significantly changed the technical content. 4/27/2012 7.0 Major Significantly changed the technical content. 7/16/2012 7.1 Minor Clarified the meaning of the technical content. 10/8/2012 8.0 Major Significantly changed the technical content.
2/11/2013 8.0 None No changes to the meaning, language, or formatting of the technical content. 7/26/2013 9.0 Major Significantly changed the technical content. 11/18/2013 10.0 Major Significantly changed the technical content. 2/10/2014 10.0 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 11.0 Major Significantly changed the technical content. 7/31/2014 11.0 None No changes to the meaning, language, or formatting of the technical content. 10/30/2014 11.1 Minor Clarified the meaning of the technical content. 3/16/2015 12.0 Major Significantly changed the technical content. 5/26/2015 13.0 Significantly changed
particular days of the week. five occurrences. Monthly recurrence Schedules events according to one of the following patterns: On the nth day of month. On a specific day of the week on the first, second, third, fourth, or last week of every month (for example, the first Tuesday of the month). An event that repeats on the fourth of every month, effective Monday, April 30, 2007, without an end date. Every n months recurrence A combination of the monthly and weekly patterns. An every n months pattern can schedule events according to one of the following patterns: On the mth day every n months. On any day of the week An event that occurs on the last Thursday of every two months, effective March 12, 2007, with an end date of December 31, 2007.
HjMonthNth 0x000B The has an every nth month pattern in the Hijri calendar. For this value in the PatternType field, the value of the CalendarType field MUST be set to 0x0000. HjMonthEnd 0x000C The event has a month end recurrence in the Hijri calendar. For this value in the PatternType field, the value of the CalendarType field MUST be set to 0x0000. CalendarType (2 bytes): An integer that specifies the type of calendar that is used. The acceptable values for the calendar type are listed in the following table. Name Value Meaning Default The default value for the calendar type is Gregorian. If the of the PatternType field is HjMonth, HjMonthNth, or HjMonthEnd and the value of the CalendarType field is Default, this recurrence uses the Hijri calendar. CAL_GREGORIAN Gregorian (localized) calendar CAL_GREGORIAN_US Gregorian (U.S.) calendar CAL_JAPAN Japanese Emperor era calendar CAL_TAIWAN Taiwan calendar CAL_KOREA Korean Tangun era calendar CAL_HIJRI Hijri (Arabic Lunar) calendar CAL_THAI Thai calendar CAL_HEBREW Hebrew lunar calendar CAL_GREGORIAN_ME_FRENCH Gregorian Middle East French calendar
The number of minutes between midnight January 1, 1601, and the first ever day on which the event would occur. Weekly The number of minutes between midnight January 1, 1601, and the first day of the first ever week in which the event would occur. Monthly or Yearly The number of minutes between midnight January 1, 1601, and the first day of the first ever month in which the event would occur. Period (4 bytes): An integer that specifies the interval at which the meeting pattern specified in PatternTypeSpecific field repeats. The Period value MUST be between 1 and the maximum recurrence interval, which is 999 days for daily recurrences, 99 weeks for weekly recurrences, and 99 months for monthly recurrences. The following table lists the values for this field based on the recurrence frequency, which is specified in the RecurFrequency field. Frequency Value recurrence The period is stored as the minutes in whole number of days. For example, to define a recurrence that occurs every two days, the Period field is set to 0x00000B40, which equals 2880 minutes, or two days. Weekly recurrence The period is stored in weeks. For example, if the Period field is set to 0x00000002, the meeting occurs every two weeks. Monthly or yearly recurrence The period is stored in months. If the recurrence is a yearly recurrence, The Period field MUST be set to 12. SlidingFlag (4 This field is only used for scheduling tasks; otherwise the value MUST be zero (0). For more details about sliding tasks, see section 3.1.4.6.2. PatternTypeSpecific (variable): A structure that specifies the details of the recurrence pattern. The structure varies according to the value of the PatternType field, as specified in sections , , , and . EndType (4 bytes): An integer that specifies the ending type for the recurrence. This field MUST be set to one of the values listed in the following table. Recurrence range type End date 0x00002021 End after N occurrences 0x00002022 Never end SHOULD be 0x00002023 but can be 0xFFFFFFFF OccurrenceCount (4 bytes): An integer that specifies the number of occurrences in a recurrence.
ReminderSet* LocationLength* LocationLength2* Location* (variable) ... BusyStatus* Attachment* SubType* AppointmentColor ... StartDateTime (4 bytes): The start time of the exception in local time in minutes since midnight, January 1, 1601. EndDateTime (4 bytes): The end time of the exception in local time in minutes since midnight, January 1, 1601. OriginalStartDate (4 The original starting time of the exception in local time in minutes since midnight, January 1, 1601. OverrideFlags (2 bytes): A bit field that specifies what data in the ExceptionInfo structure has a value different from the recurring series. The valid flags for this field are summarized in the following table. Flag Meaning ARO_SUBJECT 0x0001 Indicates that the Subject, SubjectLength, and SubjectLength2 fields are present. ARO_MEETINGTYPE 0x0002 Indicates that the MeetingType is present. ARO_REMINDERDELTA 0x0004 Indicates that the ReminderDelta field is present. ARO_REMINDER 0x0008 Indicates that the ReminderSet is present. ARO_LOCATION 0x0010 Indicates that the Location, LocationLength, and LocationLength2 fields are present.
SlidingFlag ULONG 4 00 00 00 00 This field is only used for scheduling tasks. Otherwise, the value can only be zero. EndType ULONG 4 21 20 00 00 Ends after an end date. (0x00002021) OccurrenceCount ULONG 4 0C 00 00 00 Not used. FirstDOW ULONG 4 00 00 00 00 The first day of the week on the calendar is Sunday (the default value). DeletedInstanceCount ULONG 4 02 00 00 00 are two deleted instances. DeletedInstanceDate ULONG 4 A0 C1 DC 0C The date of the deleted instance is 4/19/2007. DeletedInstanceDate ULONG 4 80 D2 DC 0C The date of the deleted instance is 4/22/2007. ModifiedInstanceCount 4 00 00 00 00 There are no modified instances. StartDate 4 20 7E DC 0C The date of the recurrence, given in minutes since midnight January 1, 1601, is 215,776,800 (0x0CDC7E20), which corresponds to 4/7/2011. EndDate ULONG 4 00 16 DD 0C The end date of the recurrence, given in minutes since midnight January 1, 1601, is 215,815,680
PidLidAutoFillLocation (section ) { 0x823A PidLidToAttendeesString (section ) { 0x823B PidLidCcAttendeesString (section ) { 0x823C PidLidAppointmentNotAllowPropose (section ) { 0x825A PidLidAppointmentTimeZoneDefinitionStartDisplay (section ) { 0x825E PidLidAppointmentTimeZoneDefinitionEndDisplay (section ) { 0x825F PidLidAppointmentTimeZoneDefinitionRecur (section ) { 0x8260 PidLidExceptionReplaceTime (section ) { 0x8228 PidLidFExceptionalAttendees (section ) { 0x822B PidLidFExceptionalBody (section ) { 0x8206 PidLidReminderDelta ( section 2.2.1.3) { 0x8501 PidLidReminderTime ([MS-OXORMDR] section 2.2.1.4) { 0x8502 PidLidReminderSet ([MS-OXORMDR] section 2.2.1.1) { 0x8503
153 141 D 118 Data model - abstract 80 110 77 Delegate Information object properties 77 77 77 77 77 55 128 E Examples 128 133 127 129 132 112 133 Examples of objects 138 141 133 74 75 73 Exeptions properties 74 75 F 16 G Global object ID examples 127 128 127 10 H triggered events 110 Higher-layer triggered events - client 81 81 81 83 83 106 83 106 I 171 171 15 Initialization 81 110 10 M 72 Meeting Cancellation object properties 72 72 72 72 72 72 Meeting example 161 150 153 141 141 148 152 146 73 Meeting Forward Notification object properties 73 73 73 73 59 Meeting object properties 60 59 59 59 59 59 60 59 60 60 Meeting Request object properties 70 70 69 70 67 68 68 68 69 69 69 67 67 70 Meeting Response object properties
71 71 71 71 71 72 71 71 Meeting Update object properties 70 70 69 70 67 68 68 68 69 69 69 67 Meeting-related object properties 63 63 63 62 64 63 67 62 Message processing 111 Message processing - client 109 106 108 108 107 108 17 Messages 58 76 57 17 77 73 72 73 59 67 70 62 17 N 119 14 O Other local events 110 111 16 P 171 Per appointment item abstract data model type 80 Per calendar abstract data model type 80 Per mailbox abstract data model type 80 Per meeting item abstract data model type 80 21 18 54 60 71 19 19 59 69 69 23 59 71 71 71 32 59 59 17 59 18 19 19 32 129 28 31 23 63 60 72 17 70 70 21 67 67 128 25 58 21 21 26 26 57 59 68 68 73 127 23 72
68 68 26 20 71 53 18 72 68 68 53 22 22 22 22 22 22 69 69 69 69 69 69 60 26 73 72 53 53 20 72 20 63 63 57 62 64 28 132 27 21 63 19 76 76 26 77 53 57 72 73 67 71 67 26 67 27 27 77 77 77 77 26 72 73 71 16 16 172 R 148 152 60 Recurrence BLOB examples 118 119 112 112 114 125 122 112 14 15 14 16 S 133 Security 171 171 146 Sequencing rules 111 Sequencing rules - client 109 106 108 108 107 108 Server 110 110 110 111 111 111 111 110 16 T Timer events 110 111 Timers 81 110 179 17 Triggered events - client 81 81 81