We have around 400 Windows PCs, no WSUS server, and roughly 500 Mbps of usable internet bandwidth. Updates keep saturating the connection on patch Tuesday despite trying several settings. What should we configure and check?
What Delivery Optimization GPO settings help with patch Tuesday congestion?
Answers
Start with Delivery Optimization Download Mode 1, LAN, and allow inbound TCP 7680 between eligible peers. That lets PCs on the same subnet share update content instead of each downloading every byte from Microsoft.
Check the network layout before expecting much from it. Separate subnets and firewall rules can limit which machines can reach one another. A small set of PCs allowed to download earlier can also help seed content, but somebody still has to get the initial bytes from the internet.
Reply to this answer
Peering alone won't put a hard ceiling on internet use. Configure a Delivery Optimization background download bandwidth limit as well. Start conservatively, then adjust based on how quickly updates complete and what the connection looks like.
Remember that a per-device cap adds up across 400 PCs. A percentage setting also isn't a guarantee that the combined traffic will stay under a particular site-wide Mbps limit. If downloads still interfere with business traffic, look at network traffic shaping too.
c.826+drumfob:
Check foreground download settings separately. A background limit won't necessarily cover every update download.
Reply to this answer
Split the rollout into groups instead of having every PC start together. Let an earlier group download first, then release updates to the rest in stages. That gives peer caching a chance to help and spreads the load over more time.
Multiple policies or a patch management tool can help manage those schedules. WSUS is another option to evaluate if you want a local update source, but you don't need to deploy it just to test Delivery Optimization.
Reply to this answer
Before changing everything again, pick a few representative PCs and check what they're actually doing. Delivery Optimization's Activity Monitor shows traffic from Microsoft and peers. Compare that with the effective policies, the subnet each PC is on, and whether TCP 7680 is allowed between them.
Test after an update is available and give peers time to obtain content. Seeing a PC download from Microsoft isn't by itself proof that peering is broken. If peer traffic stays absent, investigate policy application and connectivity first.
Reply to this answer
Check which service is responsible for the traffic before applying a bandwidth policy. BITS limits can help with BITS downloads, but don't assume they control every Delivery Optimization transfer. Also check whether any older settings you're using are still supported for your Windows versions.
Reply to this answer
Add your answer
Answers are reviewed before publication.
7q~bramblet_361:
LAN mode is value 1, not 99. Check the applied policy on a few PCs rather than relying only on what's configured in the GPO.