We are current branch 1602. To be specific, our testing from the application model has deployments set to run as system whether or not the deployment is user or system based. When the deployment runs optionally, the bits job is created by system and the job runs foreground and ignores BITS rate limits.
With legacy package and program deployments, also set to always "run as sysyem", when the optional deployment is run, the bits job is created as the user, and it happens in the background, following our rate limits. As to #2, it just happens randomly that the transfer switches back and forth between the branch cache and the dp. When it happens with a package and program, it seems that bits rules are at least followed. On Jul 21, 2016 13:38, "Michael Niehaus" <[email protected]> wrote: > 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]] *On Behalf Of *Jay Marsett > *Sent:* Thursday, July 21, 2016 10:57 AM > *To:* [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. > > > >
