Optimisation of Delivery Optimisation

[jthompson]

Hi all

 

In an effort to improve how our staff laptops stay updated during the 2020s, I've made some changes and am wondering how others have tweaked their Delivery Optimisation settings away from the defaults.

 

Instead of receiving updates directly from WSUS on an internal FQDN only, our WSUS is now available using an externally reachable FQDN and does not cache updates. Clients check-in to WSUS and download their updates directly from MS, with Delivery Optimisation set up in LAN mode.

 

For staff laptops this now works nicely and will keep them up to date during holidays, maternity leave, etc. On site, this means we have plenty of computers that will be either downloading updates from the web or using DO. Should I be looking to leverage DO as much as possible on site by reducing the "Minimum Peer Caching Content File Size" in Group Policy to something really small?

 

What DO settings might others recommend for the average secondary school?

[Steve21]

Instead of receiving updates directly from WSUS on an internal FQDN only, our WSUS is now available using an externally reachable FQDN and does not cache updates.

 

I mean if you've already done that (and set it up securely), why not just enable caching and act as their server? They'll download it from your site effectively, and you don't need DO internally that way (Ok bandwidth etc, but you'll be controlling updates still and assuming this is for lock downs etc, it's not going to be hundreds of clients and updates daily etc, and would work just like if they're on a VPN connection)

 

Remembering that the majority will update internally, and only the odd offsite/maternity will really use that download speed, and during holidays etc will it matter if you're using more speed?

 

(Personally always found DO to be a bit spiteful in terms of losing local storage, added network bandwidth etc, for not much gains)

 

Steve