Beaten by Niehaus, shame on me! #1 is why also why our free StifleR client resets any FOREGROUND over a certain size to be high or normal depending on your config. But then we found that this wasn’t the case any more… gah! But sure its fixed in 1602 at least, maybe even 1511? Maybe I haven’t tried Apps and only pgk/prg and TS? Hmm…
#2 BC is not so disk intensive, more CPU intensive. Still typically you hardly notice when a machine is pulling from it unless it’s a 3GB .wim and you only have one client to pull from. Then you will see some action. Still then it’s only pulling with 60Mb/s so modern machines should hardly sweat. Can you pull the same file of it using Explorer without any issues? /A From: [email protected] [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: den 21 juli 2016 20:33 To: [email protected] Subject: RE: [mssms] Bits and BranchCache revisited On #1, can you clarify the version of ConfigMgr you are using? My understanding is that the behavior you described is as expected, but that this changed in the most recent current branch release to always be a background transfer. No idea what’s going on with #2, but it would be interesting to see if it happens with a different PC. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jay Marsett Sent: Thursday, July 21, 2016 10:57 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Bits and BranchCache revisited Finally have some real feedback about BranchCache and BITS. Got our site built and began unit testing, What we found so far; 1. Seems like all Package and Program downloads are BITS background transfers, so they follow rate limits, however, User initiated Application downloads STILL happen in the foreground. Anyone seen any documentation that explains that? 2. Seeing a single test machine that randomly seems to have issues as large transfers from Branchcache are occuring. The system becomes unstable, freezes as the hybrid drive software (lenovo expresscache) seems to peg the HD, as this is occuring, the transfer from cache seems to stop, and it begins to transfer from the DP. Then randomly, back to the BranchCache. Seems to happen with any type of "Cacheable" content, but only user initiated Application installs seem to ignore the BITS rate limits. Anyone seen this behavior? Have any documentation that can explain it? We haven't yet debugged the problem laptop yet, but theoretically, all of our test systems are identical. Long story short, it makes it impossible to use self service with the AppCatalog if we can't reasonably plan for when this type of issue might occur in this BranchCache with BITS model. If all Application based pushes need to be background, we can't use self service. Please let me know your thoughts.
