BranchCache Early Adopter's Guide

BranchCache Early Adopters Guide
Microsoft Windows Family of Operating Systems

Microsoft Corporation
Published: May 2009
Astract
This document provides an overview of the BranchCache feature introduced in indows! "
and indows #erver! 200$ %2& 'fter a thorou(h introduction of BranchCache and its modes of
operation) the document describes BranchCache confi(uration& *t then provides troubleshootin(
details and a list of tools to be used by BranchCache administrators&
Copyright information
This document supports a preliminary release of a software product that may be chan(ed
substantially prior to final commercial release& This document is provided for informational
purposes only and Microsoft ma+es no warranties) either e,press or implied) in this document&
*nformation in this document) includin( -%. and other *nternet eb site references) is sub/ect to
chan(e without notice& The entire ris+ of the use or the results from the use of this document
remains with the user& -nless otherwise noted) the companies) or(ani0ations) products) domain
names) e1mail addresses) lo(os) people) places) and events depicted in e,amples herein are
fictitious& 2o association with any real company) or(ani0ation) product) domain name) e1mail
address) lo(o) person) place) or event is intended or should be inferred& Complyin( with all
applicable copyri(ht laws is the responsibility of the user& ithout limitin( the ri(hts under
copyri(ht) no part of this document may be reproduced) stored in or introduced into a retrieval
system) or transmitted in any form or by any means 3electronic) mechanical) photocopyin()
recordin() or otherwise4) or for any purpose) without the e,press written permission of Microsoft
Corporation&
Microsoft may have patents) patent applications) trademar+s) copyri(hts) or other intellectual
property ri(hts coverin( sub/ect matter in this document& 5,cept as e,pressly provided in any
written license a(reement from Microsoft) the furnishin( of this document does not (ive you any
license to these patents) trademar+s) copyri(hts) or other intellectual property&
6 2009 Microsoft Corporation& 'll ri(hts reserved&
Microsoft) 'ctive 7irectory) 8utloo+) indows) indows #erver) *nternet 5,plorer) and
BranchCache are trademar+s of the Microsoft (roup of companies& 'll other trademar+s are
property of their respective owners&
Contents
BranchCache 5arly 'dopter9s :uide&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& "
BranchCache 8verview&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& "
7istributed Cache mode&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& $
;osted Cache mode&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 9
#erver Confi(uration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& <0
*nstallin( the BranchCache feature&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& <0
Confi(urin( a eb server or a B*T# application server to use BranchCache&&&&&&&&&&&&&&&&&&&&&&&&&&&&<<
Confi(urin( a #-# server to use BranchCache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&<<
Confi(urin( a file server to use BranchCache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& <2
-sin( :roup Policy to confi(ure BranchCache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& <=
-sin( the %e(istry 5ditor to confi(ure dis+ use for stored identifiers&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&<>
#ettin( the BranchCache support ta( on a file share&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&<>
'dditional steps for server clusters&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& <?
Client Confi(uration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& <?
Client confi(uration usin( :roup Policy&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& <?
Confi(urin( the client firewall&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& <$
Client confi(uration usin( netsh&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& <9
7eployin( BranchCache with %emote 'ccess Technolo(ies&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&20
;osted Cache mode and host1based @P2 software&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&20
BranchCache and Microsoft 7irect'ccess&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&20
2on1Microsoft Airewall #ettin(s for BranchCache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&2<
2on1Microsoft firewall settin(s for 7istributed Cache clients&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&2<
BM#1PCC%7C: Peer Content Cachin( and %etrieval 7iscovery Protocol&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&2<
BM#1PCC%%C: Peer Content Cachin( and %etrieval: %etrieval Protocol&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&22
2on1Microsoft firewall settin(s for ;osted Cache clients&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&22
BM#1PCC%%C: Peer Content Cachin( and %etrieval: %etrieval Protocol&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&22
BM#1PC;CC: Peer Content Cachin( and %etrieval: ;osted Cache Protocol&&&&&&&&&&&&&&&&&&&&&&&&&&22
2on1Microsoft firewall settin(s for the ;osted Cache server&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&22
BM#1PCC%%C: Peer Content Cachin( and %etrieval: %etrieval Protocol&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&2=
BM#1PC;CC: Peer Content Cachin( and %etrieval: ;osted Cache Protocol&&&&&&&&&&&&&&&&&&&&&&&&&&2=
BranchCache protocols for content servers 3such as a eb server or file server4&&&&&&&&&&&&&&&&&&&&2=
;osted Cache #erver #etup&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2=
*nstall the BranchCache feature&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2>
5nable the BranchCache feature and enable ;osted Cache mode&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&2?
7eploy a certificate&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2?
*mport the certificate&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2D
.in+ the certificate to BranchCache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2"
%esi0e the cache on the ;osted Cache server&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&2$
Modify the ;osted Cache #erver Ports&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2$
Modifyin( the %etrieval Protocol Port 3TCP Port $04&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&2$
Modifyin( the ;osted Cache Protocol Port 3TCP Port >>=4&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&29
@erification and Monitorin(&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& =0
@erifyin( client confi(uration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& =0
@erifyin( the ;osted Cache #erver confi(uration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&=2
7ebu((in( certificate issues&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ==
@erifyin( content server confi(uration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& =?
@erifyin( end1to1end deployment with performance counters&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&=?
'bout server1side identifier (eneration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& =D
Calculatin( BranchCache efficiency with performance counters&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&=D
Troubleshootin(&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& =$
BranchCache doesn9t function&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& =$
BranchCache and client performance&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& =9
'pplication failures&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >0
Tools *nde,&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >0
:roup Policy&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >0
:roup Policy administrative template&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >0
Turn on BranchCache settin(&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ><
Turn on BranchCache E 7istributed Cache Mode settin(&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&><
Turn on BranchCache E ;osted Cache mode settin(&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&>2
#et percenta(e of dis+ space used for client computer cache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&>2
Confi(ure BranchCache for networ+ files&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >2
7isablin( B*T# use of BranchCache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >=
2etsh Commands&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >=
dump&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >=
e,port+ey&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >>
flush&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >>
import+ey&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >>
reset&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >?
set mode&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >?
set cachesi0e&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >?
set +ey&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >D
set localcache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >D
set service&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >"
show hostedcache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >$
show localcache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >$
show status&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >$
Performance Counters&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >$
'ttempted 7iscoveries&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >$
'vera(e Branch %ate&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >9
Bytes from Cache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >9
Bytes from #erver&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >9
Bytes #erved&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& >9
Cache Complete Aile #e(ments&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?0
Cache ;it %atio&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?0
Cache Partial Aile #e(ments&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?0
7iscovery Time&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?<
;osted Cache E Client file se(ment offers accepted&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&?<
;osted Cache E Client file se(ment offers made&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&?<
%eFuestsAilledBy#erver&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?<
Protocol #pecific Counters&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?2
Bytes Arom Cache&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?2
Bytes Arom #erver&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?2
Cache ;it %atio&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?2
eb server performance counters&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?=
Client Cache Miss Bytes&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?=
;ash Bytes&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?=
;ypothetical #erver Bytes ithout Cachin(&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&?=
Processed ;TTP %eFuests&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?=
#erver Cache Miss Bytes&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?>
Total ;TTP %eFuests&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?>
Chan(in( BranchCache Ports&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?>
;osted Cache server&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ?>
;osted Cache clients&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ??
5vent .o(s&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ??
-p(rade 2otes&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& D0
-p(radin( a ;osted Cache server from indows " Beta to a later indows " version&&&&&&&&&&&&D0
;osted Cache mi(ration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& D0
BranchCache and #ystem %estore&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& D0
BranchCache Early Adopters Guide
BranchCache is desi(ned to reduce '2 lin+ utili0ation and improve application
responsiveness for branch office wor+ers who access content from servers in remote locations&
Branch office client computers use a locally maintained cache of data to reduce traffic over a
'2 lin+& The cache can be distributed across client computers 3distributed cache mode4 or can
be housed on a server in the branch 3hosted cache mode4& BranchCache only optimi0es traffic
flows between indows #erver! 200$ %2 servers and indows! " clients&
#erver Confi(uration
Client Confi(uration
7eployin( BranchCache with %emote 'ccess Technolo(ies
2on1Microsoft Airewall #ettin(s for BranchCache
;osted Cache #erver #etup
@erification and Monitorin(
Troubleshootin(
Tools *nde,
2etsh Commands
Performance Counters
Chan(in( BranchCache Ports
5vent .o(s
-p(rade 2otes
!ote
Aor a complete view of indows " resources) articles) demos) and (uidance) please visit
the #prin(board #eries for indows " on the indows Client TechCenter&
Aor a eb version of this document) see the BranchCache 5arly 'dopter9s :uide in the
indows " Technical .ibrary 3http://go.microsoft.com/fwlink/?LinkId=1486414&
BranchCache O"er"iew
BranchCache is desi(ned to reduce '2 lin+ utili0ation and improve application
responsiveness for branch office wor+ers who access content from servers in remote locations&
Branch office client computers use a locally maintained cache of data to reduce traffic over a
'2 lin+& The cache can be distributed across client computers 37istributed Cache mode4 or can
be housed on a server in the branch 3;osted Cache mode4&
BranchCache is desi(ned to prevent unauthori0ed access to content& Content is encrypted when
transferred between peers or between clients and the hosted cache server& Content can only be
decrypted usin( the identifiers provided by the content server in the main office& The content
server will only provide identifiers to authori0ed clients& BranchCache supports the optimi0ation of
downloads over end1to1end secure transports such as ;TTP# and *Psec&
BranchCache only optimi0es traffic flows between indows #erver 200$ %2 servers and
indows " clients& The BranchCache feature is an optional component on indows
#erver 200$ %2 and must be installed and enabled before BranchCache can be used& To
optimi0e #MB traffic) the file server role must be enabled& BranchCache is installed on indows "
client computers by default) but *T administrators must enable BranchCache and create firewall
rules to enable traffic between client computers&
#istriuted Cache mode
*f client computers are confi(ured to use 7istributed Cache mode) the cached content is
distributed amon( client computers on the branch office networ+& 2o infrastructure or services are
reFuired in the branch office beyond client computers runnin( indows "&
Figure $ 7istributed cache mode
<& Client < issues a reFuest for a file on a BranchCache1enabled server in headFuarters& This
reFuest can be transmitted over any of the BranchCache1enabled protocols 3;TTP) #MB) or
B*T#4& The client indicates to the server that it is BranchCache capable) usin( fields)
messa(es) or headers that are already part of the BranchCache1enabled protocol&
The server responds) and transmits a set of identifiers that describe the chun+s of content the
client wants to download& These identifiers are transmitted by usin( the BranchCache1
enabled protocol&
2& Client < searches locally for computer that has already downloaded and cached the content&
This search is conducted by usin( the BranchCache discovery protocol 3which) in turn) uses
#17iscovery4) which is a multicast protocol sent over -7P& Client < is the first computer in
the branch to download this piece of content) so it does not receive any responses&
$
=& Client < issues another reFuest to the server in headFuarters by usin( the BranchCache1
enabled protocol 3;TTP) #MB) or B*T#4& This reFuest is not mar+ed as BranchCache
capable& The server responds with the reFuested data& The client then adds this data to its
local cache&
>& Client 2 issues a reFuest for the same content that Client < downloaded earlier& Client 2
receives identifiers describin( the content from the server in headFuarters&
?& Client 2 uses the BranchCache discovery protocol to search for the content& Client < receives
this reFuest) finds the reFuested content in its local cache) and sends a response to Client 2&
D& Client 2 reFuests the content from Client < by usin( the BranchCache retrieval protocol
3which) in turn) uses ;TTP4& Client < transmits the content to Client 2) protectin( it with the
BranchCache encryption scheme& Client 2 verifies the data a(ainst the identifiers
downloaded from the server in headFuarters&
%osted Cache mode
*n hosted cache mode) cached content is maintained on a computer runnin( indows
#erver 200$ %2 on the branch office networ+&
Figure & ;osted cache mode
<& Client < issues a reFuest to a BranchCache1enabled server in headFuarters& This reFuest can
be transmitted over any of the BranchCache1enabled protocols 3;TTP) #MB) B*T#4& The
client indicates to the server that it is BranchCache capable) usin( fields) messa(es) or
headers that are already part of the BranchCache1enabled protocol&
The server responds) and transmits a set of identifiers that describe the chun+s of content
that the client wants to download& These identifiers are transmitted by usin( the
BranchCache1enabled protocol&
2& Client < reFuests the content from the hosted cache in the branch by usin( the BranchCache
retrieval protocol BM#1PCC%7C 3uses ;TTP) TCP) source port: ephemeral) destination port: $0
by default4& The hosted cache response informs Client < that the tar(et data is not available&
9
=& Client < issues another reFuest to the server in headFuarters by usin( the BranchCache1
enabled protocol 3;TTP) #MB) B*T#4& This reFuest is not mar+ed BranchCache capable& The
server responds with the reFuested data&
>& Client < adverti0es the newly downloaded content to the ;osted Cache server by usin( the
BranchCache hosted cache protocol BM#1PC;CC& This protocol is carried in ;TTP# 3TCP)
source port: ephemeral) destination port: >>= by default4&
?& The ;osted Cache server connects to the client and downloads the recently adverti0ed
content by usin( the BranchCache retrieval protocol BM#1PCC%7C 3which) in turn) uses ;TTP)
TCP) source port: ephemeral) destination port: $0 by default4&
D& Client 2 issues a reFuest for the same content that Client < downloaded earlier& Client 2
receives identifiers describin( the content from the server in headFuarters&
"& Client 2 reFuests the content from the hosted cache in the branch by usin( the BranchCache
retrieval protocol BM#1PCC%7C 3which) in turn) uses ;TTP) TCP) source port: ephemeral)
destination port: $0 by default4& The hosted cache responds with the data& Client 2 verifies the
data by usin( the identifiers downloaded from the server in headFuarters&
*f a client computer cannot locate content on the ;osted Cache server) it returns to the server in
the main office and reFuests a download&
;osted Cache mode and 7istributed Cache mode are mutually e,clusive& ' client computer can
be confi(ured to use only a sin(le cachin( mode at one time&
Ser"er Configuration
BranchCache is not installed by default on indows #erver 200$ %2& To confi(ure a eb server
or an application server that uses the Bac+(round *ntelli(ent Transfer #ervice 3B*T#4 protocol)
you must install the BranchCache feature usin( server mana(er& To confi(ure a file server to use
BranchCache) you must install the BranchCache for 2etwor+ Ailes feature) and confi(ure the
server usin( :roup Policy& Aor a indows #erver 200$ %2 computer to act as a BranchCache
client) you must first install the BranchCache feature and then follow the client confi(uration steps
in this document&
'nstalling the BranchCache feature
-se the 'dd Aeatures i0ard of #erver Mana(er in indows #erver 200$ %2 to enable
BranchCache on a eb server or B*T# application server&
(o install the BranchCache feature
<& Clic+ Start) point to Administrati"e (ools) and then clic+ Ser"er Manager&
2& %i(ht1clic+ Features and then clic+ Add Features&
=& *n the 'dd Aeatures i0ard) select BranchCache) and then clic+ !e)t&
<0
>& *n the Confirm *nstallation #elections dialo( bo,) clic+ 'nstall&
?& *n the *nstallation %esults dialo( bo,) confirm that BranchCache installed successfully)
and then clic+ Close&
Configuring a We ser"er or a B'(S application
ser"er to use BranchCache
To enable BranchCache acceleration of content served by a eb server or application server
usin( the B*T# protocol) you must install the BranchCache feature and ensure that the
BranchCache service has started& 2o other steps are necessary&
Configuring a WS*S ser"er to use BranchCache
*n addition to enablin( BranchCache in your environment) the #-# server must be confi(ured
to store update files locally 3both the update metadata and the update files are downloaded and
stored locally on the #-# server4& This ensures that the clients (et the update files from the
#-# server rather than directly from Microsoft -pdate& To learn more about #-# server
confi(uration) see 'dvanced #ynchroni0ation 8ptions for #-# 3http:GG(o&microsoft&comGfwlin+GH
.in+*dI<?0?9"4 on Microsoft Tech2et&
<<
Configuring a file ser"er to use BranchCache
The BranchCache for 2etwor+ Ailes role service of the Aile #ervices server role needs to be
installed before you can enable BranchCache for any file shares& 'fter you install the
BranchCache for 2etwor+ Ailes role service) use the :roup Policy Mana(ement Console to
enable BranchCache on the server& Jou can enable BranchCache for all shares on a file server or
only on selected shares&
!ote
Jou do not need to install the BranchCache feature usin( the 'dd Aeatures i0ard) as
described earlier in the (uide) when confi(urin( a file server&
BranchCache for 2etwor+ Ailes is a role service of the Aile #ervices role& -se the 'dd %oles
i0ard of #erver Mana(er to install the Aile #ervices role and the BranchCache for 2etwor+ Ailes
role service&
*sing Group +olicy to configure BranchCache
Jou can use the local :roup Policy 5ditor to confi(ure BranchCache on a sin(le server& *f you
have multiple file servers) and they are easily identifiable in your 'ctive 7irectory!11for e,ample)
they are or(ani0ed under a common or(ani0ational unit 38-411you may wish to use :roup Policy
to confi(ure BranchCache for multiple servers in one step&
<2
(o use Group +olicy to configure BranchCache
<& 8pen the :roup Policy Mana(ement Console& Clic+ Start) point to Administrati"e
(ools) and then clic+ Group +olicy Management Console&
2& #elect the domain in which you will apply the :roup Policy ob/ect) or select ,ocal
Computer +olicy-
=& #elect !ew from the Action menu to create a new :roup Policy ob/ect 3:P84&
>& Choose a name for the new :P8 and clic+ O.&
?& %i(ht1clic+ the :P8 /ust created and choose Edit&
D& Clic+ Computer Configuration) point to +olicies) Administrati"e (emplates) !etwor/)
and then clic+ ,anman Ser"er&
"& 7ouble1clic+ %ash +ulication for BranchCache&
$& Clic+ Enaled&
9& -nder Options) choose one of the followin( %ash pulication actions:
a& 'llow hash publication for all file shares&
b& 'llow hash publication for file shares ta((ed with KBranchCache support&L
c& 7isallow hash publication on all file shares&
<0& Clic+ O.&
*sing the 0egistry Editor to configure dis/ use for
stored identifiers
The identifiers used to describe bloc+s of content are stored on the file server& The re(istry can be
used to limit the ma,imum percent or physical dis+ space used on the server to store these
identifiers&
<=
Caution
*ncorrectly editin( the re(istry may severely dama(e your system& Before ma+in(
chan(es to the re(istry) you should bac+ up any valued data on the computer&
(o configure stored identifiers
<& 8pen an elevated command prompt 3clic+ Start) clic+ All +rograms) clic+ Accessories)
ri(ht1clic+ Command +rompt) and then clic+ 0un as administrator4&
2& 't the command prompt) type 0egedit-e)e) and then press Enter&
=& 2avi(ate to ;M.MNCurrentControl#etN#erviceN.anman#erverNParameters&
>& %i(ht1clic+ the %ashStorage,imit+ercent value) and then clic+ Modify&
?& *n the 1alue bo,) type the percenta(e of dis+ space that you would li+e BranchCache to
use& Clic+ O.&
D& Close the %e(istry 5ditor&
Setting the BranchCache support tag on a file
share
By default) only shares with the BranchCache support ta( will be optimi0ed& This is also the case
if the :roup Policy ;ash Publication for BranchCache settin( is enabled and the option Allow
hash pulication for file shares tagged with BranchCache support is selected& The followin(
section e,plains how to set the BranchCache support ta( on a file share&
(o set the BranchCache support tag on a share
<& Clic+ Start) point to Administrati"e (ools) and then clic+ Share and Storage
Management&
2& %i(ht1clic+ a share and then clic+ +roperties&
=& Clic+ Ad"anced&
>& 8n the Caching tab) select Only the files and programs that users specify are
a"ailale offline&
?& #elect Enale BranchCache) and then clic+ O.&
D& Clic+ O.) and then close the #hare and #tora(e Mana(ement Console&
Additional steps for ser"er clusters
BranchCache1enabled servers use a piece of crypto(raphic data when (eneratin( identifiers for
data bloc+s& *n a server cluster) this crypto(raphic data must be replicated across all
BranchCache1enabled servers in the cluster to +eep the (eneration of identifiers consistent
across all computers&
<>
(o replicate cryptographic data
<& 8pen an elevated command prompt 3clic+ Start) clic+ All +rograms) clic+ Accessories)
2& 't the command prompt) type netsh ranchcache set /ey
passphrase23M45+ASS+%0ASE6) and then press Enter& Choose a phrase +nown only
to you& %epeat this process usin( the same phrase on all computers that are participatin(
in the cluster&
Client Configuration
BranchCache is disabled by default on client computers& Ta+e the followin( steps to enable
BranchCache on client computers:
<& Turn on BranchCache&
2& 5nable either 7istributed Cache mode or ;osted Cache mode&
=& Confi(ure the client firewall to enable BranchCache protocols&
5nablin( 7istributed Cache or ;osted Cache mode 3step 24 without e,plicitly enablin( the overall
BranchCache feature 3step <4 will leave BranchCache disabled on a client computer&
*t is possible to enable BranchCache on a client computer 3step <4 without enablin( ;osted
Cache mode or 7istributed Cache mode 3step 24& *n this confi(uration) the client computer only
uses the local cache and will not attempt to download from peers or from a ;osted Cache server&
Multiple users of a sin(le computer will benefit from a shared local cache in this local cachin(
mode&
Confi(uration can be automated usin( :roup Policy or can be achieved manually by usin( the
netsh command& This section describes both confi(uration approaches&
Client configuration using Group +olicy
To enable BranchCache on indows " client computers usin( :roup Policy) you must first create
a :roup Policy ob/ect 3:P84 that will carry the BranchCache confi(uration& 'fter creatin( the
:P8) you confi(ure the settin( that enables BranchCache and choose whether BranchCache will
operate in 7istributed Cache mode or ;osted Cache mode&
(o create a G+O7 enale BranchCache7 and select the cache mode
<& Clic+ Start) point to Administrati"e (ools) and clic+ Group +olicy Management
Console&
2& *n the console tree) select the domain in which you will apply the :P8&
=& Create a new :P8 by selectin( !ew from the Action menu&
>& Choose a name for the new :P8) and then clic+ O.&
<?
?& %i(ht clic+ the :P8 you created and choose Edit&
D& Clic+ Computer Configuration) point to +olicies) Administrati"e (emplates8 +olicy
definitions 9A#M: files; retrie"ed from the local machine) !etwor/) and then clic+
BranchCache&
"& 7ouble1clic+ (urn on BranchCache&
$& Clic+ Enaled) and then clic+ O.&
<D
9& To use 7istributed Cache mode) double1clic+ (urn on BranchCache < #istriuted
Caching mode) clic+ Enaled) and then clic+ O.&
EorE
To use ;osted Cache mode) double1clic+ (urn on BranchCache < %osted cache
mode) clic+ Enaled) and then clic+ O.&
<0& To enable BranchCache for #MB traffic) double1clic+ BranchCache for networ/ files)
clic+ Enaled) select a latency value under Options) and then clic+ O.&
<"
Configuring the client firewall
To support *M5v21enabled @P2 connections) first install the 'ctive 7irectory Certificate #ervices
and eb #erver 3**#4 server roles to enable eb enrollment of a computer certificate&
*n 7istributed Cache Mode) BranchCache uses the ;TTP protocol for data transfer between
client computers and the #17iscovery protocol for cached content discovery& The client firewall
must be confi(ured to allow incomin( ;TTP and #17iscovery traffic on computers that use
7istributed Cache mode&
The ;TTP protocol is also used by clients confi(ured to use the ;osted Cache mode) but the
#17iscovery protocol is not& Clients operatin( in ;osted Cache mode must be confi(ured to
allow incomin( ;TTP traffic from the ;osted Cache server&
This section e,plains how to confi(ure the host firewall usin( :roup Policy to enable
BranchCache&
(o configure firewall rules for BranchCache using Group +olicy
<& Clic+ Start) point to Administrati"e (ools) and clic+ Group +olicy Management
Console&
2& %i(ht clic+ the :P8 you created for BranchCache and choose Edit&
=& Clic+ Computer Configuration) point to +olicies) Windows Settings) Security
Settings) Windows Firewall with Ad"anced Security) and then clic+ 'nound 0ules&
<$
>& Create a firewall rule for ;TTP 3reFuired in both 7istributed Cache and ;osted Cache
modes4:
a& Arom the Action menu) select !ew&
*f you are authorin( the :roup Policy ob/ect on a computer that is runnin( indows
#erver 200$ %2 or indows ": Clic+ +redefined) select BranchCache < Content
0etrie"al 9*ses %((+;) and then clic+ !e)t&
*f you are authorin( the :roup Policy ob/ect on a computer that does not include the
predefined BranchCache firewall rules: Clic+ +ort) and then clic+ O.& Clic+ (C+)
clic+ Specific local ports) type => in the te,t bo,) and then clic+ !e)t&
b& Clic+ Allow the connection) and then clic+ !e)t&
c& Choose the networ+s in which the rule will apply& *n most cases) it is appropriate to
select the #omain profile) and leave the +ri"ate and +ulic profiles unselected&
d& Type a name for the firewall rule) and then clic+ Finish&
?& Create a firewall rule for #17iscovery 3only reFuired in 7istributed Cache mode4:
a& Arom the Action menu) select !ew&
*f you are authorin( the :roup Policy ob/ect on a computer that is runnin( indows
#erver 200$ %2 or indows ": Clic+ +redefined) select BranchCache < +eer
#isco"ery 9*ses WS#;) and then clic+ !e)t&
*f you are authorin( the :roup Policy ob/ect on a computer that does not include the
predefined BranchCache firewall rules: Clic+ +ort) and then clic+ O.& Clic+ *#+)
clic+ Specific local ports) type ?@>& in the te,t bo,) and then clic+ !e)t&
b& Clic+ Allow the connection) and then clic+ !e)t&
c& Choose the networ+s in which the rule will apply& *n most cases) it is appropriate to
select the #omain profile) and leave the +ri"ate and +ulic profiles unselected&
d& Type a name for the firewall rule) and then clic+ Finish&
Client configuration using netsh
hen confi(urin( client computers) you can enable BranchCache and choose between
7istributed Cache mode and ;osted Cache mode with a sin(le netsh command&
!ote
:roup Policy overrides netsh confi(uration&
(o enale BranchCache in #istriuted Cache mode
<& 8pen an elevated Command Prompt window 3clic+ the Start button) type command in the
Start Search bo,) ri(ht1clic+ Command +rompt) and then clic+ 0un as administrator4&
2& %un the followin( command: netsh ranchcache set ser"ice mode2#'S(0'B*(E#
!ote
%unnin( this command automatically confi(ures the host firewall for 7istributed
<9
Cache mode&
(o enale BranchCache in %osted Cache mode
<& 8pen an elevated Command Prompt window 3clic+ the Start button) type command in the
Start Search bo,) ri(ht1clic+ Command +rompt) and then clic+ 0un as administrator4&
2& %un the followin( command: netsh ranchcache set ser"ice mode2%OS(E#C,'E!(
,OCA('O!2A%osted Cache nameB& here OHosted Cache nameP is the fully Fualified
domain name of the computer servin( as a ;osted Cache&
!ote
%unnin( this command automatically confi(ures the host firewall for ;osted
Cache mode&
#eploying BranchCache with 0emote Access
(echnologies
%osted Cache mode and hostCased 1+!
software
2ote that it is not appropriate to enable ;osted Cache on clients in a branch office if these clients
use a host1based @P2 that does not support split tunnelin(& *n this scenario) client computers
route traffic throu(h the main office @P2 servers when downloadin( from the local ;osted Cache&
BranchCache is compatible with @P2 software that supports split tunnelin(&
BranchCache and Microsoft #irectAccess
*f the computers in your branch office connect directly to the internet and access corporate
resources usin( 7irect'ccess) you must ta+e some e,tra steps to enable BranchCache&
To confi(ure clients in 7istributed Cache mode) you must confi(ure *PsecGfirewall rules that
allow the #17iscovery 3-7P multicast on port ="024 and ;TTP 3TCP on port $04 protocols
to e,ecute between roamin( peers&
To confi(ure clients in ;osted Cache mode) you must confi(ure *PsecGfirewall rules that allow
;TTP 3TCP on port $04 protocols to e,ecute between the roamin( peer and the remote
;osted Cache server&
BranchCache uses a custom encryption scheme based on '5#<2$ for transfers between peers
in 7istributed Cache mode and between a roamin( client and the ;osted Cache server& There is
minimal value in enablin( encryption with *Psec for BranchCache for these transfers&
20
!onCMicrosoft Firewall Settings for
BranchCache
*f your or(ani0ation uses a non1Microsoft firewall) confi(ure the firewall to allow the traffic for the
protocols and pro(rams that BranchCache uses& This section provides a reference of protocols
and the settin(s that you can use to confi(ure firewalls to allow BranchCache traffic&
Aor more information about the protocols referenced in this section) see the followin( topics on
the Microsoft eb site:
BM#1PCC%7C: Peer Content Cachin( and %etrieval 7iscovery Protocol #pecification
3http:GG(o&microsoft&comGfwlin+GH.in+*dI<?<=0?4
BM#1PCC%%C: Peer Content Cachin( and %etrieval: %etrieval Protocol #pecification
3http:GG(o&microsoft&comGfwlin+GH.in+*dI<?<=0D4
BM#1PC;CC: Peer Content Cachin( and %etrieval: ;osted Cache Protocol #pecification
3http:GG(o&microsoft&comGfwlin+GH.in+*dI<?<=0"4
!onCMicrosoft firewall settings for #istriuted
Cache clients
This section describes firewall settin(s for 7istributed Cache clients when 7istributed Cache
mode is used&
DMSC+CC0#E8 +eer Content Caching and 0etrie"al #isco"ery
+rotocol
7istributed Cache clients must support inbound and outbound M#1PCC%7 traffic) which is carried
in the eb #ervices 7ynamic 7iscovery 3#17iscovery4 protocol& Airewall settin(s must allow
multicast traffic) inbound and outbound traffic) and pro(ram traffic as follows:
'+"F multicast8 2=9&2??&2??&2?0
'+"G multicast8 AA02::C
'nound traffic8 .ocal port: ="02) %emote port: ephemeral
Outound traffic8 .ocal port: ephemeral) %emote port: ="02
+rogram8 QsystemrootQNsystem=2Nsvchost&e,e 3BranchCache #ervice BPeer7ist#vcC4
DMSC+CC00E8 +eer Content Caching and 0etrie"al8 0etrie"al
+rotocol
7istributed Cache clients must support inbound and outbound M#1PCC%% traffic) which is carried
in the ;TTP <&< B%AC 2D<DC protocol& Airewall settin(s must allow inbound) outbound) and
pro(ram traffic as follows:
'nound traffic8 .ocal port: $0) %emote port: ephemeral
Outound traffic8 .ocal port: ephemeral) %emote port: $0
2<
+rogram8 #J#T5M
!onCMicrosoft firewall settings for %osted Cache
clients
This section describes firewall settin(s for ;osted Cache clients when ;osted Cache mode is
used&
+rotocol
;osted Cache clients must support inbound and outbound M#1PCC%% traffic) which is carried in
the ;TTP <&< B%AC 2D<DC protocol& Airewall settin(s must allow inbound) outbound) and pro(ram
traffic as follows:
+rogram8 #J#T5M
DMSC+C%CE8 +eer Content Caching and 0etrie"al8 %osted Cache
+rotocol
;osted Cache clients must support inbound and outbound M#1PC;C traffic) which is carried in
the ;TTP <&< over T.# 3;TTPs4 B%AC 2$<$C protocol& Airewall settin(s must enable outbound
traffic as follows:
Outound traffic8 .ocal port: ephemeral) %emote port: >>=
+rogram8 #J#T5M
!onCMicrosoft firewall settings for the %osted
Cache ser"er
This section describes firewall settin(s for the ;osted Cache server when ;osted Cache mode is
used&
+rotocol
The ;osted Cache server must support inbound and outbound M#1PCC%% traffic) which is
carried in the ;TTP <&< B%AC 2D<DC protocol& Airewall settin(s must allow inbound) outbound) and
pro(ram traffic as follows:
+rogram8 #J#T5M
22
DMSC+C%CE8 +eer Content Caching and 0etrie"al8 %osted Cache
+rotocol
The ;osted Cache server must support inbound M#1PC;C traffic) which is carried in the ;TTP
<&< over T.# 3;TTPs4 B%AC 2$<$C protocol& Airewall settin(s must enable inbound and pro(ram
traffic as follows:
'nound traffic8 .ocal port: >>=) %emote port: ephemeral
+rogram8 #J#T5M
BranchCache protocols for content ser"ers 9such
as a We ser"er or file ser"er;
2o additional ports or protocols are reFuired on the content server& 'll BranchCache
communication with clients occurs in the conte,t of the optimi0ed protocol 3;TTP) #MB) and
B*T#4& 5,tensions to these protocols enable BranchCache on client computers that are runnin(
indows "&
Aor more information) see the followin( topics on the Microsoft eb site:
BM#1PCC%TPC: Peer Content Cachin( and %etrieval: ;yperte,t Transfer Protocol 3;TTP4
Client 5,tensions 3http:GG(o&microsoft&comGfwlin+GH.in+*dI<?<=094
BM#1#MB2C: #erver Messa(e Bloc+ 3#MB4 @ersion 2 Protocol #pecification
3http:GG(o&microsoft&comGfwlin+GH.in+*dI<?<=<04
%osted Cache Ser"er Setup
8nly a indows #erver 200$ %2 computer can be confi(ured as a ;osted Cache server& 'n
e,istin( application server in the branch office can be a ;osted Cache server if it is up(raded to
indows #erver 200$ %2&
The ;osted Cache is trusted by client computers to cache and distribute data that may be under
access control& Aor this reason) client computers use transport layer security 3T.#4 when
communicatin( with the ;osted Cache server& To support authentication) the ;osted Cache
server must be provisioned with a certificate that is trusted by clients and is suitable for server
authentication&
Ta+e the followin( steps to confi(ure a indows #erver 200$ %2 computer to be a ;osted Cache
server:
<& *nstall the BranchCache feature&
2& 5nable the BranchCache feature and enable ;osted Cache server mode&
=& 7eploy a certificate to the ;osted Cache that will be trusted by client computers& *t may be
necessary to distribute this certificate to client computers if it does not chain to a root
certificate that is already trusted& .in+ the certificate to BranchCache&
>& %esi0e the cache on the ;osted Cache server&
2=
?& Confi(ure client computers to use the ;osted Cache&
'nstall the BranchCache feature
(o install the BranchCache feature
<& Clic+ Start) point to Administrati"e (ools) and then clic+ Ser"er Manager&
2& %i(ht1clic+ Features) and then clic+ Add Features&
=& *n the 'dd Aeatures i0ard) select BranchCache) and then clic+ !e)t&
>& *n the Confirm *nstallation #elections dialo( bo,) clic+ 'nstall&
?& *n the *nstallation %esults dialo( bo,) confirm that BranchCache installed successfully)
and then clic+ Close&
Enale the BranchCache feature and enale
%osted Cache mode
Aor detailed instructions) see To enable BranchCache in ;osted Cache mode earlier in this
document&
2>
#eploy a certificate
The ;osted Cache server must be eFuipped with a certificate that is trusted by the client
computers in the branch offices& Aor information about indows #erver certificate deployment)
see #erver Certificate 7eployment 8verview&
'mport the certificate
The certificate must be added to the certificate store under the local computer account& *f the
certificate is added to the certificate store belon(in( to an administrator) or another user on the
system) you will be unable to lin+ the certificate to BranchCache) and clients will not be able to
connect to the ;osted Cache server&
(o import the certificate
<& 8pen the Microsoft Mana(ement Console 3clic+ Start) clic+ 0un) type mmc) and then
clic+ O.4&
2& Arom the File menu) select AddHremo"e snapCin&
=& #elect the Certificates snap1in) in the A"ailale snapCins list) and then clic+ Add&
>& #elect Computer Account from the list) and then clic+ !e)t&
?& #elect ,ocal Computer from the list) clic+ Finish) and then clic+ O. to complete the
snap1in addition process&
D& 5,pand the Certificates 9,ocal Computer; P +ersonal P Certificates tab&
"& Arom the Action menu) select All (as/s P 'mport to start the Certificate *mport i0ard&
Aollow the steps in the wi0ard to import your certificate accordin( to the file type& The
imported certificate appears in the ri(ht pane of the MMC&
$& 7ouble1clic+ the certificate to view its properties&
9& *n the #etails pane) select the (humprint field&
<0& Copy the Thumbprint value to the clipboard or write it down& Jou will use it later when
lin+in( the certificate to BranchCache&
2?
,in/ the certificate to BranchCache
'fter the import process has completed) you must lin+ your new certificate to the BranchCache
service on the ;osted Cache server&
(o lin/ the certificate to BranchCache
<& 8pen an elevated Command Prompt 3clic+ Start) clic+ All +rograms) clic+ Accessories)
2& Type the command: !E(S% %((+ A## SS,CE0( '++O0(2>->->->8FF?
CE0(%AS%2AthumprintB A++'#2IdG@?fJeeCa@$FCFJFdC=de&CFK&eFc$d=f=L where
OthumbprintP is thse value that you copied durin( the 'mport the certificate procedure
earlier in this document& Be sure to remove the spaces in the OthumbprintP entry&
2D
0esiMe the cache on the %osted Cache ser"er
By default) BranchCache allocates ?Q of the active partition on the ;osted Cache server& -se the
netsh set cachesiMe command to chan(e this value&
Modify the %osted Cache Ser"er +orts
The ;osted Cache accepts connections from BranchCache clients on two ports& TCP Port $0 is
used to accept connections from clients that are see+in( to download cached data usin( the
BranchCache retrieval protocol& Port >>= is used to accept connections from clients that are
see+in( to upload data to the ;osted Cache usin( the ;osted Cache protocol& Jou can chan(e
these ports on the ;osted Cache server by usin( the re(istry& *f you do so) you must update all
your BranchCache client computers to use the new ports&
Modifying the 0etrie"al +rotocol +ort 9(C+ +ort =>;
To update the retrieval port) you must modify the re(istry on the ;osted Cache server) then
modify the re(istry on each client that is confi(ured to use this ;osted Cache& The followin(
e,ample demonstrates the use of the reg command to update re(istry +eys& 'lternative
mechanisms can be used to update the re(istry&
(o update the %osted Cache ser"er
<& 8pen an elevated Command Prompt window 3clic+ Start) clic+ All +rograms) clic+
Accessories) ri(ht1clic+ Command +rompt) and then clic+ 0un as administrator4&
2& Type the command: netsh ranchcache set ser"ice hostedser"er&
=& Type the command: net stop peerdists"c&
>& Type the command: net start peerdists"c&
(o update the %osted Cache client
2& Type the command: 0EG A## N%.,MOSoftwareOMicrosoftOWindows
!(OCurrent1ersionO+eer#istO#ownloadManagerO+eersOConnectionN H"
Connect+ort Ht 0EG5#WO0# Hd AconnectportB Hf where OconnectportP is the new port
2"
on which the ;osted Cache server is acceptin( retrieval protocol connections&
=& Type the command: netsh ranchcache set ser"ice hostedclient
location2AhostedcacheB here OhostedcacheP is the fully Fualified domain name of
the ;osted Cache server&
>& Type the command: net stop peerdists"c&
Type the command: net start peerdists"c&
Modifying the %osted Cache +rotocol +ort 9(C+ +ort FF?;
To update the ;osted Cache protocol port) you must modify the re(istry on the ;osted Cache
server) then modify the re(istry on each client that is confi(ured to use this ;osted Cache& The
followin( e,ample demonstrates the use of the reg command to update re(istry +eys& 'lternative
mechanisms can be used to update the re(istry&
(o update the %osted Cache ser"er
2& Type the command: 0EG A## N%.,MOSoftwareOMicrosoftOWindows
!(OCurrent1ersionO+eer#istO%ostedCacheOConnectionN H"
,isten+ort Ht 0EG5#WO0# Hd AlistenportB Hf where OlistenportP is the new port on
which the ;osted Cache server should accept retrieval protocol connections&
=& Type the command: netsh ranchcache set ser"ice hostedser"er&
>& Type the command: net stop peerdists"c&
?& Type the command: net start peerdists"c&
(o update the %osted Cache client
2& Type the command: netsh ranchcache set ser"ice hostedclient
location2AhostedcacheB where OhostedcacheP is the fully Fualified domain name of
the ;osted Cache server&
=& Type the command: net stop peerdists"c&
>& Type the command: net start peerdists"c&
2$
1erification and Monitoring
1erifying client configuration
Type the netsh ranchcache show status all command in a Command Prompt window to
chec+ client settin(s after confi(uration by :roup Policy) netsh) or direct re(istry manipulation&
The command displays:
The BranchCache service status
The location of the local cache
The si0e of the local cache
The status of the firewall rules for the ;TTP and #17iscovery protocols that BranchCache
uses
!ote
The command searches the BranchCache firewall rule (roup& *f you did not use the
BranchCache firewall rule (roup) and you confi(ured firewall e,ceptions manually)
the command may falsely report misconfi(uration&
The followin( screenshot shows settin(s on a correctly confi(ured 7istributed Cache client:

29
!otes
BranchCache is enabled and the client is correctly set to function in 7istributed Cache
mode&
*f the computer is confi(ured in ;osted Cache mode) verify that the computer is correctly
provisioned with the fully Fualified domain name of the ;osted Cache server& Ma+e sure
that this AR72 does not include a protocol prefi, 3http:GG4&
The BranchCache service is runnin(&
The Content %etrieval -%. %eservation) Peer Content 7iscovery Airewall %ules) and
Content %etrieval Airewall %ules are properly enabled) allowin( this computer to serve
content to other peers on the same subnet&
The followin( screenshot demonstrates a correctly confi(ured ;osted Cache client:
1erifying the %osted Cache Ser"er configuration
Type the netsh ranchcache show status all command in a Command Prompt window on the
;osted Cache server to display the confi(uration& The command verifies firewall settin(s and
chec+s for a valid certificate on the ;osted Cache server&
=0
The followin( screenshot demonstrates a correctly confi(ured ;osted Cache server:

!otes
The server is correctly confi(ured to act in ;osted Cache Mode&
The BranchCache service is runnin(&
The computer is provisioned with a certificate that is bound to the BranchCache ;osted
Cache -%.&
The reFuired firewall rules are enabled&
#eugging certificate issues
The ;osted Cache server must be eFuipped with a trusted certificate for the ;osted Cache
deployment to function correctly&
To verify that a certificate is bound to the ;osted Cache -%. on the ;osted Cache server)
use the netsh http show urlacl command& @erify that a certificate is bound to the followin(
-%.: https:GGS:>>=GC?">'C=01?"9>1>'551B<BB1DD?<C?=<?029G&
The certificate must have an enhanced +ey usa(e that is suitable for server authentication&
This property can be inspected by usin( certificate mana(er&
=<
The sub/ect field of the certificate must match the fully Fualified domain name of the
computer&
The certificate must be associated with a root that is trusted by client computers& *f the
certificate is not trusted by client computers) an audit failure event on the ;osted Cache client
results when it attempts to adverti0e content to the ;osted Cache server& .oo+ for this event
in the indows 5vent viewer&
!ote
'udit failure events may be disabled by policy on some networ+s&
=2
1erifying content ser"er configuration
Type the netsh ranchcache show status all command in a Command Prompt window to
chec+ that the BranchCache feature is installed& *f the BranchCache feature is correctly installed)
your eb server will function correctly& *f the BranchCache feature is not installed) the command
will indicate this&
Aor a file server) follow the steps in the #ettin( the BranchCache support ta( on a file share
section previously in this document to ensure that file shares are correctly confi(ured for
BranchCache&
1erifying endCtoCend deployment with
performance counters
'fter confi(urin( multiple client computers and at least one eb server or file server) test the end1
to1end deployment and verify that clients successfully download content from the local cache)
each other) or the ;osted Cache server when appropriate&
==
Aout ser"erCside identifier generation
' BranchCache1enabled eb server (enerates identifiers for content dynamically on1demand&
hen content is reFuested for the first time) the server computes identifiers as the data is
transmitted to the client) and stores these identifiers for subseFuent client reFuests& The server
only transmits identifiers describin( content the second time content is accessed&
' client computer must receive identifiers from the server computer to cache content& To test a
BranchCache server deployment) you must access content three times: one to (enerate
identifiers) a second to download and cache content) and a third to test retrieval from the cache&
*t is best to test with three separate BranchCache1enabled client computers& *f you test with fewer
than three client computers) be sure to clear any application level caches between content
accesses 3for e,ample) the *nternet 5,plorer! cache4& *t is also (ood practice to clear the cache
on all client computers by usin( the netsh ranchcache flush command before testin(&
!ote
BranchCache will only e,ercise for content of (reater than D>MB in si0e& %estartin( the
BranchCache service on a eb server results in loss of all identifiers computed to that
point&
Calculating BranchCache efficiency with
performance counters
indows performance counters can be used to determine BranchCache efficiency and calculate
bandwidth savin(s&
(o determine the andwidth sa"ings across all client computers that are accessing a
We ser"er or B'(S application ser"er
<& 8n the eb server or B*T# application server) start indows Performance Monitor 3clic+
Start) clic+ 0un) type perfmon-msc) and then clic+ O.4&
2& Clic+ +erformance) clic+ Monitoring (ools) and then clic+ +erformance Monitor to
view the Performance Monitor (raph&
=& %i(ht1clic+ the (raph display) and choose Add Counters& 5,pand BranchCache .ernel
Mode in the top left pane& #elect the followin( counters: Client Cache Miss Bytes)
#erver Cache Miss Bytes) and %ypothetical Ser"er Bytes Without Caching and %ash
Bytes&
>& Clic+ Add) and then clic+ O. to add the BranchCache performance counters&
?& 2ote the value of the performance counters&
The total savin(s across all BranchCache1enabled client computers that are accessin( this server
can be calculated with the followin( formula:
Total Bytes #aved I ;ypothetical #erver Bytes ithout Cachin( 1 Client Cache Miss Bytes 1
#erver Cache Miss Bytes 1 ;ash Bytes
=>
!ote
This procedure is only valid for a eb server or B*T# application server) and it is not
possible for a file server&
(o determine the andwidth sa"ings across all protocols for a client machine in
#istriuted Cache mode or %osted Cache mode
<& 8n the client computer) start indows Performance Monitor 3clic+ Start) clic+ 0un) type
perfmon-msc) and then clic+ O.4&
=& %i(ht1clic+ the (raph display) and choose Add Counters& 5,pand BranchCache in the
top left pane& #elect the followin( counters: 0etrie"al8 Bytes from cache and 0etrie"al8
Bytes from ser"er&
The total savin(s across all BranchCache1enabled protocols for this computer is the value of
the 0etrie"al8 Bytes from cache counter& The BranchCache efficiency for all BranchCache1
enabled protocols can be calculated with the followin( formula:
#avin(s percenta(e I %etrieval: Bytes from cache G 3%etrieval: Bytes from cache S %etrieval:
Bytes from server4
(o determine the andwidth sa"ings across all protocols and all clients that are
configured to use a %osted Cache ser"er
<& 8n the ;osted Cache server) start indows Performance Monitor 3clic+ Start) clic+ 0un)
type perfmon-msc) and then clic+ O.4&
=& %i(ht1clic+ the (raph display) and choose Add Counters& 5,pand BranchCache in the
top left pane& #elect the followin( counters: 0etrie"al8 Bytes from cache and 0etrie"al8
Bytes from ser"er&
The total savin(s across all BranchCache1enabled protocols and all BranchCache1enabled clients
that are usin( this computer is the value of the %etrieval: Bytes from cache counter& The
BranchCache efficiency for all BranchCache1enabled protocols and clients can be calculated with
the followin( formula:
#avin(s percenta(e I %etrieval: Bytes from cache G 3%etrieval: Bytes from cache S %etrieval:
Bytes from server4
=?
(rouleshooting
BranchCache doesnt function
Client performance counters show no bytes comin( from the cache when accessin(
BranchCache enabled servers& Branch office clients can still download content from the servers&
Aollow the steps in @erifyin( end1to1end deployment with performance counters earlier in this
document& %un the performance monitor on both client computers&
Symptom8 BytesAdded(oCache does not increase on the first client when accessing the
BranchCacheCenaled ser"er-
The client computer may be retrievin( content from the *nternet 5,plorer cache& Be sure to
clear the *5 cache by selectin( *nternet 8ptions from the Tools menu) and clic+in( #elete&
5nsure that BranchCache is enabled on the first client usin( the netsh ranchcache show
status command&
*f attemptin( to access a file share) verify that the latency between the client and server is
hi(her than the minimum threshold&
5nsure that the BranchCache feature is installed on the server and is enabled for the protocol
under test&
Chec+ that the peerdists"c server has started on both the client and the server&
'n intermediate pro,y may alter the ;TTP reFuest comin( from the client& @erify that the
pro,y does not modify the 'CC5PT152C87*2: ;TTP header&
!ote
*#' 200D may alter this header& To confi(ure *#' 200D to function correctly with
BranchCache) disable the compression filter&
'n intermediate pro,y may down(rade the out(oin( reFuest from ;TTP <&< to ;TTP <&0&
*f the symptom is specific to file traffic) ensure that the file is not in the transparent cache&
Transparent cache is a secondary cache where the file is stored in addition to the
BranchCache& #torin( the file in the transparent cache enables subseFuent reads of the file
to be satisfied locally improvin( end1user response times and savin(s on '2 bandwidth& To
delete transparently cached data) search for Offline Files applet in Control Panel& Clic+ the
#is/ *sage tab) and then clic+ #elete (emporary Files& 2ote that this will not clear the
BranchCache cache&
Symptom8 BytesAdded(oCache does increase on the first client when accessing the
BranchCache enaled ser"er- BytesFromCache does not increase on the second client
when accessing the BranchCache enaled ser"er- #eployment is #istriuted Cache mode-
5nsure that BranchCache is enabled and that both clients are confi(ured to use the same
cachin( mode usin( the netsh ranchcache show status command&
5nsure that the correct firewall e,ceptions are set on both clients usin( the netsh
ranchcache show status command&
=D
5nsure that both clients are connected to the same subnet usin( the ipconfig command&
Ma+e sure the client cache is not full usin( netsh ranchcache show status A,,&
Symptom8 BytesAdded(oCache does increase on the first client when accessing the
BranchCache enaled ser"er- BytesFromCache does not increase on the second client
when accessing the BranchCache enaled ser"er- #eployment is %osted Cache mode-
5nsure that BranchCache is enabled and that both clients are confi(ured to use the same
cachin( mode usin( the netsh ranchcache show status command&
@erify basic connectivity from both client computers to the ;osted Cache usin( the ping
command&
5nsure that the correct firewall e,ceptions are set on both clients usin( the netsh
ranchcache show status command&
5nsure that the correct firewall e,ceptions are set on the ;osted Cache server usin( the
netsh ranchcache show status command&
5nsure that the certificate is properly installed and bound to port >>= on the ;osted Cache
computer&
Symptom8 !etsh shows BranchCache firewall rules ha"e not een set7 e"en though they
ha"e een configured using Group +olicy-
!etsh chec+s the predefined BranchCache firewall rule (roup& *f you have not enabled the
default e,ceptions defined for BranchCache on indows ") !etsh will not report your
confi(uration correctly& This is li+ely to happen if you defined firewall rules for clients usin( :roup
Policy and you defined the :roup Policy ob/ect on a computer runnin( an operatin( system older
than indows " or indows #erver 200$ %2 3which would not have the BranchCache firewall
rule (roup4& 2ote that this does not mean BranchCache will not function&
BranchCache and client performance
Symptom8 A client computer is running slowly- 's BranchCache at faultP
Many computers drawin( lar(e amounts of content from one client in a short time period may
impact des+top performance&
-se performance monitor to chec+ for hi(h service rates to peers& 5,amine
BytesSer"ed(o+eers relative to BytesFromCache and BytesFromSer"er&
The BranchCache service runs isolated in its own service host& 5,amine the CP- and
memory consumption of the service host process housin( the branch cachin( service&
#ustained hi(h rates of service to peers may be evidence of a confi(uration problem in the
branch office& Chec+ to ma+e sure that the other clients in the branch office are capable of
service data&
Clear the cache on the affected client usin( the netsh ranchcache flush command or
reduce the cache si0e on the affected client&
="
Application failures
Symptom8 A page fails to load or a share cannot e accessed-
hen BranchCache is unable to retrieve data from a peer or from the ;osted Cache) the upper
layer protocol will return to the server for content& *f a failure occurs in the Branch Cachin(
component) the upper layer protocol should seamlessly download content from the server& 2o
BranchCache misconfi(uration or failure should prevent the display of a webpa(e or connection
to a share& *f a failure does occur) use the !etwor/ #iagnostic Framewor/ #iagnose button
provided by indows 5,plorer or *nternet 5,plorer&
Symptom8 (he client computer is unale to access the file share e"en when connected to
the ser"er-
*f the client computer is unable to access a file share on the server due to the error Offline
9networ/ disconnected;) reboot the client computer and access the share a(ain&
*f the client computer is unable to access a file share on the server due to the error Offline
9slow connection;) delete the temporarily cached data) reboot the computer and access the
share& To delete temporarily cached data 3the same as the transparent cache described
above4) search for Offline Files applet in Control Panel& Clic+ the #is/ *sage tab) and then
clic+ #elete (emporary Files&
(ools 'nde)
Group +olicy
BranchCache behavior can be confi(ured on client and server computers usin( :roup Policy&
Group +olicy administrati"e template
indows " includes an administrative template that can be used to edit the BranchCache :roup
Policy ob/ect& The template can be found under 'dministrative Templates P 2etwor+ P
BranchCache usin( the indows :roup Policy editor 3(pedit&msc4& This section describes the
fields available in the administrative template&
=$
(urn on BranchCache setting
BranchCache enables clients to securely retrieve content from within the branch office instead of
havin( to retrieve it from the server hostin( the content& 7ependin( on the deployment mode) the
content can be retrieved from other clients in the branch office or from a ;osted Cache located on
a server in the branch& ' client can only retrieve content from within the branch if it is authori0ed
by the server to do so& The use of BranchCache reduces costs on the wide area networ+ 3'24
lin+ that connects your branch offices to the data center or headFuarters and increases download
speeds for content that has already been downloaded into the branch office&
This policy settin( specifies whether BranchCache is enabled& Jou should apply this policy settin(
in branch offices where bandwidth to headFuarters is low and latency is hi(h& There is no need to
deploy this policy settin( in headFuarters with fast connections to the servers hostin( the content&
*f you enable this policy settin() BranchCache is turned 8n&
*f you disable or do not confi(ure this policy settin() BranchCache is turned 8ff&
(urn on BranchCache < #istriuted Cache Mode setting
BranchCache enables clients to securely retrieve content from within the branch office instead of
havin( to retrieve it from the server hostin( the content& ith 7istributed Cache) the content is
retrieved from other clients in the branch office& ' client can only retrieve content from other
clients if it is authori0ed by the server to do so& This reduces costs on the wide area networ+
3'24 lin+ that connects your branch offices to the data center or headFuarters& 't the same
time) it increases download speeds for content that has already been downloaded into the branch
office&
This policy settin( specifies whether BranchCache 7istributed Cache mode is enabled& Jou
should apply this policy settin( in branch offices where bandwidth to headFuarters is low and
latency is hi(h& There is no need to deploy this policy settin( in headFuarters with fast
connections to the servers hostin( the content&
*f you enable this policy settin() BranchCache 7istributed Cache mode is turned 8n&
=9
*f you disable or do not confi(ure this policy settin() BranchCache 7istributed Cache mode is
turned 8ff&
(urn on BranchCache < %osted Cache mode setting
BranchCache operates by havin( client computers cache retrieved content& This cached content
can be pushed to a ;osted Cache server on the branch networ+ so that clients can retrieve
content from this server instead of havin( to retrieve it from other clients in the branch& The
content is made available by the ;osted Cache to other reFuestin( client computers if they are
authori0ed by the server&
This policy settin( is used to specify the location of the ;osted Cache server& This settin( must be
specified if a ;osted Cache is deployed in the branch& The location M-#T match the name of the
;osted Cache specified in the certificate 3recommended to be the Aully Rualified 7omain 2ame4
for the ;osted Cache& Clients use #ecure #oc+ets .ayer 3##.4 to communicate with the ;osted
Cache& The certificate root for the ;osted Cache M-#T be in the client9s trusted root store&
*f you enable this policy settin() you must specify a valid location of the ;osted Cache&
*f you disable or do not confi(ure this policy settin() the ;osted Cache is not used in the
branch&
Set percentage of dis/ space used for client
computer cache
BranchCache operates by havin( client computers dedicate dis+ space to cachin( retrieved
content& This content is made available to other reFuestin( client computers if they are authori0ed
by the server&
This policy settin( is used to specify the percenta(e of total dis+ space to dedicate to
BranchCache&
*f you enable this policy settin() you must select the percenta(e of total dis+ space to allocate
for the cache&
*f you disable or do not confi(ure this policy settin() the cache is set to ? percent of the total
dis+ space on the client computer&
Configure BranchCache for networ/ files
This policy settin( is used to enable BranchCache for networ+ files or cachin( of #MB traffic&
*f you enable this policy settin() you must select the minimum latency between client and
server) below which BranchCache BranchCache will not be used for #MB traffic&
*f you disable or do not confi(ure this policy settin() BranchCache will not optimi0e #MB
traffic&
>0
#isaling B'(S use of BranchCache
By default) the B*T# protocol will use BranchCache on a client that is BranchCache enabled& This
can be disabled usin( the B*T# administrative template available under 'dministrative Templates
P 2etwor+ P Bac+(round *ntelli(ent Transfer #ervice 3B*T#4& The BranchCache settin( is named
K7o not allow the B*T# client to use BranchCache&L
This settin( affects whether the B*T# client is allowed to use BranchCache& *f the BranchCache
component is installed and enabled on a computer) then by default B*T# /obs on that computer
can use BranchCache&
*f you enable this settin() then the B*T# client does not use BranchCache&
*f you disable or do not confi(ure this settin() then the B*T# client uses BranchCache&
!ote
This settin( does not affect the use of BranchCache by applications other than B*T#& This
settin( has no effect if the computerTs administrative settin(s for BranchCache disable its
use entirely&
!etsh Commands
dump
Synta): dump
0emar/s: Creates a script that contains the current confi(uration& *f saved to a file) this script can
be used to restore altered confi(uration settin(s& The dump function is not implemented for the
BranchCache conte,t) and it cannot be used to (enerate a script to restore BranchCache
confi(uration settin(s&
><
E)ample: dump
e)port/ey
Synta): e,port+ey BoutputfileICOAile PathP BpassphraseCIOPass PhraseP
+arameter #escription
outputfile The directory path and name of the file to which
the +ey should be e,ported
passphrase ' passphrase reFuired in order to import the
+ey
0emar/s: 5,ports the +ey that BranchCache uses to encrypt content& The +ey can then be
imported on another computer by usin( the import+ey command&
E)amples:
e,port+ey QTMPQNsecret&+ey UMey file passwordU
e,port+ey outputfileIC:NMey7irectoryNsecret&+ey UMey file passwordU
flush
Synta): flush
0emar/s: Alushes the contents of the local cache&
import/ey
Synta): import+ey BinputfileICOAile PathP BpassphraseCIOPass PhraseP
inputfile The location of the file from which the +ey
should be imported
passphrase The passphrase used when e,portin( the +ey
usin( the e,port+ey command
0emar/s: *mports a new +ey for the BranchCache service to use to protect content information&
The +ey must have been previously e,ported by means of the e,port+ey command& *f the service
is currently runnin() this command will stop and restart it in order to be(in usin( the new +ey&
E)amples:
import+ey QTMPQNsecret&+ey UMey file passwordU
import+ey inputfileIC:NMey7irectoryNsecret&+ey UMey file passwordU
>2
reset
Synta): reset
0emar/s: %esets the BranchCache service& Alushes the local cache& 5very confi(uration
parameter of BranchCache will be reset to its default value&
set mode
Synta): set mode B modeI C V online W offline X
mode 8ne of the followin( values:
online: Commit chan(es immediately
offline: 7elay commit until e,plicitly reFuested
0emar/s: #ets the current mode to online or offline&
set cachesiMe
Synta): set cachesi0e Bsi0eICV75A'-.TWOnumberPX BBpercentICVT%-5WA'.#5XC
si0e The si0e of the cache& #et to 75A'-.T to
restore the default confi(uration&
percent 7etermines if the si0e ta( is treated as a
percenta(e of the si0e of the hard dis+ or as an
e,act number of bytes& *(nored if the si0e ta( is
set to 75A'-.T&
T%-5: si0e is a percenta(e of the si0e of the
hard dis+
A'.#5: si0e is an e,act number of bytes
37efault4
0emar/s: #ets the si0e of the BranchCache serviceTs local cache& The si0e can be entered as
either an e,act number of bytes) or as a percenta(e of the si0e of the dis+ partition& 2ote that this
refers to the si0e of the dis+ on which the cache is located) not the total si0e of all dis+s present
on this computer&
E)amples:
set cachesi0e 75A'-.T
set cachesi0e 209"<?20
>=
set cachesi0e si0eI20 percentIT%-5
set /ey
Synta): set +ey BBpassphraseICOPass PhrasePC
passphrase ' passphrase to use to (enerate the +ey& *f a
passphrase is not provided) a random +ey will
be (enerated& Two +eys (enerated usin( the
same passphrase will always be identical&
-sin( a passphrase is a convenient way to
duplicate the same +ey on another computer&
38ptional4
0emar/s: :enerates a new +ey for the BranchCache service to use to protect content
information& *f the service is currently runnin() this command will stop and restart it in order to
be(in usin( the new +ey&
E)amples:
set +ey
set +ey passphraseIU* want my content to be secureU
set localcache
Synta): set localcache BdirectoryICV75A'-.TWOAile PathPX
directory The fully Fualified path to the directory in which
the local cache should be stored& #et to
75A'-.T to restore the default cache location&
0emar/s: #ets the location of the BranchCache serviceTs local cache& 2ote that the service will
be stopped and restarted if necessary to complete the chan(e& 5,istin( cache files will be moved
to the new location& That location must reside on the local computer& *f the new location is on a
different volume) the new volume must have enou(h free space to accommodate the entire
current cache file& Chec+ the si0e of the current cache file before movin( it to a new volume&
The cache file can be moved to a temporary device& *f that device is removed) BranchCache will
no lon(er cache and serve the data&
E)amples:
set localcache 75A'-.T
set localcache directoryIC:NBranchcacheN.ocalcache
>>
set ser"ice
Synta): set service
mode #et the status of the BranchCache #ervice
7*#'B.57 1 7isable the service
.8C'. 1 -ses .ocal Cachin( 8nly
7*#T%*B-T57 1 7istributed Cache 5nabled
;8#T57#5%@5% 1 #et as a ;osted Cache
#erver
;8#T57C.*52T1 #et as a ;osted Cache
Client
location #et the location of the ;osted Cache #erver&
This ta( is only necessary if the mode ta( is set
to ;8#T57C.*52T and is invalid otherwise&
clientauthentication #et the mechanism used by a ;osted Cache
#erver to authenticate clients& This ta( is only
used if the mode ta( is set to ;8#T57#5%@5%
and is invalid otherwise&
0emar/s: #ets the status of the BranchCache service& This command will also ensure that the
necessary firewall confi(uration for the chosen modeis in place& *t is stron(ly recommended that
you provide a fully Fualified domain name as the location of the ;osted Cache when settin(
;osted Cache Client mode&
E)amples:
set service 7*#'B.57
set service modeI7*#T%*B-T57
set service modeI;8#T57C.*52T locationI#5%@5%<2=
set service modeI;8#T57#5%@5% clientauthenticationI78M'*2
show hostedcache
Synta): show hostedcache
0emar/s: 7isplays the location of the ;osted Cache
show localcache
Synta): show localcache
0emar/s: 7isplays the status of the local cache&
>?
show status
Synta): show status BBdetailICVB'#*CW'..XC
detail The level of detail to display 38ptional4
B'#*C: 7isplay only basic information 37efault4
'..: 7isplay all available information
0emar/s: 7isplays the current status of the BranchCache #ervice&
E)amples:
show status
show status '..
show status detailI'..
+erformance Counters
The BranchCache performance counters e,ist under the headin( BranchCache& They are useful
debu((in( tools and can be used to monitor BranchCache effectiveness and health& #ome
performance counters are overloaded and report different measurements on BranchCache
clients) content servers and ;osted Cache servers&
Attempted #isco"eries
Client %eports the total number of content discovery
attempts sent to peers or the ;osted Cache&
#erver 2G'
;osted cache %eports the total number of content discovery
attempts received from clients&
A"erage Branch 0ate
Client %eports the avera(e download speed from
peers observed by the current node&
#erver 2G'
;osted cache %eports the avera(e upload speed to clients&
>D
Bytes from Cache
Client %eports the total number of bytes retrieved from
the local cache) peers on the same subnet or
from a ;osted Cache&
#erver 2G'
;osted cache %eports the total number bytes served to client
computers&
Bytes from Ser"er
Client %eports the total number of bytes retrieved from
the server 3content that could not be found in a
cache4&
#erver 2G'
;osted cache %eports the total number bytes downloaded
from clients&
Bytes Ser"ed
Client %eports the total number of bytes served by this
peer to other peers or to the ;osted Cache
server&
#erver 2G'
;osted cache %eports the total number bytes served to
clients&
Cache Complete File Segments
Client Count of complete) content validated) file
se(ments&
#erver 2G'
>"
;osted cache Count of complete) content validated) file
se(ments&
Cache %it 0atio
Client Percenta(e of files retrieved successfully from
the 7istributed Cache relative ori(inal content
si0e&
#erver 2G'
;osted cache Percenta(e of files retrieved successfully from
si0e&
Cache +artial File Segments
Client Count of incomplete file se(ments that need
additional data andGor validation&
#erver 2G'
;osted cache Count of incomplete file se(ments that need
additional data andGor validation&
#isco"ery (ime
Client ei(hted avera(e of time between when a peer
discovery Fuery was sent and when the first
response arrived&
#erver 2G'
;osted cache 2G'
%osted Cache < Client file segment offers
accepted
Client 2G'
>$
#erver 2G'
;osted cache Count of file se(ment offers made by peers and
accepted by the ;osted Cache& ' file se(ment
offer is made by a client computer to the ;osted
Cache server after a download from a
BranchCache enabled content server&
%osted Cache < Client file segment offers made
Client 2G'
#erver 2G'
;osted cache Count of file se(ment offers made by peers to
the ;osted Cache& ' file se(ment offer is made
by a client computer to the ;osted Cache
server after a download from a BranchCache
enabled content server&
0eQuestsFilledBySer"er
Client %eports the total numbers of reFuests for that
were retrieved from the ori(inal BranchCache
enabled content source&
#erver 2G'
;osted cache 2G'
+rotocol Specific Counters
The followin( counters are available for each of the followin( BranchCache providers: B*T#)
#MB) *2*25T) *2;TTP) and 'll 8thers
Bytes From Cache
Client %eports the total number of bytes obtained from
the local cache) from peers or from the ;osted
Cache server&
>9
#erver 2G'
;osted cache 2G'
Bytes From Ser"er
Client %eports the total number of bytes obtained from
the ori(inal content server&
#erver 2G'
;osted cache 2G'
Cache %it 0atio
Client Percenta(e of bytes retrieved successfully from
si0e&
#erver 2G'
;osted cache 2G'
We ser"er performance counters
#ome eb #erver specific BranchCache performance counters e,ist under the headin(
BranchCache Mernel Mode&
Client Cache Miss Bytes
Client 2G'
#erver Total number of bytes served because content
was not found within the branch&
;osted cache 2G'
%ash Bytes
Client 2G'
#erver Total number of bytes of identifiers transferred&
?0
;osted cache 2G'
%ypothetical Ser"er Bytes Without Caching
Client 2G'
#erver Total number of bytes that would have been
transferred if the BranchCache +ernel mode
component was not present&
;osted cache 2G'
+rocessed %((+ 0eQuests
Client 2G'
#erver Total number of BranchCache aware ;TTP
reFuests received by the server&
;osted cache 2G'
Ser"er Cache Miss Bytes
Client 2G'
#erver Total number of bytes served because hashes
for the content were not currently on the server&
;osted cache 2G'
(otal %((+ 0eQuests
Client 2G'
#erver Total number of ;TTP reFuests received by the
server&
;osted cache 2G'
?<
Changing BranchCache +orts
This section e,plains how to modify the port on the ;osted Cache server that is used by clients&
(o change the port
2& Type !etS% BranchCache set ser"ice mode2local) and then press 52T5%&
=& Close the elevated Command Prompt window&
%osted Cache ser"er
The ;osted Cache server downloads and caches content from clients by usin( TCP over port $0
by default:
REG ADD "HKLM\Software\Microsoft\Windows
NT\CurrentVersion\eerDist\Down!oadMana"er\eers\Connection" #$
Connectort #t REG%DW&RD #d 'NEW&RT( #f
nets) *r set ser )ostedc!ient !ocation+,,,,
%osted Cache clients
;osted Cache clients download content from ;osted Cache server by usin( TCP over port $0 by
default:
REG ADD "HKLM\Software\Microsoft\Windows
NT\CurrentVersion\eerDist\Down!oadMana"er\eers\Connection" #$ Listenort #t REG%DW&RD #d
'NEW&RT( #f
nets) *r set ser )ostedser$er
restart -eerdists$c
E"ent ,ogs
BranchCache has an operational lo( and a security lo(& The operational lo( is the main 5vent
.o( for the BranchCache service& *t is separate from the indows 'pplication .o(& The
operational lo( appears in the 5vent @iewer -* at K'pplications and #ervices
.o(sNMicrosoftNindowsNPeer7istN8perational&L The followin( table shows the main events for
deployment and dia(nostic purposes&
E"ent !ame E"ent #escription
#ervice#tartup5vent The BranchCache service started successfully&
?2
#ervice#hutdown5vent The BranchCache service stopped successfully&
#ervice#tartupAailed5vent The BranchCache service failed to start&
Confi(Chan(e5vent ' confi(uration chan(e was detected 3re(istry
+eys4&
;C7etectedBoth#erver'ndClient#ettin(s5vent This computer is confi(ured as a ;osted Cache
computer and it is also confi(ured to use
;osted Cache& 8nly one of these options can
be used on a (iven computer& Please fi, the
confi(uration by usin( the netsh commands&
7iscoveryBloc+edByAirewall5vent The port used for discoverin( the availability of
cached content on this client is bloc+ed by the
firewall& 's a result) other clients on the networ+
cannot discover this client& %un the command
netsh ranchcache set ser"ice distriuted
from an elevated command prompt& This opens
the needed firewall port 3="02 inbound -7P4
for enablin( discovery& 'lternatively) you can
manually open this port in the firewall& %efer to
the deployment (uide for more details&
7ownloadBloc+edByAirewall5vent The port used for servin( content to reFuestin(
clients is bloc+ed by the firewall& 's a result)
other clients on the networ+ 3includin( the
;osted Cache4 will not be able to retrieve
content from this client& Please run the
command netsh ranchcache set ser"ice
from an elevated command prompt to set the
service mode& This opens the needed firewall
port 3$0 inbound TCP4& 'lternatively) you can
manually open this port in the firewall& %efer to
the deployment (uide for more details&
;CProtocolBloc+edByAirewall5vent The port used by the ;osted Cache for
acceptin( incomin( client offers for content is
bloc+ed by the firewall& 's a result) clients will
not be able to add content to the ;osted
Cache& %un the command netsh ranchcache
set ser"ice hostedser"er from an elevated
command prompt& This opens the needed
firewall port 3by default port >>= inbound TCP4&
'lternatively) you can manually open this port in
?=
the firewall& %efer to the deployment (uide for
more details&
-rl%eservation%eFuired5vent The ;TTP namespace used for servin( content
to reFuestin( clients is not reserved& %un the
command netsh http add urlacl url2https8HH
R8=>H$$GBJ>EBCECE&CF$acC=F&KC
KFKEKG??G$B@ sddl2#89ASSG:SSS!S; from an
elevated command prompt to reserve the
namespace& %efer to the deployment (uide for
more details&
%epublishAailedTo'llocate5vent BranchCache could not free enou(h space in
the local cache to accommodate the content
bein( added& %un the command netsh
ranchcache set cachesiMe from an elevated
command prompt to increase the cache si0e&
%efer to the deployment (uide for more details&
PublishAailedTo*nitiali0e5vent BranchCache could not publish the content&
Possible reasons are:
The publication directory location is not on
an 2TA# partition&
The path is too lon( 3typically) (reater than
<90 characters4&
The path does not e,ist&
BranchCache service does not have the
permissions to write to the directory
location&
%un the command netsh ranchcache set
pulicationcache from an elevated command
prompt& %efer to the deployment (uide for more
details&
PublishAailed5vent BranchCache could not publish the content with
content1id: Q2 because the publication cache
si0e was e,ceeded or the hard dis+ drive did
not have enou(h space& %un the command
netsh ranchcache set pulicationcachesiMe
from an elevated command prompt to increase
the cache si0e& %efer to the deployment (uide
for more details&
7ownloadAromPeerAailed5vent ' reFuest messa(e sent to another
?>
BranchCache client failed with error QD&
7ownloadArom;CAailed5vent ' reFuest messa(e sent to the BranchCache
;osted Cache failed with error QD&
PeerRuarantined5vent 'nother BranchCache client has been
Fuarantined by this client for appro,imately Q2
seconds& Possible reasons are that the client
served invalid data or that it repeatedly failed to
serve data in a timely fashion&
*nvalidMessa(e5vent 'n invalid reFuest messa(e has been received
from another BranchCache client& The reFuest
has been dropped&
Peer%eFuest7enied5vent ' content retrieval reFuest from another
BranchCache client has been denied with error
Q2&
-nableToConnectTo;C5vent BranchCache tried to offer content to the
;osted Cache on Q<) but there was an error
connectin( to it 3error code: Q24& Possible
reasons are the ;osted Cache location is
incorrect) the port number used is not
confi(ured correctly on the client) or the port to
connect to is not enabled in the firewall on the
;osted Cache&
%un the command netsh ranchcache set
ser"ice hostedclient on the client from an
elevated command prompt& 'lso run the
command netsh ranchcache set ser"ice
hostedser"er on the ;osted Cache from an
elevated command prompt& %efer to the
deployment (uide for more details&
;C8fferTimed8ut5vent BranchCache tried to offer content to the
;osted Cache) but the reFuest to the ;osted
Cache timed out& Possible reasons are:
The ;osted Cache may be under heavy
load&
The ;osted Cache is not reachable due to
the port not bein( open in the firewall on
the ;osted Cache& %un the command
netsh ranchcache set ser"ice
hostedser"er on the ;osted Cache from
??
an elevated command prompt&
The ;osted Cache enabled client
authentication and the client was not /oined
to the domain& Yoin your client to the
domain& 'lternatively) run the command
hostedser"er clientauthentication2none
from an elevated command prompt&
The ;osted Cache location confi(ured on
the client is invalid& %un the command
hostedclient on the client from an elevated
command prompt&
%efer to the deployment (uide for more details&
'ccumulated5vent Q2 instance3s4 of event id Q< occurred&
Airewall%ules*nconsistency5vent The firewall rules for the BranchCache service
are confi(ured incorrectly& %un the command
netsh ranchcache set ser"ice with the
appropriate service mode to set the firewall
confi(uration correctly& %efer to the deployment
(uide for more details&
Client7ll#ervice7isabled5vent The BranchCache service could not be started
because it is disabled in the #ervice Control
Mana(er& *n the #ervice Control Mana(er on a
client computer) chan(e the service startup type
to Manual& *n the #ervice Control Mana(er on a
server) chan(e the service startup type to
Automatic&
.oadPersistedCacheAailed5vent BranchCache was unable to load the cache
3error code: Q<) sub code: Q24& Possible
reasons are that the cache file was corrupted or
it had a different version&
.oadPersistedCache#ucceeded5vent The BranchCache service started and loaded a
cache file from a dis+ that was saved on the
hard dis+ drive&
#avePersistedCache#ucceeded5vent BranchCache saved a cache file to the hard
dis+ drive&
#avePersistedCacheAailed5vent The BranchCache service stopped and was
?D
unable to save the cache file to the hard dis+
drive&
#ervice#hutdown#tart5vent The BranchCache service shutdown is
commencin(&
##.Cert2otConfi(ured5vent 'n ##. certificate is not bound to the
BranchCache port on the ;osted Cache server&
's a result) clients cannot add content to the
;osted Cache& %un the command netsh http
add sslcert from an elevated command prompt
to bind a certificate&
%epublishAailedTo*nitiali0e5vent BranchCache cannot initiali0e the local cache
at the location BPathC& Possible reasons are that
the local cache directory location is not on an
2TA# partition) the path is too lon( 3typically)
(reater than <90 characters4 or does not e,ist)
or the BranchCache service does not have the
permissions to write to the directory
location& %un the command netsh
ranchcache set localcache from an elevated
command prompt&
*pgrade !otes
This section identifies +nown issues surfaced by indows up(rades&
*pgrading a %osted Cache ser"er from
Windows @ Beta to a later Windows @ "ersion
' cache constructed on a ;osted Cache server runnin( the indows " Beta build will be lost in
an up(rade to a later version of the operatin( system& This is the result of a chan(e to the cache
file format&
%osted Cache migration
The data cache accumulated by a ;osted Cache server can be bac+ed up) restored) and
mi(rated& The ;osted Cache data files can be found under the subheadin( ,ocal Cache
,ocation in the output of the netsh ranchcache show status A,, command&
?"
*f the cache location is chan(ed prior to an operatin( system up(rade) the cache data is
preserved& This techniFue can be used instead of duplicatin( the cache files& Chan(e the cache
location by usin( the netsh ranchcache set localcache directory2AdirectoryB command&
Choose a directory that will not be affected by the up(rade&
BranchCache uses the file modification time to ensure the correctness of the cache data files&
The file modification time of all BranchCache cache data files must not be chan(ed durin( ;osted
Cache data file bac+up) restore) or mi(ration& *f the file modification time is chan(ed durin( one of
these activities) the ;osted Cache data file will become invalid&
BranchCache and System 0estore
BranchCache settin(s are saved by #ystem %estore) but the BranchCache data cache is not&
'fter usin( #ystem %estore) the BranchCache settin(s ta+e the values from the last restore point)
but the contents of the cache will not chan(e&
*f you chan(e the location of the cache file on a BranchCache client or on a ;osted Cache server
after settin( a #ystem %estore point) you must manually move the BranchCache cache file to the
location set by #ystem %estore&
!ote
*f you chan(e the cache location after restorin( the system) the cache file may be
overwritten&
?$

BranchCache Early Adopter's Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BranchCache Early Adopter's Guide

Uploaded by

Copyright:

Available Formats

BranchCache Early Adopters Guide

Microsoft Windows Family of Operating Systems

You might also like

BranchCache Early Adopter&#39;s Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BranchCache Early Adopter&#39;s Guide

Uploaded by

Copyright:

Available Formats

BranchCache Early Adopters Guide

Microsoft Windows Family of Operating Systems

You might also like

BranchCache Early Adopter's Guide

BranchCache Early Adopter's Guide