diff --git a/education/windows/federated-sign-in.md b/education/windows/federated-sign-in.md index 9c6425ae8e..aca908bb45 100644 --- a/education/windows/federated-sign-in.md +++ b/education/windows/federated-sign-in.md @@ -1,7 +1,7 @@ --- title: Configure federated sign-in for Windows devices description: Learn how federated sign-in in Windows works and how to configure it. -ms.date: 04/10/2024 +ms.date: 06/03/2024 ms.topic: how-to appliesto: - ✅ Windows 11 @@ -87,7 +87,7 @@ Review the following instructions to configure your devices using either Microso |--|--|--| | Education | Is Education Environment | Enabled | | Federated Authentication | Enable Web Sign In For Primary User | Enabled | -| Authentication | Configure Web Sign In Allowed Urls | Semicolon separated list of domains, for example: `samlidp.clever.com;clever.com;mobile-redirector.clever.com` | +| Authentication | Configure Web Sign In Allowed Urls | Enter the list of domains, with each URL in a separate row. For example:
- `samlidp.clever.com`
- `clever.com`
- `mobile-redirector.clever.com` | | Authentication | Configure Webcam Access Domain Names | This setting is optional, and it should be configured if you need to use the webcam during the sign-in process. Specify the list of domains that are allowed to use the webcam during the sign-in process, separated by a semicolon. For example: `clever.com` | [!INCLUDE [intune-settings-catalog-2](../../includes/configure/intune-settings-catalog-2.md)] @@ -134,7 +134,7 @@ Review the following instructions to configure your shared devices using either | Education | Is Education Environment | Enabled | | SharedPC | Enable Shared PC Mode With OneDrive Sync | True | | Authentication | Enable Web Sign In | Enabled | -| Authentication | Configure Web Sign In Allowed Urls | Semicolon separated list of domains, for example: `samlidp.clever.com;clever.com;mobile-redirector.clever.com` | +| Authentication | Configure Web Sign In Allowed Urls | Enter the list of domains, with each URL in a separate row. For example:
- `samlidp.clever.com`
- `clever.com`
- `mobile-redirector.clever.com` | | Authentication | Configure Webcam Access Domain Names | This setting is optional, and it should be configured if you need to use the webcam during the sign-in process. Specify the list of domains that are allowed to use the webcam during the sign-in process, separated by a semicolon. For example: `clever.com` | [!INCLUDE [intune-settings-catalog-2](../../includes/configure/intune-settings-catalog-2.md)] diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index 933c48b4b8..f0d64329cb 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: https://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 11ae7a02fc..782b1650f6 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..8ae1791776 100644 --- a/windows/deployment/do/delivery-optimization-test.md +++ b/windows/deployment/do/delivery-optimization-test.md @@ -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. @@ -90,35 +90,39 @@ The following set of instructions will be used for each machine: 1. Open PowerShell console as 'Administrator'. * Clear the DO cache: 'Delete-DeliveryOptimizationCache'. * Run 'Get-DeliveryOptimizationStatus'. + 2. Open MS Store and search for 'Asphalt Legends 9'. Select *Get* to initiate the download of the content (content size: ~3.4 GB). **On machine #1** * 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. | + |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. | -*Wait 5 minutes*. + *Wait 5 minutes*. **On machine #2** * Run 'Test Instructions' -|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. | + |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. | ### Scenario 2: Advance Setup **Goal:** + Demonstrate how Delivery Optimization peer-to-peer technology works in a non-controlled environment and expanding to three machines + **Expected Results:** + Machine 1 will download zero bytes from peers and Machine 2 will find peers and download 50-99% from peers. Machine 3 will find two peers and download 50-99% from peers. #### Test Machine Setup @@ -131,10 +135,10 @@ Machine 1 will download zero bytes from peers and Machine 2 will find peers and |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 '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 @@ -148,25 +152,25 @@ The following set of instructions will be used for each machine: * Run 'Test Instructions' -**Output: Windows 10 (21H2)** + **Output: Windows 10 (21H2)** -![Windows 10 21H2 - Machine 1 - Advanced Test.](images/test-scenarios/win10/m1-adv-complete.png) + ![Windows 10 21H2 - Machine 1 - Advanced Test.](images/test-scenarios/win10/m1-adv-complete.png) **Observations** -* The first download in the group of devices shows all bytes coming from HTTP, 'BytesFromHttp'. -* Download is in the 'Foreground' because the Store app is doing the download and in the foreground on the device because it's initiated by the user in the Store app. -* No peers are found. + * The first download in the group of devices shows all bytes coming from HTTP, 'BytesFromHttp'. + * Download is in the 'Foreground' because the Store app is doing the download and in the foreground on the device because it's initiated by the user in the Store app. + * No peers are found. -*Wait 5 minutes*. + *Wait 5 minutes*. **On machine #2:** * Run 'Test Instructions' -**Output** Windows 10 (21H2) + **Output** Windows 10 (21H2) -![Windows 10 21H2 - Machine 2 - Advanced Test.](images/test-scenarios/win10/m2-adv-complete.png) + ![Windows 10 21H2 - Machine 2 - Advanced Test.](images/test-scenarios/win10/m2-adv-complete.png) **Observations** @@ -179,9 +183,9 @@ The following set of instructions will be used for each machine: * Run 'Test Instructions' -**Output:** Windows 10 (21H2) + **Output:** Windows 10 (21H2) -![Windows 10 21H2 - Machine 3 - Advanced Test.](images/test-scenarios/win10/m3-adv-complete.png) + ![Windows 10 21H2 - Machine 3 - Advanced Test.](images/test-scenarios/win10/m3-adv-complete.png) **Observations** diff --git a/windows/deployment/do/delivery-optimization-workflow.md b/windows/deployment/do/delivery-optimization-workflow.md index 1c4f4828f2..9635f725c9 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,7 +41,6 @@ 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 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..6264ea32c4 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,15 +92,15 @@ 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: - ``` - reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v DOCacheHost /t REG_SZ /d "10.137.187.38" /f + ```powershell + reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v DOCacheHost /t REG_SZ /d "10.137.187.38" /f ``` 1. MDM path (version 1809 and later): @@ -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*. @@ -127,7 +126,7 @@ To verify that the Delivery Optimization client can download content using MCC, :::image type="content" source="./images/ent-mcc-get-deliveryoptimizationstatus.png" alt-text="Screenshot of the output of Get-DeliveryOptimization | FT from PowerShell." lightbox="./images/ent-mcc-get-deliveryoptimizationstatus.png"::: - Using the Delivery Optimization Activity Monitor - + :::image type="content" source="./images/ent-mcc-delivery-optimization-activity.png" alt-text="Screenshot of the Delivery Optimization Activity Monitor."::: ## EFLOW diff --git a/windows/deployment/do/mcc-enterprise-deploy.md b/windows/deployment/do/mcc-enterprise-deploy.md index b2883ad2fd..5cc7236b51 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 @@ -32,10 +32,9 @@ To deploy MCC to your server: 1. [Verify MCC functionality](#verify-mcc-server-functionality) 1. [Review common Issues](#common-issues) if needed. - ### 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,12 +43,13 @@ 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."::: + + :::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."::: 1. Type **Microsoft Connected Cache** into the search box, and hit **Enter** to show search results. @@ -58,8 +58,9 @@ Once you take the survey above and the MCC team adds your subscription ID to the 1. Select **Microsoft Connected Cache Enterprise** and choose **Create** on the next screen to start the process of creating the MCC resource. - :::image type="content" source="./images/ent-mcc-azure-search-result.png" alt-text="Screenshot of the Azure portal search results for Microsoft Connected Cache."::: - :::image type="content" source="./images/ent-mcc-azure-marketplace.png" alt-text="Screenshot of Microsoft Connected Cache Enterprise within the Azure Marketplace."::: + :::image type="content" source="./images/ent-mcc-azure-search-result.png" alt-text="Screenshot of the Azure portal search results for Microsoft Connected Cache."::: + + :::image type="content" source="./images/ent-mcc-azure-marketplace.png" alt-text="Screenshot of Microsoft Connected Cache Enterprise within the Azure Marketplace."::: 1. Fill in the required fields to create the MCC resource. @@ -75,8 +76,7 @@ Once you take the survey above and the MCC team adds your subscription ID to the :::image type="content" source="./images/ent-mcc-azure-create-connected-cache.png" alt-text="Screenshot of the Create a Connected Cache page within the Azure Marketplace."::: -1. Once all the information has been entered, select the **Review + Create** button. Once validation is complete, select the **Create** button to start the - resource creation. +1. Once all the information has been entered, select the **Review + Create** button. Once validation is complete, select the **Create** button to start the resource creation. :::image type="content" source="./images/ent-mcc-azure-cache-created.png" alt-text="Screenshot of the completed cache deployment within the Azure." lightbox="./images/ent-mcc-azure-cache-created.png"::: @@ -102,7 +102,7 @@ Creating an MCC node is a multi-step process and the first step is to access the 1. Selecting the **Create Cache Node** button will open the **Create Cache Node** page; **Cache Node Name** is the only field required for cache node creation. - | **Field Name**| **Expected Value**|**Description** | + | Field Name | Expected Value | Description | |---|---|---| | **Cache Node Name** | Alphanumeric name that doesn't include any spaces. | The name of the cache node. You may choose names based on location such as `Seattle-1`. This name must be unique and can't be changed later. | @@ -193,15 +193,16 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p >
>
[D] Do not run **[R] Run once** [S] Suspend [?] Help (default is "D"): -1. Choose whether you would like to create a new external virtual switch or select an existing external virtual switch. +1. Choose whether you would like to create a new external virtual switch or select an existing external virtual switch. + If creating a new external virtual switch, name your switch and be sure to choose a Local Area Connection (USB adapters work as well however, we do not recommend using Wi-Fi). A computer restart will be required if you're creating a new switch. - > [!NOTE] - > Restarting your computer after creating a switch is recommended. You'll notice network delays during installation if the computer has not been restarted. + > [!NOTE] + > Restarting your computer after creating a switch is recommended. You'll notice network delays during installation if the computer has not been restarted. - If you restarted your computer after creating a switch, start from step 2 above and skip to step 5. + 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"::: @@ -220,16 +221,22 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p For example, for host configuration where the server IP Address is 192.168.1.202 and the subnet mask is 255.255.255.0, the static IP can be anything 192.168.1.* except 192.168.1.202. :::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. + + 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 recommended values for a Branch Office/Small Enterprise deployment. + :::image type="content" source="./images/memory-storage-5.png" alt-text="Screenshot of multiple installer questions about memory and storage." lightbox="./images/memory-storage-5.png"::: -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"::: +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"::: 1. Your MCC deployment is now complete. + If you don't see any errors, continue to the next section to validate your MCC deployment. Your VM will not appear in Hyper-V Manager as it is an EFLOW VM. - After validating your MCC is properly functional, review your management solution documentation, such as [Intune](/mem/intune/configuration/delivery-optimization-windows), to set the cache host policy to the IP address of your MCC. - If you had errors during your deployment, see the [Common Issues](#common-issues) section in this article. @@ -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 @@ -285,7 +297,7 @@ A successful test result will display a status code of 200 along with additional :::image type="content" source="./images/ent-mcc-verify-server-ssh.png" alt-text="Screenshot of a successful wget with an SSH client." lightbox="./images/ent-mcc-verify-server-ssh.png"::: - :::image type="content" source="./images/ent-mcc-verify-server-powershell.png" alt-text="Screenshot of a successful wget using PowerShell." lightbox="./images/ent-mcc-verify-server-powershell.png"::: +:::image type="content" source="./images/ent-mcc-verify-server-powershell.png" alt-text="Screenshot of a successful wget using PowerShell." lightbox="./images/ent-mcc-verify-server-powershell.png"::: Similarly, enter the following URL from a browser in the network: @@ -311,9 +323,9 @@ If you're seeing errors similar to this error: `The term Get- isn't r 1. Ensure you have Hyper-V enabled: - **Windows 10:** [Enable Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v) + **Windows 10:** [Enable Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v) - **Windows Server:** [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server) + **Windows Server:** [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server) #### Verify Running MCC Container @@ -336,10 +348,9 @@ 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. -> + ### DNS needs to be configured @@ -355,53 +366,53 @@ To configure the device to work with your DNS, use the following steps: 1. Use `ifconfig` to find the appropriate NIC adapter name. - ```bash - ifconfig - ``` + ```bash + ifconfig + ``` 1. Run `nmcli device show ` to show the DNS name for the ethernet adapter. For example, to show DNS information for **eno1**: - ```bash - nmcli device show eno1 - ``` + ```bash + nmcli device show eno1 + ``` - :::image type="content" source="images/mcc-isp-nmcli.png" alt-text="Screenshot of a sample output of nmcli command to show network adapter information." lightbox="./images/mcc-isp-nmcli.png"::: + :::image type="content" source="images/mcc-isp-nmcli.png" alt-text="Screenshot of a sample output of nmcli command to show network adapter information." lightbox="./images/mcc-isp-nmcli.png"::: 1. Open or create the Docker configuration file used to configure the DNS server. - ```bash - sudo nano /etc/docker/daemon.json - ``` + ```bash + sudo nano /etc/docker/daemon.json + ``` 1. Paste the following string into the **daemon.json** file, and include the appropriate DNS server address. For example, in the previous screenshot, `IP4.DNS[1]` is `10.50.10.50`. - ```bash - { "dns": ["x.x.x.x"]} - ``` + ```bash + { "dns": ["x.x.x.x"]} + ``` 1. Save the changes to daemon.json. If you need to change permissions on this file, use the following command: - ```bash - sudo chmod 555 /etc/docker/daemon.json - ``` + ```bash + sudo chmod 555 /etc/docker/daemon.json + ``` 1. Restart Docker to pick up the new DNS setting. Then restart IoT Edge. - ```bash - sudo systemctl restart docker - sudo systemctl daemon-reload - sudo restart IoTEdge - ``` + ```bash + sudo systemctl restart docker + sudo systemctl daemon-reload + sudo restart IoTEdge + ``` ### 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 +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: + ```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..8ffa3c50c7 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 --- # Uninstall MCC -Please contact the MCC Team before uninstalling to let us know if you're facing issues. +Contact the MCC Team before uninstalling to let us know if you're facing issues. -This script will remove the following items: +This script removes the following items: 1. EFLOW + Linux VM 1. IoT Edge diff --git a/windows/deployment/do/mcc-isp-cache-node-configuration.md b/windows/deployment/do/mcc-isp-cache-node-configuration.md index b78fb6bdd2..1b038f6404 100644 --- a/windows/deployment/do/mcc-isp-cache-node-configuration.md +++ b/windows/deployment/do/mcc-isp-cache-node-configuration.md @@ -15,12 +15,12 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for ISPs -ms.date: 08/16/2023 +ms.date: 05/23/2024 --- # Cache node configuration -All cache node configuration takes place within Azure portal. This article outlines all of the settings that you're able to configure. +All cache node configuration takes place within Azure portal. This article outlines all of the settings that you're able to configure. ## Settings @@ -45,4 +45,3 @@ All cache node configuration takes place within Azure portal. This article outli | **Manual routing - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the MCC server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 | | **BGP - Neighbor ASN** | ASN | When configuring BGP, enter the ASN(s) of your neighbors that you want to establish. | | **BGP - Neighbor IP address** | IPv4 address | When configuring BGP, enter the IP address(es) of neighbors that you want to establish. | - diff --git a/windows/deployment/do/mcc-isp-create-provision-deploy.md b/windows/deployment/do/mcc-isp-create-provision-deploy.md index 675839a616..4b56a710bb 100644 --- a/windows/deployment/do/mcc-isp-create-provision-deploy.md +++ b/windows/deployment/do/mcc-isp-create-provision-deploy.md @@ -13,7 +13,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for ISPs -ms.date: 05/09/2023 +ms.date: 05/23/2024 --- # Create, configure, provision, and deploy the cache node in Azure portal @@ -54,12 +54,14 @@ You can manually upload a list of your CIDR blocks in Azure portal to enable man BGP (Border Gateway Protocol) routing is another method offered for client routing. BGP dynamically retrieves CIDR ranges by exchanging information with routers to understand reachable networks. For an automatic method of routing traffic, you can choose to configure BGP routing in Azure portal. Microsoft Connected Cache includes Bird BGP, which enables the cache node to: - - Establish iBGP peering sessions with routers, route servers, or route collectors within operator networks - - Act as a route collector + +- Establish iBGP peering sessions with routers, route servers, or route collectors within operator networks +- Act as a route collector The operator starts the iBGP peering session from the Microsoft Connected Cache side using the Azure management portal and then starts the session with the Microsoft Connected Cache node from the router. In the example configuration below: + - The operator ASN is 65100 - The ASN of the Microsoft Connected Cache cache node is 65100 and the IP address is 192.168.8.99 - iBGP peering sessions are established from the portal for ASNs 65100, 65200, and 65300. @@ -125,7 +127,7 @@ There are five IDs that the device provisioning script takes as input in order t 1. After completing cache node provisioning, navigate to the **Server provisioning** tab. Select **Download provisioning package** to download the installation package to your server. -1. Open a terminal window in the directory where you would like to deploy your cache node and run the following command to change the access permission to the Bash script: +1. Open a terminal window in the directory where you would like to deploy your cache node and run the following command to change the access permission to the Bash script: ```bash sudo chmod +x provisionmcc.sh diff --git a/windows/deployment/do/mcc-isp-faq.yml b/windows/deployment/do/mcc-isp-faq.yml index 9f0d502be8..d4b3478551 100644 --- a/windows/deployment/do/mcc-isp-faq.yml +++ b/windows/deployment/do/mcc-isp-faq.yml @@ -15,7 +15,7 @@ metadata: appliesto: - ✅ Windows 11 - ✅ Windows 10 - ms.date: 03/21/2024 + ms.date: 05/23/2024 title: Microsoft Connected Cache Frequently Asked Questions summary: | Frequently asked questions about Microsoft Connected Cache diff --git a/windows/deployment/do/mcc-isp-overview.md b/windows/deployment/do/mcc-isp-overview.md index e3474b59cb..41ecaaaf1c 100644 --- a/windows/deployment/do/mcc-isp-overview.md +++ b/windows/deployment/do/mcc-isp-overview.md @@ -13,7 +13,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for ISPs -ms.date: 03/21/2024 +ms.date: 05/23/2024 --- # Microsoft Connected Cache for ISPs overview @@ -45,7 +45,6 @@ MCC complements peering by offloading static content that is served off of multi :::image type="content" source="./media/mcc-isp-overview/mcc-isp-peeringvsmcc.png" alt-text="Chart containing Peering vs Cache Content Traffic." lightbox="./media/mcc-isp-overview/mcc-isp-peeringvsmcc.png"::: - ## How MCC works :::image type="content" source="./images/mcc-isp-diagram.png" alt-text="Data flow diagram of how Microsoft Connected Cache works." lightbox="./images/mcc-isp-diagram.png"::: @@ -90,4 +89,3 @@ The following are recommended hardware configurations based on traffic ranges: *Requires systems (chipset, CPU, motherboard) with PCIe version 3, or higher. **Drive speeds are important and to achieve higher egress, we recommend SSD NVMe in m.2 PCIe slot (version 4, or higher). - diff --git a/windows/deployment/do/mcc-isp-signup.md b/windows/deployment/do/mcc-isp-signup.md index 4959e3160d..284269f52e 100644 --- a/windows/deployment/do/mcc-isp-signup.md +++ b/windows/deployment/do/mcc-isp-signup.md @@ -13,12 +13,12 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for ISPs -ms.date: 07/07/2023 +ms.date: 05/23/2024 --- # Operator sign up and service onboarding for Microsoft Connected Cache -This article details the process of signing up for Microsoft Connected Cache for Internet Service Providers (public preview). +This article details the process of signing up for Microsoft Connected Cache for Internet Service Providers (public preview). > [!NOTE] > Microsoft Connected Cache is now in public preview. Instead of submitting a survey, you can directly onboard by following the instructions in this article. @@ -34,7 +34,7 @@ Before you begin sign up, ensure you have the following components: 1. **Access to Azure portal**: Ensure you have the credentials needed to access your organization's Azure portal. -1. **Peering DB**: Ensure your organization's [Peering DB](https://www.peeringdb.com/) page is up-to-date and active. Check that the NOC email listed is accurate, and that you have access to this email. +1. **Peering DB**: Ensure your organization's [Peering DB](https://www.peeringdb.com/) page is up-to-date and active. Check that the NOC email listed is accurate, and that you have access to this email. 1. **Server**: Ensure the server you wish to install Microsoft Connected Cache on is ready, and that the server is installed on Ubuntu 20.04 LTS. 1. **Configure cache drive**: Make sure that you have a data drive configured with full permissions on your server. You'll need to specify the location for this cache drive during the cache node configuration process. The minimum size for the data drive is 100 GB. For instructions to mount a disk on a Linux VM, see [Attach a data disk to a Linux VM](/azure/virtual-machines/linux/attach-disk-portal#find-the-disk). diff --git a/windows/deployment/do/mcc-isp-support.md b/windows/deployment/do/mcc-isp-support.md index 83f96cb12e..ba0eda79c2 100644 --- a/windows/deployment/do/mcc-isp-support.md +++ b/windows/deployment/do/mcc-isp-support.md @@ -13,7 +13,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for ISPs -ms.date: 02/07/2024 +ms.date: 05/23/2024 --- # Support and troubleshooting @@ -38,51 +38,49 @@ During sign-up, a verification code is sent to your NOC email address present in Delete any MCC resource that you're using before you resign up for the service. Deleting any existing MCC resource unlocks your ASN, which allows you to successfully sign up. - ### Cache Node Errors #### Network connectivity issues Updating Docker's DNS can help resolve some connectivity issues. - Try the following Docker DNS updates until one solves your connectivity problem. + Try the following Docker DNS updates until one solves your connectivity problem. Once connectivity is established, there's no need to continue updating Docker's DNS. ##### Update Docker's DNS to use the Google DNS resolver -``` +```bash nano /etc/docker/daemon.json ``` Update the contents of this file to match the following example, which includes the public Google DNS resolver: -``` +```bash "log-driver": "json-file", "log-opts": {"max-size": "10m","max-file": "3"},"dns":["8.8.8.8", "8.8.4.4"] -``` +``` Save and close using the command CTRL-X and then Y(es) to save - + Restart Docker for this change to take effect: -``` +```bash systemctl restart docker ``` Rerun the IoT Edge Check command to validate proper connectivity: -``` +```bash iotedge check -verbose ``` - ##### Update Docker's DNS to use your company's DNS resolver -``` +```bash nano /etc/docker/daemon.json ``` -Update the contents of this file to match the following example, which includes the public Google DNS resolver: +Update the contents of this file to match the following example, which includes the public Google DNS resolver: -``` +```bash "log-driver": "json-file", "log-opts": {"max-size": "10m","max-file": "3"},"dns":[""] ``` @@ -90,13 +88,13 @@ Save and close using the command CTRL-X and then Y(es) to save. Restart Docker for this change to take effect: -``` +```bash systemctl restart docker ``` Rerun the IoT Edge Check command to validate proper connectivity: -``` +```bash iotedge check -verbose ``` @@ -122,4 +120,3 @@ To onboard onto Microsoft Connected Cache, you'll need an Azure subscription ID. - [Pay-as-you-go-subscription](https://azure.microsoft.com/offers/ms-azr-0003p/) - [Azure free account FAQs](https://azure.microsoft.com/free/free-account-faq/) - diff --git a/windows/deployment/do/mcc-isp-update.md b/windows/deployment/do/mcc-isp-update.md index b5c55362b2..e5140cb315 100644 --- a/windows/deployment/do/mcc-isp-update.md +++ b/windows/deployment/do/mcc-isp-update.md @@ -15,16 +15,16 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for ISPs -ms.date: 10/10/2022 +ms.date: 05/23/2024 --- # Update or uninstall your cache node -This article details how to update or uninstall your cache node. +This article details how to update or uninstall your cache node. ## Update cache node -Microsoft will release updates for Microsoft Connected Cache periodically to improve performance, functionality, and security. Updates won't require any action from the customer. Instead, when an update is available, your cache node will automatically update during low traffic hours with minimal to no impact to your end customers. +Microsoft will release updates for Microsoft Connected Cache periodically to improve performance, functionality, and security. Updates won't require any action from the customer. Instead, when an update is available, your cache node will automatically update during low traffic hours with minimal to no impact to your end customers. To view which version your cache nodes are currently on, navigate to the **Cache nodes** tab to view the versions in the list view. diff --git a/windows/deployment/do/mcc-isp-verify-cache-node.md b/windows/deployment/do/mcc-isp-verify-cache-node.md index eb44ce86c1..c43bf3738f 100644 --- a/windows/deployment/do/mcc-isp-verify-cache-node.md +++ b/windows/deployment/do/mcc-isp-verify-cache-node.md @@ -12,12 +12,12 @@ ms.reviewer: mstewart ms.collection: tier3 appliesto: - ✅ Microsoft Connected Cache for ISPs -ms.date: 02/09/2023 +ms.date: 05/23/2024 --- # Verify cache node functionality and monitor health and performance -This article details how to verify that your cache node(s) are functioning properly and serving traffic. This article also details how to monitor your cache nodes. +This article details how to verify that your cache node(s) are functioning properly and serving traffic. This article also details how to monitor your cache nodes. ## Verify cache node installation is complete @@ -39,7 +39,7 @@ For example, this command provides the current status of the starting and stoppi :::image type="content" source="./images/mcc-isp-edge-journalctl.png" alt-text="Terminal output of journalctl command for iotedge." lightbox="./images/mcc-isp-edge-journalctl.png"::: -You may need to wait up to 30 minutes for the cache node software to complete downloading and begin caching. +You may need to wait up to 30 minutes for the cache node software to complete downloading and begin caching. ## Verify functionality on Azure portal @@ -75,11 +75,11 @@ If the test fails, for more information, see the [FAQ](mcc-isp-faq.yml) article. ## Verify BGP routing configuration -To verify your BGP routes are correctly configured for a cache node, navigate to **Settings > Cache nodes**. Select the cache node you wish to verify BGP routes for. +To verify your BGP routes are correctly configured for a cache node, navigate to **Settings > Cache nodes**. Select the cache node you wish to verify BGP routes for. -Verify that under **Routing Information**, the state of **BGP routes received** is True. Verify the IP space is correct. Lastly, select **Download JSON** next to **Download BGP Routes** to view the BGP routes that your cache node is currently advertising. +Verify that under **Routing Information**, the state of **BGP routes received** is True. Verify the IP space is correct. Lastly, select **Download JSON** next to **Download BGP Routes** to view the BGP routes that your cache node is currently advertising. -If **BGP routes received** is False, your **IP Space** is 0, or you're experiencing any BGP routing errors, ensure your **ASN** and **IP address** is entered correctly. +If **BGP routes received** is False, your **IP Space** is 0, or you're experiencing any BGP routing errors, ensure your **ASN** and **IP address** is entered correctly. ## Monitor cache node health and performance diff --git a/windows/deployment/do/mcc-isp-vm-performance.md b/windows/deployment/do/mcc-isp-vm-performance.md index 04c0fa00df..5fafc85e89 100644 --- a/windows/deployment/do/mcc-isp-vm-performance.md +++ b/windows/deployment/do/mcc-isp-vm-performance.md @@ -12,7 +12,7 @@ ms.reviewer: mstewart ms.collection: tier3 appliesto: - ✅ Microsoft Connected Cache for ISPs -ms.date: 12/31/2017 +ms.date: 05/23/2024 --- # Enhancing cache performance @@ -30,7 +30,7 @@ The Microsoft Connected Cache module is optimized for Ubuntu 20.04 LTS. Install #### Drive performance -The maximum number of disks supported is 9. When configuring your drives, we recommend SSD drives as cache read speed of SSD is superior to HDD. In addition, using multiple disks is recommended to improve cache performance. +The maximum number of disks supported is 9. When configuring your drives, we recommend SSD drives as cache read speed of SSD is superior to HDD. In addition, using multiple disks is recommended to improve cache performance. RAID disk configurations are discouraged as cache performance will be impacted. If using RAID disk configurations, ensure striping. diff --git a/windows/deployment/do/mcc-isp.md b/windows/deployment/do/mcc-isp.md index 4191c3cd7f..87b1740400 100644 --- a/windows/deployment/do/mcc-isp.md +++ b/windows/deployment/do/mcc-isp.md @@ -10,7 +10,7 @@ ms.reviewer: mstewart manager: aaroncz ms.localizationpriority: medium ms.collection: tier3 -ms.date: 03/07/2023 +ms.date: 05/23/2024 appliesto: - ✅ Windows 11 - ✅ Windows 10 @@ -114,7 +114,6 @@ To deploy MCC: 6. [Verify properly functioning MCC server](#verify-properly-functioning-mcc-server) 7. [Review common issues if needed](#common-issues) - ## Provide Microsoft with your Azure subscription ID As part of the MCC preview onboarding process, an Azure subscription ID must be provided to Microsoft. @@ -388,7 +387,6 @@ Before you start, make sure that you have a data drive configured on your server :::image type="content" source="./images/mcc-isp-use-bgp.png" alt-text="Screenshot of the Cache Node Configuration page with the Prefix Source set to Use BGP."::: - 1. If there are no errors, go to the next section to verify the MCC server. If there are errors: @@ -567,7 +565,6 @@ To migrate, use the following steps: :::image type="content" source="images/mcc-isp-migrate.png" alt-text="A screenshot of Azure portal showing the migration instructions for migrating a cache node from the early preview to the public preview." lightbox="images/mcc-isp-migrate.png"::: 1. Go to https://portal.azure.com and navigate to your resource to check your migrated cache nodes. - ## Uninstalling MCC In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls MCC and all the related components. Before you run this script, contact the MCC team. Only run it if you're facing issues with MCC installation. @@ -592,13 +589,12 @@ sudo ./uninstallmcc.sh ``` ## Appendix - + ### Steps to obtain an Azure subscription ID [!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..675851ae42 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,7 +47,7 @@ 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) | @@ -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 peers | +| GroupConnectionCount | Number of connections to Group peers | +| InternetConnectionCount | Number of connections to Internet peers | +| 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 `Set-DeliveryOptimizationStatus`). | `Get-DeliveryOptimizationPerfSnap` returns a list of key performance data: @@ -76,40 +76,36 @@ 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 found across all files currently in the cache | +| CacheHostConnections | Number of cache host server connections | +| CdnConnections | Number of CDN server connections | +| LanConnections | Number of peer connections over LAN | +| LinkLocalConnections | Number of peer connections over Link Local | +| GroupConnections | Number of peer connections over Group | +| InternetConnections | Number of peer connections over Internet | +| DownlinkBps | Average download bandwidth usage currently seen across all network adapters | +| DownlinkUsageBps | Average bandwidth currently used by Delivery Optimization for downloads | +| UplinkBps | Average upload bandwidth usage currently seen across all network adapters | +| UplinkUsageBps | Average bandwidth currently used by Delivery Optimization for uploads | +| ForegroundDownloadRatePct | Percentage of bandwidth to be used for foreground downloads | +| BackgroundDownloadRatePct | Percentage of bandwidth to be used for background downloads | +| UploadRatePct | Percentage of upload bandwidth to be used for uploads | +| 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: @@ -135,17 +131,17 @@ Starting in Windows 10, version 1803, `Get-DeliveryOptimizationPerfSnapThisMonth **Starting in Windows 10, version 1903:** -`set-DeliveryOptimizationStatus -ExpireOn [date time]` extends the expiration of all files in the cache. You can set the expiration immediately for all files that are in the "caching" state. For files in progress ("downloading"), the expiration is applied once the download is complete. You can set the expiration up to one year from the current date and time. +`Set-DeliveryOptimizationStatus -ExpireOn [date time]` extends the expiration of all files in the cache. You can set the expiration immediately for all files that are in the "caching" state. For files in progress ("downloading"), the expiration is applied once the download is complete. You can set the expiration up to one year from the current date and time. -`set-DeliveryOptimizationStatus -ExpireOn [date time] -FileID [FileID]` extends expiration for a single specific file in the cache. +`Set-DeliveryOptimizationStatus -ExpireOn [date time] -FileID [FileID]` extends expiration for a single specific file in the cache. You can now "pin" files to keep them persistent in the cache, only with files that are downloaded in modes 1, 2, or 3. -`set-DeliveryOptimizationStatus -Pin [True] -File ID [FileID]` keeps a specific file in the cache such that it won't be deleted until the expiration date and time (which you set with `set-DeliveryOptimizationStatus -ExpireOn [date time] -FileID [FileID]`). The file is also excluded from the cache quota calculation. +`Set-DeliveryOptimizationStatus -Pin [True] -File ID [FileID]` keeps a specific file in the cache such that it won't be deleted until the expiration date and time (which you set with `Set-DeliveryOptimizationStatus -ExpireOn [date time] -FileID [FileID]`). The file is also excluded from the cache quota calculation. -`set-DeliveryOptimizationStatus -Pin [False] -File ID [FileID]` "unpins" a file, so that it will be deleted when the expiration date and time are reached. The file is included in the cache quota calculation. +`Set-DeliveryOptimizationStatus -Pin [False] -File ID [FileID]` "unpins" a file, so that it will be deleted when the expiration date and time are reached. The file is included in the cache quota calculation. -`delete-DeliveryOptimizationCache` lets you clear files from the cache and remove all persisted data related to them. You can use these options with this cmdlet: +`Delete-DeliveryOptimizationCache` lets you clear files from the cache and remove all persisted data related to them. You can use these options with this cmdlet: - `-FileID` specifies a particular file to delete. - `-IncludePinnedFiles` deletes all files that are pinned. @@ -188,7 +184,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 +193,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 +212,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..c93596986a 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 @@ -34,35 +34,35 @@ In MDM, the same settings are under **.Vendor/MSFT/Policy/Config/DeliveryOptimiz | Group Policy setting | MDM setting | Supported from version | Notes | | --- | --- | --- | ------- | -| [Download mode](#download-mode) | DODownloadMode | 1511 | Default is set to LAN(1). The Group [Download mode](#download-mode) (2) combined with [Group ID](#group-id), enables administrators to create custom device groups that share content between devices in the group.| -| [Group ID](#group-id) | DOGroupID | 1511 | Used with Group [Download mode](#download-mode). If not set, check [GroupIDSource](#select-the-source-of-group-ids). When GroupID or GroupIDSource policies aren't set, the GroupID is defined as the AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order. | -| [Select the source of Group IDs](#select-the-source-of-group-ids) | DOGroupIDSource | 1803 | If not set, check [Group ID](#group-id). When the GroupID or GroupIDSource policies aren't set, the Group is defined as the AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order. | -| [Select a method to restrict peer selection](#select-a-method-to-restrict-peer-selection) | DORestrictPeerSelectionBy | 1803 | Starting in Windows 11, a new option to use 'Local discovery (DNS-SD)' is available to set via this policy. | +| [Download mode](#download-mode) | DODownloadMode | 1511 | Default is configured to LAN(1). The Group [Download mode](#download-mode) (2) combined with [Group ID](#group-id), enables administrators to create custom device groups that share content between devices in the group.| +| [Group ID](#group-id) | DOGroupID | 1511 | Used with Group [Download mode](#download-mode). If not configured, check [GroupIDSource](#select-the-source-of-group-ids). When GroupID or GroupIDSource policies aren't configured, the GroupID is defined as the AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order. | +| [Select the source of Group IDs](#select-the-source-of-group-ids) | DOGroupIDSource | 1803 | If not configured, check [Group ID](#group-id). When the GroupID or GroupIDSource policies aren't configured, the Group is defined as the AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order. | +| [Select a method to restrict peer selection](#select-a-method-to-restrict-peer-selection) | DORestrictPeerSelectionBy | 1803 | Starting in Windows 11, a new option to use 'Local discovery (DNS-SD)' is available to configure via this policy. | | [Minimum RAM (inclusive) allowed to use peer caching](#minimum-ram-inclusive-allowed-to-use-peer-caching) | DOMinRAMAllowedToPeer | 1703 | Default value is 4 GB. | | [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 configured as default. | +| [Cache server hostname source](#cache-server-hostname-source) | DOCacheHostSource | 2004 | No value is configured 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. @@ -114,8 +114,8 @@ When Delivery Optimization client is configured to use peers and Microsoft Conne Administrators can further customize scenarios where Delivery Optimization is used with the following settings: -- [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-inclusive-allowed-to-use-peer-caching) sets the minimum RAM required for peer caching to be enabled. -- [Minimum disk size allowed to use Peer Caching](#minimum-disk-size-allowed-to-use-peer-caching) sets the minimum disk size required for peer caching to be enabled. +- [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-inclusive-allowed-to-use-peer-caching) configures the minimum RAM required for peer caching to be enabled. +- [Minimum disk size allowed to use Peer Caching](#minimum-disk-size-allowed-to-use-peer-caching) configures the minimum disk size required for peer caching to be enabled. - [Enable Peer Caching while the device connects via VPN](#enable-peer-caching-while-the-device-connects-via-vpn) allows clients connected through VPN to use peer caching. - [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) controls the minimum battery level required for uploads to occur. You must enable this policy to allow upload while on battery. @@ -125,14 +125,14 @@ MDM Setting: **DODownloadMode** Download mode dictates which download sources clients are allowed to use when downloading Windows updates in addition to Windows Update servers. The following table shows the available download mode options and what they do. Other technical details for these policies are available in [Policy CSP - Delivery Optimization](/windows/client-management/mdm/policy-csp-deliveryoptimization). -| Download mode option | Functionality when set | +| 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. | | 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. | | Simple (99) | Simple mode disables the use of Delivery Optimization cloud services completely (for offline environments). Delivery Optimization switches to this mode automatically when the Delivery Optimization cloud services are unavailable, unreachable, or when the content file size is less than 10 MB. In this mode, Delivery Optimization provides a reliable download experience over HTTP from the download's original source or a Microsoft Connected Cache server, with no peer-to-peer caching. | -| Bypass (100) | Starting in Windows 11, this option is deprecated. Don't set **Download mode** to '100' (Bypass), which can cause some content to fail to download. If you want to disable peer-to-peer functionality, set DownloadMode to (0). If your device doesn't have internet access, set Download Mode to (99). When you set Bypass (100), the download bypasses Delivery Optimization and uses BITS instead. You don't need to set this option if you're using Configuration Manager. | +| Bypass (100) | Starting in Windows 11, this option is deprecated. Don't configure **Download mode** to '100' (Bypass), which can cause some content to fail to download. If you want to disable peer-to-peer functionality, configure DownloadMode to (0). If your device doesn't have internet access, configure Download Mode to (99). When you configure Bypass (100), the download bypasses Delivery Optimization and uses BITS instead. You don't need to configure this option if you're using Configuration Manager. | > [!NOTE] > When you use Microsoft Entra tenant, AD Site, or AD Domain as the source of group IDs, the association of devices participating in the group should not be relied on for an authentication of identity of those devices. @@ -152,152 +152,130 @@ By default, peer sharing on clients using the Group download mode (option 2) is MDM Setting: **DOGroupIDSource** -Starting in Windows 10, version 1803, set this policy to restrict peer selection to a specific source, when using a GroupID policy. The options are: +Starting in Windows 10, version 1803, configure this policy to restrict peer selection to a specific source, when using a GroupID policy. The options are: - 0 = Not set - 1 = AD Site - 2 = Authenticated domain SID - 3 = DHCP Option ID (with this option, the client queries DHCP Option ID 234 and use the returned GUID value as the Group ID) - 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. +- 5 = Starting with Windows 10, version 1903, you can use the Microsoft Entra tenant ID as a means to define groups. To do this configure 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 configured, the Group ID will be assigned automatically from the selected source. This policy is ignored if the GroupID policy is also configured. The default behavior, when the GroupID or GroupIDSource policies aren't configured, 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 configured to either DHCP Option ID (3) or DNS Suffix (4) and those methods fail, the default behavior is used instead. The option configured 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 configure 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** This setting specifies the required minimum disk size (capacity in GB) for the device to use Peer Caching. The recommended values are 64 to 256, and **the default value is 32 GB**. >[!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. +>If the [Modify Cache Drive](#modify-cache-drive) policy is configured, 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)**. +In environments configured for Delivery Optimization, you might want to configure 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 configure this value to "0" which means "unlimited" to avoid peers redownloading content. When "Unlimited" value is configured, 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%**. +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 configure 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 configured 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 configured**. -### 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. +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 configured. -### Maximum Background Download Bandwidth +### Maximum background download bandwidth MDM Setting: **DOPercentageMaxBackgroundBandwidth** -Starting in Windows 10, version 1803, specifies the maximum background 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 background downloads. However, downloads from LAN peers aren't throttled even when this policy is set. +Starting in Windows 10, version 1803, specifies the maximum background 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 background downloads. However, downloads from LAN peers aren't throttled even when this policy is configured. > [!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 MDM Setting: **DORestrictPeerSelectionBy** -Starting in Windows 10, version 1803, set this policy to restrict peer selection via selected option. In Windows 11, the 'Local Peer Discovery' option was introduced to restrict peer discovery to the local network. Currently the available options include: 0 = NAT, 1 = Subnet mask, and 2 = Local Peer Discovery. These options apply to both Download Modes LAN (1) and Group (2) and therefore means there's no peering between subnets. +Starting in Windows 10, version 1803, configure this policy to restrict peer selection via selected option. In Windows 11, the 'Local Peer Discovery' option was introduced to restrict peer discovery to the local network. Currently the available options include: 0 = NAT, 1 = Subnet mask, and 2 = Local Peer Discovery. These options apply to both Download Modes LAN (1) and Group (2) and therefore means there's no peering between subnets. -If Group mode is set, Delivery Optimization connects to locally discovered peers that are also part of the same Group (have the same Group ID). +If Group mode is configured, Delivery Optimization connects to locally discovered peers that are also part of the same Group (have the same Group ID). -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.** +In Windows 11, the Local Peer Discovery (DNS-SD) option can be configured 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 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 configured, 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, configure 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 configured, 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). +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 configure 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,38 +287,38 @@ 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** -This policy allows you to set one or more comma-separated keywords used to recognize VPN connections. **By default, this policy is not set so if a VPN is detected, the device will not use peering.** Delivery Optimization automatically detects a VPN connection by looking at the network adapter's 'Description' and 'FriendlyName' strings using the default keyword list including: "VPN", "Secure", and "Virtual Private Network" (ex: "MSFTVPN" matches the "VPN" keyword). As the number of VPNs grow it's difficult to support an ever-changing list of VPN names. To address this, we've introduced this new setting to set unique VPN names to meet the needs of individual environments. +This policy allows you to configure one or more comma-separated keywords used to recognize VPN connections. **By default, this policy is not configured so if a VPN is detected, the device will not use peering.** Delivery Optimization automatically detects a VPN connection by looking at the network adapter's 'Description' and 'FriendlyName' strings using the default keyword list including: "VPN", "Secure", and "Virtual Private Network" (ex: "MSFTVPN" matches the "VPN" keyword). As the number of VPNs grow it's difficult to support an ever-changing list of VPN names. To address this, we've introduced this new setting to add unique VPN names to meet the needs of individual environments. ### Disallow cache server downloads on VPN 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. +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.** Configure 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** -This setting specifies battery levels at which a device will be allowed to upload data. Specify any value between 1 and 100 (in percentage) to allow the device to upload data to LAN and Group peers while on DC power (Battery). Uploads will automatically pause when the battery level drops below the set minimum battery level. The recommended value to set if you allow uploads on battery is 40 (for 40%). +This setting specifies battery levels at which a device will be allowed to upload data. Specify any value between 1 and 100 (in percentage) to allow the device to upload data to LAN and Group peers while on DC power (Battery). Uploads will automatically pause when the battery level drops below the configured minimum battery level. The recommended value to configure, if you allow uploads on battery, is 40 (for 40%). 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. +> **By default, devices will not upload while on battery**. To enable uploads while on battery, you need to enable this policy and configure the battery value under which uploads pause. -### Cache Server Hostname +### Cache server hostname MDM Setting: **DOCacheHost** -Set this policy to designate one or more Microsoft Connected Cache servers to be used by Delivery Optimization. You can set one or more FQDNs or IP Addresses that are comma-separated, for example: myhost.somerandomhost.com,myhost2.somerandomhost.com,10.10.1.7. **By default, this policy has no value.** Delivery Optimization client will connect to the listed Microsoft Connected Cache servers in the order as they are listed. When multiple FQDNs or IP Addresses are listed, fallback to the CDN occurs immediately after the first failure in downloading from a cache server, unless the [DelayCacheServerFallbackBackground](#delay-background-download-cache-server-fallback-in-secs) or [DelayCacheServerFallbackForeground](#delay-foreground-download-cache-server-fallback-in-secs) policies are set. When these delay policies are set, the fallback occurs only after the configured delay time and the client continues to attempt connecting to the cache servers in round robin order before the delay time expires. +Configure this policy to designate one or more Microsoft Connected Cache servers to be used by Delivery Optimization. You can set one or more FQDNs or IP Addresses that are comma-separated, for example: myhost.somerandomhost.com,myhost2.somerandomhost.com,10.10.1.7. **By default, this policy has no value.** Delivery Optimization client will connect to the listed Microsoft Connected Cache servers in the order as they are listed. When multiple FQDNs or IP Addresses are listed, fallback to the CDN occurs immediately after the first failure in downloading from a cache server, unless the [DelayCacheServerFallbackBackground](#delay-background-download-cache-server-fallback-in-secs) or [DelayCacheServerFallbackForeground](#delay-foreground-download-cache-server-fallback-in-secs) policies are configured. When these delay policies are configured, the fallback occurs only after the configured delay time and the client continues to attempt connecting to the cache servers in round robin order before the delay time expires. >[!IMPORTANT] -> Any value will signify that the policy is set. For example, an empty string ("") isn't considered empty. +> Any value will signify that the policy is configured. For example, an empty string ("") isn't considered empty. -### Cache Server Hostname Source +### Cache server hostname source MDM Setting: **DOCacheHostSource** @@ -349,14 +327,14 @@ This policy allows you to specify how your client(s) can discover Delivery Optim - 1 = DHCP Option 235. - 2 = DHCP Option 235 Force. -With either option, the client queries DHCP Option ID 235 and use the returned value as the Cache Server Hostname. Option 2 overrides the Cache Server Hostname policy, if set. **By default, this policy has no value.** +With either option, the client queries DHCP Option ID 235 and use the returned value as the Cache Server Hostname. Option 2 overrides the Cache Server Hostname policy, if configured. **By default, this policy has no value.** -Set this policy to designate Delivery Optimization in Network Cache servers through a custom DHCP Option. Specify the custom DHCP option on your DHCP server as *text* type. You can add one or more values as either fully qualified domain names (FQDN) or IP addresses. To add multiple values, separate each FQDN or IP address with commas. +Configure this policy to designate Delivery Optimization in Network Cache servers through a custom DHCP Option. Specify the custom DHCP option on your DHCP server as *text* type. You can add one or more values as either fully qualified domain names (FQDN) or IP addresses. To add multiple values, separate each FQDN or IP address with commas. > [!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. +> 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 configured. -### 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 configured 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..10e0059d41 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? @@ -48,11 +48,11 @@ The following table lists the minimum Windows 10 version that supports Delivery #### Windows Client -| Windows Client | Minimum Windows version | HTTP Downloader | Peer to Peer | Microsoft Connected Cache (MCC) +| 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 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: | @@ -60,22 +60,22 @@ The following table lists the minimum Windows 10 version that supports Delivery | 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: | | | +| 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 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 -| Windows Server | Minimum Windows version | HTTP Downloader | Peer to Peer | Microsoft Connected Cache (MCC) +| Windows Server | Minimum Windows version | HTTP Downloader | Peer to Peer | Microsoft Connected Cache (MCC) | |----------------|--------------------------|----------------|----------|----------------| | Windows Update | Windows Server 2019 (1809) | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | | Edge Browser Updates | Windows Server 2019 (1809) | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | #### Linux (Public Preview) -| Linux ([Public Preview](https://github.com/microsoft/do-client)) | Linux versions | HTTP Downloader | Peer to Peer | Microsoft Connected Cache (MCC) +| Linux ([Public Preview](https://github.com/microsoft/do-client)) | Linux versions | HTTP Downloader | Peer to Peer | Microsoft Connected Cache (MCC) | |------------------------|----------------|-----------------|--------------|---------------| | Device Update for IoT Hub | Ubuntu 18.04, 20.04 / Debian 9, 10 | :heavy_check_mark: | | :heavy_check_mark: | > [!NOTE] 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..c9a0382033 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](https://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**. diff --git a/windows/security/application-security/application-control/windows-defender-application-control/operations/wdac-operational-guide.md b/windows/security/application-security/application-control/windows-defender-application-control/operations/wdac-operational-guide.md index 889b1c2d8d..81a98c78ca 100644 --- a/windows/security/application-security/application-control/windows-defender-application-control/operations/wdac-operational-guide.md +++ b/windows/security/application-security/application-control/windows-defender-application-control/operations/wdac-operational-guide.md @@ -3,7 +3,7 @@ title: Managing and troubleshooting Windows Defender Application Control policie description: Gather information about how your deployed Windows Defender Application Control policies are behaving. ms.localizationpriority: medium ms.date: 03/30/2023 -ms.topic: article +ms.topic: how-to ms.collection: essentials-manage --- diff --git a/windows/security/application-security/application-control/windows-defender-application-control/wdac.md b/windows/security/application-security/application-control/windows-defender-application-control/wdac.md index e178b6f5e1..f35be85ec0 100644 --- a/windows/security/application-security/application-control/windows-defender-application-control/wdac.md +++ b/windows/security/application-security/application-control/windows-defender-application-control/wdac.md @@ -8,7 +8,7 @@ ms.collection: - essentials-navigation - essentials-overview ms.date: 08/30/2023 -ms.topic: article +ms.topic: overview --- # Application Control for Windows