4.1 Product Behavior

  • Article

<1> Section 2.1: Windows Server 2008 R2 operating system is the first server to support the server feature BranchCache retrieval - Hosted Cache Mode. The Hyper-V Core and Home Server SKUs are not branch cache-capable. All other Windows Server 2008 R2 SKUs can act as branch cache clients and/or content servers.

<2> Section 2.1: Windows Server 2008 R2 and Windows 7 operating system support the client feature BranchCache retrieval - Hosted Cache Mode and Distributed Mode. BranchCache retrieval is available with Windows 7 Enterprise and Windows 7 Ultimate.

<3> Section 2.1.1.2: In Windows Vista operating system and Windows Server 2008 operating system, support for the client-side elements of Content Caching and Retrieval is available only with the optional installation of the Background Intelligent Transfer Service (BITS) (see [MC-BUP]) via the Windows Management Framework (WMF). Support for the server-side elements of this protocol is not available for Windows Server 2008. When the Windows Management Framework is installed, the BITS service use of [MS-BPDP] is replaced by [MS-PCCRD] for discovery, and [MS-BPCR] is replaced by [MS-PCCRR] for content retrieval. For more information, see [MSDN-BITS].

<4> Section 2.1.2: The use of HTTP for this content offering is not supported in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.

<5> Section 2.2: HTTP is not supported in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.

<6> Section 2.2: HTTP is not supported in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.

<7> Section 2.5.1: In Windows, the Object Store is provided by a local file system, usually NTFS.

<8> Section 2.6: Version 2.0 is not supported in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.

<9> Section 2.6: SMB Version 2.1 offers functionality that is relevant to the Peer for Content Caching and Retrieval. Content Caching was first introduced in the Windows 7 platform and can be made available on Windows Vista and Windows Server 2008 systems by the addition of a Windows Management Framework. This makes Peer Content Caching and Retrieval available only to BITS clients.

<10> Section 2.8.1.2.2: In Windows, the time-out value is set by the higher-layer applications. The recommended value is 5 seconds for each segment retrieval session. The range of permitted timeout values is from 0 to 4,294,967,294 milliseconds.

<11> Section 2.8.1.2.2: Windows uses a 15-second lifetime for an entry in the discovery cache with no associated address.

<12> Section 2.8.1.2.2: Windows uses 1 minute as the lifetime for each address that is added to a discovery cache entry.

<13> Section 2.8.2.5.1: Windows uses 16 as the default maximum number of peers that are used per download. The number is configurable from 1 to 16,384, inclusive.

<14> Section 2.8.2.5.1: Windows carries out a simple download each time a download involves less than four consecutive blocks in a single block range, which implies that the blocks are also adjacent (consecutive) in the segment.

<15> Section 2.8.2.5.6: Windows uses a 2-second timeout for each request message. The timeout is configurable between 1 millisecond and 1 minute.

<16> Section 2.8.2.5.6: Windows client-role peer allows a serving-role peer to time out up to a configurable three times, before excluding the peer from the current download. This value is configurable from 1 to 100, inclusive.

<17> Section 2.10: In Windows 7 and Windows Server 2008 R2, there are two ways for an application to use branch cache retrieval: directly by calling the branch cache platform APIs, or indirectly by calling WinINET/WinHTTP or SMBv2 APIs, which are instrumented to use branch cache, but are transparent to the applications. For more information on WinINET/WinHTTP see [MSDOCS-WinINet].

<18> Section 3.1: Windows 7 clients offer MS KRB 5, KRB5 SNMPV2, and NTLMSSP if they are configured with the fully qualified domain name (FQDN) of the hosted cache server. If a NetBIOS address or IP address is given for the hosted cache server, then only NTLMSSP is offered.

<19> Section 3.2: Windows 7 clients offer MS KRB 5, KRB5 SNMPV2, and NTLMSSP if they are configured with the fully qualified domain name (FQDN) of the hosted cache server. If a NetBIOS address or IP address is given for the hosted cache server, then only NTLMSSP is offered.