On your application of the policy, are you targeting individual devices or just allow it to be active on all devices and stuff caches where it caches??? Did you set the per device limit at say… 5%?
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jay Marsett Sent: Tuesday, June 28, 2016 12:44 PM To: mssms@lists.myitforum.com Subject: Re: [mssms] BranchCache, ConfigMgr, and PRO Sku So much great feedback! We were contemplating utilizing a pretty slow footprint for BITS policy, 1-2MB let's say, across the board, and then narrow that bandwidth further using networking equipment, where appropriate. Anyone else doing something similar? Thanks On Tue, Jun 28, 2016 at 10:29 AM, David Jones <dkjones9...@gmail.com<mailto:dkjones9...@gmail.com>> wrote: 6am-6pm 2mb, full at night On Jun 28, 2016 9:50 AM, "Jimmy Martin" <jimmy.mar...@bmhcc.org<mailto:jimmy.mar...@bmhcc.org>> wrote: I know it’s highly dependent on underlying network capabilities, but what do you (collective you) use for your bits transfer rate settings? Jimmy Martin (901) 227-8209<tel:%28901%29%20227-8209> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] On Behalf Of David Jones Sent: Friday, June 24, 2016 2:00 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] BranchCache, ConfigMgr, and PRO Sku That is exactly what we do. 35000 clients. Have had no complaints. But what does that mean in the big scheme? You could right click any client in the local network of all the sites and make them a DP. We were doing before Branchcache. On Fri, Jun 24, 2016 at 2:08 PM, Phil Wilcock <ph...@2pintsoftware.com<mailto:ph...@2pintsoftware.com>> wrote: Works fine, PRO is supported and always has been, just do it! https://technet.microsoft.com/en-us/library/mt613461.aspx#bkmk_os<https://urldefense.proofpoint.com/v2/url?u=https-3A__technet.microsoft.com_en-2Dus_library_mt613461.aspx-23bkmk-5Fos&d=CwMFaQ&c=NwimJEPcMuFfAJV6iz0C4Q&r=fmX3K5VcrxX3Cfd4TmGGXvjAEVAsqB03O3gvuJE7gdY&m=r3MqgjQbNaYBffhV9c4ZN1l8D71UW1K8VXyn98_vBuc&s=aaV0wGpEWTXQkjS3O8EweUKdXVAvp46WXQJTCY8bmW8&e=> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] On Behalf Of Jay Parekh Sent: 24 June 2016 14:45 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] BranchCache, ConfigMgr, and PRO Sku Posting for my colleague. Some reason he's post here is not coming through. Basically comes down to a client is looking to deploy a net new SCCM environment. They have 400 sites but the CTO doesn't want servers (DPs) at the sites and he will not pay for Nomad or OneSite. Also they are running Win 7 Pro on the client side. They want to see if anyone has tried a large CM deployment without local DPs and just utilizing BranchCache/BITs. Hey guys, wanted to ask a couple of questions about what we are seeing in the field with BranchCache, ConfigMgr and the PRO SKU of Windows. It is my understanding that Windows PRO editions can be configured to utilize BranchCache in a BITS only operating mode (which seems to be fine for Configuration Manager); my questions, 1. Are we seeing it appear much in the field? Are many of you using BranchCache in mixed Pro and Enterprise SKU environments, or PRO SKU only environments? 2. And more importantly, is it supportable? E.G., Will Microsoft validate and support a configuration that intentionally utilizes this seeming hole in the "BranchCache is an Enterprise feature" conundrum? This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
