From d84ba1e55545e1c09ecf18b354a68b9eb3e8833f Mon Sep 17 00:00:00 2001 From: Jonathan Herlin Date: Tue, 10 Apr 2018 11:03:29 +0200 Subject: [PATCH 1/3] Typo in BitLocker Network Unlock section Typo in BitLocker Network Unlock section --- .../bitlocker/bitlocker-frequently-asked-questions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/information-protection/bitlocker/bitlocker-frequently-asked-questions.md b/windows/security/information-protection/bitlocker/bitlocker-frequently-asked-questions.md index b56af7542a..267a2e2428 100644 --- a/windows/security/information-protection/bitlocker/bitlocker-frequently-asked-questions.md +++ b/windows/security/information-protection/bitlocker/bitlocker-frequently-asked-questions.md @@ -336,7 +336,7 @@ To use Network Unlock you must also have a PIN configured for your computer. Whe BitLocker Network Unlock has software and hardware requirements for both client computers, Windows Deployment services, and domain controllers that must be met before you can use it. Network Unlock uses two protectors, the TPM protector and the one provided by the network or by your PIN, whereas automatic unlock uses a single protector, the one stored in the TPM. If the computer is joined to a network without the key protector it will prompt you to enter your PIN. If the PIN is -not available you will need to use the recovery key to unlock the computer if it can ot be connected to the network. +not available you will need to use the recovery key to unlock the computer if it can not be connected to the network. For more info, see [BitLocker: How to enable Network Unlock](bitlocker-how-to-enable-network-unlock.md). From f3e9e1df9903abd3c87c6a75f3a0997084026258 Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Tue, 10 Apr 2018 13:05:53 -0700 Subject: [PATCH 2/3] Update TOC.md --- windows/configuration/TOC.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/configuration/TOC.md b/windows/configuration/TOC.md index 9768a7eb0b..94d5785c9f 100644 --- a/windows/configuration/TOC.md +++ b/windows/configuration/TOC.md @@ -3,9 +3,9 @@ ## [Diagnostic Data Viewer Overview](diagnostic-data-viewer-overview.md) ## [Windows 10, version 1709 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields.md) ## [Windows 10, version 1703 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1703.md) -## [Windows 10, version 1709 enhanced telemetry events and fields used by Windows Analytics](enhanced-diagnostic-data-windows-analytics-events-and-fields.md) -## [Windows 10, version 1709 diagnostic data for the Full telemetry level](windows-diagnostic-data.md) -## [Windows 10, version 1703 diagnostic data for the Full telemetry level](windows-diagnostic-data-1703.md) +## [Windows 10, version 1709 enhanced diagnostic data events and fields used by Windows Analytics](enhanced-diagnostic-data-windows-analytics-events-and-fields.md) +## [Windows 10, version 1709 diagnostic data for the Full level](windows-diagnostic-data.md) +## [Windows 10, version 1703 diagnostic data for the Full level](windows-diagnostic-data-1703.md) ## [Beginning your General Data Protection Regulation (GDPR) journey for Windows 10](gdpr-win10-whitepaper.md) ## [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md) ## [Manage Windows 10 connection endpoints](manage-windows-endpoints-version-1709.md) From a3583948725802bd6a3414e2baba202510a8d79f Mon Sep 17 00:00:00 2001 From: Charles Inglis <32555877+cinglis-msft@users.noreply.github.com> Date: Wed, 11 Apr 2018 14:15:36 -0700 Subject: [PATCH 3/3] Update update-compliance-delivery-optimization.md Added known issues section. --- .../update/update-compliance-delivery-optimization.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/windows/deployment/update/update-compliance-delivery-optimization.md b/windows/deployment/update/update-compliance-delivery-optimization.md index 92c577feea..dce1b56274 100644 --- a/windows/deployment/update/update-compliance-delivery-optimization.md +++ b/windows/deployment/update/update-compliance-delivery-optimization.md @@ -13,6 +13,10 @@ ms.date: 03/27/2018 # Delivery Optimization in Update Compliance The Update Compliance solution of Windows Analytics provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days. +>[!Note] +>Delivery Optimization Status is currently in development. See the [Known Issues](#known-issues) section for issues we are aware of and potential workarounds. + + ## Delivery Optimization Status The Delivery Optimization Status section includes three blades: @@ -40,3 +44,8 @@ The download sources that could be included are: - Group Bytes: Bytes downloaded from Group Peers which are other devices that belong to the same Group (available when the “Group” download mode is used) - HTTP Bytes: Non-peer bytes. The HTTP download source can be Microsoft Servers, Windows Update Servers, a WSUS server or an SCCM Distribution Point for Express Updates. +## Known Issues +Delivery Optimization is currently in development. The following issues are known: + +- DO Download Mode is not accurately portrayed in the Device Configuration blade. There is no workaround at this time. +