In case you have locations w/o a server consider this:
As Jason said, it is about subnets. A client in a another subnet will have to download again, over the WAN of course. So, basically, the more subnets you have, the more downloads you get anyway. And of course, if those clients are offline, another download. I'd go with using it on smaller sites, not having many subnets. Up-to 150 clients is a good value imo. It is also most efficient for e.g. rollouts, so software updates installed on all clients at the same time, then all clients share each other's content (up to the limit of concurrent connections of those) On the other hand, if you request a 5GB app for one client and that client is offline, the next client uses the WAN again. Watch for network saturation, you may get bandwidth issues. It's not a miracle worker, but free. -R From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Mittwoch, 5. Februar 2014 00:43 To: [email protected] Subject: RE: [mssms] SCCM 2012, Branch Cache, Remote DP BranchCache supports all content types - BranchCache is actually OS functionality that essentially intercepts calls to download content via BITS and thus is agnostic of content type. If you have a DP at a location, there's really no need for BranchCache. BrancheCache is about making an attempt at ensuring content only traverses a WAN link once. If you already have a DP at a location, you're already guaranteed of that and thus BranchCache adds no real value. Thus, the decision point of whether or not to use BranchCache is based upon a remote location having a DP or not. Actual management of the BranchCache cache is a blackbox and totally undefined (to my knowledge) though. There really is no way to know or control whether a client has cached the content or not. As for content location, this is all based on broadcasts to the local subnet and referrals from the server hosting the content originally (the DP in ConfigMgr's case). If a local client does not have the content cached, then the client needing the content will get it from the DP - this of course could occur in multiple scenarios including being the first client to request content, clients in the local subnet with the content not being available or having moved, or clients in the local subnet having the content no longer having it for whatever reason. A cloud DP cannot provide content for BranchCache so it plays no part. J From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Tuesday, February 4, 2014 1:42 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] SCCM 2012, Branch Cache, Remote DP I have a few questions regarding BranchCache in SCCM 2012. First of all, does BranchCache support Software Updates + Application Deployment? Or just App deployment? Trying to understand whether this works for Software Updates or not. Secondly, what are my key decision points around implementing Branch Cache or a Distribution Point for a remote site location? If I have a DP at a remote location where Branch Cache is enabled and I have PC A download an app from SCCM. Now, PC B needs that same app and will then get the App from PC A. How long does it stay cached on PC A? What happens if PC A leaves this remote location, now it points to the DP to get the content? What if the user is remote and moving from office to office? How would a cloud DP come into play with all of this? Trying to wrap my head around these scenarios. :) Thanks, Brian
