Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into wufbr-perms-7738226

2025-06-17 11:23:45 +00:00 · 2023-04-26 10:03:49 -07:00
parent 9eae3e74d9 99a289c749
commit 642352ebeb
277 changed files with 4482 additions and 7673 deletions
--- a/windows/deployment/update/waas-configure-wufb.md
+++ b/windows/deployment/update/waas-configure-wufb.md
@ -221,7 +221,7 @@ The features that are turned off by default from servicing updates will be enabl

 | Policy | Sets registry key under HKLM\Software |
 | --- | --- |
-| GPO for Windows 11, version 22H2 with [kb5022845](https://support.microsoft.com/en-us/topic/february-14-2023-kb5022845-os-build-22621-1265-90a807f4-d2e8-486e-8a43-d09e66319f38) and later: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage end user experience > **Enable features introduced via servicing that are off by default**| \Policies\Microsoft\Windows\WindowsUpdate\ExcludeWUDriversInQualityUpdate  |
+| GPO for Windows 11, version 22H2 with [kb5022845](https://support.microsoft.com/en-us/topic/february-14-2023-kb5022845-os-build-22621-1265-90a807f4-d2e8-486e-8a43-d09e66319f38) and later: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage end user experience > **Enable features introduced via servicing that are off by default**| \Policies\Microsoft\Windows\WindowsUpdate\AllowTemporaryEnterpriseFeatureControl  |
 | MDM for Windows 11, version 22H2 with [kb5022845](https://support.microsoft.com/en-us/topic/february-14-2023-kb5022845-os-build-22621-1265-90a807f4-d2e8-486e-8a43-d09e66319f38) and later: </br>../Vendor/MSFT/Policy/Config/Update/</br>**[AllowTemporaryEnterpriseFeatureControl](/windows/client-management/mdm/policy-csp-update?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#allowtemporaryenterprisefeaturecontrol)** | \Microsoft\PolicyManager\default\Update\AllowTemporaryEnterpriseFeatureControl |


--- a/windows/deployment/update/waas-wu-settings.md
+++ b/windows/deployment/update/waas-wu-settings.md
@ -11,7 +11,7 @@ ms.collection:
  - highpri
  - tier2
 ms.technology: itpro-updates
-ms.date: 03/09/2023
+ms.date: 04/25/2023
 ---

 # Manage additional Windows Update settings
@ -35,6 +35,8 @@ You can use Group Policy settings or mobile device management (MDM) to configure
 | [Do not include drivers with Windows Updates](#do-not-include-drivers-with-windows-updates) | [ExcludeWUDriversInQualityUpdate](/windows/client-management/mdm/policy-configuration-service-provider#update-excludewudriversinqualityupdate) | 1607 |
 | [Configure Automatic Updates](#configure-automatic-updates) | [AllowAutoUpdate](/windows/client-management/mdm/policy-configuration-service-provider#update-allowautoupdate) | All |
 | |  [Windows Update notifications display organization name](#display-organization-name-in-windows-update-notifications) </br></br> *Organization name is displayed by default. A registry value can disable this behavior. | Windows 11 devices that are Azure Active Directory joined or registered <!--6286260-->|
+| | [Allow Windows updates to install before initial user sign-in](#allow-windows-updates-to-install-before-initial-user-sign-in) (registry only)| Windows 11 version 22H2 with 2023-04 Cumulative Update Preview, or a later cumulative update <!--7679187-->|
+

 >[!IMPORTANT]
 >Additional information about settings to manage device restarts and restart notifications for updates is available on **[Manage device restarts after updates](waas-restart.md)**.
@ -47,7 +49,7 @@ Admins have a lot of flexibility in configuring how their devices scan and recei

 [Specify Intranet Microsoft update service location](#specify-intranet-microsoft-update-service-location) allows admins to point devices to an internal Microsoft update service location, while [Do not connect to any Windows Update Internet locations](#do-not-connect-to-any-windows-update-internet-locations) gives them the option to restrict devices to just that internal update service. [Automatic Updates Detection Frequency](#automatic-updates-detection-frequency) controls how frequently devices scan for updates.

-You can make custom device groups that'll work with your internal Microsoft update service by using [Enable client-side targeting](#enable-client-side-targeting). You can also make sure your devices receive updates that were not signed by Microsoft from your internal Microsoft update service, through [Allow signed updates from an intranet Microsoft update service location](#allow-signed-updates-from-an-intranet-microsoft-update-service-location).
+You can make custom device groups that will work with your internal Microsoft update service by using [Enable client-side targeting](#enable-client-side-targeting). You can also make sure your devices receive updates that weren't signed by Microsoft from your internal Microsoft update service, through [Allow signed updates from an intranet Microsoft update service location](#allow-signed-updates-from-an-intranet-microsoft-update-service-location).

 Finally, to make sure the updating experience is fully controlled by the admins, you can [Remove access to use all Windows Update features](#remove-access-to-use-all-windows-update-features) for users.

@ -61,10 +63,10 @@ This setting lets you specify a server on your network to function as an interna
 To use this setting in Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Windows Update\Specify Intranet Microsoft update service location**. You must set two server name values: the server from which the Automatic Updates client detects and downloads updates, and the server to which updated workstations upload statistics. You can set both values to be the same server. An optional server name value can be specified to configure Windows Update Agent to download updates from an alternate download server instead of the intranet update service.

 If the setting is set to **Enabled**, the Automatic Updates client connects to the specified intranet Microsoft update service (or alternate download server), instead of Windows Update, to search for and download updates. Enabling this setting means that end users in your organization don't have to go through a firewall to get updates, and it gives you the opportunity to test updates after deploying them.
-If the setting is set to **Disabled** or **Not Configured**, and if Automatic Updates is not disabled by policy or user preference, the Automatic Updates client connects directly to the Windows Update site on the Internet.
+If the setting is set to **Disabled** or **Not Configured**, and if Automatic Updates isn't disabled by policy or user preference, the Automatic Updates client connects directly to the Windows Update site on the Internet.

 The alternate download server configures the Windows Update Agent to download files from an alternative download server instead of the intranet update service.
-The option to download files with missing Urls allows content to be downloaded from the Alternate Download Server when there are no download Urls for files in the update metadata. This option should only be used when the intranet update service does not provide download Urls in the update metadata for files which are present on the alternate download server.
+The option to download files with missing Urls allows content to be downloaded from the Alternate Download Server when there are no download Urls for files in the update metadata. This option should only be used when the intranet update service doesn't provide download Urls in the update metadata for files that are present on the alternate download server.

 >[!NOTE]
 >If the "Configure Automatic Updates" policy is disabled, then this policy has no effect.
@ -109,7 +111,7 @@ Use **Computer Configuration\Administrative Templates\Windows Components\Windows
 Specifies the target group name or names that should be used to receive updates from an intranet Microsoft update service. This allows admins to configure device groups that will receive different updates from sources like WSUS or Configuration Manager.

 This Group Policy setting can be found under **Computer Configuration\Administrative Templates\Windows Components\Windows update\Enable client-side targeting**.
-If the setting is set to **Enabled**, the specified target group information is sent to the intranet Microsoft update service which uses it to determine which updates should be deployed to this computer.
+If the setting is set to **Enabled**, the specified target group information is sent to the intranet Microsoft update service, which uses it to determine which updates should be deployed to this computer.
 If the setting is set to **Disabled** or **Not Configured**, no target group information will be sent to the intranet Microsoft update service.

 If the intranet Microsoft update service supports multiple target groups, this policy can specify multiple group names separated by semicolons. Otherwise, a single group must be specified.
@ -123,8 +125,8 @@ This policy setting allows you to manage whether Automatic Updates accepts updat

 To configure this setting in Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Windows update\Allow signed updates from an intranet Microsoft update service location**.

-If you enable this policy setting, Automatic Updates accepts updates received through an intranet Microsoft update service location, as specified by [Specify Intranet Microsoft update service location](#specify-intranet-microsoft-update-service-location), if they are signed by a certificate found in the "Trusted Publishers" certificate store of the local computer.
-If you disable or do not configure this policy setting, updates from an intranet Microsoft update service location must be signed by Microsoft.
+If you enable this policy setting, Automatic Updates accepts updates received through an intranet Microsoft update service location, as specified by [Specify Intranet Microsoft update service location](#specify-intranet-microsoft-update-service-location), if they're signed by a certificate found in the "Trusted Publishers" certificate store of the local computer.
+If you disable or don't configure this policy setting, updates from an intranet Microsoft update service location must be signed by Microsoft.

 >[!NOTE]
 >Updates from a service other than an intranet Microsoft update service must always be signed by Microsoft and are not affected by this policy setting.
@ -136,7 +138,7 @@ To configure this policy with MDM, use [AllowNonMicrosoftSignedUpdate](/windows/

 To add more flexibility to the update process, settings are available to control update installation.

-[Configure Automatic Updates](#configure-automatic-updates) offers four different options for automatic update installation, while [Do not include drivers with Windows Updates](#do-not-include-drivers-with-windows-updates) makes sure drivers are not installed with the rest of the received updates.
+[Configure Automatic Updates](#configure-automatic-updates) offers four different options for automatic update installation, while [Do not include drivers with Windows Updates](#do-not-include-drivers-with-windows-updates) makes sure drivers aren't installed with the rest of the received updates.

 ### Do not include drivers with Windows Updates

@ -144,7 +146,7 @@ Allows admins to exclude Windows Update drivers during updates.

 To configure this setting in Group Policy, use **Computer Configuration\Administrative Templates\Windows Components\Windows update\Do not include drivers with Windows Updates**.
 Enable this policy to not include drivers with Windows quality updates.
-If you disable or do not configure this policy, Windows Update will include updates that have a Driver classification.
+If you disable or don't configure this policy, Windows Update will include updates that have a Driver classification.

 ### Configure Automatic Updates

@ -156,13 +158,13 @@ Under **Computer Configuration\Administrative Templates\Windows Components\Windo

 **2 - Notify for download and auto install** -  When Windows finds updates that apply to this device, users will be notified that updates are ready to be downloaded. After going to **Settings > Update & security > Windows Update**, users can download and install any available updates.

-**3 - Auto download and notify for Install** - Windows finds updates that apply to the device and downloads them in the background (the user is not notified or interrupted during this process). When the downloads are complete, users will be notified that they are ready to install. After going to **Settings > Update & security > Windows Update**, users can install them.
+**3 - Auto download and notify for Install** - Windows finds updates that apply to the device and downloads them in the background (the user isn't notified or interrupted during this process). When the downloads are complete, users will be notified that they're ready to install. After going to **Settings > Update & security > Windows Update**, users can install them.

 **4 - Auto download and schedule the install** - Specify the schedule using the options in the Group Policy Setting. For more information about this setting, see [Schedule update installation](waas-restart.md#schedule-update-installation).

-**5 - Allow local admin to choose setting** - With this option, local administrators will be allowed to use the settings app to select a configuration option of their choice. Local administrators will not be allowed to disable the configuration for Automatic Updates. This option is not available in any Windows 10 or later versions. 
+**5 - Allow local admin to choose setting** - With this option, local administrators will be allowed to use the settings app to select a configuration option of their choice. Local administrators won't be allowed to disable the configuration for Automatic Updates. This option isn't available in any Windows 10 or later versions. 

-**7 - Notify for install and notify for restart** (Windows Server 2016 and later only) - With this option, when Windows finds updates that apply to this device, they will be downloaded, then users will be notified that updates are ready to be installed. Once updates are installed, a notification will be displayed to users to restart the device. 
+**7 - Notify for install and notify for restart** (Windows Server 2016 and later only) - With this option, when Windows finds updates that apply to this device, they'll be downloaded, then users will be notified that updates are ready to be installed. Once updates are installed, a notification will be displayed to users to restart the device. 

 If this setting is set to **Disabled**, any updates that are available on Windows Update must be downloaded and installed manually. To do this, users must go to **Settings > Update & security > Windows Update**.

@ -173,7 +175,7 @@ If this setting is set to **Not Configured**, an administrator can still configu
 > [!NOTE]
 > Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require you to reinstall the operating system. Microsoft cannot guarantee that these problems can be resolved. Modify the registry at your own risk.

-In an environment that does not have Active Directory deployed, you can edit registry settings to configure group policies for Automatic Update.
+In an environment that doesn't have Active Directory deployed, you can edit registry settings to configure group policies for Automatic Update.

 To do this, follow these steps:

@ -203,7 +205,7 @@ To do this, follow these steps:

     * **4**: Automatically download and scheduled installation.

-     * **5**: Allow local admin to select the configuration mode. This option is not available for Windows 10 or later versions.
+     * **5**: Allow local admin to select the configuration mode. This option isn't available for Windows 10 or later versions.

     * **7**:  Notify for install and notify for restart. (Windows Server 2016 and later only)

@ -230,7 +232,7 @@ To do this, follow these steps:

   * NoAutoRebootWithLoggedOnUsers (REG_DWORD):

-     **0** (false) or **1** (true). If set to **1**, Automatic Updates does not automatically restart a computer while users are logged on.
+     **0** (false) or **1** (true). If set to **1**, Automatic Updates doesn't automatically restart a computer while users are logged on.

     > [!NOTE]
     > This setting affects client behavior after the clients have updated to the SUS SP1 client version or later versions.
@ -264,7 +266,7 @@ The organization name appears automatically for Windows 11 clients that are asso
 To disable displaying the organization name in Windows Update notifications, add or modify the following in the registry:

   - **Registry key**: `HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsUpdate\Orchestrator\Configurations`
-  -   **DWORD value name**: UsoDisableAADJAttribution
+  - **DWORD value name**: UsoDisableAADJAttribution
  - **Value data:** 1

 The following PowerShell script is provided as an example to you: 
@ -280,3 +282,17 @@ if (!(Test-Path $registryPath))

 New-ItemProperty -Path $registryPath -Name $name -Value $value -PropertyType DWORD -Force | Out-Null
 ```
+
+## Allow Windows updates to install before initial user sign-in
+*(Starting in Windows 11, version 22H2 with 2023-04 Cumulative Update Preview, or a later cumulative update)* <!--7679187-->
+
+On new devices, Windows Update doesn't begin installing background updates until a user has completed the Out of Box Experience (OOBE) and signs in for the first time. In many cases, the user signs in immediately after completing the OOBE. However, some VM-based solutions provision a device and automate the first user experience. These VMs may not be immediately assigned to a user so they won't see an initial sign-in until several days later.  
+
+In scenarios where initial sign-in is delayed, setting the following registry values allow devices to begin background update work before a user first signs in:
+
+- **Registry key**: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Orchestrator
+- **DWORD value name**: ScanBeforeInitialLogonAllowed
+- **Value data**: 1
+
+> [!Warning]
+> This value is designed to be used only for scenarios with a deferred initial user sign in. Setting this value on devices where initial user sign in isn't delayed could have a detrimental effect on performance since it may allow update work to occur as the user is signing in for the first time.
--- a/windows/deployment/update/wufb-reports-do.md
+++ b/windows/deployment/update/wufb-reports-do.md
@ -0,0 +1,166 @@
+---
+title: Delivery Optimization data in Windows Update for Business reports
+manager: aaroncz
+description: Provides information about Delivery Optimization data in Windows Update for Business reports 
+ms.prod: windows-client
+author: mestew
+ms.author: mstewart
+ms.topic: article
+ms.date: 04/12/2023
+ms.technology: itpro-updates
+---
+
+# Delivery Optimization data in Windows Update for Business reports
+<!--7715481-->
+***(Applies to: Windows 11 & Windows 10)***
+
+[Delivery Optimization](../do/waas-delivery-optimization.md) (DO) is a Windows feature that can be used to reduce bandwidth consumption by sharing the work of downloading updates among multiple devices in your environment. You can use DO with many other deployment methods, but it's a cloud-managed solution, and access to the DO cloud services is a requirement. 
+
+Windows Update for Business reports provides Delivery Optimization information in the following places:
+- The Windows Update for Business reports [workbook](wufb-reports-workbook.md)
+- [UCDOAggregatedStatus](wufb-reports-schema-ucdoaggregatedstatus.md)
+- [UCDOStatus](wufb-reports-schema-ucdostatus.md)
+
+Windows Update for Business reports doesn't include Delivery Optimization data for Windows Insider devices. 
+
+## Delivery Optimization terms
+
+Windows Update for Business reports uses the following Delivery Optimization terms:
+
+- **Peer**: A device in the solution
+- **Peering 'ON'** - Devices where DO peer-to-peer is enabled in one of the following modes:
+   - LAN (1)
+   - Group (2)
+   - Internet (3)
+- **Peering 'OFF'**: Devices where DO peer-to-peer is disabled, set to one of the following modes:
+   - HTTP Only (0)
+   - Simple Mode (99)
+   - Bypass (100), deprecated in Windows 11
+- **Bandwidth savings**: The percentage of bandwidth that was downloaded from alternate sources (Peers or Microsoft Connected Cache (MCC) out of the total amount of data downloaded.
+   - If bandwidth savings are <= 60%, a *Warning* icon is displayed
+   - When bandwidth savings are <10%, an *Error* icon is displayed.
+- **Configurations**: Based on the DownloadMode configuration set via MDM, Group Policy, or end-user via the user interface.
+- **P2P Device Count**: The device count is determined by the number of devices configured to use peering.
+- **Microsoft Connected Cache (MCC)**: Microsoft Connected Cache is a software-only caching solution that delivers Microsoft content. For more information, see [Microsoft Connected Cache overview](../do/waas-microsoft-connected-cache.md).
+- **MCC Device Count**: The device count is determined by the number of devices that have received bytes from the cache server, for supported content types.
+- **Total # of Devices**: The total number of devices with activity in last 28 days.
+- **LAN Bytes**: Bytes delivered from LAN peers.
+- **Group Bytes**: Bytes from Group peers. If a device is using Group DownloadMode, Delivery Optimization will first look for peers on the LAN and then in the Group. Therefore, if bytes are delivered from LAN peers, they'll be calculated in 'LAN Bytes'.
+- **CDN Bytes**: Bytes delivered from Content Delivery Network (CDN).
+- **City**: City is determined based on the location of the device where the maximum amount of data is downloaded.
+- **Country**: Country is determined based on the location of the device where the maximum amount of data is downloaded.
+- **ISP**: ISP is determined based on the ISP delivering the maximum bytes to the device.
+
+## Calculations for Delivery Optimization
+
+There are several calculated values that appear on the Delivery Optimization report. Listed below each calculation is the table that's used for it:
+
+**Efficiency (%) Calculations**:
+ 
+- Bandwidth Savings (BW SAV%) = 100 * (BytesFromPeers + BytesFromGroupPeers + BytesFromCache) /
+(BytesFromPeers + BytesFromGroupPeers+BytesFromCDN + BytesFromCache)
+  - [UCDOAggregatedStatus](wufb-reports-schema-ucdostatus.md) table
+- % P2P Efficiency = 100 * (BytesFromPeers + BytesFromGroupPeers) / (BytesFromPeers + BytesFromGroupPeers+BytesFromCDN+BytesFromCache)
+  - [UCDOStatus](wufb-reports-schema-ucdostatus.md) table
+- % MCC Efficiency = 100 * BytesFromCache / (BytesFromPeers + BytesFromGroupPeers+BytesFromCDN+BytesFromCache) 
+  - [UCDOStatus](wufb-reports-schema-ucdostatus.md) table
+
+**Bytes Calculations**:
+
+- TotalBytes = BytesFromCDN + BytesFromEnterpriseCache + BytesFromPeers + BytesFromGroupPeers
+  - [UCDOAggregatedStatus](wufb-reports-schema-ucdostatus.md) table
+- BytesFromCDN = BytesFromCDN
+  - [UCDOAggregatedStatus](wufb-reports-schema-ucdostatus.md) table
+- BytesFromPeers = BytesFromLAN
+  - [UCDOAggregatedStatus](wufb-reports-schema-ucdoaggregatedstatus.md) table
+- BytesFromGroupPeers = BytesFromGroupPeers
+  - [UCDOAggregatedStatus](wufb-reports-schema-ucdoaggregatedstatus.md) table
+- BytesFromCache = BytesFromCache
+  - [UCDOAggregatedStatus](wufb-reports-schema-ucdoaggregatedstatus.md) table
+
+**Volume Calculations**:
+
+- Volume by P2P = BytesFromPeers + BytesFromGroupPeers
+  - [UCDOStatus](wufb-reports-schema-ucdostatus.md) table
+- Volume by MCC = BytesFromCache
+  - [UCDOStatus](wufb-reports-schema-ucdostatus.md) table
+- Volume by CDN = BytesFrom CDN
+  - [UCDOStatus](wufb-reports-schema-ucdostatus.md) table
+
+## Mapping GroupID
+
+In the **Efficiency By Group** subsection, the **GroupID** is displayed as an encoded SHA256 hash. You can create a mapping of decoded to encoded GroupIDs using the following PowerShell example:
+
+```powershell
+$text = "<myEncodedGroupID>" ;
+
+$hashObj = [System.Security.Cryptography.HashAlgorithm]::Create('sha256') ; $dig = $hashObj.ComputeHash([System.Text.Encoding]::Unicode.GetBytes($text)) ; $digB64 = [System.Convert]::ToBase64String($dig) ; Write-Host "$text ==> $digB64"
+```
+
+In addition, you can see both the encoded and decoded GroupIDs in the Delivery Optimization logs.
+
+```powershell
+Get-DeliveryOptimizationLog -Flush | Set-Content C:\dosvc.log
+```
+
+The below two lines are together in verbose logs:
+
+```text
+2023-02-15T12:33:11.3811337Z 1514  1F4          {CGlobalConfigManager::GetGroupId} Using groupID = **<myEncodedGroupId>**
+2023-02-15T12:33:11.3811432Z 1514  1F4          {CGlobalConfigManager::GetGroupId} Hashed groupID = **<myDecodedGroupId>**
+```
+
+## Sample queries
+
+You can use the data in [UCDOAggregatedStatus](wufb-reports-schema-ucdoaggregatedstatus.md)
+and [UCDOStatus](wufb-reports-schema-ucdostatus.md) to create your own queries. Create your custom queries using [Kusto Query Language (KQL)](/azure/data-explorer/kusto/query/), but note that Windows Update for Business reports uses Azure Monitor, so some operators aren't supported. The KQL documentation specifies which operators aren't supported by Azure Monitor or if they have different functionality. For more information about KQL in Azure Monitor, see [Log queries in Azure Monitor](/azure/azure-monitor/logs/log-query-overview). The following queries are examples of how you can use the data:
+
+### Example UCDOAggregatedStatus table query
+
+The following query is used to display the total bandwidth savings % value:
+
+```kusto
+UCDOAggregatedStatus| where TimeGenerated == _SnapshotTime
+| extend LocalSourceBytes = BytesFromCache + BytesFromGroupPeers + BytesFromPeers
+| summarize LocalSources_BWSAV = round((sum(0.0 + LocalSourceBytes)/ sum(LocalSourceBytes+BytesFromCDN)) * 100.0 ,2)
+| extend Title = "BW SAV%" , SubTitle = "Local Sources"
+```
+
+### Example UCDOStatus table query
+
+The following query is used to display the Top 10 GroupIDs:
+
+```kusto
+UCDOStatus  | where TimeGenerated == _SnapshotTime
+| summarize sum(BytesFromCDN) ,  sum(BytesFromGroupPeers) , sum(BytesFromPeers) , sum(BytesFromCache) ,
+DeviceCount = count_distinct(GlobalDeviceId) by GroupID | top 10 by DeviceCount desc 
+| extend TotalBytes = (sum_BytesFromPeers + sum_BytesFromGroupPeers+sum_BytesFromCDN+sum_BytesFromCache)
+| extend P2PPercentage = ((0.0 + sum_BytesFromPeers + sum_BytesFromGroupPeers)/TotalBytes ) * 100.0  
+| extend  MCCPercentage = ((0.0 + sum_BytesFromCache)/ TotalBytes) * 100.0  , 
+ VolumeBytesFromPeers = sum_BytesFromPeers + sum_BytesFromGroupPeers
+| extend VolumeBytesFromMCC = sum_BytesFromCache , VolumeByCDN = sum_BytesFromCDN
+| project  GroupID , P2PPercentage , MCCPercentage ,  VolumeBytesFromPeers , VolumeBytesFromMCC ,VolumeByCDN , DeviceCount
+```
+
+## Frequency Asked Questions
+
+- **What time period does the Delivery Optimization data include?**
+Data is generated/aggregated for the last 28 days for active devices.
+
+- **Data is showing as 'Unknown', what does that mean?**
+You may see data in the report listed as 'Unknown'. This status indicates that the Delivery Optimization DownloadMode setting is either invalid or empty.
+
+- **How are the 'Top 10' groups identified?**
+The top groups are represented by the number of devices in a particular group, for any of the four group types (GroupID, City, Country, and ISP).
+
+- **The GroupIDs don't look familiar, why are they different?**
+The GroupID values are encoded for data protection telemetry requirements. You can find more information in the 'Mapping GroupIDs' section above.
+
+- **How can I see data for device in the office vs. out of the office?**
+Today, we don't have a distinction for data that was downloaded by location. 
+
+- **What does the data in UCDOStatus table represent?**
+A row in UCDOStatus represents data downloaded by a combination of a single device ID (AzureADDeviceId) by content type (ContentType). 
+
+- **What does the data in UCDOAggregatedStatus table represent?**
+A row in UCDOAggregatedStatus represents data summarized at the tenant level (AzureADTenantID) for each content type (ContentType).
--- a/windows/deployment/update/wufb-reports-schema-ucclientupdatestatus.md
+++ b/windows/deployment/update/wufb-reports-schema-ucclientupdatestatus.md
@ -6,7 +6,7 @@ ms.prod: windows-client
 author: mestew
 ms.author: mstewart
 ms.topic: reference
-ms.date: 06/06/2022
+ms.date: 04/24/2023
 ms.technology: itpro-updates
 ---

@ -37,7 +37,7 @@ Update Event that combines the latest client-based data with the latest service-
 | **SourceSystem** | [string](/azure/kusto/query/scalar-data-types/string)|  `Azure`| |
 | **TargetBuild** |  [string](/azure/kusto/query/scalar-data-types/string) | `10.0.18363.836` | The full build of the content this DeviceUpdateEvent is tracking. For Windows 10 updates, this value would correspond to the full build (10.0.14393.385). |
 | **TargetBuildNumber** |  [int](/azure/kusto/query/scalar-data-types/int)  | `18363` | Integer of the Major portion of Build. |
-| **TargetKBNumber** |  [int](/azure/kusto/query/scalar-data-types/int)  | `4524570` | KB Article. |
+| **TargetKBNumber** |  [string](/azure/kusto/query/scalar-data-types/string)  | `KB4524570` | KB Article. |
 | **TargetRevisionNumber** |  [int](/azure/kusto/query/scalar-data-types/int)  | `836` | Integer or the minor (or revision) portion of the build. |
 | **TargetVersion** |  [int](/azure/kusto/query/scalar-data-types/int)  | `1909` | The target operating system version, such as 1909. |
 | **TimeGenerated** |  [datetime](/azure/kusto/query/scalar-data-types/datetime)  | `2020-05-14 09:26:03.478039` | The time the snapshot generated this specific record. This is to determine to which batch snapshot this record belongs. |
@ -50,3 +50,4 @@ Update Event that combines the latest client-based data with the latest service-
 | **UpdateManufacturer** | [string](/azure/kusto/query/scalar-data-types/string) | `Microsoft` | Manufacturer of update. Microsoft for feature or quality updates, for drivers the name of driver manufacturer. |
 | **UpdateReleaseTime** |  [datetime](/azure/kusto/query/scalar-data-types/datetime)  | `2020-05-14 09:26:03.478039` | The release date of the update |
 | **UpdateSource** |  [string](/azure/kusto/query/scalar-data-types/string) | `UUP` | The source of the update such as UUP, MUv6, Media |
+ 
--- a/windows/deployment/update/wufb-reports-workbook.md
+++ b/windows/deployment/update/wufb-reports-workbook.md
@ -6,7 +6,7 @@ ms.prod: windows-client
 author: mestew
 ms.author: mstewart
 ms.topic: article
-ms.date: 11/15/2022
+ms.date: 04/12/2023
 ms.technology: itpro-updates
 ---

@ -173,7 +173,7 @@ The **Device status** group for driver updates contains the following items:

 ## <a name="bkmk_do"></a> Delivery Optimization

-The **Delivery Optimization** tab provides a summarized view of bandwidth efficiencies. This new revised report also includes [Microsoft Connected Cache](/windows/deployment/do/waas-microsoft-connected-cache) information.
+The **Delivery Optimization** tab provides a summarized view of bandwidth efficiencies. This new revised report also includes [Microsoft Connected Cache](/windows/deployment/do/waas-microsoft-connected-cache) information. For more information, see [Delivery Optimization data in Windows Update for Business reports](/windows/deployment/update/waas-delivery-optimization).

 At the top of the report, tiles display the following information: