Content Delivery LEDBAT Architecture POC



  • Content will be hosted on Server 2019 IaaS VM’s running in Azure
  • Content is zipped and distributed through IIS on IaaS VM’s
  • IaaS VM’s will be behind a Azure Load Balancer
  • Endpoint receiving content will be managed with PowerShell DSC
  • Endpoints older than Server 2012 will utilize RoboCopy for throttling without scavenging

Microsoft / Other Resources-

MS LEDBAT Announcement 

SCCM Deployment Research (Found through Johan Arwidmark’s twitter)

2Pint Enabling LEDBAT with WSUS


I was first turned onto LEDBAT in 2017 at the Microsoft Midwest Management Summit in Minnesota by a session hosted by 2Pint.  Their big reveal was this new congestion control / scavenging algorithm that can utilize all available bandwidth and automatically throttle down when other resources require bandwidth. The best part was at the time 15% of internet torrent traffic was already utilizing LEDBAT and later Apple Updates jumped on board.

The objective in my environment was to host content centrally and distribute it to all locations, including slow WAN branch locations that have a very limited amount of  available bandwidth.  The endpoints Server 2008, 2012, and 2016 in this environment all required the content.  I utilized Azure DSC to point the endpoints content location to a pair of Azure IaaS VM’s that hosted the content on an IIS website.  I enabled congestion control on the website, zipped the content and presented it through a website in which PowerShell DSC pulled from when there is an update or the endpoint is missing content.  This becomes useful when hosting print drivers, software, utilities, etc.  SCCM DP’s and WSUS now have LEDBAT native support, and can be configured through their respective GUI’s.   This content delivery is a custom solution, but fully utilized LEDBAT’s potential and solves a major slow WAN challenge.   DM me if you are interest in additional or more in-depth info.


Joe Popich