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.2.1.3: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<2> Section 2.2.2.1.4: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<3> Section 2.2.2.2.1: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<4> Section 2.2.2.2.2: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<5> Section 2.2.2.3.1: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<6> Section 2.2.2.3.2: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<7> Section 2.2.2.4.1: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<8> Section 2.2.2.4.2: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<9> Section 2.2.2.5.1:  Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release version of Outlook 2013 do not support the Execute request type. The Execute request type was introduced in Microsoft Outlook 2013 Service Pack 1 (SP1).

<10> Section 2.2.2.6: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<11> Section 2.2.2.6.2: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<12> Section 2.2.2.7: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<13> Section 2.2.2.7.2: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<14> Section 2.2.2.11: Exchange 2010 does not support the RopSeekRowFractional ROP, but Microsoft Exchange Server 2010 Service Pack 1 (SP1), Exchange 2013, and Exchange 2016 do support this ROP.

<15> Section 2.2.2.14.2:  Exchange 2007 and Exchange 2010 always set this value to "FALSE" (0x00) for hierarchy tables.

<16> Section 2.2.2.17.1: Exchange 2013 and Exchange 2016 do not support a value greater than 0 for the MaxRowCount field.

<17> Section 3.1.4.1.1: Office Outlook 2007 never performs asynchronous table ROPs against the server. Exchange 2010, Exchange 2013, and Exchange 2016 never honor requests to perform asynchronous table ROPs.

<18> Section 3.1.4.3: Exchange 2010 does not support the RopSeekRowFractional ROP, but Exchange 2010 SP1, Exchange 2013, and Exchange 2016 do support this ROP.

<19> Section 3.1.5: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<20> Section 3.2.5.1: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<21> Section 3.2.5.2: Exchange 2003 and Exchange 2007 do not fail the ROP if the columns are not set, but use a set of columns that are undefined.

<22> Section 3.2.5.2: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<23> Section 3.2.5.3: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<24> Section 3.2.5.4: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<25> Section 3.2.5.5: Exchange 2010, Exchange 2013, and Exchange 2016 set the Origin field to "BOOKMARK_END".

<26> Section 3.2.5.7: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<27> Section 3.2.5.9: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<28> Section 3.2.5.10: Exchange 2007 returns ecSuccess when the bookmark (2) has become invalid because of a RopSortTable or RopResetTable ROP request. If the bookmark has become invalid because of a RopRestrict ROP request on the content table, Exchange 2007 returns ecNotFound.

<29> Section 3.2.5.11: Exchange 2010 does not support the RopSeekRowFractional ROP, but Exchange 2010 SP1, Exchange 2013, and Exchange 2016 do support this ROP.

<30> Section 3.2.5.11: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<31> Section 3.2.5.12: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<32> Section 3.2.5.14: Exchange 2007 returns ecSuccess when the bookmark has become invalid because of a RopSortTable or RopResetTable ROP request. If the bookmark has become invalid because of a RopRestrict ROP request on the content table, Exchange 2007 returns ecNotFound.

<33> Section 3.2.5.14: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

<34> Section 3.2.5.15: Exchange 2003 and Exchange 2007 do not conform to the specification and currently send the value "ecNotSupported" in the ReturnValue field of the ROP response buffer for contents tables.

<35> Section 3.2.5.16: Exchange 2010, Exchange 2013, and Exchange 2016 do not support asynchronous operations on tables and ignore the TABL_ASYNC flags, as described in section 2.2.2.1.4.

Show: