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.

 

  • Windows NT 4.0 operating system Option Pack for Windows NT Server

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

  • Windows 10 operating system

  • Windows Server 2016 operating system 

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 1.6: This protocol is supported in Windows 2000, Windows Server 2003, Windows XP, Windows Server 2008 operating system, Windows Vista, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2, Windows 10, and Windows Server 2016.

<2> Section 2.1.2.1: Mutual authentication is used by default on Windows Server 2003, Windows XP operating system Service Pack 2 (SP2), Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016. No authentication is used on Windows 2000 or Windows XP operating system Service Pack 1 (SP1).

<3> Section 2.1.2.2: On Windows operating systems, the data that is necessary to construct the name object for the TIP interoperability provider implementation is found in the Windows registry.

<4> Section 2.2.5.1.3.4: In Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016, a GUID is used for the szTxId field in the OLETX_TIP_TX_ID structure. If szTxId is set to 0x0000000000000000 (GUID null) and the fAsync flag is set to 0x00000001 in the pull request, a new GUID will be generated and returned in the guidTx field for the TXUSER_TIPPROXYGATEWAY_MTAG_PULLED message.

<5> Section 3.3.5.1.1: In Windows 8, Windows 8.1, and Windows 10, if the Allow TIP flag of the Core Transaction Manager Facet ([MS-DTCO] section 3.2.1) is set to FALSE, the TIP interoperability provider will not be established as a protocol extension, and no RPC endpoint will be established to receive the message. Therefore, any incoming message will be rejected with an RPC error.

<6> Section 3.3.5.1.1: In Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016, a GUID is used for the szTxId field in the OLETX_TIP_TX_ID structure. If szTxId is set to 0x0000000000000000 (GUID NULL) and the fAsync flag is set to 0x00000001 in the pull request, a new GUID will be generated and returned in the guidTx field for the TXUSER_TIPPROXYGATEWAY_MTAG_PULLED message.

<7> Section 3.3.5.1.2: In Windows 8, Windows 8.1, and Windows 10, if the Allow TIP flag of the Core Transaction Manager Facet ([MS-DTCO] section 3.2.1) is set to FALSE, the TIP interoperability provider will not be established as a protocol extension, and no RPC endpoint will be established to receive the message. Therefore, any incoming message will be rejected with an RPC error.

<8> Section 3.3.7.1.1: In Windows NT 4.0 Option Pack, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016, the log size is configurable and stored in the registry. The default log size value is 4 MB and the default maximum size is 512 MB.

<9> Section 3.3.7.1.2: In Windows NT 4.0 Option Pack, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016, the log size is configurable and stored in the registry. The default log size value is 4 MB and the default maximum size is 512 MB.

<10> Section 3.3.7.2.1: In Windows NT 4.0 Option Pack, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and  Windows Server 2016, the log size is configurable and stored in the registry. The default log size value is 4 MB and the default maximum size is 512 MB.

<11> Section 3.3.7.2.3: In Windows NT 4.0 Option Pack, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016, the log size is configurable and stored in the registry. The default log size value is 4 MB and the default maximum size is 512 MB.

<12> Section 5: In Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016, the implementation of this protocol supports both the mutual authentication and incoming authentication transport security settings.

Show: