Guide:  

Quick and Easy BranchCache Setup.

Overview:  

 This article provides instructions on how to implement BranchCache.

Topology:  

• Three office locations:  
• Primary office in Atlanta (ATL).   
• Branch offices in Chicago (CHI) and Washington D.C (DCA).
• CHI and ATL host local file servers (i.e., hosted cache mode).
• DCA is the only office without a dedicated file server (i.e., distributed cache mode).
• All clients use Windows Enterprise.
    

Implement BranchCache:

• Install the BranchCache Role and Feature.
• BranchCace SSL Certificates.  
• BranchCache Group policy.

Step 1.  Add Roles and Features.

Run the Add Roles and Features Wizard on each file server.  Install the (a) BranchCache for Network Files Role; and (b)the BranchCache Feature.
Install-WindowsFeature BranchCache -IncludeManagementTools Enable-BCHostedServer -RegisterSCP

Step 2.  Adjust Caching.

Adjust the Cache Location:

netsh branchcache set publicationcache directory=D:\BranchCache\ netsh branchcache set localcache directory=D:\LocalCache\ Netsh branchcache set publicationcachesize size=5 percent=TRUE Netsh branchcache set localcachesize size=5 percent=TRUE

1. Add a server certificate in the personal certificate directory for each  BranchCache hosted cache server (e.g., ATL and CHI).
2. Bind the SSL certificate hash (i.e., thumbprint) to the hosted cache server.  Use the following command: NETSH HTTP ADD SSLCERT IPPORT=0.0.0.0:443 CERTHASH=xxxxxxxxxxx APPID={d673f5ee-a714-454d-8de2-492e4c1bd8f8}

    N.B.,  CERTHASH is the certificate's thumbprint.  Further certificate information found here.

Step 4.  Group Policy

Policies for the File Servers:  

BranchCache Firewall Policies:

Policy	Path	Action
BranchCache Content Retrieval (HTTP-In)	Computer Configuration/   Policies/    Windows  Settings/     Security Settings/      Windows Firewall with       Advanced Security/        Inbound Rules	a. Right-click Inbound Rules.  b. Left-click New Rule.     c. Add predefined BranchCache rules.
BranchCache Hosted Cache Server (HTTP-In)
BranchCache Peer Discovery (WSD-In)
BranchCache Content Retrieval (HTTP-Out)	Computer Configuration/   Policies/    Windows  Settings/     Security Settings/      Windows Firewall with       Advanced Security/        Outbound Rules	a. Right-click Inbound Rules.    b. Left-click New Rule. c. Add predefined BranchCache rules.
BranchCache Hosted Cache Clietnt (HTTP-Out)
BranchCache Hosted Cache Server (HTTP-Out)
BranchCache Peer Discovery (WSD-Out)

Optional:  BranchCache for WSUS and IIS Servers

Evaluate

That's It!

References:

Problem:  Hosted Cache server's SSL certificate expired.  New certificate has a different thumbprint.  Error when linking the new certificate thumbprint to BranchCache server.

Error:  SSL Certificate add failed, Error: 183.  Cannot create a file when that file already exists.

Solution:  You cannot associate a new certificate to the BranchCache server until the old certificate information is deleted from HTTP.sys.  Use the following commands to correct the problem:

C:\Users\Administrator> netsh http delete sslcert ipport=0.0.0.0:443
SSL Certificate successfully deleted 

Link the new certificate after the old certificate is deleted from HTTP.sys:

netsh http add sslcert ipport=0.0.0.0:443 certhash=xxxxxxxxxxxxxxxx appid={d673f5ee-a714-454d-8de2-492e4c1bd8f8}

This article explains how to preload content on a BranchCache server.

1. Generate hash package on the file server:
   
   PS C:\> Publish-BCFileContent -Path D:\share -StageData
   
2. Export hash package to temporary directory:
   
   PS C:\> Export-BCDataPackage –Destination D:\temp
   
   
3. Copy hash package to a temporary directory on the the remotely hosted-cache server.
   
   
4. Import hash package on hosted-cache server:
   
   PS C:\> Import-BCCachePackage –Path D:\temp\PeerDistPackage.zip

Problem:  BranchCache services do not work as expected.

Background:  BranchCache services are installed in a hub and spoke topology; data center serves multiple branch offices.

File servers at the data center are enabled as BranchCache content hosts.  BranchCache hosted cache servers set-up at each branch office. 

Troubleshooting: There is not a single pane BranchCahce GUI for management and monitoring -too bad!  The following steps confirm if BranchCache works:

1.  Confirm BranchCache is properly configured and operational on the servers and clients:

PowerShell:  Get-BCStatus

CMD:  netsh branchcache show status all

2.  Use Performance Monitor to check for real-time BranchCache activity (or lack of):

a)  Open PerfMon.



b)  Add the BranchCache counter.




c.)  Change graph type to "report".  The statistics will increase in real-time when any BranchCache file transfer takes place:



d)  Transfer data.  If BranchCache is working, the above highlighted numbers will increase in real-time.

Solution:

I missed the elephant in the room.

The problem was the specific version of Windows 8 used for the tests.  Windows 8 Enterprise must be used when working with BranchCache; not Professional.

This may seem obvious to anyone that has worked with the 2008R2 and Windows 7 BranchCache; however all the prerequisites from Microsoft simply read, "Windows 8" whereas Microsoft specifically indicated, "Windows 7 Enterprise".
References:

http://social.technet.microsoft.com/wiki/contents/articles/14309.branchcache-frequently-asked-questions.aspx

http://technet.microsoft.com/en-us/library/jj590747.aspx#bkmk_pre

http://technet.microsoft.com/library/jj572990

Last updated  March 30th, 2014 by Steven Jordan

     EVENT ID:  1004
       Path \\file path transitioned to slow link with latency = 74 and bandwidth = 10580536