Feedback from review

windows/deployment/do/delivery-optimization-configure.md

@@ -1,6 +1,6 @@
 ---
 title: Configure Delivery Optimization for Windows
-description: In this article, learn about the different configuration considerations to optimize Delivery Optimization in your environment.
+description: In this article, learn about the different configuration considerations to optimize Delivery Optimization (DO) in your environment.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
@@ -19,27 +19,31 @@ appliesto:
 ms.date: 07/01/2024
 ---
 
-# Configure Delivery Optimization for Windows
+# Configure Delivery Optimization (DO) for Windows
 
 ## Delivery Optimization set up considerations checklist
 
+Use this checklist to guide you through different aspects when modifying Delivery Optimization configurations for your environment.
+
 1. Allow Delivery Optimization communication
-1. Find Delivery Optimization
+2. Options to apply Delivery Optimization settings
-1. Network topology
+3. Network topology
-1. Device count
+4. Optimize P2P usage for your organization size
-1. System resources
+5. System resources
-1. Improve efficiencies
+6. Improve efficiencies
-1. Connected Cache
+7. Connected Cache
 
 ## 1. Allow DO communication
 
 :::image type="content" source="images/do-setup-allow-communication.png" alt-text="Screenshot of the considerations to allow Delivery Optimization communication." lightbox="images/do-setup-allow-communication.png":::
 
-Learn more about Firewall, Proxy, and Port requirements for Delivery Optimization communication.
+Delivery Optimization is used to download Microsoft content from different sources (HTTP source, peers, and/or dedicated cache solution). It requires communication between the DO client and the service to find the best and most reliable source of content. For this technology to work, the DO client running on the Windows device must be able to reach the DO cloud service.
+
+Find out more about the requirements for Firewall, Proxy, and Port settings to enable Delivery Optimization communication.
 
 ### Firewall
 
