I had written about Delivery Optimization sometime in May this year. While DI has gained a lot of traction and many organizations have been evaluating or moving toward that, it is always good to hear Microsoft’s story on how they have done it internally.
As part of this IT showcase – Adopting Windows as a service at Microsoft, you will observe that Mirosoft uses Delivery Optimization at scale…
Abstract from their IT Showcase – ‘To help ensure that ongoing deployments weren’t affecting our network and taking away bandwidth for other services, we used a couple of different bandwidth management strategies. Delivery Optimization, peer-to-peer caching enabled through Group Policy, was piloted and then deployed to all managed devices using Group Policy. Delivery Optimization works with all Windows Update content. Based on recommendations from the Delivery Optimization team, we used the “domain” configuration to limit sharing of content to only the devices that are members of the same Active Directory domain. The content is cached for 24 hours. Initially more than 76 percent of content came from peer devices versus the Internet.
We pre-cache the build on devices, and highly recommend it as a best practice. When we began pre-caching, we had to rely on a custom solution. Pre-caching the build on devices is now an integrated solution in System Center Configuration Manager. Another enhancement in delivery is the new user notification experience. It sends targeted notifications to users that an upgrade is available and gives them the option to either install during a time that is convenient or to set a reminder for later.‘
To read more refer to – https://www.microsoft.com/en-us/itshowcase/adopting-windows-as-a-service-at-microsoft