7 Appendix B: Product Behavior

  • Article

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

  • Microsoft Exchange Server 2007 Service Pack 1 (SP1)

  • Microsoft Exchange Server 2010

  • Microsoft Exchange Server 2013

  • Microsoft Exchange Server 2016

  • Microsoft Exchange Server 2019

  • Windows 8.1 operating system

  • Windows 10 operating system

  • Windows Server 2016 operating system

  • Windows 11 operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates 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 2010, Exchange 2013, Exchange 2016, and Exchange 2019 use both HTTP and HTTPS as the transport for Autodiscover command. Exchange 2007 SP1 uses only HTTPS as the transport for Autodiscover command.

<2> Section 2.2.1.1:  When sending an Autodiscover command request to Exchange 2007 SP1, the Content-Type header accepts the following values: "text/html" or "text/xml".

<3> Section 2.2.1.11: In Exchange 2007 SP1, the MeetingResponse command is used to accept, tentatively accept, or decline a meeting request only in the user's Inbox folder.

<4> Section 2.2.3.38: In Exchange 2007 SP1, the Culture element returns "en:en", regardless of the culture that is sent by the client.

<5> Section 2.2.3.61.1:  Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 use 42 days; Exchange 2007 SP1 uses 62 days.

<6> Section 2.2.3.88.1:  In Exchange 2007 SP1, Exchange 2013, Exchange 2016 and Exchange 2019, the valid values for the HeartbeatInterval element are 60 through 900 seconds (15 minutes) by default. The configurable minimum value is 1 second and the configurable maximum value is 900 seconds (15 minutes).

<7> Section 2.2.3.88.2:  In Exchange 2007 SP1, Exchange 2013, Exchange 2016 and Exchange 2019, the valid values for the HeartbeatInterval element are 60 through 900 seconds (15 minutes) by default. The configurable minimum value is 1 second and the configurable maximum value is 900 seconds (15 minutes).

<8> Section 2.2.3.88.2:  In Exchange 2007 SP1, Exchange 2013, Exchange 2016 and Exchange 2019, when the client requests a HeartbeatInterval greater than 15 minutes, error code 503 will be returned.

<9> Section 2.2.3.92.1:  Exchange 2007 SP1 and Windows 8.1 do not return Status element value of 2 if the request includes the InstanceId element when a non-supporting protocol version is used.

<10> Section 2.2.3.116:  In Exchange 2007 SP1, the server sends Sync response messages containing the MoreAvailable element and between zero (0) and WindowSize schema changes when it encounters elements external to the protocol.

<11> Section 2.2.3.123:  Exchange 2007 SP1, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 require that the reply message for unknown external and known external audiences be the same.

<12> Section 2.2.3.127:  Windows 8.1 uses the value "WINDOWS" for the OS element.

<13> Section 2.2.3.134:  The initial release version of Exchange 2010 requires the PhoneNumber element to have a value when the EnableOutboundSMS element, as specified in section 2.2.3.60, is set to 1. Under these conditions, if the PhoneNumber element does not have a value, the server returns a value of 5 in the Status element, as specified in section 2.2.3.177.15. Microsoft Exchange Server 2010 Service Pack 1 (SP1), Exchange 2013, Exchange 2016, and Exchange 2019 do not require the PhoneNumber element to have a value when the EnableOutboundSMS element is set to 1.

<14> Section 2.2.3.167:  Using the Settings command DeviceInformation request is not recommended for Exchange 2007 SP1.

<15> Section 2.2.3.177.8:  Exchange 2007 SP1 and later do not return a value of 155 in the Status element.

<16> Section 2.2.3.177.12:  The default value of the maximum number is 100 in Exchange 2010 and later.

<17> Section 2.2.3.183:  Exchange 2007 SP1 and Exchange 2010 do not limit the number of To elements in command requests. Update Rollup 6 for Exchange Server 2010 Service Pack 2 (SP2) and later do limit the number of To elements in command requests.

<18> Section 2.2.3.183:  Some fields that are indexed by using ANR in Active Directory by default in Exchange 2007 SP1 are as follows: Name, Alias, Email, Office. The ANR property set that can be indexed is definable by the administrator and can be extended to include other fields.

<19> Section 2.2.3.183:  The default value of the maximum number is 100 in Exchange 2010 and later.

<20> Section 3.1.5.1:  Windows 8.1 does not issue a Provision command as the first command.

<21> Section 3.1.5.2:  Windows 8.1 sends the settings:DeviceInformation element after the FolderSync command.

<22> Section 3.1.5.2: Sending the settings:DeviceInformation parameters is not recommended for Exchange 2007 SP1.

<23> Section 3.1.5.3:  Windows 8.1 does not restart the synchronization process with a synchronization key of 0 when the FolderSync response contains a Status element value of 9.

<24> Section 3.1.5.6: Exchange 2007 SP1 and Exchange 2010 do not return substitute meeting invitation email messages.

<25> Section 3.1.5.6: Exchange 2010 returns the meeting request with the email2:MeetingMessageType element ([MS-ASEMAIL] section 2.2.2.47) set to 6.

<26> Section 3.1.5.7:  When the user accepts, declines, or tentatively accepts the meeting request prior to forwarding the meeting request to another user, Exchange 2007 SP1 changes the meeting organizer to the user who forwarded the meeting request. When the user simply forwards the meeting request to another user without accepting, declining, or tentatively accepting the meeting request, Exchange 2007 SP1 does not change the meeting organizer.

<27> Section 3.1.5.10:  Exchange 2007 SP1 and Exchange 2010 do not limit the number of elements in command requests. Update Rollup 6 for Exchange 2010 SP2 and later do limit the number of elements in command requests.

<28> Section 3.1.5.10:  Exchange 2007 SP1 and Exchange 2010 do not limit the number of elements in command requests. Update Rollup 6 for Exchange 2010 SP2 and later use the specified limit values by default but can be configured to use different values.