-There are some host names that you need to permit through your Firewall for Delivery Optimization to communicate. Check the [full list](waas-delivery-optimization-faq.yml#what-hostnames-should-i-allow-through-my-firewall-to-support-delivery-optimization) of host names to permit.
+There are service endpoints that you need to permit through your Firewall to communicate with the Delivery Optimization service. Check the [full list](waas-delivery-optimization-faq.yml#what-hostnames-should-i-allow-through-my-firewall-to-support-delivery-optimization) of endpoints to permit.
 
 ### Local proxy
 
@@ -47,29 +51,40 @@ When using a proxy, you want to bypass calls from the Delivery Optimization serv
 
 ### Cloud proxy
 
-If you're using a cloud proxy, you should configure it to allow Delivery Optimization traffic to [bypass the proxy](waas-delivery-optimization-faq.yml#what-is-the-recommended-configuration-for-delivery-optimization-used-with-cloud-proxies). Otherwise, you may experience reduced performance and increased bandwidth consumption.
+To allow peer-to-peer (P2P) to work properly you need to allow direct calls to the Delivery Optimization service from your devices (bypass the *.prod.do.dsp.mp.microsoft.com in your proxy). If the calls to the DO service are funneled through your proxy, it will alter the public IP Address of the devices, preventing P2P from working properly. If you're using a cloud proxy, you should configure it to allow Delivery Optimization traffic to [bypass the proxy](waas-delivery-optimization-faq.yml#what-is-the-recommended-configuration-for-delivery-optimization-used-with-cloud-proxies). Otherwise, you may experience reduced performance and increased bandwidth consumption.
 
 ### Ports
 
 Delivery Optimization requires the use of certain ports to deliver content. Make sure all the [required ports](waas-delivery-optimization-faq.yml#which-ports-does-delivery-optimization-use) are open to make Delivery Optimization work seamlessly.
 
+| Port    | Function          |
+|---------|-------------------|
+| 7680    | Listen for P2P using TCP/IP |
+| 3544    | Uses Teredo to discover and connect to peers across NATs |
+| 443     | Used to communicate Delivery Optimization client and service |
+
 ## 2. DO presence
 
 :::image type="content" source="images/do-setup-presence.png" alt-text="Screenshot of different product areas where you find Delivery Optimization." lightbox="images/do-setup-presence.png":::
 
-Use Group Policy or MDM Policies to locate Delivery Optimization settings.
+### Group Policies
 
-**Group Policies:** Computer Configuration\Administrative Templates\Windows Components\Delivery Optimization.
+To use Group Policy to manage Delivery Optimization settings you can find them here,
-**MDM Policies:** You can use an MDM solution like Intune to configure Delivery Optimization.
 
-Delivery Optimization is increasingly found throughout Microsoft products. Learn more about the areas where there's integration to see how you can optimize the results in your environment.
+```Computer Configuration\Administrative Templates\Windows Components\Delivery Optimization.  or MDM Policies to locate Delivery Optimization settings.```
+
+### MDM Policies
+
+Similarly, in MDM, the Delivery Optimization settings are under,
+
+```.Vendor/MSFT/Policy/Config/DeliveryOptimization/.```
+
+Delivery Optimization can be used with other Microsoft products. Learn more about the areas where there's integration to see how you can optimize the results in your environment.
 
 * [Microsoft Endpoint Manager (MEM)](/mem/intune/configuration/delivery-optimization-windows)
 * [Microsoft Endpoint Configuration Manager (MECM)](/mem/configmgr/sum/deploy-use/optimize-windows-10-update-delivery)
 * [Autopilot](../windows-deployment-scenarios.md#modern-deployment-methods)/[Autopatch](../windows-autopatch/overview/windows-autopatch-overview.md) – there are no specific settings that should be configured for Autopilot or Autopatch devices. However, it’s important to remember that once the device is connected to the corporate network, Delivery Optimization policies are applied.
 
-
-
 ## 3. Network topology
 
 :::image type="content" source="images/do-setup-network-topology.png" alt-text="Screenshot of Delivery Optimization network topology considerations." lightbox="images/do-setup-network-topology.png":::
@@ -84,9 +99,12 @@ Peer groups can be defined in Delivery Optimization using a combination of setti
 
 To limit a peer group to your LAN, choose [DODownloadMode](waas-delivery-optimization-reference.md#download-mode) (1), LAN-mode. This Download Mode setting includes any devices that share the same public IP address when they connect to the Internet (behind the same NAT) in a single peer group.
 
+> [!NOTE]
+> If your network topology is a hub and spoke - consider using Group download mode mode and/or restrict peer selection to the subnet.
+
 ##### Wide area network (WAN)
 
-To achieve peer groups across NATs within the same site, over the WAN, or to have more control in your local environment, use Download Mode ‘2’, Group-mode. Group download mode allows you to define a unique GUID Group ID or use existing “boundaries” in your enterprise with the [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) setting to identify a peer group.
+To achieve peer groups across NATs within the same site, over the WAN, or to have more control in your local environment, use Download Mode ‘2’, Group-mode. Group download mode allows you to define a unique GUID Group ID or use existing logical groupings (e.g. AD Site) in your enterprise with the [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) setting to identify a peer group.
 
 ##### GroupIDSource default behavior
 
@@ -94,6 +112,9 @@ There are several options for identifying your Group ID using the [DOGroupIDSour
 
 > [!NOTE]
 > If your peer group spans across NATs, the Teredo service will be used on port 3544.
+>
+> > [!NOTE]
+> For Configuration Manager users, we recommend to leverage existing [MECM boundary groups](/mem/configmgr/sum/deploy-use/optimize-windows-10-update-delivery) to define the peer groups.
 
 ##### Restrict peer selection
 
@@ -101,19 +122,19 @@ If your environment requires a more granular approach, you can use the Restrict
 
 ### Non-peering options
 
-There are two valid Download Modes that don't use the peer-to-peer functionality to deliver content; Download Modes (0) and (99). Download Mode (0) provides hash checks of the requested content and allows for quick detection and recovery of corrupted data due to the use of piece level hash checks. Download Mode (99) will provide a reliable download experience over HTTP from the download's original source or Microsoft, with no other checks.
+There are two valid Download Modes that don't use the peer-to-peer functionality to deliver content; Download Modes (0) and (99). Download Mode (0) uses additional metadata provided by the Delivery Optimization cloud services for a peerless, reliable and efficient download experience. Download Mode (99) will provide a reliable download experience over HTTP from the download's original source or Microsoft, with no other checks.
 
 ### Peering with VPN
 
-By default, if Delivery Optimization detects a VPN, peering is not used. To enable this behavior, use the [DOAllowVPNPeerCaching](waas-delivery-optimization-reference.md#enable-peer-caching-while-the-device-connects-via-vpn) policy. The Delivery Optimization Client looks in the network adapter’s ‘Description’ and ‘FriendlyName’ strings to determine VPN usage. To allow greater flexibility for VPN identification, use the [DOVpnKeywords](waas-delivery-optimization-reference.md#vpn-keywords) to add descriptors for a particular VPN. Also related, there's a [DODisallowCacheServerDownloadsOnVPN*](waas-delivery-optimization-reference.md#disallow-cache-server-downloads-on-vpn) policy to prevent downloads from a cache server while on a VPN connection.
+By default, if Delivery Optimization detects a VPN, peering is not used. To enable this behavior, use the [DOAllowVPNPeerCaching](waas-delivery-optimization-reference.md#enable-peer-caching-while-the-device-connects-via-vpn) policy. The Delivery Optimization Client looks in the network adapter’s ‘Description’ and ‘FriendlyName’ strings to determine VPN usage. To allow greater flexibility for VPN identification, use the [DOVpnKeywords](waas-delivery-optimization-reference.md#vpn-keywords) to add descriptors for a particular VPN.
 
-## 4. Device counts
+## 4. Optimize P2P usage for your organization size
 
-:::image type="content" source="images/do-setup-device-counts.png" alt-text="Screenshot of Delivery Optimization device count considerations." lightbox="images/do-setup-device-counts.png":::
+:::image type="content" source="images/do-setup-org-size.png" alt-text="Screenshot of optimizing P2P usage for your organization." lightbox="images/do-setup-org-size.png":::
 
 Delivery Optimization is designed to perform best in a large-scale environment with many devices. Depending on the size of the environment, you should evaluate the value of the [DOMinFileSizeToCache](waas-delivery-optimization-reference.md#minimum-peer-caching-content-file-size) to optimize peering.
 
-### Cache file size
+### Minimum file size to cache
 
 Content peering has a limited number of slots available at any given time. By default, only content files that are 50 MB or larger can be used for peering. In an environment with more than 30 devices, change the [DOMinFileSizeToCache](waas-delivery-optimization-reference.md#minimum-peer-caching-content-file-size) to a lower value (10 MB), to have more content available for peering, which can be distributed among many devices. For an even larger number of devices (>100), you can raise this setting to (1 MB).
 
@@ -129,15 +150,19 @@ There are some Delivery Optimization configurations that can make an impact when
 
 ### Disk size
 
-Alter the minimum disk size a device must have to use peering with the [DOMinDiskSizeAllowedToPeer](waas-delivery-optimization-reference.md#minimum-disk-size-allowed-to-use-peer-caching) setting. You can also manage the amount of space the Delivery Optimization cache uses with the following settings:  [DOMaxCacheSize](waas-delivery-optimization-reference.md#max-cache-size)/[DOAbsoluteMaxCacheSize](waas-delivery-optimization-reference.md#absolute-max-cache-size).
+Alter the minimum disk size (default is 32 GB) a device must have to use peering with the [DOMinDiskSizeAllowedToPeer](waas-delivery-optimization-reference.md#minimum-disk-size-allowed-to-use-peer-caching) setting.
+
+### Optimize cache size
+
+You can also manage the amount of space the Delivery Optimization cache uses with the following settings:  [DOMaxCacheSize](waas-delivery-optimization-reference.md#max-cache-size) (default is 20%) and [DOAbsoluteMaxCacheSize](waas-delivery-optimization-reference.md#absolute-max-cache-size) (default is not configured).
 
 ### RAM size
 
-Control the minimum amount of RAM (inclusive) allowed to use peer caching, [DOMinRAMAllowedToPeer](waas-delivery-optimization-reference.md#minimum-ram-inclusive-allowed-to-use-peer-caching).
+Control the minimum amount of RAM (inclusive) allowed to use peer caching (default is 4 GB), [DOMinRAMAllowedToPeer](waas-delivery-optimization-reference.md#minimum-ram-inclusive-allowed-to-use-peer-caching).
 
-### Large # of devices with healthy system resources
+### Large # of devices with idle system resources
 
-In a lab situation, there's typically a set number of devices that are plugged in and have ample free disk space. By increasing the content expiration interval of [DOMaxCacheAge](waas-delivery-optimization-reference.md#max-cache-age) to 7 or more (up to 30 days), you can take advantage of these devices, using them as excellent upload sources to upload more content over a longer period.
+In an environment with a set number of devices that are plugged in and have ample free disk space try increasing the content expiration interval of [DOMaxCacheAge](waas-delivery-optimization-reference.md#max-cache-age) seven or more (up to 30 days). You can take advantage of these devices, using them as excellent upload sources to upload more content over a longer period.
 
 ## 6. Improve efficiencies
 
@@ -146,12 +171,15 @@ In a lab situation, there's typically a set number of devices that are plugged i
 Looking to improve efficiency? Some of the most powerful settings you can change that could have a significant impact within your environment include:
 
 * Help optimize peer connection over HTTP connections using the [DOMinBackgroundQoS](waas-delivery-optimization-reference.md#minimum-background-qos) policy. A good value for the [DOMinBackgroundQoS](waas-delivery-optimization-reference.md#minimum-background-qos) policy is something lower than the average download speed seen in your network. For example, if your average speed is 1000 KB/s, set this policy to 500 KB/s.
-* Improve chances of downloading from peers and/or cache server by delaying the time DO attempts to make connections before falling back to the HTTP source. The set of policies include: [DODelayBackgroundDownloadFromHttp](waas-delivery-optimization-reference.md#delay-background-download-from-http-in-secs), [DODelayForegroundDownloadFromHttp](waas-delivery-optimization-reference.md#delay-foreground-download-from-http-in-secs), [DelayCacheServerFallbackBackground*](waas-delivery-optimization-reference.md#delay-background-download-cache-server-fallback-in-secs), [DelayCacheServerFallbackForeground*](waas-delivery-optimization-reference.md#delay-foreground-download-cache-server-fallback-in-secs). For applicable scenarios (improving efficiency from peers or cache server) a good starting point is ’60 - 90’ seconds for the background settings and ’30 – 60’ for foreground settings.
+* Improve chances of downloading from peers and/or cache server by delaying the time DO attempts to make connections before falling back to the HTTP source. The set of policies include: [DODelayBackgroundDownloadFromHttp](waas-delivery-optimization-reference.md#delay-background-download-from-http-in-secs), [DODelayForegroundDownloadFromHttp](waas-delivery-optimization-reference.md#delay-foreground-download-from-http-in-secs). For applicable scenarios (improving efficiency from peers or cache server) a good starting point is 60 seconds for the background settings and 30 seconds for foreground settings.
-* Reduce any disruptions and help to manage the timing of network usage by utilizing the business hours policies, [DOSetHoursToLimitForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-foreground-download-bandwidth) and [DOSetHoursToLimitBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-background-download-bandwidth).
+
+### Bandwidth throttling options
+
+* Reduce disruptions by throttling differently at different times of day, using the business hours policies, [DOSetHoursToLimitForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-foreground-download-bandwidth) and [DOSetHoursToLimitBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-background-download-bandwidth).
 * Manage network usage as a percentage or absolute value (Note: The absolute policies are recommended in low bandwidth environments). These policies include: [DOPercentageMaxForegroundBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth)/[DOPercentageMaxBackgroundBandwidth](waas-delivery-optimization-reference.md#maximum-background-download-bandwidth), [DOMaxBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-background-download-bandwidth-in-kbs), and [DOMaxForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth-in-kbs).
 
 > [!NOTE]
-> Not all content types aren't eligible for P2P. Refer the [complete list](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) to learn more.
+> Not all content types are eligible for P2P. Refer the [complete list](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) to learn more.
 
 ## 7. Connected cache
 
@@ -165,6 +193,17 @@ Looking to improve efficiency? Some of the most powerful settings you can change
 * [DelayCacheServerFallbackBackground](waas-delivery-optimization-reference.md#delay-background-download-cache-server-fallback-in-secs) and [DelayCacheServerFallbackForeground](waas-delivery-optimization-reference.md#delay-foreground-download-cache-server-fallback-in-secs) are the delay policies to help improve chances of pulling content from the network cache host servers. (See recommended values in ‘Improving Efficiencies’ section).
 * [DODisallowCacheServerDownloadsOnVPN](waas-delivery-optimization-reference.md#disallow-cache-server-downloads-on-vpn) allows control of the cache host server to supply content, when device is on a VPN connection.
 
+## Summary of basic configuration recommendations
+
+| Use case | Policy | Recommended value |
+| --- | --- | ------------------------- |
+| Use P2P | DownloadMode | 1 or 2 |
+| Do not use P2P | DownloadMode | 0 |
+| Number of devices in the organization | MinFileSizeToCache | 1 MB for peer group > 100 devices |
+| Idle system resources | MaxCacheAge | 7 days (604800 seconds) |
+| Improve efficiencies | MinBackgroundQoS and DelayBackgroundDownloadFromHttp / DelayForegroundDownloadFromHttp  | 500 KB/s and 60/30 seconds |
+| Using Connected Cache? | DelayCacheServerFallbackBackground / DelayCacheServerFallbackForeground | 60/30 seconds |
+
 ## Monitor Delivery Optimization
 
 Whether you opt for the default Delivery Optimization configurations or tailor them to suit your environment, you will want to track the outcomes to see how they improve your efficiency. [Learn more](waas-delivery-optimization-monitor.md) about the monitoring options for Delivery Optimization.

windows/deployment/do/waas-delivery-optimization-reference.md

@@ -127,7 +127,7 @@ Download mode dictates which download sources clients are allowed to use when do
 
 | Download mode option | Functionality when configured |
 | --- | --- |
-| HTTP Only (0) | This setting disables peer-to-peer caching but still allows Delivery Optimization to download content over HTTP from the download's original source or a Microsoft Connected Cache server. This mode uses additional metadata provided by the Delivery Optimization cloud services for a peerless reliable and efficient download experience. |
+| HTTP Only (0) | This setting disables peer-to-peer caching but still allows Delivery Optimization to download content over HTTP from the download's original source or a Microsoft Connected Cache server. This mode uses additional metadata provided by the Delivery Optimization cloud services for a peerless, reliable and efficient download experience. |
 | LAN (**1 - Default**) | This default operating mode for Delivery Optimization enables peer sharing on the same network. The Delivery Optimization cloud service finds other clients that connect to the Internet using the same public IP as the target client. These clients then try to connect to other peers on the same network by using their private subnet IP.|
 | Group (2) | When group mode is set, the group is automatically selected based on the device's Active Directory Domain Services (AD DS) site (Windows 10, version 1607) or the domain the device is authenticated to (Windows 10, version 1511). In group mode, peering occurs across internal subnets, between devices that belong to the same group, including devices in remote offices. You can use GroupID option to create your own custom group independently of domains and AD DS sites. Starting with Windows 10, version 1803, you can use the GroupIDSource parameter to take advantage of other method to create groups dynamically. Group download mode is the recommended option for most organizations looking to achieve the best bandwidth optimization with Delivery Optimization. |
 | Internet (3) | Enable Internet peer sources for Delivery Optimization. |