Hi NTT Terin,
To ensure your 15GB deployment utilizes local peer-to-peer distribution, you must configure the Delivery Optimization CSP, found at ./Device/Vendor/MSFT/Policy/Config/DeliveryOptimization/DODownloadMode, setting the value to 1 to enable HTTP blended with peering within the same local network. This forces the agent to exhaust local peer sources before attempting to fetch content over your limited internet bandwidth. You should also explicitly set the Group ID, mapped to the policy at ./Device/Vendor/MSFT/Policy/Config/DeliveryOptimization/DOGroupID, to ensure that peer discovery is scoped strictly to the devices within your specific branch office subnet, preventing traffic leakage to other sites.
For even greater efficiency, consider deploying a Microsoft Connected Cache node, which acts as a local cache server. You can target this by configuring the DOCacheHost policy, which tells the client machine to prefer a specific local IP or FQDN for content retrieval. These settings are also represented in the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DeliveryOptimization\Config, where you can verify that the DownloadMode key reflects your changes. Ensure your network infrastructure allows traffic over TCP/UDP port 7680, which is required for peer discovery and content delivery protocols to function properly between your workstations. Configuring these parameters ensures that your branch office endpoints intelligently share the load rather than competing for your WAN capacity.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN