Export (0) Print
Expand All

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

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.2.3: While performing push propagation, the Name object (as specified in [MS-CMPO] section 3.2.1.4) of the transaction manager is represented by using the NAMEOBJECTBLOB (section 2.2.5.3) structure on Windows NT 4.0 Option Pack and is represented by using the SWhereabouts (section 2.2.5.11) structure on 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, and Windows Server 2012 R2.

<2> Section 2.2.1.1: MSDTC Connection Manager: OleTx Transaction Protocol version 1 is supported by all Windows versions. Version 2 is supported by 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, and Windows Server 2012 R2. Version 4 is supported by Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2. Version 5 is supported by Windows Server 2003 with SP1, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2. Version 6 is supported by Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<3> Section 2.2.1.1.1: The connection typeCONNTYPE_TXUSER_EXTENDEDWHEREABOUTS is supported by Windows XP SP2, Windows XP SP3, Windows Server 2008, Windows Vista, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<4> Section 2.2.1.1.1: The connection typeCONNTYPE_TXUSER_EXTENDEDWHEREABOUTS is supported by Windows XP SP2, Windows XP SP3, Windows Server 2008, Windows Vista, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<5> Section 2.2.1.1.1: The connection typeCONNTYPE_TXUSER_PROMOTE is supported by Windows Server 2008, Windows Vista, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<6> Section 2.2.1.1.1: The connection typeCONNTYPE_TXUSER_PROMOTE is supported by Windows Server 2008, Windows Vista, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<7> Section 2.2.1.1.1: The connection type CONNTYPE_TXUSER_SETTXTIMEOUT is supported by Windows 2000 SP4 or later.

<8> Section 2.2.1.1.1: The connection typeCONNTYPE_TXUSER_SETTXTIMEOUT2 is supported by Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<9> Section 2.2.1.1.1: The connection typeCONNTYPE_TXUSER_SETTXTIMEOUT2 is supported by Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<10> Section 2.2.1.1.1: The message TXUSER_RESOLVE_MTAG_ACCESSDENIED that is associated with connection type CONNTYPE_TXUSER_RESOLVE is supported by Windows XP SP2, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<11> Section 2.2.1.1.3: Connection type CONNTYPE_TXUSER_RESOURCEMANAGERINTERNAL is supported by Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<12> Section 2.2.1.1.3: Connection type CONNTYPE_TXUSER_RESOURCEMANAGERINTERNAL is supported by Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<13> Section 2.2.4.1: The value that Windows places in this field is undefined.

<14> Section 2.2.5.2: This structure is supported only on Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<15> Section 2.2.5.3: On Windows NT 4.0 Option Pack and Windows 2000, this field is set to a nondeterministic 4-byte value. Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2 set this field to 0xCD64CD64.

<16> Section 2.2.5.4: The dwVersionMax field is set to 1 on Windows NT 4.0 Option Pack, 2 on Windows 2000, and 3 on Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<17> Section 2.2.5.9: The field TmProtocolMsdtcV1 is included in the SWhereabouts structure on 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, and Windows Server 2012 R2. The TmProtocolMsdtcV2 field is included in the SWhereabouts structure on 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, and Windows Server 2012 R2. The TmProtocolTip field is included in the SWhereabouts structure, if the transaction manager is so configured, on 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, and Windows Server 2012 R2. The TmProtocolExtended field is included in the SWhereabouts structure, if the transaction manager is so configured, on Windows XP SP3, Windows Server 2003 SP2, Windows Server 2003 with SP3, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<18> Section 2.2.8.2.1.1.10: Windows does not have a maximum limit on the number of times an application can perform associate request on an already existing transaction by sending the TXUSER_ASSOCIATE_MTAG_ASSOCIATE message. Therefore, the TXUSER_ASSOCIATE_MTAG_TOO_MANY_LOCAL message is never sent by any Windows implementation.

<19> Section 2.2.8.3.2.1: By default, Windows XP SP2, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2 require authentication with an account that is in the administrator group. This behavior is configurable on Windows XP SP2, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<20> Section 2.2.8.3.2.8: The message TXUSER_RESOLVE_MTAG_NOT_CHILD that is associated with connection type CONNTYPE_TXUSER_RESOLVE is never sent by any Windows implementation.

<21> Section 2.2.10.2.2.8: Windows limits transactions to 32 direct enlistments.

<22> Section 3.1.4.3: Regarding the MSDTC Connection Manager: OleTx Transaction Protocol connection establishment in Windows, an MSDTC Connection Manager: OleTx Transaction Protocol session partner does send connection requests for connection types that it supports (when required by the protocol rules; see section 3). The CONNTYPE_TXUSER_EXPORT2 (section 2.2.8.2.2.3) and CONNTYPE_TXUSER_PROMOTE (section 2.2.8.1.3) could be sent to the other partner, which might not support these connection types. As a result, the requests for the unsupported connection types are rejected with an MTAG_CONNECTION_REQ_DENIED ([MS-CMP] section 2.2.5). When the CONNTYPE_TXUSER_PROMOTEconnection type is rejected, Windows implementations return the failure result to the higher business layer. When the CONNTYPE_TXUSER_EXPORT2connection type is rejected, Windows implementations fall back to the CONNTYPE_TXUSER_EXPORT (section 2.2.8.2.2.2)connection type.

