Jaybone Posted January 24, 2018 Report post Posted January 24, 2018 Hi, all. Came upon something I've not seen before. Trying to push the Config Manager client to a new server, it was going excruciatingly slow. Reading up on it led me to look at BITS stuff. Settings were all good - non-existant, actually. The only thing that helped was to change the job's priority from Normal to Foreground. That got the transfer done more or less instantly. So now the client's installed, but there are new BITS jobs stacking up. I can't get any Windows Update info from it to the CM server, etc. Now, this server sees a sustained 250-275mbit/s of inbound network traffic pretty much all the time, just by nature of the type of server it is. That leaves several hundred mbit of slack, though, as it's got a 1gbit connection. But BITS seems to be acting like its starved for bandwidth, and transfers are slow, even when the CM client is setting priority to high. We've got a server that fills an identical role and is running on identical hardware with the same NIC driver on the same network that sees even higher sustained inbound traffic (currently ~1.2gbit/s on a 3gbit/s team), but without any of this type of problem. Anyone know of a way to force BITS to be a bit more aggressive, so that things actually work? Or maybe I'm going about this wrong? E.g. ~22.5 hours after it was created, this WU job finally started, and 20-30 min after that, is only 7MB along. PS Z:\TOOLS\pstools> Get-BitsTransfer -allusers -name "wu*" | fl JobId : b70f15ba-cb48-4cbb-9487-fec406bcc230 DisplayName : WU Client Download TransferType : Download JobState : Transferring OwnerAccount : NT AUTHORITY\SYSTEM Priority : High TransferPolicy : NoSurcharge FilesTransferred : 0 FilesTotal : 1 BytesTransferred : 7577239 BytesTotal : 96814352 CreationTime : 1/23/2018 2:58:51 PM ModificationTime : 1/24/2018 1:50:56 PM MinimumRetryDelay : NoProgressTimeout : TransientErrorCount : 0 ProxyUsage : NoProxy ProxyList : ProxyBypassList : Others are still queued up. PS Z:\TOOLS\pstools> Get-BitsTransfer -allusers | ft displayname,creationtime,modificationtime,priority,jobstate DisplayName CreationTime ModificationTime Priority JobState ----------- ------------ ---------------- -------- -------- CCMDTS Job 1/23/2018 2:16:53 PM 1/23/2018 2:16:53 PM Low Queued CCMDTS Job 1/23/2018 2:16:53 PM 1/23/2018 2:16:53 PM Low Queued CCM Message Upload {1B2D... 1/23/2018 4:22:46 PM 1/23/2018 4:22:46 PM Normal Queued CCM Message Upload {098C... 1/23/2018 6:28:45 PM 1/23/2018 6:28:45 PM Normal Queued CCM Message Upload {F0B2... 1/23/2018 8:05:32 PM 1/23/2018 8:05:32 PM Normal Queued WU Client Download 1/23/2018 2:58:51 PM 1/24/2018 1:53:51 PM High Transferring CCMDTS Job 1/23/2018 12:55:51 PM 1/24/2018 1:44:22 PM High Queued CCMDTS Job 1/23/2018 12:31:08 PM 1/24/2018 1:49:22 PM High Queued Quote Share this post Link to post Share on other sites More sharing options...
Jaybone Posted January 25, 2018 Report post Posted January 25, 2018 Update: ~20 hours later, that job has transferred a whopping 20MB. 0_o Quote Share this post Link to post Share on other sites More sharing options...
AlexChurch Posted May 20, 2019 Report post Posted May 20, 2019 Did you ever figure this out? We're seeing the same issue with a few of our servers that also see naturally high throughput just because of what they do. Quote Share this post Link to post Share on other sites More sharing options...