From 5730390886ed0ee39d931d8a056e06284e75b743 Mon Sep 17 00:00:00 2001 From: "[cmknox]" <[cmknox@gmail.com]> Date: Fri, 24 May 2024 18:24:41 -0600 Subject: [PATCH] Minor fixes, revved dates, added to cmdlet details. --- windows/deployment/do/TOC.yml | 2 + .../do/delivery-optimization-endpoints.md | 4 +- .../do/delivery-optimization-proxy.md | 4 +- .../do/delivery-optimization-test.md | 66 ++++---- .../do/delivery-optimization-workflow.md | 17 +- windows/deployment/do/index.yml | 3 +- windows/deployment/do/mcc-ent-edu-overview.md | 3 +- .../deployment/do/mcc-enterprise-appendix.md | 13 +- .../deployment/do/mcc-enterprise-deploy.md | 57 ++++--- .../do/mcc-enterprise-prerequisites.md | 2 +- .../do/mcc-enterprise-update-uninstall.md | 2 +- .../do/mcc-isp-cache-node-configuration.md | 5 +- .../do/mcc-isp-create-provision-deploy.md | 10 +- windows/deployment/do/mcc-isp-faq.yml | 2 +- windows/deployment/do/mcc-isp-overview.md | 4 +- windows/deployment/do/mcc-isp-signup.md | 6 +- windows/deployment/do/mcc-isp-support.md | 29 ++-- windows/deployment/do/mcc-isp-update.md | 6 +- .../do/mcc-isp-verify-cache-node.md | 12 +- .../deployment/do/mcc-isp-vm-performance.md | 4 +- windows/deployment/do/mcc-isp.md | 8 +- .../do/waas-delivery-optimization-faq.yml | 4 +- .../do/waas-delivery-optimization-monitor.md | 82 +++++---- .../waas-delivery-optimization-reference.md | 159 +++++++++--------- .../do/waas-delivery-optimization-setup.md | 2 +- .../do/waas-delivery-optimization.md | 42 ++--- .../do/waas-microsoft-connected-cache.md | 2 +- .../do/waas-optimize-windows-10-updates.md | 2 +- windows/deployment/do/whats-new-do.md | 10 +- 29 files changed, 286 insertions(+), 276 deletions(-) diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index 933c48b4b8..ad705d0de9 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -27,6 +27,8 @@ href: delivery-optimization-proxy.md - name: Testing Delivery Optimization href: delivery-optimization-test.md + - name: Delivery Optimization Troubleshooter + href: http://aka.ms/do-fix - name: Microsoft Connected Cache items: - name: What is Microsoft Connected Cache? diff --git a/windows/deployment/do/delivery-optimization-endpoints.md b/windows/deployment/do/delivery-optimization-endpoints.md index bbfa7de7b5..02ad508984 100644 --- a/windows/deployment/do/delivery-optimization-endpoints.md +++ b/windows/deployment/do/delivery-optimization-endpoints.md @@ -14,7 +14,7 @@ appliesto: - ✅ Microsoft Connected Cache for ISPs - ✅ Microsoft Connected Cache for Enterprise and Education - ✅ Connected Cache on a Configuration Manager distribution point -ms.date: 03/31/2023 +ms.date: 05/23/2024 --- # Microsoft Connected Cache content and services endpoints @@ -22,7 +22,7 @@ ms.date: 03/31/2023 > [!NOTE] > All ports are outbound. -This article lists the content and services endpoints to allow in your firewall to be used by Microsoft Connected Cache. +This article lists the content and services endpoints to allow in your firewall to be used by Microsoft Connected Cache. Use the table below to reference any particular content types or services endpoints that are required for [Connected Cache on a Configuration Manager distribution point](/mem/configmgr/core/plan-design/hierarchy/microsoft-connected-cache), [Connected Cache managed in Azure](waas-microsoft-connected-cache.md), or both. |Domain Name |Protocol/Port(s) | Content Type | Additional Information | Microsoft Connected Cache Version | diff --git a/windows/deployment/do/delivery-optimization-proxy.md b/windows/deployment/do/delivery-optimization-proxy.md index b300268967..3449e9f030 100644 --- a/windows/deployment/do/delivery-optimization-proxy.md +++ b/windows/deployment/do/delivery-optimization-proxy.md @@ -14,7 +14,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Delivery Optimization -ms.date: 06/02/2023 +ms.date: 05/23/2024 --- # Using a proxy with Delivery Optimization @@ -36,7 +36,7 @@ If no user is signed in, even if both the Internet Explorer proxy and netsh conf You can still use netsh to import the proxy setting from Internet Explorer (`netsh winhttp import proxy source=ie`) if your proxy configuration is a static *proxyServerName:Port*. However, the same limitations mentioned previously apply. -### Summary of settings behavior +## Summary of settings behavior These tables summarize the behavior for various combinations of settings: diff --git a/windows/deployment/do/delivery-optimization-test.md b/windows/deployment/do/delivery-optimization-test.md index 313d8afd21..2ab71579fd 100644 --- a/windows/deployment/do/delivery-optimization-test.md +++ b/windows/deployment/do/delivery-optimization-test.md @@ -21,7 +21,7 @@ ms.date: 11/08/2022 ## Overview -Delivery Optimization is a powerful and useful tool to help enterprises manage bandwidth usage for downloading Microsoft content. It's a solution designed to be used in large-scale environments with large numbers of devices, various content sizes, etc. Delivery Optimization is native to currently supported versions of Windows and provides default configuration to get the most out of the typical customer environment. Delivery Optimization is used to deliver many different types of content, so Microsoft customers enjoy the best possible download experience for their environment. There are three components to Delivery Optimization: +Delivery Optimization is a powerful and useful tool to help enterprises manage bandwidth usage for downloading Microsoft content. It's a solution designed to be used in large-scal05/23/2024e environments with large numbers of devices, various content sizes, etc. Delivery Optimization is native to currently supported versions of Windows and provides default configuration to get the most out of the typical customer environment. Delivery Optimization is used to deliver many different types of content, so Microsoft customers enjoy the best possible download experience for their environment. There are three components to Delivery Optimization: 1. HTTP downloader. 1. Peer-to-peer (P2P) cloud technology. @@ -29,7 +29,7 @@ Delivery Optimization is a powerful and useful tool to help enterprises manage b One of the most powerful advantages of using Delivery Optimization is the ability to fine-tune settings that empower users to dial in Microsoft content delivery to meet the needs of specific environments. -## Monitoring The Results +## Monitoring the Results Since Delivery Optimization is on by default, you're able to monitor the value either through the Windows Settings for 'Delivery Optimization' using Delivery Optimization PowerShell [cmdlets.](waas-delivery-optimization-setup.md), and/or via the [Windows Update for Business Report](../update/wufb-reports-workbook.md) experience in Azure. @@ -70,18 +70,18 @@ Machine 1 will download zero bytes from peers and Machine 2 will download 50-99% #### Test Machine Setup |Setup Checklist| Value/Explanation -|--------|-------------------------------| -|Number of machines used| 2 | -|Virtual Machines/physical devices| 2 | -|Windows OS version | Windows 10 (21H2) and Windows 11 (21H2) | -|RAM | 8 GB | -|Disk size | 127 GB | -|Network | Connected to same network, one that is representative of the corporate network. | -|Pause Windows Updates | This controls the test environment so no other content is made available during the test, and potentially altering the outcome of the test. If there are problems and no peering happens, use 'Get-DeliveryOptimizationStatus' on the first machine to return a real-time list of the connected peers. | -|Ensure all Store apps are up to date | This helps prevent any new, unexpected updates to download during testing. | -|Delivery Optimization 'Download Mode' Policy | 2 (Group)(set on each machine) | -|Delivery Optimization 'GroupID' Policy | Set the *same* 'GUID' on each test machine. A GUID is a required value, which can be generated using PowerShell, '[[guid]::NewGuid().](https://devblogs.microsoft.com/scripting/powertip-create-a-new-guid-by-using-powershell/)'. | -|**Required on Windows 11 devices only** set Delivery Optimization 'Restrict Peer Selection' policy | 0-NAT (set on each machine). The default behavior in Windows 11 is set to '2-Local Peer Discovery'. For testing purposes, this needs to be scoped to the NAT. | +|--------|------------------------------- +|Number of machines used| 2 +|Virtual Machines/physical devices| 2 +|Windows OS version | Windows 10 (21H2) and Windows 11 (21H2) +|RAM | 8 GB +|Disk size | 127 GB +|Network | Connected to same network, one that is representative of the corporate network. +|Pause Windows Updates | This controls the test environment so no other content is made available during the test, and potentially altering the outcome of the test. If there are problems and no peering happens, use 'Get-DeliveryOptimizationStatus' on the first machine to return a real-time list of the connected peers. +|Ensure all Store apps are up to date | This helps prevent any new, unexpected updates to download during testing. +|Delivery Optimization 'Download Mode' Policy | 2 (Group)(set on each machine) +|Delivery Optimization 'GroupID' Policy | Set the *same* 'GUID' on each test machine. A GUID is a required value, which can be generated using PowerShell, '[[guid]::NewGuid().](https://devblogs.microsoft.com/scripting/powertip-create-a-new-guid-by-using-powershell/)'. +|**Required on Windows 11 devices only** set Delivery Optimization 'Restrict Peer Selection' policy | 0-NAT (set on each machine). The default behavior in Windows 11 is set to '2-Local Peer Discovery'. For testing purposes, this needs to be scoped to the NAT. #### Test Instructions @@ -97,10 +97,10 @@ The following set of instructions will be used for each machine: * Run 'Test Instructions' |Windows 10 | Windows 11 -|--------|-------------------------------| -| :::image type="content" source="images/test-scenarios/win10/m1-basic-complete.png" alt-text="Windows 10 21H2 - Machine 1 - Basic Test." lightbox="images/test-scenarios/win10/m1-basic-complete.png"::: | :::image type="content" source="images/test-scenarios/win11/m1-basic-complete.png" alt-text="Windows 11 21H2 - Machine 1 - Basic Test." lightbox="images/test-scenarios/win11/m1-basic-complete.png"::: | -| **Observations** | | -| *No peers were found on the first machine downloading the content.
* 'TotalBytesDownloaded' is equal to the file size.
*Status is set to 'Caching' the content so future peers can use it.
* Download was happening in the foreground.
*DownloadMode is set to 'Group' and no peers were found.
* No distinct observations seen between Window 10 and Windows 11 devices. | +|--------|------------------------------- +| :::image type="content" source="images/test-scenarios/win10/m1-basic-complete.png" alt-text="Windows 10 21H2 - Machine 1 - Basic Test." lightbox="images/test-scenarios/win10/m1-basic-complete.png"::: | :::image type="content" source="images/test-scenarios/win11/m1-basic-complete.png" alt-text="Windows 11 21H2 - Machine 1 - Basic Test." lightbox="images/test-scenarios/win11/m1-basic-complete.png"::: +| **Observations** +| - No peers were found on the first machine downloading the content.
- 'TotalBytesDownloaded' is equal to the file size.
- Status is set to 'Caching' the content so future peers can use it.
- Download was happening in the foreground.
- DownloadMode is set to 'Group' and no peers were found.
- No distinct observations seen between Window 10 and Windows 11 devices. *Wait 5 minutes*. @@ -108,11 +108,11 @@ The following set of instructions will be used for each machine: * Run 'Test Instructions' -|Windows 10 | Windows 11 | -|--------|--------------------------------| +|Windows 10 | Windows 11 +|--------|-------------------------------- | :::image type="content" source="images/test-scenarios/win10/m2-basic-complete.png" alt-text="Windows 10 21H2 - Machine 2 - Basic Test." lightbox="images/test-scenarios/win10/m2-basic-complete.png"::: | :::image type="content" source="images/test-scenarios/win11/m2-basic-complete.png" alt-text="Windows 11 21H2 - Machine 2 - Basic Test." lightbox="images/test-scenarios/win11/m2-basic-complete.png":::| -| **Observations** | **Observations**| -| *A peer was found for the content and 87% of total bytes came from the peer.
* One peer was found for the piece of content, which is expected as there are only two devices in the peering group.
*Download mode was set to 'Group', but since group mode includes both LAN and Group devices, Delivery Optimization prioritizes LAN peers, if found. Therefore, 'BytesFromLanPeers' shows bytes where 'BytesFromGroupPeers' doesn't.
* 'DownloadDuration' is roughly the same between machines.|*A peer was found for the content and 90% of total bytes came from the peer.
* All other points are the same as Windows 10 results. | +| **Observations** | **Observations** +| - A peer was found for the content and 87% of total bytes came from the peer.
- One peer was found for the piece of content, which is expected as there are only two devices in the peering group.
- Download mode was set to 'Group', but since group mode includes both LAN and Group devices, Delivery Optimization prioritizes LAN peers, if found. Therefore, 'BytesFromLanPeers' shows bytes where 'BytesFromGroupPeers' doesn't.
- 'DownloadDuration' is roughly the same between machines.
- A peer was found for the content and 90% of total bytes came from the peer.
- All other points are the same as Windows 10 results. ### Scenario 2: Advance Setup @@ -123,18 +123,18 @@ Machine 1 will download zero bytes from peers and Machine 2 will find peers and #### Test Machine Setup -|Setup Checklist| Value/Explanation | -|--------|-------------------------------| -|Number of machines used| 3 | -|Virtual Machines| 3 | -|Windows OS version | Windows 10 (21H2) | -|RAM | 8 GB | -|Disk size | 127 GB | -|Network | Connected to same network, one that is representative of the corporate network. | -|Delivery Optimization 'Download Mode' Policy| 2 (Group)(set on each machine) | +|Setup Checklist| Value/Explanation +|--------|------------------------------- +|Number of machines used| 3 +|Virtual Machines| 3 +|Windows OS version | Windows 10 (21H2) +|RAM | 8 GB +|Disk size | 127 GB +|Network | Connected to same network, one that is representative of the corporate network. +|Delivery Optimization 'Download Mode' Policy| 2 (Group)(set on each machine). |Delivery Optimization 'Group ID' Policy| Set the *same* 'GUID' on each test machine. A GUID is required value, which can be generated using PowerShell, '[guid]::NewGuid().](https://devblogs.microsoft.com/scripting/powertip-create-a-new-guid-by-using-powershell/)'. | -|Delivery Optimization 'Delay background download from http' Policy | 60 (set on each machine) | -|Delivery Optimization 'Delay foreground download from http Policy |60 (set on each machine) | +|Delivery Optimization 'Delay background download from http' Policy | 60 (set on each machine). +|Delivery Optimization 'Delay foreground download from http Policy |60 (set on each machine). #### Testing Instructions diff --git a/windows/deployment/do/delivery-optimization-workflow.md b/windows/deployment/do/delivery-optimization-workflow.md index 7c2b567c9c..0d20ed1538 100644 --- a/windows/deployment/do/delivery-optimization-workflow.md +++ b/windows/deployment/do/delivery-optimization-workflow.md @@ -17,7 +17,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Delivery Optimization -ms.date: 01/18/2024 +ms.date: 05/23/2024 --- # Delivery Optimization workflow, privacy, security, and endpoints @@ -41,14 +41,13 @@ This workflow allows Delivery Optimization to securely and efficiently deliver r 5. If Delivery Optimization is unable to obtain the content metadata file, or if the verification of the hash file itself fails, the download will fall back to simple mode. Simple mode will only pull content from the HTTP source and peer-to-peer won't be allowed. 6. Once downloading is complete, Delivery Optimization uses all retrieved pieces of the content to put the file together. At that point, the Delivery Optimization caller (for example, Windows Update) checks the entire file to verify the signature prior to installing it. - ## Delivery Optimization service endpoint and data information |Endpoint hostname | Port|Name|Description|Data sent from the computer to the endpoint -|--------------------------------------------|--------|---------------|-----------------------|------------------------| -| geover-prod.do.dsp.mp.microsoft.com
geo-prod.do.dsp.mp.microsoft.com
geo.prod.do.dsp.mp.microsoft.com
geover.prod.do.dsp.mp.microsoft.com | 443 | Geo | Service used to identify the location of the device in order to direct it to the nearest data center. | **Profile**: The device type (for example, PC or Xbox)
**doClientVersion**: The version of the DoSvc client
**groupID**: Group the device belongs to (set with DownloadMode = '2' (Group download mode) + groupID group policy / MDM policies) | -| kv\*.prod.do.dsp.mp.microsoft.com | 443| KeyValue | Bootstrap service provides endpoints for all other services and device configs. | **countryCode**: The country or region the client is connected from
**doClientVersion**: The version of the DoSvc client
**Profile**: The device type (for example, PC or Xbox)
**eId**: Client grouping ID
**CacheHost**: Cache host ID | -| cp\*.prod.do.dsp.mp.microsoft.com
| 443 | Content Policy | Provides content specific policies and as content metadata URLs. | **Profile**: The device type (for example, PC or Xbox)
**ContentId**: The content identifier
**doClientVersion**: The version of the DoSvc client
**countryCode**: The country the client is connected from
**altCatalogID**: If ContentID isn't available, use the download URL instead
**eID**: Client grouping ID
**CacheHost**: Cache host ID | -| disc\*.prod.do.dsp.mp.microsoft.com | 443 | Discovery | Directs clients to a particular instance of the peer matching service (Array), ensuing that clients are collocated by factors, such as content, groupID and external IP. | **Profile**: The device type (for example, PC or Xbox)
**ContentID**: The content identifier
**doClientVersion**: The version of the DoSvc client
**partitionID**: Client partitioning hint
**altCatalogID**: If ContentID isn't available, use the download URL instead
**eID**: Client grouping ID | -| array\*.prod.do.dsp.mp.microsoft.com | 443 | Arrays | Provides the client with list of peers that have the same content and belong to the same peer group. | **Profile**: The device type (for example, PC or Xbox)
**ContentID**: The content identifier
**doClientVersion**: The version of the DoSvc client
**altCatalogID**: If ContentID isn't available, use the download URL instead
**PeerID**: Identity of the device running DO client
**ReportedIp**: The internal / private IP Address
**IsBackground**: Is the download interactive or background
**Uploaded**: Total bytes uploaded to peers
**Downloaded**: Total bytes downloaded from peers
**DownloadedCdn**: Total bytes downloaded from CDN
**Left**: Bytes left to download
**Peers Wanted**: Total number of peers wanted
**Group ID**: Group the device belongs to (set via DownloadMode 2 + Group ID GP / MDM policies)
**Scope**: The Download mode
**UploadedBPS**: The upload speed in bytes per second
**DownloadBPS**: The download speed in Bytes per second
**eID**: Client grouping ID | -| dl.delivery.mp.microsoft.com
emdl.ws.microsoft.com
download.windowsupdate.com | 80 | Delivery Optimization metadata file hosting | CDN hostnames for Delivery Optimization content metadata files | Metadata download can come from different hostnames, but it's required for peer to peer. | +|--------------------------------------------|--------|---------------|-----------------------|------------------------ +| geover-prod.do.dsp.mp.microsoft.com
geo-prod.do.dsp.mp.microsoft.com
geo.prod.do.dsp.mp.microsoft.com
geover.prod.do.dsp.mp.microsoft.com | 443 | Geo | Service used to identify the location of the device in order to direct it to the nearest data center. | **Profile**: The device type (for example, PC or Xbox)
**doClientVersion**: The version of the DoSvc client
**groupID**: Group the device belongs to (set with DownloadMode = '2' (Group download mode) + groupID group policy / MDM policies) +| kv\*.prod.do.dsp.mp.microsoft.com | 443| KeyValue | Bootstrap service provides endpoints for all other services and device configs. | **countryCode**: The country or region the client is connected from
**doClientVersion**: The version of the DoSvc client
**Profile**: The device type (for example, PC or Xbox)
**eId**: Client grouping ID
**CacheHost**: Cache host ID +| cp\*.prod.do.dsp.mp.microsoft.com
| 443 | Content Policy | Provides content specific policies and as content metadata URLs. | **Profile**: The device type (for example, PC or Xbox)
**ContentId**: The content identifier
**doClientVersion**: The version of the DoSvc client
**countryCode**: The country the client is connected from
**altCatalogID**: If ContentID isn't available, use the download URL instead
**eID**: Client grouping ID
**CacheHost**: Cache host ID +| disc\*.prod.do.dsp.mp.microsoft.com | 443 | Discovery | Directs clients to a particular instance of the peer matching service (Array), ensuing that clients are collocated by factors, such as content, groupID and external IP. | **Profile**: The device type (for example, PC or Xbox)
**ContentID**: The content identifier
**doClientVersion**: The version of the DoSvc client
**partitionID**: Client partitioning hint
**altCatalogID**: If ContentID isn't available, use the download URL instead
**eID**: Client grouping ID +| array\*.prod.do.dsp.mp.microsoft.com | 443 | Arrays | Provides the client with list of peers that have the same content and belong to the same peer group. | **Profile**: The device type (for example, PC or Xbox)
**ContentID**: The content identifier
**doClientVersion**: The version of the DoSvc client
**altCatalogID**: If ContentID isn't available, use the download URL instead
**PeerID**: Identity of the device running DO client
**ReportedIp**: The internal / private IP Address
**IsBackground**: Is the download interactive or background
**Uploaded**: Total bytes uploaded to peers
**Downloaded**: Total bytes downloaded from peers
**DownloadedCdn**: Total bytes downloaded from CDN
**Left**: Bytes left to download
**Peers Wanted**: Total number of peers wanted
**Group ID**: Group the device belongs to (set via DownloadMode 2 + Group ID GP / MDM policies)
**Scope**: The Download mode
**UploadedBPS**: The upload speed in bytes per second
**DownloadBPS**: The download speed in Bytes per second
**eID**: Client grouping ID +| dl.delivery.mp.microsoft.com
emdl.ws.microsoft.com
download.windowsupdate.com | 80 | Delivery Optimization metadata file hosting | CDN hostnames for Delivery Optimization content metadata files | Metadata download can come from different hostnames, but it's required for peer to peer. diff --git a/windows/deployment/do/index.yml b/windows/deployment/do/index.yml index 03b2ddc0ac..d4f3409ae7 100644 --- a/windows/deployment/do/index.yml +++ b/windows/deployment/do/index.yml @@ -103,4 +103,5 @@ landingContent: url: delivery-optimization-endpoints.md - text: Testing Delivery Optimization url: delivery-optimization-test.md - + - text: Delivery Optimization Troubleshooter + url: http://aka.ms/do-fix diff --git a/windows/deployment/do/mcc-ent-edu-overview.md b/windows/deployment/do/mcc-ent-edu-overview.md index a6b4c0afed..b17beaa30a 100644 --- a/windows/deployment/do/mcc-ent-edu-overview.md +++ b/windows/deployment/do/mcc-ent-edu-overview.md @@ -13,12 +13,13 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for Enterprise and Education -ms.date: 05/09/2023 +ms.date: 05/23/2024 --- # Microsoft Connected Cache for Enterprise and Education Overview > [!IMPORTANT] +> > - Microsoft Connected Cache is currently a preview feature. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). > - As we near the release of public preview, we have paused onboarding. Please continue to submit the form to express interest so we can follow up with you once public preview of Microsoft Connected Cache for Enteprise and Education is available. To register your interest, fill out the form located at [https://aka.ms/MSConnectedCacheSignup](https://aka.ms/MSConnectedCacheSignup). diff --git a/windows/deployment/do/mcc-enterprise-appendix.md b/windows/deployment/do/mcc-enterprise-appendix.md index 9add17a1be..e755879ed3 100644 --- a/windows/deployment/do/mcc-enterprise-appendix.md +++ b/windows/deployment/do/mcc-enterprise-appendix.md @@ -15,7 +15,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for Enterprise and Education -ms.date: 11/07/2023 +ms.date: 05/23/2024 --- # Appendix @@ -28,7 +28,8 @@ ms.date: 11/07/2023 ### Troubleshooting If you're not able to sign up for a Microsoft Azure subscription with the **Account belongs to a directory that cannot be associated with an Azure subscription. Please sign in with a different account.** error, see the following articles: -- [Can't sign up for a Microsoft Azure subscription](/troubleshoot/azure/general/cannot-sign-up-subscription). + +- [Can't sign up for a Microsoft Azure subscription](/troubleshoot/azure/general/cannot-sign-up-subscription). - [Troubleshoot issues when you sign up for a new account in the Azure portal](/azure/cost-management-billing/manage/troubleshoot-azure-sign-up). ## Hardware specifications @@ -91,14 +92,14 @@ There are multiple methods that can be used to apply a policy to PCs that should You can either set your MCC IP address or FQDN using: -1. Registry key (version 1709 and later): +1. Registry key (version 1709 and later): `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization`
"DOCacheHost"=" " - + From an elevated command prompt: - ``` +```powershell reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v DOCacheHost /t REG_SZ /d "10.137.187.38" /f ``` @@ -110,7 +111,6 @@ You can either set your MCC IP address or FQDN using: :::image type="content" source="./images/ent-mcc-group-policy-hostname.png" alt-text="Screenshot of the Group Policy editor showing the Cache Server Hostname Group Policy setting." lightbox="./images/ent-mcc-group-policy-hostname.png"::: - ## Verify content using the DO client To verify that the Delivery Optimization client can download content using MCC, you can use the following steps: @@ -119,7 +119,6 @@ To verify that the Delivery Optimization client can download content using MCC, :::image type="content" source="./images/ent-mcc-store-example-download.png" alt-text="Screenshot of the Microsoft Store with the game, Angry Birds 2, selected."::: - 1. Verify downloads came from MCC by one of two methods: - Using the PowerShell Cmdlet Get-DeliveryOptimizationStatus you should see *BytesFromCacheServer*. diff --git a/windows/deployment/do/mcc-enterprise-deploy.md b/windows/deployment/do/mcc-enterprise-deploy.md index b2883ad2fd..8ddf51a732 100644 --- a/windows/deployment/do/mcc-enterprise-deploy.md +++ b/windows/deployment/do/mcc-enterprise-deploy.md @@ -1,6 +1,6 @@ --- title: Deploying your cache node -description: How to deploy a Microsoft Connected Cache (MCC) for Enterprise and Education cache node from the Auzre portal. +description: How to deploy a Microsoft Connected Cache (MCC) for Enterprise and Education cache node from the Azure portal. ms.service: windows-client ms.subservice: itpro-updates ms.topic: how-to @@ -13,7 +13,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for Enterprise and Education -ms.date: 11/09/2023 +ms.date: 05/23/2024 --- # Deploy your cache node @@ -24,18 +24,28 @@ This article describes how to deploy a Microsoft Connected Cache (MCC) for Enter To deploy MCC to your server: -1. [Provide Microsoft with the Azure subscription ID](#provide-microsoft-with-the-azure-subscription-id) -1. [Create the MCC Resource in Azure](#create-the-mcc-resource-in-azure) -1. [Create an MCC Node](#create-an-mcc-node-in-azure) -1. [Edit Cache Node Information](#edit-cache-node-information) -1. [Install MCC on a physical server or VM](#install-mcc-on-windows) -1. [Verify MCC functionality](#verify-mcc-server-functionality) -1. [Review common Issues](#common-issues) if needed. - +- [Deploy your cache node](#deploy-your-cache-node) + - [Steps to deploy MCC](#steps-to-deploy-mcc) + - [Provide Microsoft with the Azure subscription ID](#provide-microsoft-with-the-azure-subscription-id) + - [Create the MCC resource in Azure](#create-the-mcc-resource-in-azure) + - [Error: Validation failed](#error-validation-failed) + - [Create an MCC node in Azure](#create-an-mcc-node-in-azure) + - [Edit cache node information](#edit-cache-node-information) + - [Install MCC on Windows](#install-mcc-on-windows) + - [Run the installer](#run-the-installer) + - [Verify MCC server functionality](#verify-mcc-server-functionality) + - [Verify client side](#verify-client-side) + - [Verify server side](#verify-server-side) + - [Intune (or other management software) configuration for MCC](#intune-or-other-management-software-configuration-for-mcc) + - [Common Issues](#common-issues) + - [PowerShell issues](#powershell-issues) + - [Verify Running MCC Container](#verify-running-mcc-container) + - [DNS needs to be configured](#dns-needs-to-be-configured) + - [Resolve DNS issues](#resolve-dns-issues) ### Provide Microsoft with the Azure subscription ID -As part of the MCC preview onboarding process an Azure subscription ID must be provided to Microsoft. +As part of the MCC preview onboarding process an Azure subscription ID must be provided to Microsoft. > [!IMPORTANT] > As we near the release of public preview, we have paused onboarding. Please continue to submit the form to express interest so we can follow up with you once public preview of Microsoft Connected Cache for Enteprise and Education is available. To register your interest, fill out the form located at [https://aka.ms/MSConnectedCacheSignup](https://aka.ms/MSConnectedCacheSignup). @@ -44,9 +54,9 @@ For information about creating or locating your subscription ID, see [Steps to o ### Create the MCC resource in Azure -The MCC Azure management portal is used to create and manage MCC nodes. An Azure subscription ID is used to grant access to the preview and to create the MCC resource in Azure and Cache nodes. +The MCC Azure management portal is used to create and manage MCC nodes. An Azure subscription ID is used to grant access to the preview and to create the MCC resource in Azure and Cache nodes. -Once you take the survey above and the MCC team adds your subscription ID to the allowlist, you'll be given a link to the Azure portal where you can create the resource described below. +Once you take the survey above and the MCC team adds your subscription ID to the allowlist, you'll be given a link to the Azure portal where you can create the resource described below. 1. In the Azure portal home page, choose **Create a resource**: :::image type="content" source="./images/ent-mcc-create-azure-resource.png" alt-text="Screenshot of the Azure portal. The create a resource option is outlined in red."::: @@ -201,7 +211,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p If you restarted your computer after creating a switch, start from step 2 above and skip to step 5. - If you opt to use an existing external switch, select the switch from the presented options. Local Area Connection (or USB) is preferable to Wi-Fi. + If you opt to use an existing external switch, select the switch from the presented options. Local Area Connection (or USB) is preferable to Wi-Fi. :::image type="content" source="./images/ent-mcc-script-new-switch.png" alt-text="Screenshot of the installer script running in PowerShell when a new switch is created." lightbox="./images/ent-mcc-script-new-switch.png"::: @@ -221,12 +231,12 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p :::image type="content" source="./images/external-switch-1.jpg" alt-text="Screenshot of a sample output of ipconfig command showing example of subnet mask." lightbox="./images/external-switch-1.jpg"::: :::image type="content" source="./images/assigning-ip-2.png" alt-text="Screenshot of multiple installer questions about ipv4 address for Eflow." lightbox="./images/assigning-ip-2.png"::: - + If you would like to use your own DNS server instead of Google DNS 8.8.8.8, select **n** and set your own DNS server IP. :::image type="content" source="./images/use-custom-dns-3.png" alt-text="Screenshot of multiple installer questions about setting an alternate DNS server." lightbox="./images/use-custom-dns-3.png"::: - If you use a dynamic IP address, the DHCP server will automatically configure the IP address and DNS settings. - -1. Choose where you would like to download, install, and store the virtual hard disk for EFLOW. You'll also be asked how much memory, storage, and how many cores you would like to allocate for the VM. For this example, we chose the default values for download path, install path, and virtual hard disk path. + If you use a dynamic IP address, the DHCP server will automatically configure the IP address and DNS settings. + +1. Choose where you would like to download, install, and store the virtual hard disk for EFLOW. You'll also be asked how much memory, storage, and how many cores you would like to allocate for the VM. For this example, we chose the default values for download path, install path, and virtual hard disk path. :::image type="content" source="./images/installation-info-4.png" alt-text="Screenshot of multiple installer questions about memory and storage for EFLOW." lightbox="./images/installation-info-4.png"::: For more information, see [Sizing Recommendations](mcc-enterprise-prerequisites.md#sizing-recommendations) for memory, virtual storage, and CPU cores. For this example we chose the recommend values for a Branch Office/Small Enterprise deployment. @@ -238,7 +248,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p :::image type="content" source="./images/ent-mcc-script-select-hub.png" alt-text="Screenshot of the installer script running in PowerShell prompting you to select which IoT Hub to use." lightbox="./images/ent-mcc-script-select-hub.png"::: --> -1. When the installation is complete, you should see the following output (the values below will be your own) +1. When the installation is complete, you should see the following output (the values below will be your own) :::image type="content" source="./images/ent-mcc-script-complete.png" alt-text="Screenshot of the installer script displaying the completion summary in PowerShell." lightbox="./images/ent-mcc-script-complete.png"::: :::image type="content" source="./images/installation-complete-7.png" alt-text="Screenshot of expected output when installation is complete." lightbox="./images/installation-complete-7.png"::: @@ -267,10 +277,12 @@ Connect to the EFLOW VM and check if MCC is properly running: You should see MCC, edgeAgent, and edgeHub running. If you see edgeAgent or edgeHub but not MCC, try this command in a few minutes. The MCC container can take a few minutes to deploy. If iotedge list times out, you can run docker ps -a to list the running containers. If the 3 containers are still not running, run the following commands to check if DNS resolution is working correctly: + ```bash ping www.microsoft.com resolvectl query microsoft.com ``` + See the [common issues](#common-issues) section for more information. #### Verify server side @@ -336,7 +348,6 @@ This command will provide the current status of the starting, stopping of a cont :::image type="content" source="./images/ent-mcc-journalctl.png" alt-text="Screenshot of the output from journalctl -u iotedge -f." lightbox="./images/ent-mcc-journalctl.png"::: - > [!NOTE] > You should consult the IoT Edge troubleshooting guide ([Common issues and resolutions for Azure IoT Edge](/azure/iot-edge/troubleshoot)) for any issues you may encounter configuring IoT Edge, but we've listed a few issues that we encountered during our internal validation. > @@ -394,14 +405,14 @@ To configure the device to work with your DNS, use the following steps: ``` ### Resolve DNS issues + Follow these steps if you see a DNS error when trying to resolve hostnames during the provisioning or download of container: Run ``` Get-EflowVmEndpoint ``` to get interface name -Once you get the name +Once you get the name + ```bash Set-EflowVmDNSServers -vendpointName "interface name from above" -dnsServers @("DNS_IP_ADDRESS") Stop-EflowVm Start-EflowVm ``` - - diff --git a/windows/deployment/do/mcc-enterprise-prerequisites.md b/windows/deployment/do/mcc-enterprise-prerequisites.md index 0671eba29f..1e33e85158 100644 --- a/windows/deployment/do/mcc-enterprise-prerequisites.md +++ b/windows/deployment/do/mcc-enterprise-prerequisites.md @@ -13,7 +13,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - - ✅ Microsoft Connected Cache for Enterprise and Education -ms.date: 11/07/2023 +ms.date: 05/23/2024 --- # Requirements of Microsoft Connected Cache for Enterprise and Education (early preview) diff --git a/windows/deployment/do/mcc-enterprise-update-uninstall.md b/windows/deployment/do/mcc-enterprise-update-uninstall.md index b36d56df66..7f09c9c9a5 100644 --- a/windows/deployment/do/mcc-enterprise-update-uninstall.md +++ b/windows/deployment/do/mcc-enterprise-update-uninstall.md @@ -15,7 +15,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for Enterprise and Education -ms.date: 10/12/2022 +ms.date: 05/23/2024 --- [!INCLUDE [Get Azure subscription](includes/get-azure-subscription.md)] - ### Performance of MCC in virtual environments In virtual environments, the cache server egress peaks at around 1.1 Gbps. If you want to maximize the egress in virtual environments, it's critical to change the following two settings: diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index 73a6691166..af0a3d0fd2 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -17,7 +17,7 @@ metadata: - ✅ Windows 10 - ✅ Windows Server 2019, and later - ✅ Delivery Optimization - ms.date: 02/16/2024 + ms.date: 05/23/2024 title: Frequently Asked Questions about Delivery Optimization summary: | This article answers frequently asked questions about Delivery Optimization. @@ -38,7 +38,7 @@ summary: | - [My firewall requires IP addresses and can't process FQDNs. How do I configure it to download content with Delivery Optimization?How do I configure it to download content with Delivery Optimization?](#my-firewall-requires-ip-addresses-and-can-t-process-fqdns--how-do-i-configure-it-to-download-content-with-delivery-optimization) - [What is the recommended configuration for Delivery Optimization used with cloud proxies?](#what-is-the-recommended-configuration-for-delivery-optimization-used-with-cloud-proxies) - **Peer-to-Peer related questions**: + **Peer-to-peer related questions**: - [How does Delivery Optimization determine which content is available for peering?](#how-does-delivery-optimization-determine-which-content-is-available-for-peering) - [Does Delivery Optimization use multicast?](#does-delivery-optimization-use-multicast) diff --git a/windows/deployment/do/waas-delivery-optimization-monitor.md b/windows/deployment/do/waas-delivery-optimization-monitor.md index a41d6159c2..bc2e0b442b 100644 --- a/windows/deployment/do/waas-delivery-optimization-monitor.md +++ b/windows/deployment/do/waas-delivery-optimization-monitor.md @@ -16,14 +16,14 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Delivery Optimization -ms.date: 08/13/2023 +ms.date: 05/23/2024 --- # Monitor Delivery Optimization To monitor Delivery Optimization, you can use either the Windows Update for Business Delivery Optimization Report or Windows PowerShell cmdlets. -## Monitor with Windows Update for Business Delivery Optimization Report +## Monitor with Windows Update for Business Delivery Optimization report Windows Update for Business Delivery Optimization Report provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer, Microsoft Connected Cache (MCC), HTTP source/CDN distribution over the past 28 days. @@ -47,10 +47,10 @@ For details, see [Windows Update for Business Delivery Optimization Report](/win | TotalBytesDownloaded | The number of bytes from any source downloaded so far | | PercentPeerCaching |The percentage of bytes downloaded from peers versus over HTTP | | BytesFromPeers | Total bytes downloaded from peer devices (sum of bytes downloaded from LAN, Group, and Internet Peers) | -| BytesfromHTTP | Total number of bytes received over HTTP. This metric represents all HTTP sources, **which includes BytesFromCacheServer** | +| BytesFromHTTP | Total number of bytes received over HTTP. This metric represents all HTTP sources, **which includes BytesFromCacheServer** | | Status | Current state of the operation. Possible values are: **Downloading** (download in progress); **Complete** (download completed, but isn't uploading yet); **Caching** (download completed successfully and is ready to upload or uploading); **Paused** (download/upload paused by caller) | | Priority | Priority of the download; values are **foreground** or **background** | -| BytesFromCacheServer | Total number of bytes received from cache server (MCC) | +| BytesFromCacheServer | Total number of bytes received from cache Bserver (MCC) | | BytesFromLanPeers | Total number of bytes received from peers found on the LAN | | BytesFromGroupPeers | Total number of bytes received from peers found in the group. (Note: Group mode is LAN + Group. If peers are found on the LAN, those bytes are registered in 'BytesFromLANPeers'.) | | BytesFromInternetPeers | Total number of bytes received from internet peers | @@ -58,17 +58,17 @@ For details, see [Windows Update for Business Delivery Optimization Report](/win | BytesToGroupPeers | Total number of bytes delivered from peers found in the group | | BytesToInternetPeers | Total number of bytes delivered from peers found on the LAN | | DownloadDuration | Total download time in seconds | -| HttpConnectionCount | | -| LanConnectionCount | | -| GroupConnectionCount | | -| InternetConnectionCount | | -| DownloadMode | | +| HttpConnectionCount | Number of connections to HTTP source | +| LanConnectionCount | Number of connections to LAN peer connections | +| GroupConnectionCount | Number of connections to Group peer connections | +| InternetConnectionCount | Number of connections to Internet peer connections | +| DownloadMode | Delivery Optimization DownloadMode value | | SourceURL | Http source for the file | | CacheHost | IP address for the cache server | | NumPeers | Indicates the total number of peers returned from the service. | | PredefinedCallerApplication | Indicates the last caller that initiated a request for the file. | | ExpireOn | The target expiration date and time for the file. | -| IsPinned | A yes/no value indicating whether an item has been "pinned" in the cache (see `setDeliveryOptmizationStatus`). | +| IsPinned | A yes/no value indicating whether an item has been "pinned" in the cache (see `setDeliveryOptimizationStatus`). | `Get-DeliveryOptimizationPerfSnap` returns a list of key performance data: @@ -76,40 +76,38 @@ For details, see [Windows Update for Business Delivery Optimization Report](/win | --- | --- | | FilesDownloaded | Number of files downloaded | | FilesUploaded | Number of files uploaded | -| Files | | +| Files | Number of files available in the Delivery Optimization cache | | TotalBytesDownloaded | Total bytes downloaded | | TotalBytesUploaded | Total bytes uploaded | | AverageDownloadSize | Average transfer size (download); that is, the number bytes downloaded divided by the number of files | | AverageUploadSize | Average transfer size (upload); the number of bytes uploaded divided by the number of files | -| DownloadMode | Delivery Optimization Download mode used to deliver file | -| CacheSizeBytes | | -| TotalDiskBytes | | -| AvailableDiskBytes | | -| CpuUsagePct | | -| MemUsageKB | | -| NumberOfPeers | | -| CacheHostConnections | | -| CdnConnections | | -| LanConnections | | -| LinkLocalConnections | | -| GroupConnections | | -| InternetConnections | | -| DownlinkBps | | -| DownlinkUsageBps | | -| UplinkBps | | -| UplinkUsageBps | | -| ForegroundDownloadRatePct | | -| BackgroundDownloadRatePct | | -| UploadRatePct | | -| UplinkUsageBps | | -| ForegroundDownloadRatePct | | -| BackgroundDownloadRatePct | | -| UploadRatePct | | -| UploadCount | | -| ForegroundDownloadCount | | -| ForegroundDownloadsPending | | -| BackgroundDownloadCount | | -| BackgroundDownloadsPending | | +| DownloadMode | Delivery Optimization Download mode configured for this device | +| CacheSizeBytes | Total disk space occupied by downloaded files in Delivery Optimization cache | +| TotalDiskBytes | Total space of the disk volume on which Delivery Optimization cache is currently located | +| AvailableDiskBytes | Free space of the disk volume on which Delivery Optimization cache is currently located | +| CpuUsagePct | Average CPU usage by the Delivery Optimization process | +| MemUsageKB | Amount of committed memory currently used by the Delivery Optimization process | +| NumberOfPeers | Total number of peers used found across all files currently in the cache | +| CacheHostConnections | Number of cache host server connections | +| CdnConnections | Number of CDN server connections | +| LanConnections | Number of LAN connections | +| LinkLocalConnections | Number of Link Local connections | +| GroupConnections | Number of Group connections | +| InternetConnections | Number of Internet connections | +| DownlinkBps | Average download bandwidth usage currently seen across all network adapters | +| DownlinkUsageBps | Average bandwidth currently used by Delivery Optimization for downloads | +| UplinkBps | Average bytes per second for upload events | +| UplinkUsageBps | Average bandwidth currently used by Delivery Optimization for uploads | +| ForegroundDownloadRatePct | Average foreground download percentage rate | +| BackgroundDownloadRatePct | Average background download percentage rate | +| UploadRatePct | Percentage of upload bandwidth to be used for uploads | +| ForegroundDownloadRatePct | Average foreground download from start of the month | +| BackgroundDownloadRatePct | Average background download from start of the month | +| UploadCount | Number of files in Delivery Optimization cache currently eligible for uploading | +| ForegroundDownloadCount | Number of foreground downloads that are running | +| ForegroundDownloadsPending | Number of foreground downloads that are waiting in queue | +| BackgroundDownloadCount | Number of background downloads that are running | +| BackgroundDownloadsPending | Number of background downloads that are waiting in queue | Using the `-Verbose` option returns additional information: @@ -188,7 +186,6 @@ If `Path` isn't specified, this cmdlet reads all logs from the DoSvc log directo Log entries are written to the PowerShell pipeline as objects. To dump logs to a text file, run `Get-DeliveryOptimizationLog | Set-Content ` or something similar. - **Starting in Windows 10, version 1803:** `Get-DOConfig -Verbose` @@ -198,7 +195,7 @@ This cmdlet lists local configuration and policies that are applied to Delivery DownloadMode:Simple DownloadModeProvider:Mdm Provider -The provider is listed as "Default Provider" if it's using the Delivery Optimization platform configured default. +The provider is listed as "Default Provider" if it's using the Delivery Optimization platform configured default. The cmdlet returns the following data: @@ -217,4 +214,3 @@ The cmdlet returns the following data: - DownloadForegroundLimitPct: Corresponds to the [DOPercentageMaxForegroundBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth) policy. - MaxUploadRatePct: Corresponds to the [DOMaxUploadBandwidth](waas-delivery-optimization-reference.md#max-upload-bandwidth) policy (deprecated in Windows 10, version 2004). - UploadLimitMonthlyGB: Corresponds to the [DOMonthlyUploadDataCap](waas-delivery-optimization-reference.md#monthly-upload-data-cap) policy. - diff --git a/windows/deployment/do/waas-delivery-optimization-reference.md b/windows/deployment/do/waas-delivery-optimization-reference.md index 6cfadc06b1..f641968b07 100644 --- a/windows/deployment/do/waas-delivery-optimization-reference.md +++ b/windows/deployment/do/waas-delivery-optimization-reference.md @@ -14,7 +14,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Delivery Optimization -ms.date: 02/14/2024 +ms.date: 05/23/2024 --- # Delivery Optimization reference @@ -42,27 +42,27 @@ In MDM, the same settings are under **.Vendor/MSFT/Policy/Config/DeliveryOptimiz | [Minimum disk size allowed to use peer caching](#minimum-disk-size-allowed-to-use-peer-caching) | DOMinDiskSizeAllowedToPeer | 1703 | Default value is 32 GB. | | [Max cache age](#max-cache-age) | DOMaxCacheAge | 1511 | Default value is 259,200 seconds (three days). | | [Max cache size](#max-cache-size) | DOMaxCacheSize | 1511 | Default value is 20%. | -| [Absolute max cache size (in GBs)](#absolute-max-cache-size) | DOAbsoluteMaxCacheSize | 1607 | Default value is 10 GB.| +| [Absolute max cache size (in GBs)](#absolute-max-cache-size) | DOAbsoluteMaxCacheSize | 1607 | Default is not configured.| | [Modify cache drive](#modify-cache-drive) | DOModifyCacheDrive | 1607 | Default to the operating system drive through the %SYSTEMDRIVE% environment variable. | | [Minimum peer caching content file size](#minimum-peer-caching-content-file-size) | DOMinFileSizeToCache | 1703 | Default file size is 50 MB. | | [Monthly upload data cap](#monthly-upload-data-cap) | DOMonthlyUploadDataCap | 1607 | Default value is 20 GB. | | [Minimum background QoS](#minimum-background-qos) | DOMinBackgroundQoS | 1607 | Recommend setting this to 500 KB/s. Default value is 2500 KB/s. | | [Enable peer caching while the device connects via VPN](#enable-peer-caching-while-the-device-connects-via-vpn) | DOAllowVPNPeerCaching | 1709 | Default is to not allow peering while on VPN. | -| [VPN Keywords](#vpn-keywords) | DOVpnKeywords | 22H2 September Moment | Allows you to set one or more keywords used to recognize VPN connections. | -| [Disallow Cache Server Downloads from VPN](#disallow-cache-server-downloads-on-vpn) | DODisallowCacheServerDownloadsOnVPN | 22H2 September Moment | Disallow downloads from Microsoft Connected Cache servers when the device connects via VPN. By default, the device is allowed to download from Microsoft Connected Cache when connected via VPN. | +| [VPN keywords](#vpn-keywords) | DOVpnKeywords | 22H2 September Moment | Allows you to set one or more keywords used to recognize VPN connections. | +| [Disallow cache server downloads from VPN](#disallow-cache-server-downloads-on-vpn) | DODisallowCacheServerDownloadsOnVPN | 22H2 September Moment | Disallow downloads from Microsoft Connected Cache servers when the device connects via VPN. By default, the device is allowed to download from Microsoft Connected Cache when connected via VPN. | | [Allow uploads while the device is on battery while under set battery level](#allow-uploads-while-the-device-is-on-battery-while-under-set-battery-level) | DOMinBatteryPercentageAllowedToUpload | 1709 | Default is to not allow peering while on battery. | | [Maximum foreground download bandwidth (percentage)](#maximum-foreground-download-bandwidth) | DOPercentageMaxForegroundBandwidth | 1803 | Default is '0' which will dynamically adjust. | | [Maximum background download bandwidth (percentage)](#maximum-background-download-bandwidth) | DOPercentageMaxBackgroundBandwidth | 1803 | Default is '0' which will dynamically adjust. | | [Maximum foreground download bandwidth (in KB/s)](#maximum-foreground-download-bandwidth-in-kbs) | DOMaxForegroundDownloadBandwidth | 2004 | Default is '0' which will dynamically adjust. | | [Maximum background download bandwidth (in KB/s)](#maximum-background-download-bandwidth-in-kbs) | DOMaxBackgroundDownloadBandwidth | 2004 | Default is '0' which will dynamically adjust. | -| [Set hours to limit background download bandwidth](#set-business-hours-to-limit-background-download-bandwidth) | DOSetHoursToLimitBackgroundDownloadBandwidth | 1803 | Default isn't set. | -| [Set hours to limit foreground download bandwidth](#set-business-hours-to-limit-foreground-download-bandwidth) |DOSetHoursToLimitForegroundDownloadBandwidth | 1803 | Default isn't set. | -| [Delay background download from HTTP (in secs)](#delay-background-download-from-http-in-secs) | DODelayBackgroundDownloadFromHttp | 1803 | Default isn't set. For peering, use this policy to delay the fallback to the HTTP source. [Learn more](#policies-to-prioritize-the-use-of-peer-to-peer-and-cache-server-sources) about the different delay options. | -| [Delay foreground download from HTTP (in secs)](#delay-foreground-download-from-http-in-secs) | DODelayForegroundDownloadFromHttp | 1803 | Default isn't set. For peering, use this policy to delay the fallback to the HTTP source. [Learn more](#policies-to-prioritize-the-use-of-peer-to-peer-and-cache-server-sources) about the different delay options.| -| [Delay background download Cache Server fallback (in secs)](#delay-background-download-cache-server-fallback-in-secs) | DelayCacheServerFallbackBackground | 1903 | Default isn't set. For Microsoft Connected Cache content, use this policy to delay the fallback to the HTTP source. [Learn more](#policies-to-prioritize-the-use-of-peer-to-peer-and-cache-server-sources) about the different delay options.| -| [Delay foreground download Cache Server fallback (in secs)](#delay-foreground-download-cache-server-fallback-in-secs) | DelayCacheServerFallbackForeground | 1903 | Default isn't set. For Microsoft Connected Cache content, use this policy to delay the fallback to the HTTP source. [Learn more](#policies-to-prioritize-the-use-of-peer-to-peer-and-cache-server-sources) about the different delay options. | -| [Cache Server Hostname](#cache-server-hostname) | DOCacheHost | 1809 | No value is set as default. | -| [Cache Server Hostname Source](#cache-server-hostname-source) | DOCacheHostSource | 2004 | No value is set as default. | +| [Set hours to limit foreground download bandwidth](#set-business-hours-to-limit-foreground-download-bandwidth) |DOSetHoursToLimitForegroundDownloadBandwidth | 1803 | Default isn't configured. | +| [Set hours to limit background download bandwidth](#set-business-hours-to-limit-background-download-bandwidth) | DOSetHoursToLimitBackgroundDownloadBandwidth | 1803 | Default isn't configured. | +| [Delay foreground download from HTTP (in secs)](#delay-foreground-download-from-http-in-secs) | DODelayForegroundDownloadFromHttp | 1803 | Default isn't configured. For peering, use this policy to delay the fallback to the HTTP source. [Learn more](#policies-to-prioritize-the-use-of-peer-to-peer-and-cache-server-sources) about the different delay options.| +| [Delay background download from HTTP (in secs)](#delay-background-download-from-http-in-secs) | DODelayBackgroundDownloadFromHttp | 1803 | Default isn't configured. For peering, use this policy to delay the fallback to the HTTP source. [Learn more](#policies-to-prioritize-the-use-of-peer-to-peer-and-cache-server-sources) about the different delay options. | +| [Delay foreground download cache server fallback (in secs)](#delay-foreground-download-cache-server-fallback-in-secs) | DelayCacheServerFallbackForeground | 1903 | Default isn't configured. For Microsoft Connected Cache content, use this policy to delay the fallback to the HTTP source. [Learn more](#policies-to-prioritize-the-use-of-peer-to-peer-and-cache-server-sources) about the different delay options. | +| [Delay background download cache server fallback (in secs)](#delay-background-download-cache-server-fallback-in-secs) | DelayCacheServerFallbackBackground | 1903 | Default isn't configured. For Microsoft Connected Cache content, use this policy to delay the fallback to the HTTP source. [Learn more](#policies-to-prioritize-the-use-of-peer-to-peer-and-cache-server-sources) about the different delay options.| +| [Cache server hostname](#cache-server-hostname) | DOCacheHost | 1809 | No value is set as default. | +| [Cache server hostname source](#cache-server-hostname-source) | DOCacheHostSource | 2004 | No value is set as default. | | [Maximum download bandwidth](#maximum-download-bandwidth) | DOMaxDownloadBandwidth | 1607 (deprecated in Windows 10, version 2004); use [Maximum background download bandwidth (in KB/s)](#maximum-background-download-bandwidth-in-kbs) or [Maximum foreground download bandwidth (in KB/s)](#maximum-foreground-download-bandwidth-in-kbs) instead)| Default is '0' which will dynamically adjust. | | [Percentage of maximum download bandwidth](#percentage-of-maximum-download-bandwidth) | DOPercentageMaxDownloadBandwidth | 1607 (deprecated in Windows 10, version 2004); use [Maximum background download bandwidth (in KB/s)](#maximum-background-download-bandwidth-in-kbs) or [Maximum foreground download bandwidth (in KB/s)](#maximum-foreground-download-bandwidth-in-kbs) instead)| Default is '0' which will dynamically adjust. | | [Maximum upload bandwidth](#max-upload-bandwidth) | DOMaxUploadBandwidth | 1607 (deprecated in Windows 10, version 2004) | Default is '0' (unlimited). | @@ -73,14 +73,14 @@ In MDM, the same settings are under **.Vendor/MSFT/Policy/Config/DeliveryOptimiz Delivery Optimization uses locally cached updates to deliver contact via peers. The more content available in the cache, the more likely that peering can be used. In cases where devices have enough local storage and you'd like to cache more content. Likewise, if you have limited storage and would prefer to cache less, use the following settings to adjust the Delivery Optimization cache to suit your scenario: -- [Max Cache Size](#max-cache-size) and [Absolute Max Cache Size](#absolute-max-cache-size) control the amount of space the Delivery Optimization cache can use. -- [Max Cache Age](#max-cache-age) controls the retention period for each update in the cache. -- The system drive is the default location for the Delivery Optimization cache. [Modify Cache Drive](#modify-cache-drive) allows administrators to change that location. +- [DOMaxCacheSize](#max-cache-size) and [DOAbsoluteMaxCacheSize](#absolute-max-cache-size) control the amount of space the Delivery Optimization cache can use. +- [DOMaxCacheAge](#max-cache-age) controls the retention period for each update in the cache. +- The system drive is the default location for the Delivery Optimization cache. [DOModifyCacheDrive](#modify-cache-drive) allows administrators to change that location. >[!NOTE] ->It is possible to configure preferred cache devices. For more information, see [Group ID](#group-id). +>It is possible to configure preferred cache devices. For more information, see [DOGroupID](#group-id). -All cached files have to be above a set minimum size. This size is automatically set by the Delivery Optimization cloud services, but when local storage is sufficient and the network isn't strained or congested, administrators might choose to change it to obtain increased performance. You can set the minimum size of files to cache by adjusting [Minimum Peer Caching Content File Size](#minimum-peer-caching-content-file-size). +All cached files have to be above a set minimum size. This size is automatically set by the Delivery Optimization cloud services, but when local storage is sufficient and the network isn't strained or congested, administrators might choose to change it to obtain increased performance. You can set the minimum size of files to cache by adjusting [DOMinFileSizeToCache](#minimum-peer-caching-content-file-size). #### Impact to network @@ -94,7 +94,7 @@ More options available that control the impact Delivery Optimization has on your - [Select a method to restrict Peer Selection](#select-a-method-to-restrict-peer-selection) restricts peer selection by the options you select. - [Select the source of Group IDs](#select-the-source-of-group-ids) restricts peer selection to a specific source. -#### Policies to prioritize the use of Peer-to-Peer and Cache Server sources +#### Policies to prioritize the use of peer-to-peer and cache server sources When Delivery Optimization client is configured to use peers and Microsoft Connected Cache (MCC), to achieve the best possible content delivery experience, the client connects to both MCC and peers in parallel. If the desired content can't be obtained from MCC or peers, Delivery Optimization will automatically fallback to the HTTP source to get the requested content. There are four settings that allow you to prioritize peer-to-peer or MCC sources by delaying the immediate fallback to HTTP source, which is the default behavior. @@ -105,7 +105,7 @@ When Delivery Optimization client is configured to use peers and Microsoft Conne ##### Microsoft Connected Cache (MCC) delay fallback settings -- [Delay foreground download Cache Server fallback (in secs)](#delay-foreground-download-cache-server-fallback-in-secs) allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use a cache server. +- [Delay foreground download cache server fallback (in secs)](#delay-foreground-download-cache-server-fallback-in-secs) allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use a cache server. - [Delay background download from HTTP (in secs)](#delay-background-download-from-http-in-secs) allows you to delay the use of an HTTP source in a background download that is allowed to use a cache server. **If both peer-to-peer and MCC are configured, the peer-to-peer delay settings will take precedence over the cache server delay settings.** This setting allows Delivery Optimization to discover peers first then recognize the fallback setting for the MCC cache server. @@ -161,15 +161,15 @@ Starting in Windows 10, version 1803, set this policy to restrict peer selection - 4 = DNS Suffix - 5 = Starting with Windows 10, version 1903, you can use the Microsoft Entra tenant ID as a means to define groups. To do this set the value for DOGroupIdSource to its new maximum value of 5. -When set, the Group ID will be assigned automatically from the selected source. This policy is ignored if the GroupID policy is also set. The default behavior, when the GroupID or GroupIDSource policies aren't set, is to determine the Group ID using AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order. If GroupIDSource is set to either DHCP Option ID (3) or DNS Suffix (4) and those methods fail, the default behavior is used instead. The option set in this policy only applies to Group (2) download mode. If Group (2) isn't set as Download mode, this policy will be ignored. If you set the value to anything other than 0-5, the policy is ignored. +When set, the Group ID will be assigned automatically from the selected source. This policy is ignored if the GroupID policy is also set. The default behavior, when the GroupID or GroupIDSource policies aren't set, is to determine the Group ID using AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order. If GroupIDSource is set to either DHCP Option ID (3) or DNS Suffix (4) and those methods fail, the default behavior is used instead. The option set in this policy only applies to Group (2) download mode. If Group (2) isn't configured as Download mode, this policy will be ignored. If you set the value to anything other than 0-5, the policy is ignored. -### Minimum RAM (inclusive) allowed to use Peer Caching +### Minimum RAM (inclusive) allowed to use peer caching MDM Setting: **DOMinRAMAllowedToPeer** This setting specifies the minimum RAM size in GB required to use Peer Caching. For example if the minimum set is 1 GB, then devices with 1 GB or higher available RAM will be allowed to use Peer caching. The recommended values are 1 to 4, and **the default value is 4 GB**. -### Minimum disk size allowed to use Peer Caching +### Minimum disk size allowed to use peer caching MDM Setting: **DOMinDiskSizeAllowedToPeer** @@ -178,45 +178,37 @@ This setting specifies the required minimum disk size (capacity in GB) for the d >[!NOTE] >If the [Modify Cache Drive](#modify-cache-drive) policy is set, the disk size check applies to the new working directory specified by this policy. -### Max Cache Age +### Max cache age MDM Setting: **DOMaxCacheAge** In environments configured for Delivery Optimization, you might want to set an expiration on cached updates and Windows application installation files. If so, this setting defines the maximum number of seconds each file can be held in the Delivery Optimization cache on each Windows 10 client device. Alternatively, organizations might choose to set this value to "0" which means "unlimited" to avoid peers redownloading content. When "Unlimited" value is set, Delivery Optimization holds the files in the cache longer and cleans up the cache as needed (for example when the cache size exceeded the maximum space allowed). **The default value is 259,200 seconds (three days)**. -### Max Cache Size +### Max cache size MDM Setting: **DOMaxCacheSize** This setting limits the maximum amount of space the Delivery Optimization cache can use as a percentage of the available drive space, from 1 to 100. For example, if you set this value to 10 on a Windows client device that has 100 GB of available drive space, then Delivery Optimization uses up to 10 GB of that space. Delivery Optimization constantly assesses the available drive space and automatically clear the cache to keep the maximum cache size under the set percentage. **The default value is 20%**. -### Absolute Max Cache Size +### Absolute max cache size MDM Setting: **DOAbsoluteMaxCacheSize** -This setting specifies the maximum number of gigabytes the Delivery Optimization cache can use. This is different from the [**Max Cache Size**](#max-cache-size) setting, which is a percentage of available disk space. Also, if you configure this policy, it overrides the [**Max Cache Size**](#max-cache-size) setting. **The default value is 10 GB**. +This setting specifies the maximum number of gigabytes the Delivery Optimization cache can use. This is different from the [**Max Cache Size**](#max-cache-size) setting, which is a percentage of available disk space. Also, if you configure this policy, it overrides the [**Max Cache Size**](#max-cache-size) setting. **The default value is not set**. -### Minimum Peer Caching Content File Size +### Minimum peer caching content file size MDM Setting: **DOMinFileSizeToCache** This setting specifies the minimum content file size in MB enabled to use Peer Caching. The recommended values are from 1 to 100000. **The default file size is 50 MB** to participate in peering. -### Maximum Download Bandwidth - -MDM Setting: **DOMaxDownloadBandwidth** - -Deprecated in Windows 10, version 2004. -This setting specifies the maximum download bandwidth that can be used across all concurrent Delivery Optimization downloads in kilobytes per second (KB/s). **A default value of "0"** means that Delivery Optimization dynamically adjusts and optimizes the maximum bandwidth used. - - -### Maximum Foreground Download Bandwidth +### Maximum foreground download bandwidth MDM Setting: **DOPercentageMaxForegroundBandwidth** Starting in Windows 10, version 1803, specifies the maximum foreground download bandwidth that Delivery Optimization uses across all concurrent download activities as a percentage of available download bandwidth. **The default value of "0"** means that Delivery Optimization dynamically adjusts to use the available bandwidth for foreground downloads. However, downloads from LAN peers aren't throttled even when this policy is set. -### Maximum Background Download Bandwidth +### Maximum background download bandwidth MDM Setting: **DOPercentageMaxBackgroundBandwidth** @@ -225,31 +217,17 @@ Starting in Windows 10, version 1803, specifies the maximum background download > [!NOTE] > It is recommended to use the absolute value download options 'DOMaxBackgroundDownloadBandwidth' and 'DOMaxForegroundDownloadBandwidth', rather than percentage-based options, for low bandwidth environments. -### Percentage of Maximum Download Bandwidth - -MDM Setting: **DOPercentageMaxDownloadBandwidth** - -Deprecated in Windows 10, version 2004. -This setting specifies the maximum download bandwidth that Delivery Optimization can use across all concurrent download activities as a percentage of available download bandwidth. **The default value of "0"** means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads. - -### Max Upload Bandwidth - -MDM Setting: **DOMaxUploadBandwidth** - -Deprecated in Windows 10, version 2004. -This setting allows you to limit the number of upload bandwidth individual clients can use for Delivery Optimization. Consider this setting when clients are providing content to requesting peers on the network. This option is set in kilobytes per second (KB/s). **The default value is "0" or "unlimited"** which means Delivery Optimization dynamically optimizes for minimal usage of upload bandwidth; however it doesn't cap the upload bandwidth rate at a set rate. - -### Set Business Hours to Limit Background Download Bandwidth - -MDM Setting: **DOSetHoursToLimitBackgroundDownloadBandwidth** - -Starting in Windows 10, version 1803, specifies the maximum background download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth. **By default, this policy isn't set.** - -### Set Business Hours to Limit Foreground Download Bandwidth +### Set business hours to limit foreground download bandwidth MDM Setting: **DOSetHoursToLimitForegroundDownloadBandwidth** -Starting in Windows 10, version 1803, specifies the maximum foreground download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth. **By default, this policy isn't set.** +Starting in Windows 10, version 1803, specifies the maximum foreground download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth. **By default, this policy isn't configured.** + +### Set business hours to limit background download bandwidth + +MDM Setting: **DOSetHoursToLimitBackgroundDownloadBandwidth** + +Starting in Windows 10, version 1803, specifies the maximum background download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth. **By default, this policy isn't configured.** ### Select a method to restrict peer selection @@ -261,43 +239,43 @@ If Group mode is set, Delivery Optimization connects to locally discovered peers In Windows 11, the Local Peer Discovery (DNS-SD) option can be set via MDM or Group Policy. However, in Windows 10, this feature can be enabled by setting the `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\DORestrictPeerSelectionBy` value to **2**. -### Delay background download from HTTP (in secs) - -MDM Setting: **DODelayBackgroundDownloadFromHttp** - -Starting in Windows 10, version 1803, this allows you to delay the use of an HTTP source in a background download that is allowed to use peer-to-peer. The maximum value is 4294967295 seconds. **By default, this policy isn't set.** - ### Delay foreground download from HTTP (in secs) MDM Setting: **DODelayForegroundDownloadFromHttp** -Starting in Windows 10, version 1803, allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use peer-to-peer. The maximum value is 4294967295 seconds. **By default, this policy isn't set.** +Starting in Windows 10, version 1803, allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use peer-to-peer. The maximum value is 4294967295 seconds. **By default, this policy isn't configured.** -### Delay Foreground Download Cache Server Fallback (in secs) +### Delay background download from HTTP (in secs) + +MDM Setting: **DODelayBackgroundDownloadFromHttp** + +Starting in Windows 10, version 1803, this allows you to delay the use of an HTTP source in a background download that is allowed to use peer-to-peer. The maximum value is 4294967295 seconds. **By default, this policy isn't configured.** + +### Delay foreground download cache server fallback (in secs) MDM Setting: **DelayCacheServerFallbackForeground** -Starting in Windows 10, version 1903, allows you to delay the fallback from cache server to the HTTP source for foreground content download by X seconds. If the 'Delay foreground download from HTTP policy is set, it will apply first (to allow downloads from peers) and then this policy will be applied. **By default, this policy isn't set.** +Starting in Windows 10, version 1903, allows you to delay the fallback from cache server to the HTTP source for foreground content download by X seconds. If the 'Delay foreground download from HTTP policy is set, it will apply first (to allow download from peers). **By default, this policy isn't configured.** -### Delay Background Download Cache Server Fallback (in secs) +### Delay background download cache server fallback (in secs) MDM Setting: **DelayCacheServerFallbackBackground** -Starting in Windows 10, version 1903, set this policy to delay the fallback from cache server to the HTTP source for a background content download by X seconds. If the 'Delay background download from HTTP' policy is set, it will apply first (to allow downloads from peers) and then this policy will be applied. **By default, this policy isn't set.** +Starting in Windows 10, version 1903, set this policy to delay the fallback from cache server to the HTTP source for a background content download by X seconds. If the 'Delay background download from HTTP' policy is set, it will apply first (to allow downloads from peers) and then this policy will be applied. **By default, this policy isn't configured.** -### Minimum Background QoS +### Minimum background QoS MDM Setting: **DOMinBackgroundQoS** This value specifies the minimum download speed guarantee that a client attempts to achieve and will fulfill by downloading more kilobytes from HTTP sources. The lower this value is, the more content is sourced using peers on the network rather than HTTP sources. The higher this value, the more content is received from HTTP sources, versus peers on the local network. **The default value is 2500 KB/s.** -### Modify Cache Drive +### Modify cache drive MDM Setting: **DOModifyCacheDrive** This setting allows for an alternate Delivery Optimization cache location on the clients. **By default, the cache is stored on the operating system drive through the %SYSTEMDRIVE% environment variable.** You can set the value to an environment variable (for example, %SYSTEMDRIVE%), a drive letter (for example, D:), or a folder path (for example, D:\DOCache). -### Monthly Upload Data Cap +### Monthly upload data cap MDM Setting: **DOMonthlyUploadDataCap** @@ -309,7 +287,7 @@ MDM Setting: **DOAllowVPNPeerCaching** This setting determines whether a device will be allowed to participate in Peer Caching while connected to VPN. **By default, if a VPN connection is detected, peering isn't allowed, except when the 'Local Discovery' (DNS-SD) option is chosen.** Specify "true" to allow the device to participate in Peer Caching while connected via VPN to the domain network. The device can download from or upload to other domain network devices, either on VPN or on the corporate domain network. -### VPN Keywords +### VPN keywords MDM Setting: **DOVpnKeywords** @@ -321,7 +299,7 @@ MDM Setting: **DODisallowCacheServerDownloadsOnVPN** This policy disallows downloads from Connected Cache servers when the device connects via VPN. **By default, the device is allowed to download from Connected Cache when connected via VPN.** Set this policy if you prefer devices to download directly from the Internet when connected remotely (via VPN) instead of pulling from a Microsoft Connected Cache server deployed on your corporate network. -### Allow uploads while the device is on battery while under set Battery level +### Allow uploads while the device is on battery while under set battery level MDM Setting: **DOMinBatteryPercentageAllowedToUpload** @@ -331,7 +309,7 @@ The device can download from peers while on battery regardless of this policy. >[!IMPORTANT] > **By default, devices will not upload while on battery**. To enable uploads while on battery, you need to enable this policy and set the battery value under which uploads pause. -### Cache Server Hostname +### Cache server hostname MDM Setting: **DOCacheHost** @@ -340,7 +318,7 @@ Set this policy to designate one or more Microsoft Connected Cache servers to be >[!IMPORTANT] > Any value will signify that the policy is set. For example, an empty string ("") isn't considered empty. -### Cache Server Hostname Source +### Cache server hostname source MDM Setting: **DOCacheHostSource** @@ -356,7 +334,7 @@ Set this policy to designate Delivery Optimization in Network Cache servers thro > [!NOTE] > If you format the DHCP Option ID incorrectly, the client will fall back to the Cache Server Hostname policy value if that value has been set. -### Maximum Foreground Download Bandwidth (in KB/s) +### Maximum foreground download bandwidth (in KB/s) MDM Setting: **DOMaxForegroundDownloadBandwidth** @@ -364,10 +342,33 @@ Specifies the maximum foreground download bandwidth in kilobytes/second that the **The default value of "0" means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads.** -### Maximum Background Download Bandwidth (in KB/s) +### Maximum background download bandwidth (in KB/s) MDM Setting: **DOMaxBackgroundDownloadBandwidth** Specifies the maximum background download bandwidth in kilobytes/second that the device can use across all concurrent download activities using Delivery Optimization. **The default value "0" means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads.** + +## Deprecated policies + +### Maximum download bandwidth + +MDM Setting: **DOMaxDownloadBandwidth** + +Deprecated in Windows 10, version 2004. +This setting specifies the maximum download bandwidth that can be used across all concurrent Delivery Optimization downloads in kilobytes per second (KB/s). **A default value of "0"** means that Delivery Optimization dynamically adjusts and optimizes the maximum bandwidth used. + +### Percentage of maximum download bandwidth + +MDM Setting: **DOPercentageMaxDownloadBandwidth** + +Deprecated in Windows 10, version 2004. +This setting specifies the maximum download bandwidth that Delivery Optimization can use across all concurrent download activities as a percentage of available download bandwidth. **The default value of "0"** means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads. + +### Max upload bandwidth + +MDM Setting: **DOMaxUploadBandwidth** + +Deprecated in Windows 10, version 2004. +This setting allows you to limit the number of upload bandwidth individual clients can use for Delivery Optimization. Consider this setting when clients are providing content to requesting peers on the network. This option is set in kilobytes per second (KB/s). **The default value is "0" or "unlimited"** which means Delivery Optimization dynamically optimizes for minimal usage of upload bandwidth; however it doesn't cap the upload bandwidth rate at a set rate. diff --git a/windows/deployment/do/waas-delivery-optimization-setup.md b/windows/deployment/do/waas-delivery-optimization-setup.md index 3435fc58f4..0a8cced507 100644 --- a/windows/deployment/do/waas-delivery-optimization-setup.md +++ b/windows/deployment/do/waas-delivery-optimization-setup.md @@ -16,7 +16,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Delivery Optimization -ms.date: 08/15/2023 +ms.date: 05/23/2024 --- # Set up Delivery Optimization for Windows diff --git a/windows/deployment/do/waas-delivery-optimization.md b/windows/deployment/do/waas-delivery-optimization.md index caf711d69b..fa995d9ba8 100644 --- a/windows/deployment/do/waas-delivery-optimization.md +++ b/windows/deployment/do/waas-delivery-optimization.md @@ -16,7 +16,7 @@ ms.localizationpriority: medium appliesto: - ✅ Windows 11 - ✅ Windows 10 -ms.date: 06/02/2023 +ms.date: 05/23/2024 --- # What is Delivery Optimization? @@ -39,32 +39,32 @@ For information about setting up Delivery Optimization, including tips for the b The following table lists the minimum Windows 10 version that supports Delivery Optimization: | Device type | Minimum Windows version -|------------------|---------------| -| Computers running Windows 10 | Windows 10 1511 | -| Computers running Server Core installations of Windows Server | Windows Server 2019 | -| Windows IoT devices | Windows 10 1803 | +|------------------|--------------- +| Computers running Windows 10 | Windows 10 1511 +| Computers running Server Core installations of Windows Server | Windows Server 2019 +| Windows IoT devices | Windows 10 1803 ### Types of download content supported by Delivery Optimization #### Windows Client | Windows Client | Minimum Windows version | HTTP Downloader | Peer to Peer | Microsoft Connected Cache (MCC) -|------------------|---------------|----------------|----------|----------------| -| Windows Update ([feature updates quality updates, language packs, drivers](../update/get-started-updates-channels-tools.md#types-of-updates)) | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | -| Windows 10/11 UWP Store apps | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | -| Windows 11 Win32 Store apps | Windows 11 | :heavy_check_mark: | | | -| Windows 10 Store for Business apps | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | -| Windows Defender definition updates | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | -| Intune Win32 apps| Windows 10 1709, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | -| Microsoft 365 Apps and updates | Windows 10 1709, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | -| Edge Browser Updates | Windows 10 1809, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | -| Configuration Manager Express updates| Windows 10 1709 + Configuration Manager version 1711, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | -| Dynamic updates| Windows 10 1903, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | -| MDM Agent | Windows 11 | :heavy_check_mark: | | | -| Xbox Game Pass (PC) | Windows 10 1809, Windows 11 | :heavy_check_mark: | | :heavy_check_mark: | -| Windows Package Manager| Windows 10 1809, Windows 11 | :heavy_check_mark: | | | -| MSIX Installer| Windows 10 2004, Windows 11 | :heavy_check_mark: | | | -| Teams (via MSIX Installer) | Windows 10 2004, Windows 11 | :heavy_check_mark: | | | +|------------------|---------------|----------------|----------|---------------- +| Windows Update ([feature updates quality updates, language packs, drivers](../update/get-started-updates-channels-tools.md#types-of-updates)) | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: +| Windows 10/11 UWP Store apps | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: +| Windows 11 Win32 Store apps | Windows 11 | :heavy_check_mark: +| Windows 10 Store for Business apps | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: +| Windows Defender definition updates | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: +| Intune Win32 apps| Windows 10 1709, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: +| Microsoft 365 Apps and updates | Windows 10 1709, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: +| Edge Browser Updates | Windows 10 1809, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: +| Configuration Manager Express updates| Windows 10 1709 + Configuration Manager version 1711, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: +| Dynamic updates| Windows 10 1903, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: +| MDM Agent | Windows 11 | :heavy_check_mark: | | +| Xbox Game Pass (PC) | Windows 10 1809, Windows 11 | :heavy_check_mark: | | :heavy_check_mark: +| Windows Package Manager| Windows 10 1809, Windows 11 | :heavy_check_mark: | | +| MSIX Installer| Windows 10 2004, Windows 11 | :heavy_check_mark: | | +| Teams (via MSIX Installer) | Windows 10 2004, Windows 11 | :heavy_check_mark: | | #### Windows Server diff --git a/windows/deployment/do/waas-microsoft-connected-cache.md b/windows/deployment/do/waas-microsoft-connected-cache.md index 2ae4a2017f..a1cd9a0ca8 100644 --- a/windows/deployment/do/waas-microsoft-connected-cache.md +++ b/windows/deployment/do/waas-microsoft-connected-cache.md @@ -13,7 +13,7 @@ ms.localizationpriority: medium appliesto: - ✅ Windows 11 - ✅ Windows 10 -ms.date: 06/02/2023 +ms.date: 05/23/2024 --- # What is Microsoft Connected Cache? diff --git a/windows/deployment/do/waas-optimize-windows-10-updates.md b/windows/deployment/do/waas-optimize-windows-10-updates.md index d145e150d9..330f5c1225 100644 --- a/windows/deployment/do/waas-optimize-windows-10-updates.md +++ b/windows/deployment/do/waas-optimize-windows-10-updates.md @@ -13,7 +13,7 @@ ms.localizationpriority: medium appliesto: - ✅ Windows 11 - ✅ Windows 10 -ms.date: 02/14/2023 +ms.date: 05/23/2024 --- # Optimize Windows update delivery diff --git a/windows/deployment/do/whats-new-do.md b/windows/deployment/do/whats-new-do.md index d9a769354f..3b6e535c4f 100644 --- a/windows/deployment/do/whats-new-do.md +++ b/windows/deployment/do/whats-new-do.md @@ -13,12 +13,13 @@ ms.localizationpriority: medium appliesto: - ✅ Windows 11 - ✅ Windows 10 -ms.date: 06/02/2023 +ms.date: 05/23/2024 --- # What's new in Delivery Optimization This article contains information about what's new in Delivery Optimization, a peer-to-peer distribution method in Windows 10 and Windows 11. + ## Microsoft Connected Cache (early preview) Microsoft Connected Cache (MCC) is a software-only caching solution that delivers Microsoft content within Enterprise networks. MCC can be deployed to as many bare-metal servers or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying the client policy using management tools such as Intune. @@ -32,6 +33,13 @@ There are two different versions: ## New in Delivery Optimization for Windows +### General + +[Check out](http://aka.ms/do-fix) the new Delivery Optimization Troubleshooter. This tool provides a device health check to verify the device is set up properly to use Delivery Optimization. To scope the output more specifically, use one of the two switches: + +- -p2p: Provides output specific to P2P settings, efficiency, and errors. +- -mcc: Provides output specific to MCC settings and verifies the client can access the cache server. + ### Windows 11 22H2 - New setting: Customize vpn detection by choosing custom keywords. Now, you don't have to rely on Delivery Optimization keywords to detect your Vpn. By using the new VpnKeywords configuration you can add keywords for Delivery Optimization to use when detecting a Vpn when in use. You can find this configuration **[VPN Keywords](waas-delivery-optimization-reference.md#vpn-keywords)** in Group Policy or MDM under **DOVpnKeywords**.