6 Appendix A: 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.

 

  • Windows Server 2003 R2 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

  • Windows Server operating system

  • Windows Server 2019 operating system

  • Windows Server 2022 operating system 

  • Windows 11 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 3.1.5.1:  For an example of how Windows performs hash window and horizon negotiation, see [MS-FRS2]  section 3.2.4.1.14.

<2> Section 3.1.5.3.1:  The RDC library in Windows supports a maximum recursion depth of eight.

<3> Section 3.1.5.4: If the similarity data appears in a protocol, the Windows-based client and server use the methods described in section 3.1.5.4.1 to compute similarity data.

<4> Section 3.1.5.4.2:  FRS2 [MS-FRS2] can use several seed files, some of which are selected by finding the files that have the largest number of matching similarity traits. FRS2 also uses other techniques for finding seed files.

<5> Section 5.1: Windows Distributed File System (DFS) replication [MS-FRS2], the only Microsoft component using RDC at the time of this writing, computes a SHA-1 hash [FIPS180-2] over the contents of the file. And if it does not match, it transfers the file without using RDC.