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.1:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the MAPI extensions to HTTP. The MAPI extensions to HTTP were introduced in Microsoft Outlook 2013 Service Pack 1 (SP1) and Microsoft Exchange Server 2013 Service Pack 1 (SP1).

<2> Section 2.2.1:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the NotificationWait request type. The NotificationWait request type was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<3> Section 2.2.1.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the NotificationWait request type. The NotificationWait request type was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<4> Section 2.2.1.3.1:  Exchange 2003 and Office Outlook 2003 do not support the EcDoAsyncConnectEx method, as specified in [MS-OXCRPC] section 3.1.4.4.

<5> Section 2.2.1.3.2: Exchange 2003 and Office Outlook 2003 do not support the EcDoAsyncWaitEx method, as specified in [MS-OXCRPC] section 3.3.4.1.

<6> Section 2.2.1.3.3: Exchange 2003, Exchange 2007, Office Outlook 2003, Office Outlook 2007, and Outlook 2010 support the EcRRegisterPushNotification method, as specified in [MS-OXCRPC] section 3.1.4.5. The initial release version of Exchange 2010, and Microsoft Exchange Server 2010 Service Pack 1 (SP1), do not support the EcRRegisterPushNotification method, and the returned value is always ecNotSupported (0x80040102). Microsoft Exchange Server 2010 Service Pack 2 (SP2) does support the EcRRegisterPushNotification method if a registry key is created to support push notifications, as described in [MSFT-ConfigStaticUDPPort]. Outlook 2013 and Outlook 2016 do not send the EcRRegisterPushNotification RPC method call. Exchange 2013 and Exchange 2016 do not support the EcRRegisterPushNotification method, and the returned value is always ecNotSupported (0x80040102).

<7> Section 2.2.1.3.4:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Execute request type. The Execute request type was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<8> Section 2.2.1.4.1:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Execute response type. The Execute response type was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<9> Section 2.2.1.4.1.2:  Exchange 2003, Exchange 2007, and Exchange 2010 do not set the value of the TagCount field to 0x0000; they set the value of the field to the number of property tags in the Tags field.

<10> Section 2.2.1.4.1.2:  In Exchange 2013 the value of MessageFlags is zero.

<11> Section 3.1.1:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support cookies. The cookies element was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<12> Section 3.1.4.3: Exchange 2003 and Exchange 2007 do not require that a table view is created in order to send table notifications.

<13> Section 3.1.4.3: Exchange 2003 and Exchange 2007 do not stop sending notifications if the RopResetTable ROP ([MS-OXCROPS] section 2.2.5.15) is received.

<14> Section 3.1.5.2: Exchange 2003 does not support the EcDoAsyncConnectEx method call or asynchronous RPC notifications.

<15> Section 3.1.5.3: Exchange 2003 does not support the EcDoAsyncWaitEx method call or asynchronous RPC notifications.

<16> Section 3.1.5.4: Exchange 2003 and Exchange 2007 support push notifications and the EcRRegisterPushNotification method, as specified in [MS-OXCRPC] section 3.1.4.5. The initial release version of Exchange 2010, and Exchange 2010 SP1 do not support push notifications or the EcRRegisterPushNotification method. Exchange 2010 SP2 does support push notifications and the EcRRegisterPushNotification method if a registry key is created, as described in [MSFT-ConfigStaticUDPPort]. Microsoft Exchange Server 2010 Service Pack 3 (SP3) and Exchange 2013 do not support push notifications of the EcRRegisterPushNotification method.

<17> Section 3.2.4.2: Exchange 2003 and Exchange 2007 do not require that the client send any ROPs to the server in order to receive TableModified event notifications, as specified in section 2.2.1.1.1. In Exchange 2003 and Exchange 2007, the subscription is created automatically when the client creates a Table object on the server.

<18> Section 3.2.4.2: The client will continue to receive table notifications even if the RopResetTable ROP ([MS-OXCROPS] section 2.2.5.15) is sent, if the server is Exchange 2003 or Exchange 2007.

<19> Section 3.2.4.3:  Office Outlook 2003 does not support the asynchronous RPC notification method. Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 do support the asynchronous RPC notification method.

<20> Section 3.2.4.4:  Office Outlook 2003, Office Outlook 2007 and Outlook 2010 do support the push notification method. Outlook 2013 and Outlook 2016 do not support the push notification method.

<21> Section 3.2.4.5:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Execute request type. The Execute request type was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<22> Section 3.2.5.4:  Outlook 2013 and Outlook 2016 do not support the push notification method and do not send the EcRRegisterPushNotification RPC method call.

<23> Section 3.2.5.5.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Execute request type. The Execute request type was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<24> Section 3.2.5.7:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Execute request type. The Execute request type was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

Show: