http://blogs.msdn.com/b/steverac/archive/2010/02/06/configuring-sccm-and-branch-cache.aspx
This was written for CM 2007 but other than a new Windows 8 GPO setting “Configure Client BranchCache Version Support” (which you’ll need to adjust from the default for backward compatibility if you’ll have both Win7 and Win8 clients participate in the peer caching), the process is pretty much identical. You’ll need to make sure you install the BranchCache feature on your DPs as checking the “Enable Branchcache Support” checkbox on the DP will not automatically install the feature (install feature, then check the enable box). The only issues I’ve run into so far are: 1) If a client happens to have a web or web-type app listening on port 80, it won’t allow that client’s Branchcache service to start (it can’t bind to port 80). That specific client won’t participate, but tends to be a very rare scenario. 2) If you set the latency value too low (like 0), very large packages (2-3+gb) can run into content download issues when deployed to a bunch of clients within the same subnet at once. I recommend either setting something a bit higher than 0 depending on your site-site latency, or unchecking the “share content” box for those larger packages, or deploy the large ones in a more gradual manner. When a large # of clients on a given subnet start downloading a large amount of data from their peers while the same peers are installing this same large application, the client with some older SATA I/II’s can become a bottleneck. That said, it’s a great feature with a very easy implementation, providing a consistently high amount of network team happiness. From: [email protected] [mailto:[email protected]] On Behalf Of Corkill, Daniel Sent: Thursday, August 14, 2014 7:20 AM To: [email protected] Subject: RE: [mssms] Configuring bits throttling I might look into the branch cache option. Are there any recommended guides for configuring this? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Thursday, 14 August 2014 7:03 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Configuring bits throttling Daniel While considering BITS throttling is a great idea may I ask whether you have considered using BranchCache in this scenario? In this case you would likely download the content to a remote office only once or twice and then serve it locally. Another scenario which can work well with updates - sometimes a remote office will have a direct Internet connection which is less slow than that which CORP supplies. In this environment you can set updated to download direct from WUMU while still deploying the catalog through CM On 14 Aug 2014, at 08:18, "Corkill, Daniel" <[email protected]<mailto:[email protected]>> wrote: I have a number of WAN sites that are on links ranging from 512k to 1.5m; each site has a handful of computers and no DPs. When I deploy monthly updates and these clients begin downloading them, I’m obviously concerned about effecting the links. I’m looking into BITS throttling via custom client settings but I’m unsure what I should actually limit the bandwidth to. Does anyone have any guidance on how I can determine the fastest speed I can set before I start effecting links? Daniel. ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law. ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law.
