Yeah would be a simple change – FOREGROUND priority in BITS really is a real bandwidth hogger, so maybe an override option would be pertinent, as some folks on fast networks will be fine with the setting as it is?
While we’re on the topic of BITS – could we also stop using the old XP BITS policy for bandwidth control in ConfigMgr? Surely the newer Work/Maintenance schedule policies would give more granular control. Uservoice here we come! Cheers, Phil Phil Wilcock 2Pint Software http://2pintsoftware.com @2pintsoftware From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: 31 January 2016 11:14 To: ms...@lists.myitforum.com Subject: RE: [mssms] Default BITS behaviour when user executing from Software Center/RAP Yeah, another way of putting it is, anything kicked off by the user cannot be bandwidth managed. Which can be pretty devastating for the network if you are on a slow link. Good or bad? Pretty bad IMHO. From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Jason Wallace Sent: den 31 januari 2016 12:05 To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: Re: [mssms] Default BITS behaviour when user executing from Software Center/RAP Hi Andreas So the rule here is that something that is Required will always download in background. That is, I believe correct even if the deadline has been passed. If something is marked as available then it will only ever download in foreground. This also applies to a job which is required but is kicked off by the user in Software Center. If don't have content staged locally to the user then the first user's session will begin downloading the content. Hopefully at least some of that content will then have been cached. On 31 Jan 2016, at 10:54, Andreas Hammarskjöld <jun...@2pintsoftware.com<mailto:jun...@2pintsoftware.com>> wrote: Hello boys & girls, So what many people might not know is that when a user executes a program the CM client puts the BITS job to download the job into a priority of FOREGROUND. That might have been a smart thing to do in order to get content fast, as it’s the highest priority and stops all other jobs from downloading. Sadly though, it also totally bypasses and bandwidth limitation in place. So a user executing a download of large package like AutoCAD in a remote poor bandwidth location could be a bad thing. So we deal with this issue in the new StifleR client (which will be free to use) and reset the job to HIGH which uses policy. So there will be a workaround soon. Alternative is also to use the Free BranchCache for OSD downloader BITSFIST.exe as an ACP. Now to the question, before we file this as a BUG/DCR, do people think that this kind behavior is a good thing? It must be like this for a reason? (Although I can’t think of any reason, but I am not the smartest person in the room). Some MS feedback would be good here. Regards, Andreas Hammarskjöld Co-Founder & Dev Guy Skunkworks Division 2Pint Software<https://2pintsoftware.com/> Mobile: +46 727 253995 andr...@2pintsoftware.com<mailto:andr...@2pintsoftware.com> https://twitter.com/AndHammarskjold