<23> Section 3.1.4.3: Regarding the sending of messages over an established MSDTC Connection Manager: OleTx Transaction Protocol connection in Windows, an MSDTC Connection Manager: OleTx Transaction Protocol session partner never sends messages that it supports (when required by the protocol rules) (see section 3), but that are not supported by the negotiated protocol version (in the context of the connection'sconnection type) with one exception: TXUSER_RESOLVE_MTAG_ACCESSDENIED (section 2.2.8.3.2.1). For TXUSER_RESOLVE_MTAG_ACCESSDENIED, a partner that supports this message sends it (when required by protocol rules) even if it is not supported by the negotiated protocol version.

<24> Section 3.1.6: On receiving an invalid message on a connection, the participant terminates the associated session on Windows XP SP1, Windows 2000, and the Windows NT 4.0 Option Pack.

<25> Section 3.2.3: No authentication is supported by 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, and Windows Server 2012 R2. Incoming authentication and mutual authentication are supported by Windows XP SP2, Windows Server 2003 with SP1, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2. The security level is configurable to any of the three values on Windows XP SP2, Windows Server 2003 with SP1, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<26> Section 3.2.3.1: The Timeout field value defaults to zero on 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, and Windows Server 2012 R2.

<27> Section 3.2.3.2: On 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, and Windows Server 2012 R2, 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.

<28> Section 3.2.3.3: The Core Transaction Manager Facet (section 1.3.3.3.1) ensures that transactions with duplicate identifiers will not be created on Windows NT 4.0 Option Pack, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2. However, the Core Transaction Manager Facet (section 1.3.3.3.1) does not ensure the same on Windows Vista and requires the application of Windows Vista SP1 to restore the correct protocol behavior.

<29> Section 3.2.7.11: The limit of Subordinate Enlistments depends on the type of the Enlistment. The limit on Subordinate Transaction ManagerEnlistments is 16 on Windows NT 4.0 Option Pack and 64 on 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, and Windows Server 2012 R2. The limit on Subordinate Resource ManagerEnlistments is 32 on 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, and Windows Server 2012 R2.

<30> Section 3.2.7.13: The Core Transaction Manager Facet (section 1.3.3.3.1) ensures that transactions with duplicate identifiers will not be created on Windows NT 4.0 Option Pack, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2; however, the Core Transaction Manager Facet (section 1.3.3.3.1) does not ensure the same on Windows Vista and requires the application of Windows Vista SP1 to restore the correct protocol behavior.

<31> Section 3.2.7.21: The limit of Subordinate Enlistments depends on the type of the Enlistment. The limit on Subordinate Transaction Managerenlistments is 16 on Windows NT 4.0 Option Pack and 64 on 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, and Windows Server 2012 R2. The limit on Subordinate Resource Manager enlistments is 32 on 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, and Windows Server 2012 R2.

<32> Section 3.3.4.1: In Windows Vista, the Core Transaction Manager Facet (section 1.3.3.3.1) does not ensure that transactions with duplicate identifiers are not created. If an identifier that already exists in the transaction table is sent as the guidTX field with TXUSER_BEGINNER_MTAG_PROMOTE Message (section 3.4.5.1.3.1), a duplicate entry having the same transaction identifier will be created in the transaction table. As a result, the transaction identifier having duplicate entries in the transaction table is not uniquely mapped to a single transaction object and any subsequent lookup for a transaction object with this identifier may return any one of the duplicate transaction objects. Any subsequent processing rule that involves finding a transaction object by this transaction identifier may have an undefined outcome as a result of this Windows Vista-specific behavior. This undefined behavior was identified post release and has since been addressed in subsequent releases. An implementation MUST avoid duplicate transaction identifiers when beginning a transaction that uses the CONNTYPE_TXUSER_PROMOTE connection type (section 3.3.4.1.3) by always using a new GUID as specified in [RFC4122] for the predetermined transaction identifier.

<33> Section 3.4.5.3.2.1: By default, Windows XP SP2, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2 require authentication with an account that is in the administrator group. This behavior is configurable on Windows XP SP2, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<34> Section 3.4.5.3.2.2: By default, Windows XP SP2, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2 require authentication with an account that is in the administrator group. This behavior is configurable on Windows XP SP2, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<35> Section 3.4.5.3.2.3: By default, Windows XP SP2, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2 require authentication with an account that is in the administrator group. This behavior is configurable on Windows XP SP2, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.

<36> Section 3.7.2.1: The value of the Redeliver Commit Timer (section 3.7.2.1) is 1,000 milliseconds if the underlying transport is down. Otherwise, it is 500 milliseconds on 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, and Windows Server 2012 R2. This value is not configurable.

<37> Section 3.8.2.1: The value of the Check Abort Timer (section 3.8.2.1) is 1,000 milliseconds on 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, and Windows Server 2012 R2. This value is not configurable.

<38> Section 5.1: Mutual authentication is used by default on Windows XP SP2, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2. No authentication is used on Windows NT 4.0 Option Pack, Windows 2000, and Windows XP SP1.

 
Show:
© 2015 Microsoft