7 Appendix B: Product Behavior

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

The terms "earlier" and "later", when used with a product version, refer to either all preceding versions or all subsequent versions, respectively. The term "through" refers to the inclusive range of versions. Applicable Microsoft products are listed chronologically in this section.

Windows Client

  • Windows NT 4.0 operating system

  • Windows 2000 Professional operating system

  • Windows XP operating system

  • Windows Vista operating system

  • Windows 7 operating system

  • Windows 8 operating system

  • Windows 8.1 operating system

  • Windows 10 operating system

  • Windows 11 operating system

Windows Server

  • Windows NT 4.0

  • Windows 2000 Server operating system

  • Windows Server 2003 operating system

  • Windows Server 2008 operating system

  • Windows Server 2008 R2 operating system

  • Windows Server 2012 operating system

  • Windows Server 2012 R2 operating system

  • Windows Server 2016 operating system

  • Windows Server operating system

  • Windows Server 2019 operating system

  • Windows Server 2022 operating system

  • Windows Server 2025 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 1.7: The ICertPassage Interface is supported by all applicable Windows releases. However, CMC (Certificate Management Protocol using CMS) request formats and CMC response formats are not supported by Windows 2000 operating system and earlier. CMC is specified in [RFC2797].

<2> Section 2.2.1:  Windows 2000 and earlier do not support the CMC request format (as specified in [RFC2797]).

<3> Section 3.1.3: For authenticated RPC, the client in Windows XP and later and the server in Windows Server 2003 and later, passes RPC_C_AUTHN_GSS_NEGOTIATE and RPC_C_AUTHN_LEVEL_PKT_PRIVACY. The client in Windows 2000 Server passes RPC_C_AUTHN_GSS_NEGOTIATE only to RPC. These values are used to allow RPC to negotiate the authentication level on behalf of the client with the server, as specified in [MS-RPCE].

<4> Section 3.2.3: The exchange private key was not used in Windows Server 2003 and earlier.

<5> Section 3.2.4.1: ICertPassage clients are supported on Windows 2000 Professional and later and ICertPassage servers are supported on Windows NT Server operating system and later.

<6> Section 3.2.4.1.1: The implementation of this method on Windows Server 2003 and later is identical to the ICertRequestD::Request method, as specified in [MS-WCCE] section 3.2.1.4.2.1. However, the implementation of this method on Windows 2000 Server has the following differences from the specified ICertRequestD::Request method. In ICertPassage on Windows 2000 Server:

  • The format of the certificates request passed in the pctbRequest parameter cannot be CMC, as specified in [RFC2797].

  • Windows 2000 Server does not return or support issued certificates in the CMC format, as specified in [RFC2797].

<7> Section 3.2.4.1.1: In Windows Server 2003 and later, the error returned is RPC_S_SERVER_UNAVAILABLE (0x800706ba). Windows 2000 does not return an error.