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.

  • 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

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: RMS version 1.0 servers, RMS version 1.0 SP1 servers, and RMS version 1.0 SP2 servers run on Windows Server 2003. RMS version 2.0 servers do not run on Windows Server 2003.

<2> Section 2.1: On Windows, RMS version 1.0 and RMS version 1.0 SP1 do not implement the GroupExpansionWebServiceSoap port type. RMS version 2.0 does not implement the Binary Group Expansion interface.

RMS version 2.0 does not implement the SubEnrollServiceSoap port type.

RMS version 1.0, RMS version 1.0 SP1, and RMS version 1.0 SP2 support SOAP 1.1 [SOAP1.1] only. RMS version 2.0 supports both SOAP 1.1 and SOAP 1.2.

RMS supports HTTPS for securing its communications, although Secure Sockets Layer (SSL) is not configured by default.

<3> Section 2.3.1: The RMS server populates these strings with implementation-specific values. For successful responses, the RMS server ignores the contents of all such strings. If an exception occurs, the RMS server will use the strings serialized as member values of the RemotingException record in its error logging. No requirements are placed on the format of these strings.

<4> Section 2.3.4.1: The Microsoft RMS implementations will marshal one BinaryLibrary object every time at least one record is included referencing that LibraryID. The Microsoft RMS implementations will marshal the name of these libraries as present on the particular version of the implementation that is running. When processed, the Microsoft implementation will match the library name against the implementation-specific name of that library. If the strings do not match, the reply will be discarded.

<5> Section 2.3.4.1: The LibraryName field will be set to "Plugin.DirectoryServices, Version=1.0.3246.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" in all Microsoft RMS version 1.0 implementations.

<6> Section 2.3.4.1: The LibraryName field will be set to "Plugin.DirectoryServices, Version=5.2.3790.134, Culture=neutral, PublicKeyToken=31bf3856ad364e35" in all Microsoft RMS version 1.0 SP1 implementations.

<7> Section 2.3.4.1: The LibraryName field will be set to "Plugin.DirectoryServices, Version=5.2.3790.300, Culture=neutral, PublicKeyToken=31bf3856ad364e35" in all Microsoft RMS version 1.0 SP2 implementations

<8> Section 2.3.5.3: Windows places the record that defines the ID before or after the referencing record.

<9> Section 3.1.4.1: On Windows, all versions of RMS use a MinimumVersion and MaximumVersion of 1.0.0.0 for all SOAP requests in the RMS: Server-Server Protocol.

For SOAP responses:

  • All versions of RMS use a MinimumVersion of 1.0.0.0.

  • RMS versions 1.0 and 1.0 SP1 use a MaximumVersion of 1.0.0.0.

  • RMS version 1.0 SP2, Windows Server 2008, and Windows Server 2008 R2 use a MaximumVersion of 1.1.0.0.

  • Windows Server 2008 R2 Service Pack 1 (SP1), Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server operating system, and Windows Server 2019 use a MaximumVersion of 1.2.0.0.

<10> Section 3.2.4.1: In Windows, this is not used by RMS 2.0; it is only used by RMS 1.0, RMS 1.0 SP1, and RMS 1.0 SP2.

<11> Section 3.2.4.1: In Windows, this is not used by RMS 1.0 or RMS 1.0 SP1; it is only used by RMS 1.0 SP2 and RMS 2.0.

<12> Section 3.2.4.1: In Windows, this is not used by RMS 1.0, RMS 1.0 SP1, or RMS 1.0 SP2; it is only used by RMS 2.0.

<13> Section 3.2.4.1: In Windows, this is not used by RMS 1.0, RMS 1.0 SP1, or RMS 1.0 SP2; it is only used by RMS 2.0.

<14> Section 3.2.4.1.1.1: On Windows RMS Server requests only one service location at a time.

<15> Section 3.2.4.1.4.1: On Windows, this value is not used by RMS 2.0; this value is used only by RMS 1.0, RMS 1.0 SP1, and RMS 1.0 SP2.

<16> Section 3.2.4.1.4.1: On Windows, this value is not used by RMS 1.0 or RMS 1.0 SP1; this value is used only by RMS 1.0 SP2 and RMS 2.0.

<17> Section 3.2.4.1.4.1: On Windows, this value is not used by RMS 1.0, RMS 1.0 SP1, or RMS 1.0 SP2; this value is used only by RMS 2.0.

<18> Section 3.2.4.1.4.1: On Windows, this value is not used by RMS 1.0, RMS 1.0 SP1, or RMS 1.0 SP2; this value is used only by RMS 2.0.

<19> Section 3.3.1: In Windows, RMS server currently generates a random 1,024-bit RSA key pair on installation and retains this state.

<20> Section 3.3.4.1: RMS expects a 1024-bit RSA PKCS#1-encoded public key. For more information on PKCS#1, see [PKCS1].

<21> Section 3.3.4.1.3.2: On Windows, RMS expects a 1024-bit RSA PKCS#1-encoded public key.

<22> Section 3.4: The SubEnrollServiceSoap port type is implemented only by RMS version 1.0, RMS version 1.0 SP1, and RMS version 1.0 SP2. Because RMS version 2.0 self-bootstraps, it neither calls nor exposes this interface.

<23> Section 3.5.4.1: In Windows, the predefined maximum count of cross-forest calls is 10. After the incremented count of cross-forest calls reaches 10, Windows will reject the request and return a fault.