From 75be2783cf39dd2816c960fa9bf80357a1ad5166 Mon Sep 17 00:00:00 2001 From: Carmen Forsmann Date: Fri, 14 Apr 2023 16:14:34 -0600 Subject: [PATCH 01/12] Update waas-delivery-optimization-faq.yml --- windows/deployment/do/waas-delivery-optimization-faq.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index f363e5116d..66d5f82e1b 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -99,3 +99,9 @@ sections: > [!NOTE] > If you use public IP addresses instead of private in LAN mode, the bytes downloaded from or uploaded to LAN peers with public IP addresses might be reported as coming from Internet peers. + - question: How are downloads initiated by Delivery Optimization? + answer: Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). + + - question: How does Delivery Optimization determine which content is available for peering? + answer: Delivery Optimization uses the cache content on the device to determine what is available for peering. There is a limited number (4) of slots for cached content that is available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots. + From f5000ee018bd39dd5e8ef62cb429116380ff2dfd Mon Sep 17 00:00:00 2001 From: Carmen Forsmann Date: Fri, 14 Apr 2023 16:21:36 -0600 Subject: [PATCH 02/12] Update waas-delivery-optimization-faq.yml --- windows/deployment/do/waas-delivery-optimization-faq.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index 66d5f82e1b..7dcafef147 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -100,8 +100,10 @@ sections: > If you use public IP addresses instead of private in LAN mode, the bytes downloaded from or uploaded to LAN peers with public IP addresses might be reported as coming from Internet peers. - question: How are downloads initiated by Delivery Optimization? - answer: Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). + answer: | + Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). - question: How does Delivery Optimization determine which content is available for peering? - answer: Delivery Optimization uses the cache content on the device to determine what is available for peering. There is a limited number (4) of slots for cached content that is available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots. + answer: | + Delivery Optimization uses the cache content on the device to determine what is available for peering. There is a limited number (4) of slots for cached content that is available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots. From 95384f5df5bbfd7baca40382012f32b2ad3ab32b Mon Sep 17 00:00:00 2001 From: Carmen Forsmann Date: Fri, 14 Apr 2023 16:30:38 -0600 Subject: [PATCH 03/12] Update waas-delivery-optimization-faq.yml --- windows/deployment/do/waas-delivery-optimization-faq.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index 7dcafef147..9d0334392d 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -101,7 +101,7 @@ sections: - question: How are downloads initiated by Delivery Optimization? answer: | - Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). + Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). - question: How does Delivery Optimization determine which content is available for peering? answer: | From 5cc83ba33c0d275e03982db29a5a814b9d76902c Mon Sep 17 00:00:00 2001 From: Carmen Forsmann Date: Fri, 14 Apr 2023 16:41:14 -0600 Subject: [PATCH 04/12] Update waas-delivery-optimization-faq.yml --- windows/deployment/do/waas-delivery-optimization-faq.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index 9d0334392d..6cbda96233 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -99,11 +99,11 @@ sections: > [!NOTE] > If you use public IP addresses instead of private in LAN mode, the bytes downloaded from or uploaded to LAN peers with public IP addresses might be reported as coming from Internet peers. - - question: How are downloads initiated by Delivery Optimization? - answer: | + - question: How are downloads initiated by Delivery Optimization? + answer: | Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). - - question: How does Delivery Optimization determine which content is available for peering? - answer: | + - question: How does Delivery Optimization determine which content is available for peering? + answer: | Delivery Optimization uses the cache content on the device to determine what is available for peering. There is a limited number (4) of slots for cached content that is available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots. From 18e2d4750d7a7cecf3e3d6d3c22b377561d531af Mon Sep 17 00:00:00 2001 From: Christine Eaton <40660908+ceaton001@users.noreply.github.com> Date: Mon, 17 Apr 2023 11:45:27 +0100 Subject: [PATCH 05/12] Update windows-autopatch-device-registration-overview.md Removed references to Dynamic Windows 10 and Windows 11 groups that are no longer created. --- .../deploy/windows-autopatch-device-registration-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md index b6ead33041..55898ea671 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md @@ -48,7 +48,7 @@ See the following detailed workflow diagram. The diagram covers the Windows Auto | **Step 4: Check prerequisites** | The Windows Autopatch prerequisite function makes an Intune Graph API call to sequentially validate device readiness attributes required for the registration process. For detailed information, see the [Detailed prerequisite check workflow diagram](#detailed-prerequisite-check-workflow-diagram) section. The service checks the following device readiness attributes, and/or prerequisites:
  1. **Serial number, model, and manufacturer.**
    1. Checks if the serial number already exists in the Windows Autopatch’s managed device database.
  2. **If the device is Intune-managed or not.**
    1. Windows Autopatch looks to see **if the Azure AD device ID has an Intune device ID associated with it**.
      1. If **yes**, it means this device is enrolled into Intune.
      2. If **not**, it means the device isn't enrolled into Intune, hence it can't be managed by the Windows Autopatch service.
    2. **If the device is not managed by Intune**, the Windows Autopatch service can't gather device attributes such as operating system version, Intune enrollment date, device name and other attributes. When this happens, the Windows Autopatch service uses the Azure AD device attributes gathered and saved to its memory in **step 3a**.
      1. Once it has the device attributes gathered from Azure AD in **step 3a**, the device is flagged with the **Prerequisite failed** status, then added to the **Not registered** tab so the IT admin can review the reason(s) the device wasn't registered into Windows Autopatch. The IT admin will remediate these devices. In this case, the IT admin should check why the device wasn’t enrolled into Intune.
      2. A common reason is when the Azure AD device ID is stale, it doesn’t have an Intune device ID associated with it anymore. To remediate, [clean up any stale Azure AD device records from your tenant](windows-autopatch-register-devices.md#clean-up-dual-state-of-hybrid-azure-ad-joined-and-azure-registered-devices-in-your-azure-ad-tenant).
    3. **If the device is managed by Intune**, the Windows Autopatch prerequisite check function continues to the next prerequisite check, which evaluates whether the device has checked into Intune in the last 28 days.
  3. **If the device is a Windows device or not.**
    1. Windows Autopatch looks to see if the device is a Windows and corporate-owned device.
      1. **If yes**, it means this device can be registered with the service because it's a Windows corporate-owned device.
      2. **If not**, it means the device is a non-Windows device, or it's a Windows device but it's a personal device.
  4. **Windows Autopatch checks the Windows SKU family**. The SKU must be either:
    1. **Enterprise**
    2. **Pro**
    3. **Pro Workstation**
  5. **If the device meets the operating system requirements**, Windows Autopatch checks whether the device is either:
    1. **Only managed by Intune.**
      1. If the device is only managed by Intune, the device is marked as Passed all prerequisites.
    2. **Co-managed by both Configuration Manager and Intune.**
      1. If the device is co-managed by both Configuration Manager and Intune, an additional prerequisite check is evaluated to determine if the device satisfies the co-management-enabled workloads required by Windows Autopatch to manage devices in a co-managed state. The required co-management workloads evaluated in this step are:
        1. **Windows Updates Policies**
        2. **Device Configuration**
        3. **Office Click to Run**
      2. If Windows Autopatch determines that one of these workloads isn’t enabled on the device, the service marks the device as **Prerequisite failed** and moves the device to the **Not registered** tab.
| | **Step 5: Calculate deployment ring assignment** | Once the device passes all prerequisites described in **step #4**, Windows Autopatch starts its deployment ring assignment calculation. The following logic is used to calculate the Windows Autopatch deployment ring assignment:
  1. If the Windows Autopatch tenant’s existing managed device size is **≤ 200**, the deployment ring assignment is **First (5%)**, **Fast (15%)**, remaining devices go to the **Broad ring (80%)**.
  2. If the Windows Autopatch tenant’s existing managed device size is **>200**, the deployment ring assignment will be **First (1%)**, **Fast (9%)**, remaining devices go to the **Broad ring (90%)**.
| | **Step 6: Assign devices to a deployment ring group** | Once the deployment ring calculation is done, Windows Autopatch assigns devices to one of the following deployment ring groups:
  1. **Modern Workplace Devices-Windows Autopatch-First**
    1. The Windows Autopatch device registration process doesn’t automatically assign devices to the Test ring represented by the Azure AD group (Modern Workplace Devices-Windows Autopatch-Test). It’s important that you assign devices to the Test ring to validate the update deployments before the updates are deployed to a broader population of devices.
  2. **Modern Workplace Devices-Windows Autopatch-Fast**
  3. **Modern Workplace Devices-Windows Autopatch-Broad**
| -| **Step 7: Assign devices to an Azure AD group** | Windows Autopatch also assigns devices to the following Azure AD groups when certain conditions apply:
  1. **Modern Workplace Devices - All**
    1. This group has all devices managed by Windows Autopatch.
  2. When registering **Windows 10 devices**, use **Modern Workplace Devices Dynamic - Windows 10**
    1. This group has all devices managed by Windows Autopatch and that have Windows 10 installed.
  3. When registering **Windows 11 devices**, use **Modern Workplace Devices Dynamic - Windows 11**
    1. This group has all devices managed by Windows Autopatch and that have Windows 11 installed.
  4. When registering **virtual devices**, use **Modern Workplace Devices - Virtual Machine**
    1. This group has all virtual devices managed by Windows Autopatch.
    | +| **Step 7: Assign devices to an Azure AD group** | Windows Autopatch also assigns devices to the following Azure AD groups when certain conditions apply:
    1. **Modern Workplace Devices - All**
      1. This group has all devices managed by Windows Autopatch.
    2. **Modern Workplace Devices - Virtual Machine**
      1. This group has all **virtual devices** managed by Windows Autopatch.
      | | **Step 8: Post-device registration** | In post-device registration, three actions occur:
      1. Windows Autopatch adds devices to its managed database.
      2. Flags devices as **Active** in the **Ready** tab.
      3. The Azure AD device ID of the device successfully registered is added into the Microsoft Cloud Managed Desktop Extension’s allowlist. Windows Autopatch installs the Microsoft Cloud Managed Desktop Extension agent once devices are registered, so the agent can communicate back to the Microsoft Cloud Managed Desktop Extension service.
        1. The agent is the **Modern Workplace - Autopatch Client setup** PowerShell script that was created during the Windows Autopatch tenant enrollment process. The script is executed once devices are successfully registered into the Windows Autopatch service.
        | | **Step 9: Review device registration status** | IT admins review the device registration status in both the **Ready** and **Not registered** tabs.
        1. If the device was **successfully registered**, the device shows up in the **Ready** tab.
        2. If **not**, the device shows up in the **Not registered** tab.
        | | **Step 10: End of registration workflow** | This is the end of the Windows Autopatch device registration workflow. | From 047174950af24ed7e1e64040e68344bb25530907 Mon Sep 17 00:00:00 2001 From: Carmen Forsmann Date: Mon, 17 Apr 2023 08:44:21 -0600 Subject: [PATCH 06/12] Update waas-delivery-optimization-faq.yml --- windows/deployment/do/waas-delivery-optimization-faq.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index 6cbda96233..21e2d8223e 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -101,9 +101,9 @@ sections: - question: How are downloads initiated by Delivery Optimization? answer: | - Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). + Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). [Learn more](waas-delivery-optimization#types-of-download-content-supported-by-delivery-optimization) about the complete list of Delivery Optimization callers. - question: How does Delivery Optimization determine which content is available for peering? answer: | - Delivery Optimization uses the cache content on the device to determine what is available for peering. There is a limited number (4) of slots for cached content that is available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots. + Delivery Optimization uses the cache content on the device to determine what is available for peering. For the upload source device there is a limited number (4) of slots for cached content that is available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots. From 1c2f371a1e89886742797dbf968d329094b73369 Mon Sep 17 00:00:00 2001 From: Carmen Forsmann Date: Mon, 17 Apr 2023 08:47:35 -0600 Subject: [PATCH 07/12] Update waas-delivery-optimization-faq.yml --- windows/deployment/do/waas-delivery-optimization-faq.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index 21e2d8223e..303e6a22c3 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -101,7 +101,7 @@ sections: - question: How are downloads initiated by Delivery Optimization? answer: | - Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). [Learn more](waas-delivery-optimization#types-of-download-content-supported-by-delivery-optimization) about the complete list of Delivery Optimization callers. + Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). [Learn more](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) about the complete list of Delivery Optimization callers. - question: How does Delivery Optimization determine which content is available for peering? answer: | From 79356e6dcd7b3662513576b7b0e8156d97001e67 Mon Sep 17 00:00:00 2001 From: Carmen Forsmann Date: Mon, 17 Apr 2023 09:00:42 -0600 Subject: [PATCH 08/12] Update waas-delivery-optimization-faq.yml --- .../deployment/do/waas-delivery-optimization-faq.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index 303e6a22c3..ab1278c4e9 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -1,7 +1,7 @@ ### YamlMime:FAQ metadata: title: Delivery Optimization Frequently Asked Questions - description: The following is a list of frequently asked questions for Delivery Optimization. + description: List of frequently asked questions for Delivery Optimization. ms.reviewer: mstewart ms.prod: windows-client author: cmknox @@ -29,7 +29,7 @@ sections: answer: | Delivery Optimization listens on port 7680 for requests from other peers by using TCP/IP. The service will register and open this port on the device. The port must be set to accept inbound traffic through your firewall. If you don't allow inbound traffic over port 7680, you can't use the peer-to-peer functionality of Delivery Optimization. However, devices can still successfully download by using HTTP or HTTPS traffic over port 80 (such as for default Windows Update data). - Delivery Optimization will use Teredo to create peer groups, which include devices across NATs (or any form of internal subnet that uses gateways or firewalls between subnets). For this to work, you must allow inbound TCP/IP traffic over port 3544. Look for a "NAT traversal" setting in your firewall to set this up. + Delivery Optimization will use Teredo to create peer groups, which include devices across NATs (or any form of internal subnet that uses gateways or firewalls between subnets). To enable this scenario, you must allow inbound TCP/IP traffic over port 3544. Look for a "NAT traversal" setting in your firewall to set this up. Delivery Optimization also communicates with its cloud service by using HTTP/HTTPS over port 80. @@ -70,7 +70,7 @@ sections: If the connection is identified as a VPN, Delivery Optimization will suspend uploads to other peers. However, you can allow uploads over a VPN by using the [Enable Peer Caching while the device connects via VPN](../do/waas-delivery-optimization-reference.md#enable-peer-caching-while-the-device-connects-via-vpn) policy. - If you have defined a boundary group in Configuration Manager for VPN IP ranges, you can set the [DownloadMode](../do/waas-delivery-optimization-reference.md#download-mode) policy to 0 for that boundary group, to ensure that there will be no peer-to-peer activity over the VPN. When the device is not connected using a VPN, it can still use peer-to-peer with the default of LAN. + If you have defined a boundary group in Configuration Manager for VPN IP ranges, you can set the [DownloadMode](../do/waas-delivery-optimization-reference.md#download-mode) policy to 0 for that boundary group, to ensure that there will be no peer-to-peer activity over the VPN. When the device isn't connected using a VPN, it can still use peer-to-peer with the default of LAN. With split tunneling, make sure to allow direct access to these endpoints: @@ -101,9 +101,9 @@ sections: - question: How are downloads initiated by Delivery Optimization? answer: | - Delivery Optimization only starts a download when it is initated by an application/service that has been integrated with Delivery Optimization (e.g. Edge browser). [Learn more](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) about the complete list of Delivery Optimization callers. + Delivery Optimization only starts when an application/service that has been integrated with Delivery Optimizationdownload initiates a download (for example, Edge browser). [Learn more](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) about the complete list of Delivery Optimization callers. - question: How does Delivery Optimization determine which content is available for peering? answer: | - Delivery Optimization uses the cache content on the device to determine what is available for peering. For the upload source device there is a limited number (4) of slots for cached content that is available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots. + Delivery Optimization uses the cache content on the device to determine what is available for peering. For the upload source device there's a limited number (4) of slots for cached content that is available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots. From 993b0de41ea61f5dd9e7648bbc7cd7df4ac8a355 Mon Sep 17 00:00:00 2001 From: Carmen Forsmann Date: Mon, 17 Apr 2023 09:11:51 -0600 Subject: [PATCH 09/12] Update waas-delivery-optimization-faq.yml --- windows/deployment/do/waas-delivery-optimization-faq.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index ab1278c4e9..91340c5637 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -101,7 +101,7 @@ sections: - question: How are downloads initiated by Delivery Optimization? answer: | - Delivery Optimization only starts when an application/service that has been integrated with Delivery Optimizationdownload initiates a download (for example, Edge browser). [Learn more](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) about the complete list of Delivery Optimization callers. + Delivery Optimization only starts when an application/service that has been integrated with Delivery Optimization initiates a download (for example, Edge browser). [Learn more](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) about the complete list of Delivery Optimization callers. - question: How does Delivery Optimization determine which content is available for peering? answer: | From 37d872deebb063b47cec8eaefb59bc985190a86d Mon Sep 17 00:00:00 2001 From: Christine Eaton <40660908+ceaton001@users.noreply.github.com> Date: Mon, 17 Apr 2023 17:11:26 +0100 Subject: [PATCH 10/12] Update windows-autopatch-changes-to-tenant.md Added a group missing from the list (after checking with Andre that it's still used). --- .../references/windows-autopatch-changes-to-tenant.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/references/windows-autopatch-changes-to-tenant.md b/windows/deployment/windows-autopatch/references/windows-autopatch-changes-to-tenant.md index b330342957..bf23950f18 100644 --- a/windows/deployment/windows-autopatch/references/windows-autopatch-changes-to-tenant.md +++ b/windows/deployment/windows-autopatch/references/windows-autopatch-changes-to-tenant.md @@ -45,7 +45,8 @@ The following groups target Windows Autopatch configurations to devices and mana | ----- | ----- | | Modern Workplace-All | All Modern Workplace users | | Modern Workplace - Windows 11 Pre-Release Test Devices | Device group for Windows 11 Pre-Release testing. | -| Modern Workplace Devices-All | All Modern Workplace devices | +| Modern Workplace Devices-All | All Autopatch devices | +| Modern Workplace Devices-Virtual Machine | All Autopatch virtual devices | | Modern Workplace Devices-Windows Autopatch-Test | Deployment ring for testing update deployments prior production rollout | | Modern Workplace Devices-Windows Autopatch-First | First production deployment ring for early adopters | | Modern Workplace Devices-Windows Autopatch-Fast | Fast deployment ring for quick rollout and adoption | From 563fed4aa999013e18e2f096872be7680186290d Mon Sep 17 00:00:00 2001 From: Aaron Czechowski Date: Mon, 17 Apr 2023 09:30:17 -0700 Subject: [PATCH 11/12] editorial revision --- windows/deployment/do/waas-delivery-optimization-faq.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index 91340c5637..1a0f413fd5 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -12,7 +12,7 @@ metadata: - highpri - tier3 ms.topic: faq - ms.date: 08/04/2022 + ms.date: 04/17/2023 title: Delivery Optimization Frequently Asked Questions summary: | **Applies to** @@ -101,9 +101,9 @@ sections: - question: How are downloads initiated by Delivery Optimization? answer: | - Delivery Optimization only starts when an application/service that has been integrated with Delivery Optimization initiates a download (for example, Edge browser). [Learn more](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) about the complete list of Delivery Optimization callers. + Delivery Optimization only starts when an application or service that's integrated with Delivery Optimization starts a download. For example, the Microsoft Edge browser. For more information about Delivery Optimization callers, see [Types of download content supported by Delivery Optimization](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization). - question: How does Delivery Optimization determine which content is available for peering? answer: | - Delivery Optimization uses the cache content on the device to determine what is available for peering. For the upload source device there's a limited number (4) of slots for cached content that is available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots. + Delivery Optimization uses the cache content on the device to determine what's available for peering. For the upload source device, there's a limited number (4) of slots for cached content that's available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots. From c250de836935a6b0ea08ca83af33fc0e97be6053 Mon Sep 17 00:00:00 2001 From: Aaron Czechowski Date: Mon, 17 Apr 2023 10:10:28 -0700 Subject: [PATCH 12/12] add note re window size --- .../windows-sandbox-configure-using-wsb-file.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/security/threat-protection/windows-sandbox/windows-sandbox-configure-using-wsb-file.md b/windows/security/threat-protection/windows-sandbox/windows-sandbox-configure-using-wsb-file.md index 4ff1d859be..e9790d83e9 100644 --- a/windows/security/threat-protection/windows-sandbox/windows-sandbox-configure-using-wsb-file.md +++ b/windows/security/threat-protection/windows-sandbox/windows-sandbox-configure-using-wsb-file.md @@ -30,6 +30,9 @@ A configuration file enables the user to control the following aspects of Window - **Clipboard redirection**: Shares the host clipboard with the sandbox so that text and files can be pasted back and forth. - **Memory in MB**: The amount of memory, in megabytes, to assign to the sandbox. +> [!NOTE] +> The size of the sandbox window currently isn't configurable. + ## Creating a configuration file To create a configuration file: