From 6472cf6a18a9b30c06538dbee4637866cc3a33aa Mon Sep 17 00:00:00 2001 From: Anders Ahl <58516456+GenerAhl@users.noreply.github.com> Date: Tue, 29 Apr 2025 14:27:41 +0200 Subject: [PATCH 1/2] Update waas-delivery-optimization.md Corrected and updated a broken link. --- windows/deployment/do/waas-delivery-optimization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/waas-delivery-optimization.md b/windows/deployment/do/waas-delivery-optimization.md index 53fd47a91e..afc3a9c85f 100644 --- a/windows/deployment/do/waas-delivery-optimization.md +++ b/windows/deployment/do/waas-delivery-optimization.md @@ -85,7 +85,7 @@ In Windows client Enterprise, Professional, and Education editions, Delivery Opt At Microsoft, to help ensure that ongoing deployments weren't affecting our network and taking away bandwidth for other services, Microsoft IT 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. Based on recommendations from the Delivery Optimization team, we used the "group" 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. More than 76 percent of content came from peer devices versus the Internet. -For more information, check out the [Adopting Windows as a Service at Microsoft](https://www.microsoft.com/itshowcase/Article/Content/851/Adopting-Windows-as-a-service-at-Microsoft) technical case study. +For more information, check out the [Preparing your organization for a seamless Windows deployment]([https://www.microsoft.com/itshowcase/Article/Content/851/Adopting-Windows-as-a-service-at-Microsoft](https://www.microsoft.com/insidetrack/blog/preparing-your-organization-for-a-seamless-windows-10-deployment/)) technical case study. ## Using a proxy with Delivery Optimization From 3509f513340fe01bc1d86ff7b0cceebf1519ab74 Mon Sep 17 00:00:00 2001 From: Aaron Czechowski Date: Fri, 2 May 2025 10:56:02 -0700 Subject: [PATCH 2/2] remove link to itshowcase --- windows/deployment/do/waas-delivery-optimization.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/windows/deployment/do/waas-delivery-optimization.md b/windows/deployment/do/waas-delivery-optimization.md index afc3a9c85f..2a785d27d8 100644 --- a/windows/deployment/do/waas-delivery-optimization.md +++ b/windows/deployment/do/waas-delivery-optimization.md @@ -85,8 +85,6 @@ In Windows client Enterprise, Professional, and Education editions, Delivery Opt At Microsoft, to help ensure that ongoing deployments weren't affecting our network and taking away bandwidth for other services, Microsoft IT 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. Based on recommendations from the Delivery Optimization team, we used the "group" 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. More than 76 percent of content came from peer devices versus the Internet. -For more information, check out the [Preparing your organization for a seamless Windows deployment]([https://www.microsoft.com/itshowcase/Article/Content/851/Adopting-Windows-as-a-service-at-Microsoft](https://www.microsoft.com/insidetrack/blog/preparing-your-organization-for-a-seamless-windows-10-deployment/)) technical case study. - ## Using a proxy with Delivery Optimization If a proxy is being used in your environment, see [Using a proxy with Delivery Optimization](delivery-optimization-proxy.md) to understand the proxy settings needed to properly using Delivery Optimization.