7 Appendix B: 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 Vista operating system

  • Windows Server 2008 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.3: In server role, Windows resets the metadata version to one each time the protocol is initialized.

<2> Section 3.1.3: In server role, Windows defines a single scope by prepending the string "https://" to the FQDN of the host.

<3> Section 3.1.4.1: In server role, Windows always sends a single scope, defined by prepending the string "https://" to the FQDN of the host.

<4> Section 3.1.4.1: In server role, Windows includes one XAddr for each active non-loopback IPv4 address and each globally aggregatable IPv6 address.

<5> Section 3.1.4.3: In server role, Windows sends a URI list containing all server addresses from the table of connected subnets.

<6> Section 3.1.4.4: In server role, Windows always sends a single scope, defined by prepending the string "https://" to the FQDN of the host.

<7> Section 3.1.4.4: In server role, Windows includes one XAddr for each active non-loopback IPv4 address and each globally aggregatable IPv6 address.

<8> Section 3.1.4.5: In server role, Windows ignores Resolve messages.

<9> Section 3.1.4.6: In server role, Windows does not send these messages, and ignores them if received.

<10> Section 3.1.6.1: In server role, Windows sends a Bye message.

<11> Section 3.1.6.1: In server role, Windows closes the ports if and only if no other WS-Discovery–based protocols are active on the host.

<12> Section 3.1.6.2: In server role, Windows does not increment its metadata version when the address list changes.

<13> Section 3.1.6.2: In server role, Windows does not send the Hello message.

<14> Section 3.1.6.2: In server role, Windows sends a URI list containing all server addresses from the table of connected subnets.

<15> Section 3.1.6.3: In server role, Windows does not increment its metadata version when the address list changes.

<16> Section 3.1.6.3: Windows Vista and Windows Server 2008 do not send a Hello message.

<17> Section 3.1.6.3: In server role, Windows sends a URI list containing all server addresses from the table of connected subnets.

<18> Section 3.2.1.2: In client role, Windows authenticates servers by using the BITS Peer-Caching: Peer Authentication Protocol, as specified in [MS-BPAU].

<19> Section 3.2.1.2: In client role, Windows always discards Bye messages.

<20> Section 3.2.1.4: In client role, Windows defines a single scope by prepending the string "https://" to the FQDN of the host.

<21> Section 3.2.4.1: In client role, Windows verifies that the /s:Body/d:Hello/a:EndpointReference/msbits:Fqdn element matches the Active Directory domain to which the client belongs. Windows supports the protocol only on hosts that are members of an Active Directory domain.

<22> Section 3.2.4.2: In client role, Windows always discards Bye messages.

<23> Section 3.2.4.3: In client role, Windows always sends a single scope, defined by prepending the string "https://" to the FQDN of the host.

<24> Section 3.2.6.8: In client role, Windows closes the ports if and only if no other WS-Discovery–based protocols are active on the host.