From a0b726daf0c03797d10980a0d1defa849ac055bb Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Fri, 3 May 2019 23:38:14 -0700
Subject: [PATCH 001/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...system-components-to-microsoft-services.md | 155 ++++++------------
1 file changed, 53 insertions(+), 102 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 923bfedcb3..1616b648c6 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -48,55 +48,6 @@ Note that **Get Help** and **Give us Feedback** links no longer work after the W
We are always striving to improve our documentation and welcome your feedback. You can provide feedback by contacting telmhelp@microsoft.com.
-## What's new in Windows 10, version 1809 Enterprise edition
-
-Here's a list of changes that were made to this article for Windows 10, version 1809:
-
-- Added a policy to disable Windows Defender SmartScreen
-
-## What's new in Windows 10, version 1803 Enterprise edition
-
-Here's a list of changes that were made to this article for Windows 10, version 1803:
-
-- Added a policy to turn off notifications network usage
-- Added a policy for Microsoft Edge to turn off configuration updates for the Books Library
-- Added a policy for Microsoft Edge to turn off Address Bar drop-down list suggestions
-
-## What's new in Windows 10, version 1709 Enterprise edition
-
-Here's a list of changes that were made to this article for Windows 10, version 1709:
-
-- Added the Phone calls section
-- Added the Storage Health section
-- Added discussion of apps for websites in the Microsoft Store section
-
-## What's new in Windows 10, version 1703 Enterprise edition
-
-Here's a list of changes that were made to this article for Windows 10, version 1703:
-
-- Added an MDM policy for Font streaming
-- Added an MDM policy for Network Connection Status Indicator
-- Added an MDM policy for the Micosoft Account Sign-In Assistant
-- Added instructions for removing the Sticky Notes app
-- Added registry paths for some Group Policies
-- Added the Find My Device section
-- Added the Tasks section
-- Added the App Diagnostics section
-
-- Added the following Group Policies:
-
- - Prevent managing SmartScreen Filter
- - Turn off Compatibility View
- - Turn off Automatic Download and Install of updates
- - Do not connect to any Windows Update locations
- - Turn off access to all Windows Update features
- - Specify Intranet Microsoft update service location
- - Enable Windows NTP client
- - Turn off Automatic download of the ActiveX VersionList
- - Allow Automatic Update of Speech Data
- - Accounts: Block Microsoft Accounts
- - Do not use diagnostic data for tailored experiences
-
## Management options for each setting
The following sections list the components that make network connections to Microsoft services by default. You can configure these settings to control the data that is sent to Microsoft. To prevent Windows from sending any data to Microsoft, configure diagnostic data at the Security level, turn off Windows Defender diagnostic data and MSRT reporting, and turn off all of these connections.
@@ -108,59 +59,59 @@ The following table lists management options for each setting, beginning with Wi
>[!NOTE]
>For some settings, MDM policies only partly cover capabilities available through Group Policy. See each setting’s section for more details.
-| Setting | UI | Group Policy | MDM policy | Registry | Command line |
-| - | :-: | :-: | :-: | :-: | :-: |
-| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  | |  | |
-| [2. Cortana and Search](#bkmk-cortana) |  |  |  |  | |
-| [3. Date & Time](#bkmk-datetime) |  |  | |  | |
-| [4. Device metadata retrieval](#bkmk-devinst) | |  |  |  | |
-| [5. Find My Device](#find-my-device) |  |  | |  | |
-| [6. Font streaming](#font-streaming) | |  |  |  | |
-| [7. Insider Preview builds](#bkmk-previewbuilds) |  |  |  |  | |
-| [8. Internet Explorer](#bkmk-ie) |  |  | |  | |
-| [9. License Manager](#bkmk-licmgr) | | | |  | |
-| [10. Live Tiles](#live-tiles) | |  | |  | |
-| [11. Mail synchronization](#bkmk-mailsync) |  | |  |  | |
-| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  |  | |
-| [13. Microsoft Edge](#bkmk-edge) |  |  |  |  | |
-| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  |  | |
-| [15. Offline maps](#bkmk-offlinemaps) |  |  | |  | |
-| [16. OneDrive](#bkmk-onedrive) | |  | |  | |
-| [17. Preinstalled apps](#bkmk-preinstalledapps) |  | | | |  |
-| [18. Settings > Privacy](#bkmk-settingssection) | | | | | |
-| [18.1 General](#bkmk-general) |  |  |  |  | |
-| [18.2 Location](#bkmk-priv-location) |  |  |  |  | |
-| [18.3 Camera](#bkmk-priv-camera) |  |  |  |  | |
-| [18.4 Microphone](#bkmk-priv-microphone) |  |  |  |  | |
-| [18.5 Notifications](#bkmk-priv-notifications) |  |  | |  | |
-| [18.6 Speech](#bkmk-priv-speech) |  |  |  |  | |
-| [18.7 Account info](#bkmk-priv-accounts) |  |  |  |  | |
-| [18.8 Contacts](#bkmk-priv-contacts) |  |  |  |  | |
-| [18.9 Calendar](#bkmk-priv-calendar) |  |  |  |  | |
-| [18.10 Call history](#bkmk-priv-callhistory) |  |  |  |  | |
-| [18.11 Email](#bkmk-priv-email) |  |  |  |  | |
-| [18.12 Messaging](#bkmk-priv-messaging) |  |  |  |  | |
-| [18.13 Phone calls](#bkmk-priv-phone-calls) |  |  |  |  | |
-| [18.14 Radios](#bkmk-priv-radios) |  |  |  |  | |
-| [18.15 Other devices](#bkmk-priv-other-devices) |  |  |  |  | |
-| [18.16 Feedback & diagnostics](#bkmk-priv-feedback) |  |  |  |  | |
-| [18.17 Background apps](#bkmk-priv-background) |  |  |  | | |
-| [18.18 Motion](#bkmk-priv-motion) |  |  |  |  | |
-| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |  | |
-| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |  | |
-| [18.21 Inking & Typing](#bkmk-priv-ink) |  | |  |  | |
-| [19. Software Protection Platform](#bkmk-spp) | |  |  |  | |
-| [20. Storage Health](#bkmk-storage-health) | |  | | | |
-| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |  | |
-| [22. Teredo](#bkmk-teredo) | |  | |  |  |
-| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  | |  | |
-| [24. Windows Defender](#bkmk-defender) | |  |  |  | |
-| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |  | |
-| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |  | |
-| [26. Microsoft Store](#bkmk-windowsstore) | |  | |  | |
-| [27.1 Apps for websites](#bkmk-apps-for-websites) | |  | | |
-| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |  | |
-| [28. Windows Update](#bkmk-wu) |  |  |  | | |
+| Setting | UI | Group Policy | MDM policy | Registry |
+| - | :-: | :-: | :-: | :-: |
+| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  | |  |
+| [2. Cortana and Search](#bkmk-cortana) |  |  |  |  |
+| [3. Date & Time](#bkmk-datetime) |  |  | |  |
+| [4. Device metadata retrieval](#bkmk-devinst) | |  |  |  |
+| [5. Find My Device](#find-my-device) |  |  | |  |
+| [6. Font streaming](#font-streaming) | |  |  |  |
+| [7. Insider Preview builds](#bkmk-previewbuilds) |  |  |  |  |
+| [8. Internet Explorer](#bkmk-ie) |  |  | |  |
+| [9. License Manager](#bkmk-licmgr) | | | |  |
+| [10. Live Tiles](#live-tiles) | |  | |  |
+| [11. Mail synchronization](#bkmk-mailsync) |  | |  |  |
+| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  |  |
+| [13. Microsoft Edge](#bkmk-edge) |  |  |  |  |
+| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  |  |
+| [15. Offline maps](#bkmk-offlinemaps) |  |  | |  |
+| [16. OneDrive](#bkmk-onedrive) | |  | |  |
+| [17. Preinstalled apps](#bkmk-preinstalledapps) |  | | | |
+| [18. Settings > Privacy](#bkmk-settingssection) | | | | |
+| [18.1 General](#bkmk-general) |  |  |  |  |
+| [18.2 Location](#bkmk-priv-location) |  |  |  |  |
+| [18.3 Camera](#bkmk-priv-camera) |  |  |  |  |
+| [18.4 Microphone](#bkmk-priv-microphone) |  |  |  |  |
+| [18.5 Notifications](#bkmk-priv-notifications) |  |  | |  |
+| [18.6 Speech](#bkmk-priv-speech) |  |  |  |  |
+| [18.7 Account info](#bkmk-priv-accounts) |  |  |  |  |
+| [18.8 Contacts](#bkmk-priv-contacts) |  |  |  |  |
+| [18.9 Calendar](#bkmk-priv-calendar) |  |  |  |  |
+| [18.10 Call history](#bkmk-priv-callhistory) |  |  |  |  |
+| [18.11 Email](#bkmk-priv-email) |  |  |  |  |
+| [18.12 Messaging](#bkmk-priv-messaging) |  |  |  |  |
+| [18.13 Phone calls](#bkmk-priv-phone-calls) |  |  |  |  |
+| [18.14 Radios](#bkmk-priv-radios) |  |  |  |  |
+| [18.15 Other devices](#bkmk-priv-other-devices) |  |  |  |  |
+| [18.16 Feedback & diagnostics](#bkmk-priv-feedback) |  |  |  |  |
+| [18.17 Background apps](#bkmk-priv-background) |  |  |  | |
+| [18.18 Motion](#bkmk-priv-motion) |  |  |  |  |
+| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |  |
+| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |  |
+| [18.21 Inking & Typing](#bkmk-priv-ink) |  | |  |  |
+| [19. Software Protection Platform](#bkmk-spp) | |  |  |  |
+| [20. Storage Health](#bkmk-storage-health) | |  | | |
+| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |  |
+| [22. Teredo](#bkmk-teredo) | |  | |  |
+| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  | |  |
+| [24. Windows Defender](#bkmk-defender) | |  |  |  |
+| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |  |
+| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |  |
+| [26. Microsoft Store](#bkmk-windowsstore) | |  | |  |
+| [27.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
+| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |  |
+| [28. Windows Update](#bkmk-wu) |  |  |  | |
### Settings for Windows Server 2016 with Desktop Experience
From 903400c4d1b9e698b50eeb5aff849015b3e4569c Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Fri, 3 May 2019 23:55:14 -0700
Subject: [PATCH 002/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...system-components-to-microsoft-services.md | 178 +++++++++---------
1 file changed, 89 insertions(+), 89 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 1616b648c6..99e29bee27 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -118,110 +118,110 @@ The following table lists management options for each setting, beginning with Wi
See the following table for a summary of the management settings for Windows Server 2016 with Desktop Experience.
-| Setting | UI | Group Policy | Registry | Command line |
-| - | :-: | :-: | :-: | :-: |
-| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  |  | |
-| [2. Cortana and Search](#bkmk-cortana) |  |  |  | |
-| [3. Date & Time](#bkmk-datetime) |  |  |  | |
-| [4. Device metadata retrieval](#bkmk-devinst) | |  |  | |
-| [6. Font streaming](#font-streaming) | |  |  | |
-| [7. Insider Preview builds](#bkmk-previewbuilds) |  |  |  | |
-| [8. Internet Explorer](#bkmk-ie) |  |  |  | |
-| [10. Live Tiles](#live-tiles) | |  |  | |
-| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  | |
-| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  | |
-| [16. OneDrive](#bkmk-onedrive) | |  | | |
-| [18. Settings > Privacy](#bkmk-settingssection) | | | | |
-| [18.1 General](#bkmk-general) |  |  |  | |
-| [19. Software Protection Platform](#bkmk-spp) | |  |  | |
-| [20. Teredo](#bkmk-teredo) | |  |  |  |
-| [24. Windows Defender](#bkmk-defender) | |  |  | |
-| [26. Microsoft Store](#bkmk-windowsstore) | |  |  | |
-| [27.1 Apps for websites](#bkmk-apps-for-websites) | |  | | |
-| [28. Windows Update](#bkmk-wu) | |  |  | |
+| Setting | UI | Group Policy | Registry |
+| - | :-: | :-: | :-: |
+| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  |  |
+| [2. Cortana and Search](#bkmk-cortana) |  |  |  |
+| [3. Date & Time](#bkmk-datetime) |  |  |  |
+| [4. Device metadata retrieval](#bkmk-devinst) | |  |  |
+| [6. Font streaming](#font-streaming) | |  |  |
+| [7. Insider Preview builds](#bkmk-previewbuilds) |  |  |  |
+| [8. Internet Explorer](#bkmk-ie) |  |  |  |
+| [10. Live Tiles](#live-tiles) | |  |  |
+| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  |
+| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  |
+| [16. OneDrive](#bkmk-onedrive) | |  | |
+| [18. Settings > Privacy](#bkmk-settingssection) | | | |
+| [18.1 General](#bkmk-general) |  |  |  |
+| [19. Software Protection Platform](#bkmk-spp) | |  |  |
+| [20. Teredo](#bkmk-teredo) | |  |  |
+| [24. Windows Defender](#bkmk-defender) | |  |  |
+| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
+| [27.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
+| [28. Windows Update](#bkmk-wu) | |  |  |
### Settings for Windows Server 2016 Server Core
See the following table for a summary of the management settings for Windows Server 2016 Server Core.
-| Setting | Group Policy | Registry | Command line |
-| - | :-: | :-: | :-: | :-: | :-: |
-| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) |  |  | |
-| [3. Date & Time](#bkmk-datetime) |  |  | |
-| [6. Font streaming](#font-streaming) |  |  | |
-| [14. Network Connection Status Indicator](#bkmk-ncsi) |  | | |
-| [19. Software Protection Platform](#bkmk-spp) |  | | |
-| [22. Teredo](#bkmk-teredo) |  | |  |
-| [24. Windows Defender](#bkmk-defender) |  |  | |
-| [28. Windows Update](#bkmk-wu) |  |  | |
+| Setting | Group Policy | Registry |
+| - | :-: | :-: |
+| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) |  |  |
+| [3. Date & Time](#bkmk-datetime) |  |  |
+| [6. Font streaming](#font-streaming) |  |  |
+| [14. Network Connection Status Indicator](#bkmk-ncsi) |  | |
+| [19. Software Protection Platform](#bkmk-spp) |  |
+| [22. Teredo](#bkmk-teredo) |  | |
+| [24. Windows Defender](#bkmk-defender) |  |  |
+| [28. Windows Update](#bkmk-wu) |  |  |
### Settings for Windows Server 2016 Nano Server
See the following table for a summary of the management settings for Windows Server 2016 Nano Server.
-| Setting | Registry | Command line |
-| - | :-: | :-: | :-: | :-: | :-: |
-| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) |  | |
-| [3. Date & Time](#bkmk-datetime) |  | |
-| [22. Teredo](#bkmk-teredo) | |  |
-| [28. Windows Update](#bkmk-wu) |  | |
+| Setting | Registry |
+| - | :-: | :-: |
+| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) |  |
+| [3. Date & Time](#bkmk-datetime) |  |
+| [22. Teredo](#bkmk-teredo) | |
+| [28. Windows Update](#bkmk-wu) |  |
### Settings for Windows Server 2019
See the following table for a summary of the management settings for Windows Server 2019.
-| Setting | UI | Group Policy | MDM policy | Registry | Command line |
-| - | :-: | :-: | :-: | :-: | :-: |
-| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  | |  | |
-| [2. Cortana and Search](#bkmk-cortana) |  |  |  |  | |
-| [3. Date & Time](#bkmk-datetime) |  |  | |  | |
-| [4. Device metadata retrieval](#bkmk-devinst) | |  |  |  | |
-| [5. Find My Device](#find-my-device) |  |  | |  | |
-| [6. Font streaming](#font-streaming) | |  |  |  | |
-| [7. Insider Preview builds](#bkmk-previewbuilds) |  |  |  |  | |
-| [8. Internet Explorer](#bkmk-ie) |  |  | |  | |
-| [10. Live Tiles](#live-tiles) | |  | |  | |
-| [11. Mail synchronization](#bkmk-mailsync) |  | |  |  | |
-| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  |  | |
-| [13. Microsoft Edge](#bkmk-edge) |  |  |  |  | |
-| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  |  | |
-| [15. Offline maps](#bkmk-offlinemaps) |  |  | |  | |
-| [16. OneDrive](#bkmk-onedrive) | |  | |  | |
-| [17. Preinstalled apps](#bkmk-preinstalledapps) |  | | | |  |
-| [18. Settings > Privacy](#bkmk-settingssection) | | | | | |
-| [18.1 General](#bkmk-general) |  |  |  |  | |
-| [18.2 Location](#bkmk-priv-location) |  |  |  |  | |
-| [18.3 Camera](#bkmk-priv-camera) |  |  |  |  | |
-| [18.4 Microphone](#bkmk-priv-microphone) |  |  |  |  | |
-| [18.5 Notifications](#bkmk-priv-notifications) |  |  | |  | |
-| [18.6 Speech](#bkmk-priv-speech) |  |  |  |  | |
-| [18.7 Account info](#bkmk-priv-accounts) |  |  |  |  | |
-| [18.8 Contacts](#bkmk-priv-contacts) |  |  |  |  | |
-| [18.9 Calendar](#bkmk-priv-calendar) |  |  |  |  | |
-| [18.10 Call history](#bkmk-priv-callhistory) |  |  |  |  | |
-| [18.11 Email](#bkmk-priv-email) |  |  |  |  | |
-| [18.12 Messaging](#bkmk-priv-messaging) |  |  |  |  | |
-| [18.13 Phone calls](#bkmk-priv-phone-calls) |  |  |  |  | |
-| [18.14 Radios](#bkmk-priv-radios) |  |  |  |  | |
-| [18.15 Other devices](#bkmk-priv-other-devices) |  |  |  |  | |
-| [18.16 Feedback & diagnostics](#bkmk-priv-feedback) |  |  |  |  | |
-| [18.17 Background apps](#bkmk-priv-background) |  |  |  | | |
-| [18.18 Motion](#bkmk-priv-motion) |  |  |  |  | |
-| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |  | |
-| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |  | |
-| [18.21 Inking & Typing](#bkmk-priv-ink) | | |  |  | |
-| [19. Software Protection Platform](#bkmk-spp) | |  |  |  | |
-| [20. Storage Health](#bkmk-storage-health) | |  | | | |
-| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |  | |
-| [22. Teredo](#bkmk-teredo) | |  | |  |  |
-| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  | |  | |
-| [24. Windows Defender](#bkmk-defender) | |  |  |  | |
-| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |  | |
-| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |  | |
-| [26. Microsoft Store](#bkmk-windowsstore) | |  | |  | |
-| [27.1 Apps for websites](#bkmk-apps-for-websites) | |  | | |
-| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |  | |
-| [28. Windows Update](#bkmk-wu) |  |  |  | | |
+| Setting | UI | Group Policy | MDM policy | Registry |
+| - | :-: | :-: | :-: | :-: |
+| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  | |  |
+| [2. Cortana and Search](#bkmk-cortana) |  |  |  |  |
+| [3. Date & Time](#bkmk-datetime) |  |  | |  |
+| [4. Device metadata retrieval](#bkmk-devinst) | |  |  |  |
+| [5. Find My Device](#find-my-device) |  |  | |  |
+| [6. Font streaming](#font-streaming) | |  |  |  |
+| [7. Insider Preview builds](#bkmk-previewbuilds) |  |  |  |  |
+| [8. Internet Explorer](#bkmk-ie) |  |  | |  |
+| [10. Live Tiles](#live-tiles) | |  | |  |
+| [11. Mail synchronization](#bkmk-mailsync) |  | |  |  |
+| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  |  |
+| [13. Microsoft Edge](#bkmk-edge) |  |  |  |  |
+| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  |  |
+| [15. Offline maps](#bkmk-offlinemaps) |  |  | |  |
+| [16. OneDrive](#bkmk-onedrive) | |  | |  |
+| [17. Preinstalled apps](#bkmk-preinstalledapps) |  | | | |
+| [18. Settings > Privacy](#bkmk-settingssection) | | | | |
+| [18.1 General](#bkmk-general) |  |  |  |  |
+| [18.2 Location](#bkmk-priv-location) |  |  |  |  |
+| [18.3 Camera](#bkmk-priv-camera) |  |  |  |  |
+| [18.4 Microphone](#bkmk-priv-microphone) |  |  |  |  |
+| [18.5 Notifications](#bkmk-priv-notifications) |  |  | |  |
+| [18.6 Speech](#bkmk-priv-speech) |  |  |  |  |
+| [18.7 Account info](#bkmk-priv-accounts) |  |  |  |  |
+| [18.8 Contacts](#bkmk-priv-contacts) |  |  |  |  |
+| [18.9 Calendar](#bkmk-priv-calendar) |  |  |  |  |
+| [18.10 Call history](#bkmk-priv-callhistory) |  |  |  |  |
+| [18.11 Email](#bkmk-priv-email) |  |  |  |  |
+| [18.12 Messaging](#bkmk-priv-messaging) |  |  |  |  |
+| [18.13 Phone calls](#bkmk-priv-phone-calls) |  |  |  |  |
+| [18.14 Radios](#bkmk-priv-radios) |  |  |  |  |
+| [18.15 Other devices](#bkmk-priv-other-devices) |  |  |  |  |
+| [18.16 Feedback & diagnostics](#bkmk-priv-feedback) |  |  |  |  |
+| [18.17 Background apps](#bkmk-priv-background) |  |  |  | |
+| [18.18 Motion](#bkmk-priv-motion) |  |  |  |  |
+| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |  |
+| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |  |
+| [18.21 Inking & Typing](#bkmk-priv-ink) | | |  |  |
+| [19. Software Protection Platform](#bkmk-spp) | |  |  |  |
+| [20. Storage Health](#bkmk-storage-health) | |  | | |
+| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |  |
+| [22. Teredo](#bkmk-teredo) | |  | |  |
+| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  | |  |
+| [24. Windows Defender](#bkmk-defender) | |  |  |  |
+| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |  |
+| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |  |
+| [26. Microsoft Store](#bkmk-windowsstore) | |  | |  |
+| [27.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
+| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |  |
+| [28. Windows Update](#bkmk-wu) |  |  |  | |
## How to configure each setting
From ccf0f2ea9ab2b074c63d6860648d7a374edf96f4 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Fri, 3 May 2019 23:58:37 -0700
Subject: [PATCH 003/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 99e29bee27..a3902d9ea0 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -160,7 +160,7 @@ See the following table for a summary of the management settings for Windows Ser
See the following table for a summary of the management settings for Windows Server 2016 Nano Server.
| Setting | Registry |
-| - | :-: | :-: |
+| - | :-: |
| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) |  |
| [3. Date & Time](#bkmk-datetime) |  |
| [22. Teredo](#bkmk-teredo) | |
From bc561e1fe8930093b0ceeca03ca548c70f65e3ff Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Sat, 4 May 2019 00:07:13 -0700
Subject: [PATCH 004/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...system-components-to-microsoft-services.md | 100 +++++++++---------
1 file changed, 50 insertions(+), 50 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index a3902d9ea0..53d253142c 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -59,59 +59,59 @@ The following table lists management options for each setting, beginning with Wi
>[!NOTE]
>For some settings, MDM policies only partly cover capabilities available through Group Policy. See each setting’s section for more details.
-| Setting | UI | Group Policy | MDM policy | Registry |
-| - | :-: | :-: | :-: | :-: |
-| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  | |  |
-| [2. Cortana and Search](#bkmk-cortana) |  |  |  |  |
-| [3. Date & Time](#bkmk-datetime) |  |  | |  |
-| [4. Device metadata retrieval](#bkmk-devinst) | |  |  |  |
-| [5. Find My Device](#find-my-device) |  |  | |  |
-| [6. Font streaming](#font-streaming) | |  |  |  |
-| [7. Insider Preview builds](#bkmk-previewbuilds) |  |  |  |  |
-| [8. Internet Explorer](#bkmk-ie) |  |  | |  |
-| [9. License Manager](#bkmk-licmgr) | | | |  |
-| [10. Live Tiles](#live-tiles) | |  | |  |
-| [11. Mail synchronization](#bkmk-mailsync) |  | |  |  |
-| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  |  |
-| [13. Microsoft Edge](#bkmk-edge) |  |  |  |  |
-| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  |  |
-| [15. Offline maps](#bkmk-offlinemaps) |  |  | |  |
-| [16. OneDrive](#bkmk-onedrive) | |  | |  |
-| [17. Preinstalled apps](#bkmk-preinstalledapps) |  | | | |
-| [18. Settings > Privacy](#bkmk-settingssection) | | | | |
-| [18.1 General](#bkmk-general) |  |  |  |  |
-| [18.2 Location](#bkmk-priv-location) |  |  |  |  |
-| [18.3 Camera](#bkmk-priv-camera) |  |  |  |  |
-| [18.4 Microphone](#bkmk-priv-microphone) |  |  |  |  |
-| [18.5 Notifications](#bkmk-priv-notifications) |  |  | |  |
-| [18.6 Speech](#bkmk-priv-speech) |  |  |  |  |
-| [18.7 Account info](#bkmk-priv-accounts) |  |  |  |  |
-| [18.8 Contacts](#bkmk-priv-contacts) |  |  |  |  |
-| [18.9 Calendar](#bkmk-priv-calendar) |  |  |  |  |
-| [18.10 Call history](#bkmk-priv-callhistory) |  |  |  |  |
-| [18.11 Email](#bkmk-priv-email) |  |  |  |  |
-| [18.12 Messaging](#bkmk-priv-messaging) |  |  |  |  |
-| [18.13 Phone calls](#bkmk-priv-phone-calls) |  |  |  |  |
-| [18.14 Radios](#bkmk-priv-radios) |  |  |  |  |
-| [18.15 Other devices](#bkmk-priv-other-devices) |  |  |  |  |
-| [18.16 Feedback & diagnostics](#bkmk-priv-feedback) |  |  |  |  |
-| [18.17 Background apps](#bkmk-priv-background) |  |  |  | |
-| [18.18 Motion](#bkmk-priv-motion) |  |  |  |  |
-| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |  |
-| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |  |
-| [18.21 Inking & Typing](#bkmk-priv-ink) |  | |  |  |
-| [19. Software Protection Platform](#bkmk-spp) | |  |  |  |
+| Setting | UI | Group Policy | Registry |
+| - | :-: | :-: | :-: |
+| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  |  |
+| [2. Cortana and Search](#bkmk-cortana) |  |  |  |
+| [3. Date & Time](#bkmk-datetime) |  |  |  |
+| [4. Device metadata retrieval](#bkmk-devinst) | |  |  |
+| [5. Find My Device](#find-my-device) |  |  |  |
+| [6. Font streaming](#font-streaming) | |  |  |
+| [7. Insider Preview builds](#bkmk-previewbuilds) |  |  |  |
+| [8. Internet Explorer](#bkmk-ie) |  |  |  |
+| [9. License Manager](#bkmk-licmgr) | | |  |
+| [10. Live Tiles](#live-tiles) | |  |  |
+| [11. Mail synchronization](#bkmk-mailsync) |  | |  |
+| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  |
+| [13. Microsoft Edge](#bkmk-edge) |  |  |  |
+| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  |
+| [15. Offline maps](#bkmk-offlinemaps) |  |  |  |
+| [16. OneDrive](#bkmk-onedrive) | |  |  |
+| [17. Preinstalled apps](#bkmk-preinstalledapps) |  | | |
+| [18. Settings > Privacy](#bkmk-settingssection) | | | |
+| [18.1 General](#bkmk-general) |  |  |  |
+| [18.2 Location](#bkmk-priv-location) |  |  |  |
+| [18.3 Camera](#bkmk-priv-camera) |  |  |  |
+| [18.4 Microphone](#bkmk-priv-microphone) |  |  |  |
+| [18.5 Notifications](#bkmk-priv-notifications) |  |  | |
+| [18.6 Speech](#bkmk-priv-speech) |  |  |  |
+| [18.7 Account info](#bkmk-priv-accounts) |  |  |  |
+| [18.8 Contacts](#bkmk-priv-contacts) |  |  |  |
+| [18.9 Calendar](#bkmk-priv-calendar) |  |  |  |
+| [18.10 Call history](#bkmk-priv-callhistory) |  |  |  |
+| [18.11 Email](#bkmk-priv-email) |  |  |  |
+| [18.12 Messaging](#bkmk-priv-messaging) |  |  |  |
+| [18.13 Phone calls](#bkmk-priv-phone-calls) |  |  |  |
+| [18.14 Radios](#bkmk-priv-radios) |  |  |  |
+| [18.15 Other devices](#bkmk-priv-other-devices) |  |  |  |
+| [18.16 Feedback & diagnostics](#bkmk-priv-feedback) |  |  |  |
+| [18.17 Background apps](#bkmk-priv-background) |  |  |  |
+| [18.18 Motion](#bkmk-priv-motion) |  |  |  |
+| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |
+| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |
+| [18.21 Inking & Typing](#bkmk-priv-ink) |  | |  |
+| [19. Software Protection Platform](#bkmk-spp) | |  |  |
| [20. Storage Health](#bkmk-storage-health) | |  | | |
-| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |  |
+| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |
| [22. Teredo](#bkmk-teredo) | |  | |  |
-| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  | |  |
-| [24. Windows Defender](#bkmk-defender) | |  |  |  |
-| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |  |
-| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |  |
-| [26. Microsoft Store](#bkmk-windowsstore) | |  | |  |
+| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  | |
+| [24. Windows Defender](#bkmk-defender) | |  |  |
+| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |
+| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |
+| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
| [27.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
-| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |  |
-| [28. Windows Update](#bkmk-wu) |  |  |  | |
+| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |
+| [28. Windows Update](#bkmk-wu) |  |  | |
### Settings for Windows Server 2016 with Desktop Experience
From 79db69e04c022b5e2529c3914165a208813953be Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Sat, 4 May 2019 00:19:24 -0700
Subject: [PATCH 005/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...system-components-to-microsoft-services.md | 102 +++++++++---------
1 file changed, 51 insertions(+), 51 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 53d253142c..1b00182dc9 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -170,58 +170,58 @@ See the following table for a summary of the management settings for Windows Ser
See the following table for a summary of the management settings for Windows Server 2019.
-| Setting | UI | Group Policy | MDM policy | Registry |
-| - | :-: | :-: | :-: | :-: |
-| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  | |  |
+| Setting | UI | Group Policy | Registry |
+| - | :-: | :-: | :-: |
+| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  |  |
| [2. Cortana and Search](#bkmk-cortana) |  |  |  |  |
-| [3. Date & Time](#bkmk-datetime) |  |  | |  |
-| [4. Device metadata retrieval](#bkmk-devinst) | |  |  |  |
-| [5. Find My Device](#find-my-device) |  |  | |  |
-| [6. Font streaming](#font-streaming) | |  |  |  |
-| [7. Insider Preview builds](#bkmk-previewbuilds) |  |  |  |  |
-| [8. Internet Explorer](#bkmk-ie) |  |  | |  |
-| [10. Live Tiles](#live-tiles) | |  | |  |
-| [11. Mail synchronization](#bkmk-mailsync) |  | |  |  |
-| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  |  |
-| [13. Microsoft Edge](#bkmk-edge) |  |  |  |  |
-| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  |  |
-| [15. Offline maps](#bkmk-offlinemaps) |  |  | |  |
-| [16. OneDrive](#bkmk-onedrive) | |  | |  |
-| [17. Preinstalled apps](#bkmk-preinstalledapps) |  | | | |
-| [18. Settings > Privacy](#bkmk-settingssection) | | | | |
-| [18.1 General](#bkmk-general) |  |  |  |  |
-| [18.2 Location](#bkmk-priv-location) |  |  |  |  |
-| [18.3 Camera](#bkmk-priv-camera) |  |  |  |  |
-| [18.4 Microphone](#bkmk-priv-microphone) |  |  |  |  |
-| [18.5 Notifications](#bkmk-priv-notifications) |  |  | |  |
-| [18.6 Speech](#bkmk-priv-speech) |  |  |  |  |
-| [18.7 Account info](#bkmk-priv-accounts) |  |  |  |  |
-| [18.8 Contacts](#bkmk-priv-contacts) |  |  |  |  |
-| [18.9 Calendar](#bkmk-priv-calendar) |  |  |  |  |
-| [18.10 Call history](#bkmk-priv-callhistory) |  |  |  |  |
-| [18.11 Email](#bkmk-priv-email) |  |  |  |  |
-| [18.12 Messaging](#bkmk-priv-messaging) |  |  |  |  |
-| [18.13 Phone calls](#bkmk-priv-phone-calls) |  |  |  |  |
-| [18.14 Radios](#bkmk-priv-radios) |  |  |  |  |
-| [18.15 Other devices](#bkmk-priv-other-devices) |  |  |  |  |
-| [18.16 Feedback & diagnostics](#bkmk-priv-feedback) |  |  |  |  |
-| [18.17 Background apps](#bkmk-priv-background) |  |  |  | |
-| [18.18 Motion](#bkmk-priv-motion) |  |  |  |  |
-| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |  |
-| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |  |
-| [18.21 Inking & Typing](#bkmk-priv-ink) | | |  |  |
-| [19. Software Protection Platform](#bkmk-spp) | |  |  |  |
-| [20. Storage Health](#bkmk-storage-health) | |  | | |
-| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |  |
-| [22. Teredo](#bkmk-teredo) | |  | |  |
-| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  | |  |
-| [24. Windows Defender](#bkmk-defender) | |  |  |  |
-| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |  |
-| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |  |
-| [26. Microsoft Store](#bkmk-windowsstore) | |  | |  |
-| [27.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
-| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |  |
-| [28. Windows Update](#bkmk-wu) |  |  |  | |
+| [3. Date & Time](#bkmk-datetime) |  |  |  |
+| [4. Device metadata retrieval](#bkmk-devinst) | |  |  |
+| [5. Find My Device](#find-my-device) |  |  |  |
+| [6. Font streaming](#font-streaming) | |  |  |
+| [7. Insider Preview builds](#bkmk-previewbuilds) |  |  |  |
+| [8. Internet Explorer](#bkmk-ie) |  |  |  |
+| [10. Live Tiles](#live-tiles) | |  |  |
+| [11. Mail synchronization](#bkmk-mailsync) |  | |  |
+| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  |
+| [13. Microsoft Edge](#bkmk-edge) |  |  |  |
+| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  |
+| [15. Offline maps](#bkmk-offlinemaps) |  |  |  |
+| [16. OneDrive](#bkmk-onedrive) | |  |  |
+| [17. Preinstalled apps](#bkmk-preinstalledapps) |  | | |
+| [18. Settings > Privacy](#bkmk-settingssection) | | | |
+| [18.1 General](#bkmk-general) |  |  |  |
+| [18.2 Location](#bkmk-priv-location) |  |  |  |
+| [18.3 Camera](#bkmk-priv-camera) |  |  |  |
+| [18.4 Microphone](#bkmk-priv-microphone) |  |  |  |
+| [18.5 Notifications](#bkmk-priv-notifications) |  |  | |
+| [18.6 Speech](#bkmk-priv-speech) |  |  |  |
+| [18.7 Account info](#bkmk-priv-accounts) |  |  |  |
+| [18.8 Contacts](#bkmk-priv-contacts) |  |  |  |
+| [18.9 Calendar](#bkmk-priv-calendar) |  |  |  |
+| [18.10 Call history](#bkmk-priv-callhistory) |  |  |  |
+| [18.11 Email](#bkmk-priv-email) |  |  |  |
+| [18.12 Messaging](#bkmk-priv-messaging) |  |  |  |
+| [18.13 Phone calls](#bkmk-priv-phone-calls) |  |  |  |
+| [18.14 Radios](#bkmk-priv-radios) |  |  |  |
+| [18.15 Other devices](#bkmk-priv-other-devices) |  |  |  |
+| [18.16 Feedback & diagnostics](#bkmk-priv-feedback) |  |  |  |
+| [18.17 Background apps](#bkmk-priv-background) |  |  | |
+| [18.18 Motion](#bkmk-priv-motion) |  |  |  |
+| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |
+| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |
+| [18.21 Inking & Typing](#bkmk-priv-ink) | | |  |
+| [19. Software Protection Platform](#bkmk-spp) | |  |  |
+| [20. Storage Health](#bkmk-storage-health) | |  | |
+| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |
+| [22. Teredo](#bkmk-teredo) | |  |  |
+| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  |  |
+| [24. Windows Defender](#bkmk-defender) | |  |  |
+| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |
+| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |
+| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
+| [27.1 Apps for websites](#bkmk-apps-for-websites) | | |
+| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |
+| [28. Windows Update](#bkmk-wu) |  |  | |
## How to configure each setting
From 9d88227d5998fa30f911f3dfeda3a962f8291f1b Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Sat, 4 May 2019 00:21:54 -0700
Subject: [PATCH 006/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...ndows-operating-system-components-to-microsoft-services.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 1b00182dc9..77904998e6 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -109,7 +109,7 @@ The following table lists management options for each setting, beginning with Wi
| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |
| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |
| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
-| [27.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
+| [26.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |
| [28. Windows Update](#bkmk-wu) |  |  | |
@@ -219,7 +219,7 @@ See the following table for a summary of the management settings for Windows Ser
| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |
| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |
| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
-| [27.1 Apps for websites](#bkmk-apps-for-websites) | | |
+| [26.1 Apps for websites](#bkmk-apps-for-websites) | | |
| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |
| [28. Windows Update](#bkmk-wu) |  |  | |
From 974f967c4580d243267ca923492f1361725dd740 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Sat, 4 May 2019 00:25:48 -0700
Subject: [PATCH 007/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...ndows-operating-system-components-to-microsoft-services.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 77904998e6..53e0bf5f70 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -137,7 +137,7 @@ See the following table for a summary of the management settings for Windows Ser
| [20. Teredo](#bkmk-teredo) | |  |  |
| [24. Windows Defender](#bkmk-defender) | |  |  |
| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
-| [27.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
+| [26.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
| [28. Windows Update](#bkmk-wu) | |  |  |
### Settings for Windows Server 2016 Server Core
@@ -221,7 +221,7 @@ See the following table for a summary of the management settings for Windows Ser
| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
| [26.1 Apps for websites](#bkmk-apps-for-websites) | | |
| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |
-| [28. Windows Update](#bkmk-wu) |  |  | |
+| [28. Windows Update](#bkmk-wu) | |  |  |
## How to configure each setting
From bcd69a998272ade26e8d20e1447c40171e9f0803 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Sat, 4 May 2019 00:27:24 -0700
Subject: [PATCH 008/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 53e0bf5f70..37c46d6aaf 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -446,7 +446,7 @@ To turn off Insider Preview builds for Windows 10:
### 8. Internet Explorer
> [!NOTE]
-> The following Group Policies and Registry Keys are for user interactive scenarios rather then the typical idle traffic scenario. Find the Internet Explorer Group Policy objects under **Computer Configuration > Administrative Templates > Windows Components > Internet Explorer** and make these settings:
+> The following Group Policies and Registry Keys are for user interactive scenarios rather then the typical idle traffic scenario. Find the Internet Explorer Group Policy objects under **Computer Configuration > Administrative Templates > Windows Components > Internet Explorer** and make these settings:
| Policy | Description |
|------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
From 81600f747eb272afa1dcc50a2e1e77e9ae1def95 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Sat, 4 May 2019 00:41:15 -0700
Subject: [PATCH 009/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...system-components-to-microsoft-services.md | 290 +-----------------
1 file changed, 1 insertion(+), 289 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 37c46d6aaf..72bb0cefbe 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -325,14 +325,6 @@ You can also apply the Group Policies using the following registry keys:
If your organization tests network traffic, do not use a network proxy as Windows Firewall does not block proxy traffic. Instead, use a network traffic analyzer. Based on your needs, there are many network traffic analyzers available at no cost.
-### 2.2 Cortana and Search MDM policies
-
-For Windows 10 only, the following Cortana MDM policies are available in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx).
-
-| Policy | Description |
-|------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
-| Experience/AllowCortana | Choose whether to let Cortana install and run on the device. |
-| Search/AllowSearchToUseLocation | Choose whether Cortana and Search can provide location-aware search results.
Default: Allowed|
### 3. Date & Time
@@ -363,9 +355,6 @@ To prevent Windows from retrieving device metadata from the Internet:
- Create a new REG_DWORD registry setting named **PreventDeviceMetadataFromNetwork** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\Device Metadata** and set it to 1 (one).
- -or -
-
-- Apply the DeviceInstallation/PreventDeviceMetadataFromNetwork MDM policy from the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-deviceinstallation#deviceinstallation-preventdevicemetadatafromnetwork).
### 5. Find My Device
@@ -393,13 +382,6 @@ If you're running Windows 10, version 1607, Windows Server 2016, or later:
- Create a new REG_DWORD registry setting **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\EnableFontProviders** to **0 (zero)**.
- -or-
-
-- In Windows 10, version 1703, you can apply the System/AllowFontProviders MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) where:
-
- - **False**. Font streaming is Disabled.
-
- - **True**. Font streaming is Enabled.
> [!NOTE]
> After you apply this policy, you must restart the device for it to take effect.
@@ -433,15 +415,6 @@ To turn off Insider Preview builds for Windows 10:
- Create a new REG_DWORD registry setting named **AllowBuildPreview** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\PreviewBuilds** with a **value of 0 (zero)**
- -or-
-
-- Apply the System/AllowBuildPreview MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) where:
-
- - **0**. Users cannot make their devices available for downloading and installing preview software.
-
- - **1**. Users can make their devices available for downloading and installing preview software.
-
- - **2**. (default) Not configured. Users can make their devices available for download and installing preview software.
### 8. Internet Explorer
@@ -562,9 +535,6 @@ To turn off mail synchronization for Microsoft Accounts that are configured on a
- Remove any Microsoft Accounts from the Mail app.
- -or-
-
-- Apply the Accounts/AllowMicrosoftAccountConnection MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) where 0 is not allowed and 1 is allowed. This does not apply to Microsoft Accounts that have already been configured on the device.
To turn off the Windows Mail app:
@@ -583,8 +553,6 @@ To prevent communication to the Microsoft Account cloud authentication service.
To disable the Microsoft Account Sign-In Assistant:
-- Apply the Accounts/AllowMicrosoftAccountSignInAssistant MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) where 0 is turned off and 1 is turned on.
-
- Change the **Start** REG_DWORD registry setting in **HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\wlidsvc** to a value of **4**.
@@ -627,21 +595,6 @@ Alternatively, you can configure the these Registry keys as described:
| Choose whether employees can configure Compatibility View. | HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\MicrosoftEdge\\BrowserEmulation
REG_DWORD: MSCompatibilityMode
Value: **0**|
-### 13.2 Microsoft Edge MDM policies
-
-The following Microsoft Edge MDM policies are available in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx).
-
-| Policy | Description |
-|------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
-| Browser/AllowAutoFill | Choose whether employees can use autofill on websites.
**Set to: Not Allowed** |
-| Browser/AllowDoNotTrack | Choose whether employees can send Do Not Track headers.
**Set to: Allowed** |
-| Browser/AllowMicrosoftCompatbilityList | Specify the Microsoft compatibility list in Microsoft Edge.
**Set to: Not Allowed** |
-| Browser/AllowPasswordManager | Choose whether employees can save passwords locally on their devices.
**Set to: Not Allowed** |
-| Browser/AllowSearchSuggestionsinAddressBar | Choose whether the Address Bar shows search suggestions..
**Set to: Not Allowed** |
-| Browser/AllowSmartScreen | Choose whether SmartScreen is turned on or off.
**Set to: Not Allowed** |
-| Browser/FirstRunURL | Choose the home page for Microsoft Edge on Windows Mobile 10.
**Set to:** blank |
-
-
For a complete list of the Microsoft Edge policies, see [Available policies for Microsoft Edge](https://docs.microsoft.com/microsoft-edge/deploy/available-policies).
### 14. Network Connection Status Indicator
@@ -654,7 +607,6 @@ You can turn off NCSI by doing one of the following:
- **Enable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **Internet Communication Management** > **Internet Communication Settings** > **Turn off Windows Network Connectivity Status Indicator active tests**
-- In Windows 10, version 1703 and later, apply the Connectivity/DisallowNetworkConnectivityActiveTests MDM policy from the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-connectivity#connectivity-disallownetworkconnectivityactivetests) with a value of 1.
> [!NOTE]
> After you apply this policy, you must restart the device for the policy setting to take effect.
@@ -673,10 +625,6 @@ You can turn off the ability to download and update offline maps.
- Create a REG_DWORD registry setting named **AutoDownloadAndUpdateMapData** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\Maps** with a **value of 0 (zero)**.
- -or-
-
-- In Windows 10, version 1607 and later, apply the Maps/EnableOfflineMapsAutoUpdate MDM policy from the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-maps#maps-enableofflinemapsautoupdate) with a **value of 0**.
-
-and-
- In Windows 10, version 1607 and later, **Enable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Maps** > **Turn off unsolicited network traffic on the Offline Maps settings page**
@@ -703,10 +651,6 @@ To turn off OneDrive in your organization:
- Create a REG_DWORD registry setting named **PreventNetworkTrafficPreUserSignIn** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\OneDrive** with a **value of 1 (one)**
--or-
-
-- Set the System/DisableOneDriveFileSync MDM policy from the [Policy CSP](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-system#system-disableonedrivefilesync) to True (value 1) to disable OneDrive File Sync.
-
### 17. Preinstalled apps
@@ -951,14 +895,6 @@ To turn off **Send Microsoft info about how I write to help us improve typing an
- Turn off the feature in the UI.
- -or-
-
-- Apply the TextInput/AllowLinguisticDataCollection MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) where:
-
- - **0**. Not allowed
-
- - **1**. Allowed (default)
-
To turn off **Let websites provide locally relevant content by accessing my language list**:
- Turn off the feature in the UI.
@@ -999,18 +935,6 @@ To turn off **Location for this device**:
- Create a REG_DWORD registry setting named **LetAppsAccessLocation** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 2 (two)**.
- -or-
-
-- Apply the System/AllowLocation MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx), where:
-
- - **0**. Turned off and the employee can't turn it back on.
-
- - **1**. Turned on, but lets the employee choose whether to use it. (default)
-
- - **2**. Turned on and the employee can't turn it off.
-
- > [!NOTE]
- > You can also set this MDM policy in System Center Configuration Manager using the [WMI Bridge Provider](https://msdn.microsoft.com/library/dn905224.aspx).
To turn off **Location**:
@@ -1053,17 +977,6 @@ To turn off **Let apps use my camera**:
- Create a REG_DWORD registry setting named **LetAppsAccessCamera** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two).
- -or-
-
-- Apply the Camera/AllowCamera MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx), where:
-
- - **0**. Apps can't use the camera.
-
- - **1**. Apps can use the camera.
-
- > [!NOTE]
- > You can also set this MDM policy in System Center Configuration Manager using the [WMI Bridge Provider](https://msdn.microsoft.com/library/dn905224.aspx).
-
To turn off **Choose apps that can use your camera**:
@@ -1085,14 +998,6 @@ To turn off **Let apps use my microphone**:
-or-
-- Apply the Privacy/LetAppsAccessMicrophone MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccessmicrophone), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsAccessMicrophone** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two)
To turn off **Choose apps that can use your microphone**:
@@ -1101,9 +1006,6 @@ To turn off **Choose apps that can use your microphone**:
### 18.5 Notifications
->[!IMPORTANT]
->Disabling notifications will also disable the ability to manage the device through MDM. If you are using an MDM solution, make sure cloud notifications are enabled through one of the options below.
-
To turn off notifications network usage:
- Apply the Group Policy: **Computer Configuration** > **Administrative Templates** > **Start Menu and Taskbar** > **Notifications** > **Turn off Notifications network usage**
@@ -1114,13 +1016,6 @@ To turn off notifications network usage:
- Create a REG_DWORD registry setting named **NoCloudApplicationNotification** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\CurrentVersion\\PushNotifications** with a value of 1 (one)
- -or-
-
-
-- Apply the Notifications/DisallowCloudNotification MDM policy from the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-notifications#notifications-disallowcloudnotification), where:
-
- - **0**. WNS notifications allowed
- - **1**. No WNS notifications allowed
In the **Notifications** area, you can also choose which apps have access to notifications.
@@ -1136,14 +1031,6 @@ To turn off **Let apps access my notifications**:
-or-
-- Apply the Privacy/LetAppsAccessNotifications MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccessnotifications), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsAccessNotifications** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two)
### 18.6 Speech
@@ -1160,10 +1047,6 @@ To turn off streaming audio to Microsoft Speech services,
-or-
-- Set the Privacy\AllowInputPersonalization MDM Policy from the Policy CSP to **0 - Not allowed**
-
- -or-
-
- Create a REG_DWORD registry setting named **HasAccepted** in **HKEY_CURRENT_USER\\Software\\Microsoft\\Speech_OneCore\\Settings\\OnlineSpeechPrivacy** with a **value of 0 (zero)**
### 18.7 Account info
@@ -1182,14 +1065,6 @@ To turn off **Let apps access my name, picture, and other account info**:
-or-
-- Apply the Privacy/LetAppsAccessAccountInfo MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccessaccountinfo), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsAccessAccountInfo** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two).
@@ -1214,14 +1089,6 @@ To turn off **Choose apps that can access contacts**:
-or-
-- Apply the Privacy/LetAppsAccessContacts MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccesscontacts), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsAccessContacts** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two).
### 18.9 Calendar
@@ -1240,14 +1107,6 @@ To turn off **Let apps access my calendar**:
-or-
-- Apply the Privacy/LetAppsAccessCalendar MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccesscalendar), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsAccessCalendar** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two).
To turn off **Choose apps that can access calendar**:
@@ -1270,14 +1129,6 @@ To turn off **Let apps access my call history**:
-or-
- - Apply the Privacy/LetAppsAccessCallHistory MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccesscallhistory), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsAccessCallHistory** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two).
### 18.11 Email
@@ -1296,14 +1147,6 @@ To turn off **Let apps access and send email**:
-or-
- - Apply the Privacy/LetAppsAccessEmail MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccessemail), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsAccessEmail** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two).
### 18.12 Messaging
@@ -1322,14 +1165,6 @@ To turn off **Let apps read or send messages (text or MMS)**:
-or-
-- Apply the Privacy/LetAppsAccessMessaging MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccessmessaging), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsAccessMessaging** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two).
To turn off **Choose apps that can read or send messages**:
@@ -1362,14 +1197,6 @@ To turn off **Let apps make phone calls**:
-or-
-- Apply the Privacy/LetAppsAccessPhone MDM policy from the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccessphone), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsAccessPhone** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two).
@@ -1393,14 +1220,6 @@ To turn off **Let apps control radios**:
-or-
-- Apply the Privacy/LetAppsAccessRadios MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccessradios), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsAccessRadios** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two).
@@ -1422,10 +1241,6 @@ To turn off **Let apps automatically share and sync info with wireless devices t
-or-
-- Set the Privacy/LetAppsSyncWithDevices MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappssyncwithdevices) to **2**. Force deny
-
- -or-
-
- Create a REG_DWORD registry setting named **LetAppsSyncWithDevices** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 2 (two)**.
To turn off **Let your apps use your trusted devices (hardware you've already connected, or comes with your PC, tablet, or phone)**:
@@ -1440,14 +1255,6 @@ To turn off **Let your apps use your trusted devices (hardware you've already co
- Create a REG_DWORD registry setting named **LetAppsAccessTrustedDevices** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 2 (two)**.
- -or-
-
-- Apply the **Privacy/LetAppsAccessTrustedDevices** MDM policy from the [Policy CSP](/windows/client-management/mdm/policy-csp-privacy.md#privacy-letappsaccesstrusteddevices
-), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
### 18.16 Feedback & diagnostics
@@ -1502,19 +1309,7 @@ To change the level of diagnostic and usage data sent when you **Send your devic
> [!NOTE]
> If the **Security** option is configured by using Group Policy or the Registry, the value will not be reflected in the UI. The **Security** option is only available in Windows 10 Enterprise edition.
-
- -or-
-
-- Apply the System/AllowTelemetry MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx), where:
-
- - **0**. Maps to the **Security** level.
-
- - **1**. Maps to the **Basic** level.
-
- - **2**. Maps to the **Enhanced** level.
-
- - **3**. Maps to the **Full** level.
-
+
To turn off tailored experiences with relevant tips and recommendations by using your diagnostics data:
@@ -1557,9 +1352,6 @@ To turn off **Let apps run in the background**:
- Create a REG_DWORD registry setting named **LetAppsRunInBackground** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 2 (two)**
- -or-
-
-- Set the Privacy/LetAppsRunInBackground MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccessruninbackground) to **2 Force Deny**.
> [!NOTE]
> Some apps, including Cortana and Search, might not function as expected if you set **Let apps run in the background** to **Force Deny**.
@@ -1580,14 +1372,6 @@ To turn off **Let Windows and your apps use your motion data and collect motion
- Create a REG_DWORD registry setting named **LetAppsAccessMotion** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 2 (two)**.
- -or-
-
-- Apply the Privacy/LetAppsAccessMotion MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccessmotion), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
-
### 18.19 Tasks
@@ -1605,13 +1389,6 @@ To turn this off:
- Create a REG_DWORD registry setting named **LetAppsAccessTasks** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 2 (two)**.
- -or-
-
-- Apply the Privacy/LetAppsAccessTasks MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsaccesstasks), where:
-
- - **0**. User in control
- - **1**. Force allow
- - **2**. Force deny
### 18.20 App Diagnostics
@@ -1629,10 +1406,6 @@ To turn this off:
- Create a REG_DWORD registry setting named **LetAppsGetDiagnosticInfo** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 2 (two)**.
- -or-
-
-- Set the Privacy/LetAppsGetDiagnosticInfo MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappsgetdiagnosticinfo) to **2**. Force deny
-
### 18.21 Inking & Typing
@@ -1646,11 +1419,6 @@ To turn off Inking & Typing data collection (note: there is no Group Policy for
- Set **RestrictImplicitTextCollection** registry REG_DWORD setting in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\InputPersonalization** to a **value of 1 (one)**
- -or-
-
- - Set the Privacy\AllowInputPersonalization MDM Policy from the Policy CSP.
- [TextInput/AllowLinguisticDataCollection](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-textinput#textinput-allowlinguisticdatacollection) to **0** (not allowed). This policy setting controls the ability to send inking and typing data to Microsoft to improve the language recognition and suggestion capabilities of apps and services running on Windows.
-
If you're running at least Windows 10, version 1703, you can turn off updates to the speech recognition and speech synthesis models:
@@ -1660,10 +1428,6 @@ If you're running at least Windows 10, version 1703, you can turn off updates to
- Create a REG_DWORD registry setting named **AllowSpeechModelUpdate** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Speech** with a **value of 0 (zero)**
- -or-
-
- - Set the Speech/AllowSpeechModelUpdate MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962(v=vs.85).aspx#Speech_AllowSpeechModelUpdate) to **0**
-
> [!NOTE]
> Releases 1803 and earlier support **Speech, Inking, & Typing** as a combined settings area. For customizing those setting please follow the below instructions. For 1809 and above **Speech** and **Inking & Typing** are separate settings pages, please see the specific section (18.6 Speech or 18.21 Inking and Typing) above for those areas.
@@ -1702,10 +1466,6 @@ In the **Speech, Inking, & Typing** area, you can let Windows and Cortana better
-or-
- - Apply the Licensing/DisallowKMSClientOnlineAVSValidation MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) and **set the value to 1 (Enabled)**.
-
- -or-
-
- Create a REG_DWORD registry setting named **NoGenTicket** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows NT\\CurrentVersion\\Software Protection Platform** with a **value of 1 (one)**.
**For Windows Server 2019 or later:**
@@ -1749,11 +1509,6 @@ You can control if your settings are synchronized:
- Create a REG_DWORD registry setting named **DisableSettingSync** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\SettingSync** with a value of 2 (two) and another named **DisableSettingSyncUserOverride** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\SettingSync** with a value of 1 (one).
- -or-
-
-- Apply the Experience/AllowSyncMySettings MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) and **set the value to 0 (not allowed)**.
-
-
To turn off Messaging cloud sync:
- Note: There is no Group Policy corresponding to this registry key.
@@ -1812,10 +1567,6 @@ You can disconnect from the Microsoft Antimalware Protection Service.
- Delete the registry setting **named** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Updates**.
--OR-
-
-- For Windows 10 only, apply the Defender/AllowClouldProtection MDM policy from the [Defender CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx).
-
You can stop sending file samples back to Microsoft.
@@ -1823,10 +1574,6 @@ You can stop sending file samples back to Microsoft.
-or-
-- For Windows 10 only, apply the Defender/SubmitSamplesConsent MDM policy from the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-defender) to **2 (two) for Never Send**.
-
- -or-
-
- Use the registry to set the REG_DWORD value **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows Defender\\Spynet\\SubmitSamplesConsent** to **2 (two) for Never Send**.
@@ -1893,10 +1640,6 @@ To disable Windows Defender Smartscreen:
- Create a SZ registry setting named **ConfigureAppInstallControl** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\SmartScreen** with a value of **Anywhere**.
--OR-
-
-- Set the Browser/AllowSmartScreen MDM policy from the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) to **0 (turned Off)**.
-
### 25. Windows Spotlight
@@ -1911,10 +1654,6 @@ If you're running Windows 10, version 1607 or later, you need to:
-or-
-- For Windows 10 only, apply the Experience/AllowWindowsSpotlight MDM policy from the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-experience), with a value of 0 (zero).
-
- -or-
-
- Create a new REG_DWORD registry setting named **DisableWindowsSpotlightFeatures** in **HKEY_CURRENT_USER\\SOFTWARE\\Policies\\Microsoft\\Windows\\CloudContent** with a value of 1 (one).
@@ -2056,18 +1795,6 @@ You can find the Delivery Optimization Group Policy objects under **Computer Con
- Create a new REG_DWORD registry setting named **DODownloadMode** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\DeliveryOptimization** to a value of **100 (one hundred)**.
-### 27.4 Delivery Optimization MDM policies
-
-The following Delivery Optimization MDM policies are available in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx).
-
-| MDM Policy | Description |
-|---------------------------|-----------------------------------------------------------------------------------------------------|
-| DeliveryOptimization/DODownloadMode | Lets you choose where Delivery Optimization gets or sends updates and apps, including
0. Turns off Delivery Optimization.
1. Gets or sends updates and apps to PCs on the same NAT only.
2. Gets or sends updates and apps to PCs on the same local network domain.
3. Gets or sends updates and apps to PCs on the Internet.
99. Simple download mode with no peering.
100. Use BITS instead of Windows Update Delivery Optimization.
|
-| DeliveryOptimization/DOGroupID | Lets you provide a Group ID that limits which PCs can share apps and updates.
**Note** This ID must be a GUID.|
-| DeliveryOptimization/DOMaxCacheAge | Lets you specify the maximum time (in seconds) that a file is held in the Delivery Optimization cache.
The default value is 259200 seconds (3 days).|
-| DeliveryOptimization/DOMaxCacheSize | Lets you specify the maximum cache size as a percentage of disk size.
The default value is 20, which represents 20% of the disk.|
-| DeliveryOptimization/DOMaxUploadBandwidth | Lets you specify the maximum upload bandwidth (in KB/second) that a device uses across all concurrent upload activity.
The default value is 0, which means unlimited possible bandwidth.|
-
For more info about Delivery Optimization in general, see [Windows Update Delivery Optimization: FAQ](https://go.microsoft.com/fwlink/p/?LinkId=730684).
@@ -2118,21 +1845,6 @@ You can turn off automatic updates by doing one of the following. This is not re
- Add a REG_DWORD value named **AutoDownload** to **HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\WindowsStore\\WindowsUpdate** and set the value to 5.
- -or-
-
-- For Windows 10 only, apply the Update/AllowAutoUpdate MDM policy from the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update), where:
-
- - **0**. Notify the user before downloading the update.
-
- - **1**. Auto install the update and then notify the user to schedule a device restart.
-
- - **2** (default). Auto install and restart.
-
- - **3**. Auto install and restart at a specified time.
-
- - **4**. Auto install and restart without end-user control.
-
- - **5**. Turn off automatic updates.
For China releases of Windows 10 there is one additional Regkey to be set to prevent traffic:
From a214762af7e9a4335c0dd463fa450c40666d625a Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 11:24:29 -0700
Subject: [PATCH 010/156] added new topic
---
.../TOC.md | 1 +
...win32-apps-on-windows-10-s-mode-devices.md | 47 +++++++++++++++++++
2 files changed, 48 insertions(+)
create mode 100644 windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
diff --git a/windows/security/threat-protection/windows-defender-application-control/TOC.md b/windows/security/threat-protection/windows-defender-application-control/TOC.md
index 8b71416a15..ee04e5c824 100644
--- a/windows/security/threat-protection/windows-defender-application-control/TOC.md
+++ b/windows/security/threat-protection/windows-defender-application-control/TOC.md
@@ -31,6 +31,7 @@
### [Use a Windows Defender Application Control policy to control specific plug-ins, add-ins, and modules](use-windows-defender-application-control-policy-to-control-specific-plug-ins-add-ins-and-modules.md)
### [Use signed policies to protect Windows Defender Application Control against tampering](use-signed-policies-to-protect-windows-defender-application-control-against-tampering.md)
#### [Signing WDAC policies with SignTool.exe](signing-policies-with-signtool.md)
+### [Sideload Win32 apps on S mode](sideloading-win32-apps-on-windows-10-s-mode-devices.md)
### [Disable WDAC policies](disable-windows-defender-application-control-policies.md)
### [Device Guard and AppLocker](windows-defender-device-guard-and-applocker.md)
diff --git a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
new file mode 100644
index 0000000000..c9842bdb33
--- /dev/null
+++ b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
@@ -0,0 +1,47 @@
+---
+title: Sideloading Win32 apps on Windows 10 S mode devices (Windows 10)
+description: Windows Defender Application Control restricts which applications users are allowed to run and the code that runs in the system core.
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: security
+ms.localizationpriority: medium
+author: jsuther1974
+ms.date: 05/06/2018
+---
+
+# Sideloading Win32 apps on Windows 10 S mode devices
+
+**Applies to:**
+
+- Windows 10
+- Windows Server 2016
+
+Windows 10 S mode is a locked-down system that only runs Store apps.
+Although it provides tight security and thereby promises reduced management, its application control restrictions make it difficult for some to adopt it widely.
+Sideloading makes S mode a more viable proposition for enterprise and education workloads by allowing critical Desktop apps in addition to Store apps.
+
+## Process Overview
+
+To allow Win32 apps to run on a Windows 10 device in S mode, admins must ‘unlock’ the device so exceptions can be made to S mode policy, and then upload a corresponding signed catalog for each app to Intune. Here are the steps:
+
+1. Unlock S mode devices through Intune
+ - Admin uses the Device Guard Signing Service (DGSS) in the Microsoft Store for Business to generate a root certificate for the organization and upload it to Intune
+ - Intune will ensure this certificate is included in a device’s unlock token from OCDUS, and any app catalogs which are signed with it will be able to run on the unlocked device
+2. Create a supplemental policy to allow Win32 apps
+ - Admin uses Windows Defender Application Control tools to create a supplemental policy
+ - Admin uses DGSS to sign their supplemental policy
+ - Admin uploads signed supplemental policy to Intune
+3. Allow Win32 app catalogs through Intune
+ - Admin creates catalog files (1 for every app) and signs them using DGSS or other certificate infrastructure
+ - Admin submits the signed catalog to Intune
+ - Intune applies the signed catalog to unlocked S mode device using Sidecar
+
+## [Admin] Setting up Business Store to use DGSS
+
+1. In the Azure portal, create a new resource of type Azure Active Directory, then create an associated global admin user.
+2. Log in to the Microsoft Store for Business as the global admin then go to Organization > Private Store and accept
+• This will automatically generate a root certificate for the organization
+3. To download a root cert or upload policies/catalogs to sign, navigate to Manage > Settings > Devices
+• Note: you can only upload .bin and .cat files
+[Admin] Creating and Signing a Supplemental Policy
From a66303016109175aa7f35a1394aa7175ca8b0b9a Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 11:48:20 -0700
Subject: [PATCH 011/156] added new topic
---
...win32-apps-on-windows-10-s-mode-devices.md | 54 ++++++++++++++++---
1 file changed, 48 insertions(+), 6 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
index c9842bdb33..60b8c97f46 100644
--- a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
+++ b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
@@ -37,11 +37,53 @@ To allow Win32 apps to run on a Windows 10 device in S mode, admins must ‘unlo
- Admin submits the signed catalog to Intune
- Intune applies the signed catalog to unlocked S mode device using Sidecar
-## [Admin] Setting up Business Store to use DGSS
+## Setting up Business Store to use DGSS
1. In the Azure portal, create a new resource of type Azure Active Directory, then create an associated global admin user.
-2. Log in to the Microsoft Store for Business as the global admin then go to Organization > Private Store and accept
-• This will automatically generate a root certificate for the organization
-3. To download a root cert or upload policies/catalogs to sign, navigate to Manage > Settings > Devices
-• Note: you can only upload .bin and .cat files
-[Admin] Creating and Signing a Supplemental Policy
+2. Log in to the Microsoft Store for Business as the global admin then go to **Organization** > **Private Store** and accept.
+ This will automatically generate a root certificate for the organization.
+3. To download a root cert or upload policies/catalogs to sign, navigate to **Manage** > **Settings** > **Devices**.
+ Note: you can only upload .bin and .cat files.
+
+## Creating and Signing a Supplemental Policy
+
+1. Create new base policy using [New-CIPolicy](https://docs.microsoft.com/powershell/module/configci/new-cipolicy?view=win10-ps)
+ ```powershell
+ New-CIPolicy -Level PcaCertificate -UserPEs -ScanPath -MultiplePolicyFormat 3> -FilePath
+ ```
+2. Change it to a supplemental policy using [Set-CIPolicyIdInfo](https://docs.microsoft.com/powershell/module/configci/set-cipolicyidinfo?view=win10-ps)
+ ```powershell
+ Set-CIPolicyIdInfo -BasePolicyToSupplementPath -SupplementsBasePolicyID 5951A96A-E0B5-4D3D-8FB8-3E5B61030784 -FilePath
+ ```
+ Note: ‘5951A96A-E0B5-4D3D-8FB8-3E5B61030784' is the S-mode Base Policy ID.
+3. Put policy in enforce mode using [Set-RuleOption](https://docs.microsoft.com/powershell/module/configci/set-ruleoption?view=win10-ps)
+ ```powershell
+ Set-RuleOption -FilePath -Option 3 –Delete
+ ```
+ This deletes the ‘audit mode’ qualifier.
+4. Convert to .bin using [ConvertFrom-CIPolicy](https://docs.microsoft.com/powershell/module/configci/convertfrom-cipolicy?view=win10-ps)
+ ```powershell
+ ConvertFrom-CIPolicy -XmlFilePath -BinaryFilePath
+ ```
+ Note: PolicyID can be found by inspecting the Supplemental Policy XML. Convert to .bin to sign with DGSS (recommended) or .cip to sign locally.
+5. To sign using the recommended DGSS option through the Microsoft Store for Business, click **Manage** > **Settings** > **Devices** > **Upload** > **Sign**.
+ To sign locally using signtool, see [Signing policies with signtool](signing-policies-with-signtool.md)
+
+## Creating and Signing an App Catalog
+An admin must generate an app catalog for every deployed app:
+1. Use Package Inspector to [create a catalog](https://docs.microsoft.com/microsoft-store/add-unsigned-app-to-code-integrity-policy#a-href-idcreate-catalog-filesacreate-catalog-files-for-your-unsigned-app)
+ - Start Package Inspector to scan the installer:
+ ```console
+ PackageInspector.exe start C: -path
+ ```
+ - Open app installer
+ - Stop Package Inspector:
+ ```console
+ PackageInspector.exe stop C: -Name -cdfpath
+ ```
+2. To sign using the recommended DGSS option through the Microsoft Store for Business, click **Manage** > **Settings** > **Devices** > **Upload** > **Sign**.
+ To sign locally using signtool, see [Signing policies with signtool](signing-policies-with-signtool.md)
+
+## User experience
+
+Users will either have apps pushed directly to their devices by their admins, or they can download apps that their admins have made available through Company Portal
From 23ac84be9b08141ee17b575da3bc986f7c47a65f Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 11:50:30 -0700
Subject: [PATCH 012/156] edits
---
...sideloading-win32-apps-on-windows-10-s-mode-devices.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
index 60b8c97f46..249ce3ddce 100644
--- a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
+++ b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
@@ -67,7 +67,7 @@ To allow Win32 apps to run on a Windows 10 device in S mode, admins must ‘unlo
```
Note: PolicyID can be found by inspecting the Supplemental Policy XML. Convert to .bin to sign with DGSS (recommended) or .cip to sign locally.
5. To sign using the recommended DGSS option through the Microsoft Store for Business, click **Manage** > **Settings** > **Devices** > **Upload** > **Sign**.
- To sign locally using signtool, see [Signing policies with signtool](signing-policies-with-signtool.md)
+ To sign locally using signtool, see [Signing policies with signtool](signing-policies-with-signtool.md).
## Creating and Signing an App Catalog
An admin must generate an app catalog for every deployed app:
@@ -76,14 +76,14 @@ An admin must generate an app catalog for every deployed app:
```console
PackageInspector.exe start C: -path
```
- - Open app installer
+ - Open the app installer.
- Stop Package Inspector:
```console
PackageInspector.exe stop C: -Name -cdfpath
```
2. To sign using the recommended DGSS option through the Microsoft Store for Business, click **Manage** > **Settings** > **Devices** > **Upload** > **Sign**.
- To sign locally using signtool, see [Signing policies with signtool](signing-policies-with-signtool.md)
+ To sign locally using signtool, see [Signing policies with signtool](signing-policies-with-signtool.md).
## User experience
-Users will either have apps pushed directly to their devices by their admins, or they can download apps that their admins have made available through Company Portal
+Users will either have apps pushed directly to their devices by their admins, or they can download apps that their admins have made available through the Company Portal.
From ec802e324eb6f1d8caf26495f7a7c1d1e9be267a Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 12:08:33 -0700
Subject: [PATCH 013/156] adding path-based rules
---
.../select-types-of-rules-to-create.md | 33 +++++++++++++++++--
1 file changed, 30 insertions(+), 3 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
index 1a987c35e7..22294479af 100644
--- a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
+++ b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
@@ -23,8 +23,6 @@ Windows Defender Application Control (WDAC) provides control over a computer run
A common system imaging practice in today’s IT organization is to establish a “golden” image as a reference for what an ideal system should look like, and then use that image to clone additional company assets. WDAC policies follow a similar methodology, that begins with the establishment of a golden computer. As with imaging, you can have multiple golden computers based on model, department, application set, and so on. Although the thought process around the creation of WDAC policies is similar to imaging, these policies should be maintained independently. Assess the necessity of additional WDAC policies based on what should be allowed to be installed and run and for whom. For more details on doing this assessment, see the [WDAC Design Guide](windows-defender-application-control-design-guide.md).
-> **Note** Each computer can have only **one** WDAC policy at a time. Whichever way you deploy this policy, it is renamed to SIPolicy.p7b and copied to **C:\\Windows\\System32\\CodeIntegrity** and, for UEFI computers, **<EFI System Partition>\\Microsoft\\Boot**. Keep this in mind when you create your WDAC policies.
-
Optionally, WDAC can align with your software catalog as well as any IT department–approved applications. One straightforward method to implement WDAC is to use existing images to create one master WDAC policy. You do so by creating a WDAC policy from each image, and then by merging the policies. This way, what is installed on all of those images will be allowed to run, if the applications are installed on a computer based on a different image. Alternatively, you may choose to create a base applications policy and add policies based on the computer’s role or department. Organizations have a choice of how their policies are created, merged or serviced, and managed.
If you plan to use an internal CA to sign catalog files or WDAC policies, see the steps in [Optional: Create a code signing certificate for Windows Defender Application Control](create-code-signing-cert-for-windows-defender-application-control.md).
@@ -103,4 +101,33 @@ To create the WDAC policy, they build a reference server on their standard hardw
As part of normal operations, they will eventually install software updates, or perhaps add software from the same software providers. Because the "Publisher" remains the same on those updates and software, they will not need to update their WDAC policy. If they come to a time when the internally-written, unsigned application must be updated, they must also update the WDAC policy so that the hash in the policy matches the hash of the updated internal application.
-They could also choose to create a catalog that captures information about the unsigned internal application, then sign and distribute the catalog. Then the internal application could be handled by WDAC policies in the same way as any other signed application. An update to the internal application would only require that the catalog be regenerated, signed, and distributed (no restarts would be required).
\ No newline at end of file
+They could also choose to create a catalog that captures information about the unsigned internal application, then sign and distribute the catalog. Then the internal application could be handled by WDAC policies in the same way as any other signed application. An update to the internal application would only require that the catalog be regenerated, signed, and distributed (no restarts would be required).
+
+## Path-based rules
+
+Beginning with Windows 10 version 1903, WDAC policies can contain path-based rules.
+
+- New-CIPolicy parameters
+o FilePath: create path rules under path for anything not user-writeable (at the individual file level)
+New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
+ Optionally, add -UserWriteablePaths to ignore user writeability
+o FilePathRule: create a rule where filepath string is directly set to value of
+New-CIPolicyRule -FilePathRule
+• Useful for wildcards like C:\foo\*
+• Usage: same flow as per-app rules
+$rules = New-CIPolicyRule …
+$rules += New-CIPolicyRule …
+…
+New-CIPolicy -Rules $rules -f .\mypolicy.xml -u
+• Wildcards supported:
+o Suffix (ex. C:\foo\*) OR Prefix (ex. *\foo\bar.exe)
+ One or the other, not both at the same time
+ Does not support wildcard in the middle (ex. C:\*\foo.exe)
+o Examples:
+ %WINDIR%\...
+ %SYSTEM32%\...
+ %OSDRIVE%\...
+• Disable default FilePath rule protection of enforcing user-writeability
+Set-RuleOption -o 18 .\policy.xml
+o Adds “Disabled:Runtime FilePath Rule Protection” to the policy
+
From 44bb04a93af5d51764df038568758bab57e09d8e Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 12:24:44 -0700
Subject: [PATCH 014/156] new section
---
.../select-types-of-rules-to-create.md | 60 ++++++++++++-------
1 file changed, 38 insertions(+), 22 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
index 22294479af..14ae09388f 100644
--- a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
+++ b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
@@ -108,26 +108,42 @@ They could also choose to create a catalog that captures information about the u
Beginning with Windows 10 version 1903, WDAC policies can contain path-based rules.
- New-CIPolicy parameters
-o FilePath: create path rules under path for anything not user-writeable (at the individual file level)
-New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
- Optionally, add -UserWriteablePaths to ignore user writeability
-o FilePathRule: create a rule where filepath string is directly set to value of
-New-CIPolicyRule -FilePathRule
-• Useful for wildcards like C:\foo\*
-• Usage: same flow as per-app rules
-$rules = New-CIPolicyRule …
-$rules += New-CIPolicyRule …
-…
-New-CIPolicy -Rules $rules -f .\mypolicy.xml -u
-• Wildcards supported:
-o Suffix (ex. C:\foo\*) OR Prefix (ex. *\foo\bar.exe)
- One or the other, not both at the same time
- Does not support wildcard in the middle (ex. C:\*\foo.exe)
-o Examples:
- %WINDIR%\...
- %SYSTEM32%\...
- %OSDRIVE%\...
-• Disable default FilePath rule protection of enforcing user-writeability
-Set-RuleOption -o 18 .\policy.xml
-o Adds “Disabled:Runtime FilePath Rule Protection” to the policy
+ - FilePath: create path rules under path for anything not user-writeable (at the individual file level)
+ ```console
+ New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
+ ```
+ Optionally, add -UserWriteablePaths to ignore user writeability
+
+ - FilePathRule: create a rule where filepath string is directly set to value of
+ ```console
+ New-CIPolicyRule -FilePathRule
+ ```
+ Useful for wildcards like C:\foo\\*
+
+- Usage: same flow as per-app rules
+ ```xml
+ $rules = New-CIPolicyRule …
+ $rules += New-CIPolicyRule …
+ …
+ ```
+
+ ```console
+ New-CIPolicyRule -f .\mypolicy.xml -u
+ ```
+
+- Wildcards supported:
+ Suffix (ex. C:\foo\\*) OR Prefix (ex. *\foo\bar.exe)
+ - One or the other, not both at the same time
+ - Does not support wildcard in the middle (ex. C:\\*\foo.exe)
+ - Examples:
+ - %WINDIR%\\...
+ - %SYSTEM32%\\...
+ - %OSDRIVE%\\...
+
+- Disable default FilePath rule protection of enforcing user-writeability
+ For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy:
+ ```console
+ Set-RuleOption -o 18 .\policy.xml
+ ```
+
From 5b121e06fda2b52493fb9818c21f4441d71459ea Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 12:29:36 -0700
Subject: [PATCH 015/156] escaped ex
---
.../select-types-of-rules-to-create.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
index 14ae09388f..9dca57a76c 100644
--- a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
+++ b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
@@ -108,13 +108,13 @@ They could also choose to create a catalog that captures information about the u
Beginning with Windows 10 version 1903, WDAC policies can contain path-based rules.
- New-CIPolicy parameters
- - FilePath: create path rules under path for anything not user-writeable (at the individual file level)
+ - FilePath: create path rules under path \ for anything not user-writeable (at the individual file level)
```console
New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
```
Optionally, add -UserWriteablePaths to ignore user writeability
- - FilePathRule: create a rule where filepath string is directly set to value of
+ - FilePathRule: create a rule where filepath string is directly set to value of \
```console
New-CIPolicyRule -FilePathRule
```
From cab27d69904f9b3ab8c26581297700979e1d8af6 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 12:43:42 -0700
Subject: [PATCH 016/156] added new toc entry
---
.../TOC.md | 1 +
.../select-types-of-rules-to-create.md | 44 ------------
...improvements-in-windows-10-version-1903.md | 67 +++++++++++++++++++
3 files changed, 68 insertions(+), 44 deletions(-)
create mode 100644 windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
diff --git a/windows/security/threat-protection/windows-defender-application-control/TOC.md b/windows/security/threat-protection/windows-defender-application-control/TOC.md
index ee04e5c824..89a1b3bafb 100644
--- a/windows/security/threat-protection/windows-defender-application-control/TOC.md
+++ b/windows/security/threat-protection/windows-defender-application-control/TOC.md
@@ -34,6 +34,7 @@
### [Sideload Win32 apps on S mode](sideloading-win32-apps-on-windows-10-s-mode-devices.md)
### [Disable WDAC policies](disable-windows-defender-application-control-policies.md)
### [Device Guard and AppLocker](windows-defender-device-guard-and-applocker.md)
+### [Windows Defender Application Control improvements in Windows 10 version 1903](windows-defender-application-control-improvements-in-windows-10-version-1903.md)
## [AppLocker](applocker\applocker-overview.md)
### [Administer AppLocker](applocker\administer-applocker.md)
diff --git a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
index 9dca57a76c..85b9f016f2 100644
--- a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
+++ b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
@@ -103,47 +103,3 @@ As part of normal operations, they will eventually install software updates, or
They could also choose to create a catalog that captures information about the unsigned internal application, then sign and distribute the catalog. Then the internal application could be handled by WDAC policies in the same way as any other signed application. An update to the internal application would only require that the catalog be regenerated, signed, and distributed (no restarts would be required).
-## Path-based rules
-
-Beginning with Windows 10 version 1903, WDAC policies can contain path-based rules.
-
-- New-CIPolicy parameters
- - FilePath: create path rules under path \ for anything not user-writeable (at the individual file level)
- ```console
- New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
- ```
- Optionally, add -UserWriteablePaths to ignore user writeability
-
- - FilePathRule: create a rule where filepath string is directly set to value of \
- ```console
- New-CIPolicyRule -FilePathRule
- ```
- Useful for wildcards like C:\foo\\*
-
-- Usage: same flow as per-app rules
- ```xml
- $rules = New-CIPolicyRule …
- $rules += New-CIPolicyRule …
- …
- ```
-
- ```console
- New-CIPolicyRule -f .\mypolicy.xml -u
- ```
-
-- Wildcards supported:
- Suffix (ex. C:\foo\\*) OR Prefix (ex. *\foo\bar.exe)
- - One or the other, not both at the same time
- - Does not support wildcard in the middle (ex. C:\\*\foo.exe)
- - Examples:
- - %WINDIR%\\...
- - %SYSTEM32%\\...
- - %OSDRIVE%\\...
-
-- Disable default FilePath rule protection of enforcing user-writeability
- For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy:
- ```console
- Set-RuleOption -o 18 .\policy.xml
- ```
-
-
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
new file mode 100644
index 0000000000..69413bcaca
--- /dev/null
+++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
@@ -0,0 +1,67 @@
+---
+title: Windows Defender Application Control improvements in Windows 10 version 1903 (Windows 10)
+description: Windows Defender Application Control restricts which applications users are allowed to run and the code that runs in the system core.
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: security
+ms.localizationpriority: medium
+author: jsuther1974
+ms.date: 05/06/2018
+---
+
+# Windows Defender Application Control improvements in Windows 10 version 1903
+
+**Applies to:**
+
+- Windows 10
+- Windows Server 2016
+
+## Path-based rules
+
+Beginning with Windows 10 version 1903, WDAC policies can contain path-based rules.
+
+- New-CIPolicy parameters
+ - FilePath: create path rules under path \ for anything not user-writeable (at the individual file level)
+ ```console
+ New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
+ ```
+ Optionally, add -UserWriteablePaths to ignore user writeability
+
+ - FilePathRule: create a rule where filepath string is directly set to value of \
+ ```console
+ New-CIPolicyRule -FilePathRule
+ ```
+ Useful for wildcards like C:\foo\\*
+
+- Usage: same flow as per-app rules
+ ```xml
+ $rules = New-CIPolicyRule …
+ $rules += New-CIPolicyRule …
+ …
+ ```
+
+ ```console
+ New-CIPolicyRule -f .\mypolicy.xml -u
+ ```
+
+- Wildcards supported:
+ Suffix (ex. C:\foo\\*) OR Prefix (ex. *\foo\bar.exe)
+ - One or the other, not both at the same time
+ - Does not support wildcard in the middle (ex. C:\\*\foo.exe)
+ - Examples:
+ - %WINDIR%\\...
+ - %SYSTEM32%\\...
+ - %OSDRIVE%\\...
+
+- Disable default FilePath rule protection of enforcing user-writeability
+ For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy:
+ ```console
+ Set-RuleOption -o 18 .\policy.xml
+ ```
+
+## Multiple Policies
+
+Beginning with Windows 10 vesion 1903, WDAC supportd multiple code integrity policies for one device.
+
+
From db7c319f3b849c3f30bd30b317083e59c33ed170 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 14:28:02 -0700
Subject: [PATCH 017/156] added preview text
---
...win32-apps-on-windows-10-s-mode-devices.md | 3 +++
...improvements-in-windows-10-version-1903.md | 27 ++++++++++---------
2 files changed, 17 insertions(+), 13 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
index 249ce3ddce..5bbde4033e 100644
--- a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
+++ b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
@@ -17,6 +17,9 @@ ms.date: 05/06/2018
- Windows 10
- Windows Server 2016
+>[!IMPORTANT]
+>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
+
Windows 10 S mode is a locked-down system that only runs Store apps.
Although it provides tight security and thereby promises reduced management, its application control restrictions make it difficult for some to adopt it widely.
Sideloading makes S mode a more viable proposition for enterprise and education workloads by allowing critical Desktop apps in addition to Store apps.
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
index 69413bcaca..d3c5ebd625 100644
--- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
+++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
@@ -17,9 +17,14 @@ ms.date: 05/06/2018
- Windows 10
- Windows Server 2016
+>[!IMPORTANT]
+>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
+
+This topic covers improvements introduced in Windows 10, version 1903.
+
## Path-based rules
-Beginning with Windows 10 version 1903, WDAC policies can contain path-based rules.
+Beginning with Windows 10 version 1903, Windows Defender Application Control (WDAC) policies can contain path-based rules.
- New-CIPolicy parameters
- FilePath: create path rules under path \ for anything not user-writeable (at the individual file level)
@@ -34,29 +39,25 @@ Beginning with Windows 10 version 1903, WDAC policies can contain path-based rul
```
Useful for wildcards like C:\foo\\*
-- Usage: same flow as per-app rules
- ```xml
+- Usage follows the same flow as per-app rules:
+ ```powershell
$rules = New-CIPolicyRule …
$rules += New-CIPolicyRule …
…
- ```
-
- ```console
New-CIPolicyRule -f .\mypolicy.xml -u
```
-- Wildcards supported:
- Suffix (ex. C:\foo\\*) OR Prefix (ex. *\foo\bar.exe)
- - One or the other, not both at the same time
- - Does not support wildcard in the middle (ex. C:\\*\foo.exe)
+- Wildcards supported
+ - Suffix (ex. C:\foo\\*) OR Prefix (ex. *\foo\bar.exe)
+ - One or the other, not both at the same time
+ - Does not support wildcard in the middle (ex. C:\\*\foo.exe)
- Examples:
- %WINDIR%\\...
- %SYSTEM32%\\...
- %OSDRIVE%\\...
-- Disable default FilePath rule protection of enforcing user-writeability
- For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy:
- ```console
+- Disable default FilePath rule protection of enforcing user-writeability. For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy:
+ ```powershell
Set-RuleOption -o 18 .\policy.xml
```
From a878d791762b0a5706f03e78be9aa0689303c967 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 14:29:59 -0700
Subject: [PATCH 018/156] Update
windows-defender-application-control-improvements-in-windows-10-version-1903.md
---
...ication-control-improvements-in-windows-10-version-1903.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
index d3c5ebd625..1cf88aa97e 100644
--- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
+++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
@@ -28,13 +28,13 @@ Beginning with Windows 10 version 1903, Windows Defender Application Control (WD
- New-CIPolicy parameters
- FilePath: create path rules under path \ for anything not user-writeable (at the individual file level)
- ```console
+ ```powershell
New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
```
Optionally, add -UserWriteablePaths to ignore user writeability
- FilePathRule: create a rule where filepath string is directly set to value of \
- ```console
+ ```powershell
New-CIPolicyRule -FilePathRule
```
Useful for wildcards like C:\foo\\*
From 43571b22c515a289d7749145e97fe99fd6d97cbc Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 14:31:41 -0700
Subject: [PATCH 019/156] edits
---
...ation-control-improvements-in-windows-10-version-1903.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
index 1cf88aa97e..7aa79f9097 100644
--- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
+++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
@@ -66,3 +66,9 @@ Beginning with Windows 10 version 1903, Windows Defender Application Control (WD
Beginning with Windows 10 vesion 1903, WDAC supportd multiple code integrity policies for one device.
+WDAC – Composable (stacked) code integrity policies for supporting multiple code integrity policies
+### Precedence
+- Multiple base policies: intersection
+ - Only applications allowed by both policies run without generating block events
+- Base + supplemental policy: union
+ - Files that are allowed by the base policy or the supplemental policy are not blocked
From fc8eff7139bd482802f06d98ef4c8a9262cfafbf Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 17:16:22 -0700
Subject: [PATCH 020/156] added PS examples
---
...improvements-in-windows-10-version-1903.md | 170 +++++++++++++++++-
1 file changed, 167 insertions(+), 3 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
index 7aa79f9097..86738f84e8 100644
--- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
+++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
@@ -63,12 +63,176 @@ Beginning with Windows 10 version 1903, Windows Defender Application Control (WD
## Multiple Policies
-Beginning with Windows 10 vesion 1903, WDAC supportd multiple code integrity policies for one device.
+Beginning with Windows 10 version 1903, WDAC supports multiple code integrity policies for one device.
-
-WDAC – Composable (stacked) code integrity policies for supporting multiple code integrity policies
### Precedence
+
- Multiple base policies: intersection
- Only applications allowed by both policies run without generating block events
- Base + supplemental policy: union
- Files that are allowed by the base policy or the supplemental policy are not blocked
+
+### Newly Supported Scenarios
+
+WDAC brings you the ability to support multiple CI policies. Three scenarios are now supported:
+
+1. Enforce and Audit Side-by-Side (Intersection)
+ - To validate policy changes before deploying in enforcement mode, deploy an audit-mode base policy side-by-side with an existing enforcement-mode base policy
+2. Multiple Base Policies (Intersection)
+ - Enforce two or more base policies simultaneously to allow simpler policy targeting for policies with different scope/intent
+ - Ex. Base1 is a corporate standard policy that is relatively loose to accommodate all organizations while forcing minimum corp standards (e.g. Windows works + Managed Installer + path rules). Base2 is a team-specific policy that further restricts what is allowed to run (e.g. Windows works + Managed Installer + corporate signed apps only)
+3. Supplemental Policies (Union)
+ - Deploy a supplemental policy (or policies) to expand a base policy
+ - Ex. The Azure host base policy restricts tightly to just allow Windows and hardware drivers. Can add a supplemental policy to allow just the additional signer rules needed to support signed code from the Exchange team.
+
+## COM Whitelisting
+
+• https://docs.microsoft.com/en-us/windows/desktop/com/the-component-object-model
+
+Get GUID of application to allow by either:
+- Finding block event in Event Viewer (Application and Service Logs > Microsoft > Windows > AppLocker > MSI and Script) and extracting GUID
+- Creating audit policy (using New-CIPolicy –Audit), potentially with specific provider, and use info from block events to get GUID
+
+### Author setting
+
+Three elements:
+- Provider: platform on which code is running (values are Powershell, WSH, IE, VBA, MSI, or a wildcard “AllHostIds”)
+- Key: GUID for the program you with to run, in the format Key="{33333333-4444-4444-1616-161616161616}"
+- ValueName: needs to be set to "EnterpriseDefinedClsId"
+One attribute:
+- Value: needs to be “true” for allow and “false” for deny
+ Note: without quotation marks
+ Note: deny only works in base policies
+- The setting needs to be placed in the order of ASCII values, first by Provider, then Key, then ValueName
+
+### Examples
+
+```xml
+
+
+ true
+
+
+
+
+ false
+
+
+
+
+ true
+
+
+```
+
+## New PowerShell parameters
+
+New-CIPolicy
+- MultiplePolicyFormat: allows for multiple policies
+
+```powershell
+New-CIPolicy [-FilePath] -Level {None | Hash | FileName | SignedVersion | Publisher | FilePublisher | LeafCertificate | PcaCertificate | RootCertificate | WHQL | WHQLPublisher | WHQLFilePublisher | PFN | FilePath}
+ [-DriverFiles ] [-Fallback {None | Hash | FileName | SignedVersion | Publisher | FilePublisher | LeafCertificate | PcaCertificate | RootCertificate | WHQL | WHQLPublisher | WHQLFilePublisher | PFN | FilePath}]
+ [-Audit] [-ScanPath ] [-ScriptFileNames] [-AllowFileNameFallbacks] [-SpecificFileNameLevel {None | OriginalFileName | InternalName | FileDescription | ProductName | PackageFamilyName | FilePath}] [-UserPEs] [-NoScript]
+ [-Deny] [-NoShadowCopy] [-MultiplePolicyFormat] [-OmitPaths ] [-PathToCatroot ] [] – to generate new policy format(base policy and policy type and policy guid)
+```
+
+Set-CIPolicyIdInfo
+- **SupplementsBasePolicyID**: guid of new supplemental policy
+- **BasePolicyToSupplementPath**: base policy that the supplemental policy applies to
+- **ResetPolicyID**: reset the policy guids back to a random guid
+
+```powershell
+Set-CIPolicyIdInfo [-FilePath] [-PolicyName ] [-SupplementsBasePolicyID ] [-BasePolicyToSupplementPath ] [-ResetPolicyID] [-PolicyId ] []
+```
+
+Add-SignerRule
+- **Supplemental**: provides supplemental signers
+
+```powershell
+Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
+```
+
+Set-RuleOption
+- **Enabled:Allow Supplemental Policies**: makes base policy able to be supplemented
+
+### Examples
+
+**Scenario #1: Creating a new base policy**
+
+```powershell
+New-CiPolicy -MulitplePolicyFormat -foo –bar
+```
+
+- **MultiplePolicyFormat** switch results in 1) random GUIDs being generated for the policy ID and 2) the policy type being specified as base.
+ Can optionally choose to make it supplementable:
+ - Set-RuleOption has a new option **Enabled:Allow Supplemental Policies** to set for base policy
+- For signed policies that are being made supplementable, need to ensure that supplemental signers are defined. Use “Add-SignerRule” to provide supplemental signers.
+ ```powershell
+ Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
+ ```
+
+**Scenario #2: Creating a new supplemental policy**
+
+1. Scan using `New-CiPolicy –MuliplePolicyFormat` to generate a base policy:
+ ```powershell
+ New-CIPolicy -Level PcaCertificate -UserPEs -ScanPath -MultiplePolicyFormat 3> -FilePath
+ ```
+2. Change this new base policy to a supplemental policy
+ - Provide path of base in `Set-CIPolicyIdInfo –BasePolicytoSupplementPath`
+ - Provide GUID of base in `Set-CIPolicyIdInfo –SupplementsBasePolicyID`
+ ```powershell
+ Set-CIPolicyIdInfo -BasePolicyToSupplementPath -SupplementsBasePolicyID -FilePath
+ ```
+ - Can revert the policy back to being a base policy using `-ResetPolicyID`
+
+**Scenario #3: Merging policies**
+
+- When merging, the policy type and ID of the leftmost/first policy specified is used
+ - If the leftmost is a base policy with ID , then regardless of what the GUIDS and types are for any subsequent policies, the merged policy will be a base policy with ID
+
+## Packaged App Rules
+
+`New-CIPolicyRule -Package $Package -Deny` to block apps is your best use case, so something like:
+
+1. Get the info about an installed package.
+ ```powershell
+ $package = Get-AppxPackage -name
+ ```
+ Dependencies field in output is full Package object, can be accessed and passed directly to New-CIPolicyRule.
+2. Make a rule.
+ ```powershell
+ $Rule = New-CIPolicyRule -Package $package -deny
+ ```
+3. Repeat for other packages you want to block using $rule +=….
+4. Make a policy for just the blocks you created for packages.
+ ```powershell
+ New-CIpolicy -rules $rule -f .\policy.xml -u
+ ```
+5. Merge with allow windows policy, or you could also use examplepolicies\AllowAll.xml.
+ ```powershell
+ Merge-CIPolicy -PolicyPaths .\policy.xml,C:\windows\Schemas\codeintegrity\examplepolicies\DefaultWindows_Audit.xml -o allowWindowsDenyPackages.xml
+ ```
+6. Disable audit mode.
+ ```powershell
+ Set-RuleOption -o 3 -Delete .\allowWindowsDenyPackages.xml
+ ```
+7. Enable invalidate EAs on reboot.
+ ```powershell
+ Set-RuleOption -o 15 .\allowWindowsDenyPackages.xml
+ ```
+8. Compile the policy
+ ```powershell
+ ConvertFrom-CIPolicy .\AllowWindowsDenyPackages.xml C:\compiledpolicy.bin
+ ```
+9. Install the policy withwout restarting.
+ ```powershell
+ Invoke-CimMethod -Namespace root\Microsoft\Windows\CI -ClassName PS_UpdateAndCompareCIPolicy -MethodName Update -Arguments @{FilePath = "C:\compiledpolicy.bin"}
+ ```
+
+After doing this on the next build of Dev3, for the apps that you blocked, already installed apps should fail to launch, and should you put this policy on another machine that hasn’t yet installed the apps, store should block them from being purchased/installed.
+If you wanted to make a rule for an app that isn’t already installed, first make a rule for an app that is. Then for the app you want to actually block take the store URL (from store page click … then share, then copy link to get something like: https://www.microsoft.com/store/productId/9WZDNCRFJ3TJ) and grab the hash code at the end (in bold) then replace the bolded bit below:
+https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9wzdncrfj3tj/applockerdata
+then grab packagefamilyname and replace the one in the xml you got in step 4 with the PFN from the link above, then run through 5-9 again.
+
+
From 7bb830d8e386dde5fa961af312871748c931c9fa Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 17:17:56 -0700
Subject: [PATCH 021/156] added faq
---
...improvements-in-windows-10-version-1903.md | 70 +++++++++++++++++++
1 file changed, 70 insertions(+)
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
index 86738f84e8..3bee320959 100644
--- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
+++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
@@ -235,4 +235,74 @@ If you wanted to make a rule for an app that isn’t already installed, first ma
https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9wzdncrfj3tj/applockerdata
then grab packagefamilyname and replace the one in the xml you got in step 4 with the PFN from the link above, then run through 5-9 again.
+## FAQs
+
+Misc
+a. Questions:
+• What uniquely identifies a “file”? SHA1, SHA256, either, both?
+o What is the “Flat hash” vs. normal?
+Either hash works as a unique identifier, would recommend sha256 though just because lower collision chance.
+“Authenticode Hash” is the hash we use, it is calculated in a way that does not change even if the file is embed signed, whereas “flat hash” is just a direct hash on the bytes of the file and changes with signature.
+For Scripts/MSIs an embedded hash would use the SIP of the particular script type, while a catalog hash would use the flat hash (since catalogs are only aware of a few select SIPs, particularly the PE exe/dll one), so the 8028/8029 events log the “CatalogHash” as well, in case it differs from the hash used to evaluate against an embedded sig
+
+• What property of a file is used to map out to a publisher?
+Files are tied to publishers via their signature (either embed signed or catalog signed via a signed catalog containing that files hash), correlate 3089 events in order to get publisher data
+
+• Can you give a description/enumeration of values for “signing level”?
+
+Base signing levels are:
+#define SE_SIGNING_LEVEL_UNCHECKED 0x00000000
+#define SE_SIGNING_LEVEL_UNSIGNED 0x00000001
+#define SE_SIGNING_LEVEL_ENTERPRISE 0x00000002
+#define SE_SIGNING_LEVEL_CUSTOM_1 0x00000003
+#define SE_SIGNING_LEVEL_DEVELOPER SE_SIGNING_LEVEL_CUSTOM_1
+#define SE_SIGNING_LEVEL_AUTHENTICODE 0x00000004
+#define SE_SIGNING_LEVEL_CUSTOM_2 0x00000005
+#define SE_SIGNING_LEVEL_STORE 0x00000006
+#define SE_SIGNING_LEVEL_CUSTOM_3 0x00000007
+#define SE_SIGNING_LEVEL_ANTIMALWARE SE_SIGNING_LEVEL_CUSTOM_3
+#define SE_SIGNING_LEVEL_MICROSOFT 0x00000008
+#define SE_SIGNING_LEVEL_CUSTOM_4 0x00000009
+#define SE_SIGNING_LEVEL_CUSTOM_5 0x0000000A
+#define SE_SIGNING_LEVEL_DYNAMIC_CODEGEN 0x0000000B
+#define SE_SIGNING_LEVEL_WINDOWS 0x0000000C
+#define SE_SIGNING_LEVEL_CUSTOM_7 0x0000000D
+#define SE_SIGNING_LEVEL_WINDOWS_TCB 0x0000000E
+#define SE_SIGNING_LEVEL_CUSTOM_6 0x0000000F
+
+The TL;DR on signing levels is we have collections of certificates+EKUs that we use to define broad “security levels” based on signer, for example SE_SIGNING_LEVEL_WINDOWS generally maps to “signed as part of a production windows build)
+Some also inherit from others (e.g. signing level windows is a subset of microsoft)
+
+See minkernel\published\base\ntseapi_x.w and ntseapi.w, and/or poke around in onecore\base\ci\dll\cipolicy.c searching for references to se_signing_level* for more on signing levels and how they are used with CIPolicy
+
+• What is the “SI Signing Scenario”?
+Pretty sure this one maps to either kernel or user mode (0 or 1 respectively), CIPolicy lets you configure whitelists for each separately, e.g. you probably wouldn’t want some random user mode app, say notepad++ to run as a kernel driver 😊
+
+• Can you also provide the “description” for the events? I know audit/block are each one of two values next to each other, but do they audit/block a specific file type only? Script? Exe?
+3076 Audit for exe/dll generated by CI in the createprocess stack
+3077 enforced version
+3089 Signing information event correlated with either a 3076/3077 event, contains # of signatures and an index as to which signature it is, one 3089 is generated for each signature of a file (so many 3089 map to one 3076/77). Unsigned files will generate a single 3089 with TotalSignatureCount 0
+8028 Audit for scripts/msis generated by WLDP being called by the scripthosts themselves (scripthosts opt in to enforcement, so we don’t enforce on 3rd party scripthosts like python/ruby)
+8029 Enforce for scripts
+We don’t currently have signer information in the script events
+
+• I don’t understand what the “Policy” fields are.
+Code Integrity Policy is at its core an enterprise whitelisting solution. For these events to be generated, customers would have had to generate a policy xml, compile it, and deploy it. PolicyName/PolicyID fields are optional fields customers can add to the policy to get propagated into the events, policy hash is literally the hash of the policy (and policy hash matching guarantees that two events were blocked by the same policy). Since you can have multiple concurrent policies on one system supplementing each other, knowing what policy actually blocked the binary from running is useful
+
+• Is this purely file based or do I need to worry about the “PackageName” grouping?
+o Eg… do I need the packagename to get back to a publisher or are individual files from the package all mapped up directly?
+An event is generated for each individual binary that failed policy. The PackageFamilyName is put in the process token of all binaries loading under an appx and is can be used in rules in policy to attempt to allow an entire package to run rather than whitelisting each individual binary, but we will still generate an individual event for each binary that fails
+I can’t currently remember if the PackageFamilyName field is even calculated or just zeroed out if there aren’t PFN rules in a policy
+
+• What field in 3089 am I able to join on to map from File to Publisher?
+CorrelationID is actually not in the event templates I sent you and is actually an optional field in the metadata of every eventviewer event. In the XML of the event the correlationID’s path is:
+
+For comparison, the rest of the fields look like:
+valuevalue2…
+
+• 3076/77 don’t seem to include ‘File Path’. Can this be deduced from ‘File Name’?
+• 8028/8029 don’t seem to include ‘File Name’. Can this be deduced from ‘File Path’?
+“File Name” in 3076/77 is actually the path in NT form (\Device\HarddiskVolume3\Windows\System32\myfile.dll), and the “originalfilename” field maps to what would be “File Name” in a file rule in policy XML
+For 8028/8029 File Path is the C:\ path to the file and you’ll notice a trend where we didn’t bother to include all the same fields we do for the PE files so there is no “originalFileName”
+
From fd96a3d538cf448adb87c3cb857d242e986a5f09 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Mon, 6 May 2019 17:32:02 -0700
Subject: [PATCH 022/156] added Q&A
---
...improvements-in-windows-10-version-1903.md | 82 +++++++++++--------
1 file changed, 49 insertions(+), 33 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
index 3bee320959..b563a2c54f 100644
--- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
+++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
@@ -237,20 +237,23 @@ then grab packagefamilyname and replace the one in the xml you got in step 4 wit
## FAQs
-Misc
-a. Questions:
-• What uniquely identifies a “file”? SHA1, SHA256, either, both?
-o What is the “Flat hash” vs. normal?
-Either hash works as a unique identifier, would recommend sha256 though just because lower collision chance.
+**Q:** What uniquely identifies a “file”? SHA1, SHA256, either, both? What is the “Flat hash” vs. normal?
+
+**A:** Either hash works as a unique identifier, would recommend sha256 though just because lower collision chance.
+
“Authenticode Hash” is the hash we use, it is calculated in a way that does not change even if the file is embed signed, whereas “flat hash” is just a direct hash on the bytes of the file and changes with signature.
+
For Scripts/MSIs an embedded hash would use the SIP of the particular script type, while a catalog hash would use the flat hash (since catalogs are only aware of a few select SIPs, particularly the PE exe/dll one), so the 8028/8029 events log the “CatalogHash” as well, in case it differs from the hash used to evaluate against an embedded sig
-• What property of a file is used to map out to a publisher?
-Files are tied to publishers via their signature (either embed signed or catalog signed via a signed catalog containing that files hash), correlate 3089 events in order to get publisher data
+**Q:** What property of a file is used to map out to a publisher?
+
+**A:** Files are tied to publishers via their signature (either embed signed or catalog signed via a signed catalog containing that files hash), correlate 3089 events in order to get publisher data
-• Can you give a description/enumeration of values for “signing level”?
+**Q:** Can you give a description/enumeration of values for “signing level”?
-Base signing levels are:
+**A:** Base signing levels are:
+
+```xml
#define SE_SIGNING_LEVEL_UNCHECKED 0x00000000
#define SE_SIGNING_LEVEL_UNSIGNED 0x00000001
#define SE_SIGNING_LEVEL_ENTERPRISE 0x00000002
@@ -269,40 +272,53 @@ Base signing levels are:
#define SE_SIGNING_LEVEL_CUSTOM_7 0x0000000D
#define SE_SIGNING_LEVEL_WINDOWS_TCB 0x0000000E
#define SE_SIGNING_LEVEL_CUSTOM_6 0x0000000F
+```
-The TL;DR on signing levels is we have collections of certificates+EKUs that we use to define broad “security levels” based on signer, for example SE_SIGNING_LEVEL_WINDOWS generally maps to “signed as part of a production windows build)
-Some also inherit from others (e.g. signing level windows is a subset of microsoft)
+The TL;DR on signing levels is we have collections of certificates+EKUs that we use to define broad “security levels” based on signer, for example SE_SIGNING_LEVEL_WINDOWS generally maps to “signed as part of a production Windows build)
+Some also inherit from others (e.g. signing level Windows is a subset of Microsoft)
-See minkernel\published\base\ntseapi_x.w and ntseapi.w, and/or poke around in onecore\base\ci\dll\cipolicy.c searching for references to se_signing_level* for more on signing levels and how they are used with CIPolicy
+**Q:** What is the “SI Signing Scenario”?
+This maps to either kernel or user mode (0 or 1 respectively). CIPolicy lets you configure whitelists for each separately.
-• What is the “SI Signing Scenario”?
-Pretty sure this one maps to either kernel or user mode (0 or 1 respectively), CIPolicy lets you configure whitelists for each separately, e.g. you probably wouldn’t want some random user mode app, say notepad++ to run as a kernel driver 😊
-
-• Can you also provide the “description” for the events? I know audit/block are each one of two values next to each other, but do they audit/block a specific file type only? Script? Exe?
-3076 Audit for exe/dll generated by CI in the createprocess stack
-3077 enforced version
-3089 Signing information event correlated with either a 3076/3077 event, contains # of signatures and an index as to which signature it is, one 3089 is generated for each signature of a file (so many 3089 map to one 3076/77). Unsigned files will generate a single 3089 with TotalSignatureCount 0
-8028 Audit for scripts/msis generated by WLDP being called by the scripthosts themselves (scripthosts opt in to enforcement, so we don’t enforce on 3rd party scripthosts like python/ruby)
-8029 Enforce for scripts
+**Q:** Can you also provide the “description” for the events?
+
+I know audit/block are each one of two values next to each other, but do they audit/block a specific file type only? Script? Exe?
+
+|-------|--------------------------|
+|Event ID| Description |
+|3076 |Audit for exe/dll generated by CI in the createprocess stack|
+|3077 |Enforced version |
+|3089 |Signing information event correlated with either a 3076/3077 event, contains # of signatures and an index as to which signature it is, one 3089 is generated for each signature of a file (so many 3089 map to one 3076/77). Unsigned files will generate a single 3089 with TotalSignatureCount 0 |
+|8028 |Audit for scripts/msis generated by WLDP being called by the scripthosts themselves (scripthosts opt in to enforcement, so we don’t enforce on 3rd party scripthosts like python/ruby)|
+|8029 |Enforce for scripts|
+
We don’t currently have signer information in the script events
-• I don’t understand what the “Policy” fields are.
-Code Integrity Policy is at its core an enterprise whitelisting solution. For these events to be generated, customers would have had to generate a policy xml, compile it, and deploy it. PolicyName/PolicyID fields are optional fields customers can add to the policy to get propagated into the events, policy hash is literally the hash of the policy (and policy hash matching guarantees that two events were blocked by the same policy). Since you can have multiple concurrent policies on one system supplementing each other, knowing what policy actually blocked the binary from running is useful
+**Q:** I don’t understand what the “Policy” fields are.
+
+**A:** Code Integrity Policy is at its core an enterprise whitelisting solution. For these events to be generated, customers would have had to generate a policy xml, compile it, and deploy it. PolicyName/PolicyID fields are optional fields customers can add to the policy to get propagated into the events, policy hash is literally the hash of the policy (and policy hash matching guarantees that two events were blocked by the same policy). Since you can have multiple concurrent policies on one system supplementing each other, knowing what policy actually blocked the binary from running is useful
-• Is this purely file based or do I need to worry about the “PackageName” grouping?
-o Eg… do I need the packagename to get back to a publisher or are individual files from the package all mapped up directly?
-An event is generated for each individual binary that failed policy. The PackageFamilyName is put in the process token of all binaries loading under an appx and is can be used in rules in policy to attempt to allow an entire package to run rather than whitelisting each individual binary, but we will still generate an individual event for each binary that fails
-I can’t currently remember if the PackageFamilyName field is even calculated or just zeroed out if there aren’t PFN rules in a policy
+**Q:** Is this purely file based or do I need to worry about the “PackageName” grouping? For example, do I need the packagename to get back to a publisher or are individual files from the package all mapped up directly?
+
+**A:** An event is generated for each individual binary that failed policy. The PackageFamilyName is put in the process token of all binaries loading under an appx and is can be used in rules in policy to attempt to allow an entire package to run rather than whitelisting each individual binary, but we will still generate an individual event for each binary that fails.
+
-• What field in 3089 am I able to join on to map from File to Publisher?
-CorrelationID is actually not in the event templates I sent you and is actually an optional field in the metadata of every eventviewer event. In the XML of the event the correlationID’s path is:
+**Q:** What field in 3089 am I able to join on to map from File to Publisher?
+
+**A:** CorrelationID is actually not in the event templates I sent you and is actually an optional field in the metadata of every eventviewer event. In the XML of the event the correlationID’s path is:
+
+```xml
+```
For comparison, the rest of the fields look like:
+```xml
valuevalue2…
+```
+
-• 3076/77 don’t seem to include ‘File Path’. Can this be deduced from ‘File Name’?
-• 8028/8029 don’t seem to include ‘File Name’. Can this be deduced from ‘File Path’?
-“File Name” in 3076/77 is actually the path in NT form (\Device\HarddiskVolume3\Windows\System32\myfile.dll), and the “originalfilename” field maps to what would be “File Name” in a file rule in policy XML
-For 8028/8029 File Path is the C:\ path to the file and you’ll notice a trend where we didn’t bother to include all the same fields we do for the PE files so there is no “originalFileName”
+**Q:** 3076/77 don’t seem to include ‘File Path’. Can this be deduced from ‘File Name’? 8028/8029 don’t seem to include ‘File Name’. Can this be deduced from ‘File Path’?
+
+**A:** “File Name” in 3076/77 is actually the path in NT form (\Device\HarddiskVolume3\Windows\System32\myfile.dll), and the “originalfilename” field maps to what would be “File Name” in a file rule in policy XML.
+For 8028/8029, File Path is the C:\ path to the file and you’ll notice a trend where we didn’t bother to include all the same fields we do for the PE files so there is no “originalFileName”.
From 2a7799ee70852037f9ca761a8bef08fb60b89db1 Mon Sep 17 00:00:00 2001
From: ManikaDhiman
Date: Tue, 7 May 2019 12:19:40 -0700
Subject: [PATCH 023/156] Added 19H1 policies
---
.../policy-configuration-service-provider.md | 60 +-
.../mdm/policy-csp-internetexplorer.md | 601 +++++++++++++++++-
2 files changed, 653 insertions(+), 8 deletions(-)
diff --git a/windows/client-management/mdm/policy-configuration-service-provider.md b/windows/client-management/mdm/policy-configuration-service-provider.md
index a27926a537..05d54e0bec 100644
--- a/windows/client-management/mdm/policy-configuration-service-provider.md
+++ b/windows/client-management/mdm/policy-configuration-service-provider.md
@@ -1323,6 +1323,9 @@ The following diagram shows the Policy configuration service provider in tree fo
InternetExplorer/AllowEnhancedProtectedMode
+
+ InternetExplorer/AllowEnhancedSuggestionsInAddressBar
+
@@ -1389,6 +1392,9 @@ The following diagram shows the Policy configuration service provider in tree fo
InternetExplorer/ConsistentMimeHandlingInternetExplorerProcesses
+
+ InternetExplorer/DisableActiveXVersionListAutoDownload
+
InternetExplorer/DisableAdobeFlash
@@ -1398,6 +1404,9 @@ The following diagram shows the Policy configuration service provider in tree fo
InternetExplorer/DisableBypassOfSmartScreenWarningsAboutUncommonFiles
+
+ InternetExplorer/DisableCompatView
+
InternetExplorer/DisableConfiguringHistory
@@ -1416,12 +1425,18 @@ The following diagram shows the Policy configuration service provider in tree fo
InternetExplorer/DisableEncryptionSupport
+
+ InternetExplorer/DisableFeedsBackgroundSync
+
InternetExplorer/DisableFirstRunWizard
InternetExplorer/DisableFlipAheadFeature
+
+ InternetExplorer/DisableGeolocation
+
InternetExplorer/DisableHomePageChange
@@ -1449,6 +1464,9 @@ The following diagram shows the Policy configuration service provider in tree fo
InternetExplorer/DisableUpdateCheck
+
+ InternetExplorer/DisableWebAddressAutoComplete
+
InternetExplorer/DoNotAllowActiveXControlsInProtectedMode
@@ -1842,6 +1860,9 @@ The following diagram shows the Policy configuration service provider in tree fo
InternetExplorer/MimeSniffingSafetyFeatureInternetExplorerProcesses
+
+ InternetExplorer/NewTabDefaultPage
+
InternetExplorer/NotificationBarInternetExplorerProcesses
@@ -3812,6 +3833,7 @@ The following diagram shows the Policy configuration service provider in tree fo
- [InternetExplorer/AllowCertificateAddressMismatchWarning](./policy-csp-internetexplorer.md#internetexplorer-allowcertificateaddressmismatchwarning)
- [InternetExplorer/AllowDeletingBrowsingHistoryOnExit](./policy-csp-internetexplorer.md#internetexplorer-allowdeletingbrowsinghistoryonexit)
- [InternetExplorer/AllowEnhancedProtectedMode](./policy-csp-internetexplorer.md#internetexplorer-allowenhancedprotectedmode)
+- [InternetExplorer/AllowEnhancedSuggestionsInAddressBar](./policy-csp-internetexplorer.md#internetexplorer-allowenhancedsuggestionsinaddressbar)
- [InternetExplorer/AllowEnterpriseModeFromToolsMenu](./policy-csp-internetexplorer.md#internetexplorer-allowenterprisemodefromtoolsmenu)
- [InternetExplorer/AllowEnterpriseModeSiteList](./policy-csp-internetexplorer.md#internetexplorer-allowenterprisemodesitelist)
- [InternetExplorer/AllowFallbackToSSL3](./policy-csp-internetexplorer.md#internetexplorer-allowfallbacktossl3)
@@ -3834,17 +3856,21 @@ The following diagram shows the Policy configuration service provider in tree fo
- [InternetExplorer/CheckServerCertificateRevocation](./policy-csp-internetexplorer.md#internetexplorer-checkservercertificaterevocation)
- [InternetExplorer/CheckSignaturesOnDownloadedPrograms](./policy-csp-internetexplorer.md#internetexplorer-checksignaturesondownloadedprograms)
- [InternetExplorer/ConsistentMimeHandlingInternetExplorerProcesses](./policy-csp-internetexplorer.md#internetexplorer-consistentmimehandlinginternetexplorerprocesses)
+- [InternetExplorer/DisableActiveXVersionListAutoDownload](./policy-csp-internetexplorer.md#internetexplorer-disableactivexversionlistautodownload)
- [InternetExplorer/DisableAdobeFlash](./policy-csp-internetexplorer.md#internetexplorer-disableadobeflash)
- [InternetExplorer/DisableBypassOfSmartScreenWarnings](./policy-csp-internetexplorer.md#internetexplorer-disablebypassofsmartscreenwarnings)
- [InternetExplorer/DisableBypassOfSmartScreenWarningsAboutUncommonFiles](./policy-csp-internetexplorer.md#internetexplorer-disablebypassofsmartscreenwarningsaboutuncommonfiles)
+- [InternetExplorer/DisableCompatView](./policy-csp-internetexplorer.md#internetexplorer-disablecompatview)
- [InternetExplorer/DisableConfiguringHistory](./policy-csp-internetexplorer.md#internetexplorer-disableconfiguringhistory)
- [InternetExplorer/DisableCrashDetection](./policy-csp-internetexplorer.md#internetexplorer-disablecrashdetection)
- [InternetExplorer/DisableCustomerExperienceImprovementProgramParticipation](./policy-csp-internetexplorer.md#internetexplorer-disablecustomerexperienceimprovementprogramparticipation)
- [InternetExplorer/DisableDeletingUserVisitedWebsites](./policy-csp-internetexplorer.md#internetexplorer-disabledeletinguservisitedwebsites)
- [InternetExplorer/DisableEnclosureDownloading](./policy-csp-internetexplorer.md#internetexplorer-disableenclosuredownloading)
- [InternetExplorer/DisableEncryptionSupport](./policy-csp-internetexplorer.md#internetexplorer-disableencryptionsupport)
+- [InternetExplorer/DisableFeedsBackgroundSync](./policy-csp-internetexplorer.md#internetexplorer-disablefeedsbackgroundsync)
- [InternetExplorer/DisableFirstRunWizard](./policy-csp-internetexplorer.md#internetexplorer-disablefirstrunwizard)
- [InternetExplorer/DisableFlipAheadFeature](./policy-csp-internetexplorer.md#internetexplorer-disableflipaheadfeature)
+- [InternetExplorer/DisableGeolocation](./policy-csp-internetexplorer.md#internetexplorer-disablegeolocation)
- [InternetExplorer/DisableHomePageChange](./policy-csp-internetexplorer.md#internetexplorer-disablehomepagechange)
- [InternetExplorer/DisableIgnoringCertificateErrors](./policy-csp-internetexplorer.md#internetexplorer-disableignoringcertificateerrors)
- [InternetExplorer/DisableInPrivateBrowsing](./policy-csp-internetexplorer.md#internetexplorer-disableinprivatebrowsing)
@@ -3854,6 +3880,7 @@ The following diagram shows the Policy configuration service provider in tree fo
- [InternetExplorer/DisableSecondaryHomePageChange](./policy-csp-internetexplorer.md#internetexplorer-disablesecondaryhomepagechange)
- [InternetExplorer/DisableSecuritySettingsCheck](./policy-csp-internetexplorer.md#internetexplorer-disablesecuritysettingscheck)
- [InternetExplorer/DisableUpdateCheck](./policy-csp-internetexplorer.md#internetexplorer-disableupdatecheck)
+- [InternetExplorer/DisableWebAddressAutoComplete](./policy-csp-internetexplorer.md#internetexplorer-disablewebaddressautocomplete)
- [InternetExplorer/DoNotAllowActiveXControlsInProtectedMode](./policy-csp-internetexplorer.md#internetexplorer-donotallowactivexcontrolsinprotectedmode)
- [InternetExplorer/DoNotAllowUsersToAddSites](./policy-csp-internetexplorer.md#internetexplorer-donotallowuserstoaddsites)
- [InternetExplorer/DoNotAllowUsersToChangePolicies](./policy-csp-internetexplorer.md#internetexplorer-donotallowuserstochangepolicies)
@@ -3984,6 +4011,7 @@ The following diagram shows the Policy configuration service provider in tree fo
- [InternetExplorer/LockedDownTrustedSitesZoneNavigateWindowsAndFrames](./policy-csp-internetexplorer.md#internetexplorer-lockeddowntrustedsiteszonenavigatewindowsandframes)
- [InternetExplorer/MKProtocolSecurityRestrictionInternetExplorerProcesses](./policy-csp-internetexplorer.md#internetexplorer-mkprotocolsecurityrestrictioninternetexplorerprocesses)
- [InternetExplorer/MimeSniffingSafetyFeatureInternetExplorerProcesses](./policy-csp-internetexplorer.md#internetexplorer-mimesniffingsafetyfeatureinternetexplorerprocesses)
+- [InternetExplorer/NewTabDefaultPage](./policy-csp-internetexplorer.md#internetexplorer-newtabdefaultpage)
- [InternetExplorer/NotificationBarInternetExplorerProcesses](./policy-csp-internetexplorer.md#internetexplorer-notificationbarinternetexplorerprocesses)
- [InternetExplorer/PreventManagingSmartScreenFilter](./policy-csp-internetexplorer.md#internetexplorer-preventmanagingsmartscreenfilter)
- [InternetExplorer/PreventPerUserInstallationOfActiveXControls](./policy-csp-internetexplorer.md#internetexplorer-preventperuserinstallationofactivexcontrols)
@@ -4373,6 +4401,7 @@ The following diagram shows the Policy configuration service provider in tree fo
- [InternetExplorer/AllowCertificateAddressMismatchWarning](./policy-csp-internetexplorer.md#internetexplorer-allowcertificateaddressmismatchwarning)
- [InternetExplorer/AllowDeletingBrowsingHistoryOnExit](./policy-csp-internetexplorer.md#internetexplorer-allowdeletingbrowsinghistoryonexit)
- [InternetExplorer/AllowEnhancedProtectedMode](./policy-csp-internetexplorer.md#internetexplorer-allowenhancedprotectedmode)
+- [InternetExplorer/AllowEnhancedSuggestionsInAddressBar](./policy-csp-internetexplorer.md#internetexplorer-allowenhancedsuggestionsinaddressbar)
- [InternetExplorer/AllowEnterpriseModeFromToolsMenu](./policy-csp-internetexplorer.md#internetexplorer-allowenterprisemodefromtoolsmenu)
- [InternetExplorer/AllowEnterpriseModeSiteList](./policy-csp-internetexplorer.md#internetexplorer-allowenterprisemodesitelist)
- [InternetExplorer/AllowFallbackToSSL3](./policy-csp-internetexplorer.md#internetexplorer-allowfallbacktossl3)
@@ -4395,17 +4424,21 @@ The following diagram shows the Policy configuration service provider in tree fo
- [InternetExplorer/CheckServerCertificateRevocation](./policy-csp-internetexplorer.md#internetexplorer-checkservercertificaterevocation)
- [InternetExplorer/CheckSignaturesOnDownloadedPrograms](./policy-csp-internetexplorer.md#internetexplorer-checksignaturesondownloadedprograms)
- [InternetExplorer/ConsistentMimeHandlingInternetExplorerProcesses](./policy-csp-internetexplorer.md#internetexplorer-consistentmimehandlinginternetexplorerprocesses)
+- [InternetExplorer/DisableActiveXVersionListAutoDownload](./policy-csp-internetexplorer.md#internetexplorer-disableactivexversionlistautodownload)
- [InternetExplorer/DisableAdobeFlash](./policy-csp-internetexplorer.md#internetexplorer-disableadobeflash)
- [InternetExplorer/DisableBypassOfSmartScreenWarnings](./policy-csp-internetexplorer.md#internetexplorer-disablebypassofsmartscreenwarnings)
- [InternetExplorer/DisableBypassOfSmartScreenWarningsAboutUncommonFiles](./policy-csp-internetexplorer.md#internetexplorer-disablebypassofsmartscreenwarningsaboutuncommonfiles)
+- [InternetExplorer/DisableCompatView](./policy-csp-internetexplorer.md#internetexplorer-disablecompatview)
- [InternetExplorer/DisableConfiguringHistory](./policy-csp-internetexplorer.md#internetexplorer-disableconfiguringhistory)
- [InternetExplorer/DisableCrashDetection](./policy-csp-internetexplorer.md#internetexplorer-disablecrashdetection)
- [InternetExplorer/DisableCustomerExperienceImprovementProgramParticipation](./policy-csp-internetexplorer.md#internetexplorer-disablecustomerexperienceimprovementprogramparticipation)
- [InternetExplorer/DisableDeletingUserVisitedWebsites](./policy-csp-internetexplorer.md#internetexplorer-disabledeletinguservisitedwebsites)
- [InternetExplorer/DisableEnclosureDownloading](./policy-csp-internetexplorer.md#internetexplorer-disableenclosuredownloading)
- [InternetExplorer/DisableEncryptionSupport](./policy-csp-internetexplorer.md#internetexplorer-disableencryptionsupport)
+- [InternetExplorer/DisableFeedsBackgroundSync](./policy-csp-internetexplorer.md#internetexplorer-disablefeedsbackgroundsync)
- [InternetExplorer/DisableFirstRunWizard](./policy-csp-internetexplorer.md#internetexplorer-disablefirstrunwizard)
- [InternetExplorer/DisableFlipAheadFeature](./policy-csp-internetexplorer.md#internetexplorer-disableflipaheadfeature)
+- [InternetExplorer/DisableGeolocation](./policy-csp-internetexplorer.md#internetexplorer-disablegeolocation)
- [InternetExplorer/DisableHomePageChange](./policy-csp-internetexplorer.md#internetexplorer-disablehomepagechange)
- [InternetExplorer/DisableIgnoringCertificateErrors](./policy-csp-internetexplorer.md#internetexplorer-disableignoringcertificateerrors)
- [InternetExplorer/DisableInPrivateBrowsing](./policy-csp-internetexplorer.md#internetexplorer-disableinprivatebrowsing)
@@ -4415,6 +4448,7 @@ The following diagram shows the Policy configuration service provider in tree fo
- [InternetExplorer/DisableSecondaryHomePageChange](./policy-csp-internetexplorer.md#internetexplorer-disablesecondaryhomepagechange)
- [InternetExplorer/DisableSecuritySettingsCheck](./policy-csp-internetexplorer.md#internetexplorer-disablesecuritysettingscheck)
- [InternetExplorer/DisableUpdateCheck](./policy-csp-internetexplorer.md#internetexplorer-disableupdatecheck)
+- [InternetExplorer/DisableWebAddressAutoComplete](./policy-csp-internetexplorer.md#internetexplorer-disablewebaddressautocomplete)
- [InternetExplorer/DoNotAllowActiveXControlsInProtectedMode](./policy-csp-internetexplorer.md#internetexplorer-donotallowactivexcontrolsinprotectedmode)
- [InternetExplorer/DoNotAllowUsersToAddSites](./policy-csp-internetexplorer.md#internetexplorer-donotallowuserstoaddsites)
- [InternetExplorer/DoNotAllowUsersToChangePolicies](./policy-csp-internetexplorer.md#internetexplorer-donotallowuserstochangepolicies)
@@ -4545,6 +4579,7 @@ The following diagram shows the Policy configuration service provider in tree fo
- [InternetExplorer/LockedDownTrustedSitesZoneNavigateWindowsAndFrames](./policy-csp-internetexplorer.md#internetexplorer-lockeddowntrustedsiteszonenavigatewindowsandframes)
- [InternetExplorer/MKProtocolSecurityRestrictionInternetExplorerProcesses](./policy-csp-internetexplorer.md#internetexplorer-mkprotocolsecurityrestrictioninternetexplorerprocesses)
- [InternetExplorer/MimeSniffingSafetyFeatureInternetExplorerProcesses](./policy-csp-internetexplorer.md#internetexplorer-mimesniffingsafetyfeatureinternetexplorerprocesses)
+- [InternetExplorer/NewTabDefaultPage](./policy-csp-internetexplorer.md#internetexplorer-newtabdefaultpage)
- [InternetExplorer/NotificationBarInternetExplorerProcesses](./policy-csp-internetexplorer.md#internetexplorer-notificationbarinternetexplorerprocesses)
- [InternetExplorer/PreventManagingSmartScreenFilter](./policy-csp-internetexplorer.md#internetexplorer-preventmanagingsmartscreenfilter)
- [InternetExplorer/PreventPerUserInstallationOfActiveXControls](./policy-csp-internetexplorer.md#internetexplorer-preventperuserinstallationofactivexcontrols)
@@ -4989,7 +5024,7 @@ The following diagram shows the Policy configuration service provider in tree fo
- [Accounts/AllowMicrosoftAccountConnection](#accounts-allowmicrosoftaccountconnection)
- [ApplicationManagement/AllowAllTrustedApps](#applicationmanagement-allowalltrustedapps)
-- [ApplicationManagement/AllowAppStoreAutoUpdate](#applicationmanagement-allowappstoreautoupdate)
+- [ApplicationManagement/AllowAppStoreAutoUpdate](#applicationmanagement-allowappstoreautoupdate)
- [ApplicationManagement/AllowDeveloperUnlock](#applicationmanagement-allowdeveloperunlock)
- [Authentication/AllowFastReconnect](#authentication-allowfastreconnect)
- [Authentication/PreferredAadTenantDomainName](#authentication-preferredaadtenantdomainname)
@@ -5014,7 +5049,10 @@ The following diagram shows the Policy configuration service provider in tree fo
- [DeviceLock/MaxInactivityTimeDeviceLock](#devicelock-maxinactivitytimedevicelock)
- [DeviceLock/MinDevicePasswordComplexCharacters](#devicelock-mindevicepasswordcomplexcharacters)
- [DeviceLock/MinDevicePasswordLength](#devicelock-mindevicepasswordlength)
-- [Experience/AllowCortana](#experience-allowcortana)
+- [Experience/AllowCortana](#experience-allowcortana)
+- [InternetExplorer/DisableActiveXVersionListAutoDownload](#internetexplorer-disableactivexversionlistautodownload)
+- [InternetExplorer/DisableCompatView](#internetexplorer-disablecompatview)
+- [InternetExplorer/DisableGeolocation](#internetexplorer-disablegeolocation)
- [Privacy/AllowInputPersonalization](#privacy-allowinputpersonalization)
- [Search/AllowSearchToUseLocation](#search-allowsearchtouselocation)
- [Security/RequireDeviceEncryption](#security-requiredeviceencryption)
@@ -5062,6 +5100,9 @@ The following diagram shows the Policy configuration service provider in tree fo
- [DeviceLock/AllowIdleReturnWithoutPassword](#devicelock-allowidlereturnwithoutpassword)
- [DeviceLock/DevicePasswordEnabled](#devicelock-devicepasswordenabled)
- [Experience/AllowCortana](#experience-allowcortana)
+- [InternetExplorer/DisableActiveXVersionListAutoDownload](#internetexplorer-disableactivexversionlistautodownload)
+- [InternetExplorer/DisableCompatView](#internetexplorer-disablecompatview)
+- [InternetExplorer/DisableGeolocation](#internetexplorer-disablegeolocation)
- [Privacy/AllowInputPersonalization](#privacy-allowinputpersonalization)
- [Search/AllowSearchToUseLocation](#search-allowsearchtouselocation)
- [Security/RequireDeviceEncryption](#security-requiredeviceencryption)
@@ -5152,12 +5193,27 @@ The following diagram shows the Policy configuration service provider in tree fo
- [CredentialProviders/AllowPINLogon](#credentialproviders-allowpinlogon)
- [CredentialProviders/BlockPicturePassword](#credentialproviders-blockpicturepassword)
- [DataProtection/AllowDirectMemoryAccess](#dataprotection-allowdirectmemoryaccess)
+- [InternetExplorer/DisableActiveXVersionListAutoDownload](#internetexplorer-disableactivexversionlistautodownload)
+- [InternetExplorer/DisableCompatView](#internetexplorer-disablecompatview)
+- [InternetExplorer/DisableGeolocation](#internetexplorer-disablegeolocation)
- [Wifi/AllowAutoConnectToWiFiSenseHotspots](#wifi-allowautoconnecttowifisensehotspots)
- [Wifi/AllowInternetSharing](#wifi-allowinternetsharing)
- [Wifi/AllowWiFi](#wifi-allowwifi)
- [Wifi/WLANScanMode](#wifi-wlanscanmode)
+
+## Policies supported by Windows 10 IoT Enterprise
+
+- [InternetExplorer/AllowEnhancedSuggestionsInAddressBar](#internetexplorer-allowenhancedsuggestionsinaddressbar)
+- [InternetExplorer/DisableActiveXVersionListAutoDownload](#internetexplorer-disableactivexversionlistautodownload)
+- [InternetExplorer/DisableCompatView](#internetexplorer-disablecompatview)
+- [InternetExplorer/DisableFeedsBackgroundSync](#internetexplorer-disablefeedsbackgroundsync)
+- [InternetExplorer/DisableGeolocation](#internetexplorer-disablegeolocation)
+- [InternetExplorer/DisableWebAddressAutoComplete](#internetexplorer-disablewebaddressautocomplete)
+- [InternetExplorer/NewTabDefaultPage](#internetexplorer-newtabdefaultpage)
+
+
## Policies that can be set using Exchange Active Sync (EAS)
diff --git a/windows/client-management/mdm/policy-csp-internetexplorer.md b/windows/client-management/mdm/policy-csp-internetexplorer.md
index 823af29f0b..28f3b3a7da 100644
--- a/windows/client-management/mdm/policy-csp-internetexplorer.md
+++ b/windows/client-management/mdm/policy-csp-internetexplorer.md
@@ -6,12 +6,13 @@ ms.topic: article
ms.prod: w10
ms.technology: windows
author: MariciaAlforque
-ms.date: 05/14/2018
+ms.date: 05/06/2019
---
# Policy CSP - InternetExplorer
-
+> [!WARNING]
+> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
@@ -40,6 +41,9 @@ ms.date: 05/14/2018
InternetExplorer/AllowEnhancedProtectedMode
+
+ InternetExplorer/AllowEnhancedSuggestionsInAddressBar
+
InternetExplorer/AllowEnterpriseModeFromToolsMenu
@@ -106,6 +110,9 @@ ms.date: 05/14/2018
InternetExplorer/ConsistentMimeHandlingInternetExplorerProcesses
+
+ InternetExplorer/DisableActiveXVersionListAutoDownload
+
InternetExplorer/DisableAdobeFlash
@@ -115,6 +122,9 @@ ms.date: 05/14/2018
InternetExplorer/DisableBypassOfSmartScreenWarningsAboutUncommonFiles
+
+ InternetExplorer/DisableCompatView
+
InternetExplorer/DisableConfiguringHistory
@@ -133,12 +143,18 @@ ms.date: 05/14/2018
InternetExplorer/DisableEncryptionSupport
+
+ InternetExplorer/DisableFeedsBackgroundSync
+
InternetExplorer/DisableFirstRunWizard
InternetExplorer/DisableFlipAheadFeature
+
+ InternetExplorer/DisableGeolocation
+
InternetExplorer/DisableHomePageChange
@@ -166,6 +182,9 @@ ms.date: 05/14/2018
InternetExplorer/DisableUpdateCheck
+
+ InternetExplorer/DisableWebAddressAutoComplete
+
InternetExplorer/DoNotAllowActiveXControlsInProtectedMode
@@ -559,6 +578,9 @@ ms.date: 05/14/2018
InternetExplorer/MimeSniffingSafetyFeatureInternetExplorerProcesses
+
+ InternetExplorer/NewTabDefaultPage
+
InternetExplorer/NotificationBarInternetExplorerProcesses
@@ -1216,6 +1238,82 @@ ADMX Info:
+
+**InternetExplorer/AllowEnhancedSuggestionsInAddressBar**
+
+
+
+
+ Home |
+ Pro |
+ Business |
+ Enterprise |
+ Education |
+ Mobile |
+ Mobile Enterprise |
+
+
+  |
+ 6 |
+ 6 |
+ 6 |
+ 6 |
+ |
+ |
+
+
+
+
+
+[Scope](./policy-configuration-service-provider.md#policy-scope):
+
+> [!div class = "checklist"]
+> * User
+> * Device
+
+
+
+
+
+This policy setting allows Internet Explorer to provide enhanced suggestions as the user types in the Address bar. To provide enhanced suggestions, the user's keystrokes are sent to Microsoft through Microsoft services.
+
+If you enable this policy setting, users receive enhanced suggestions while typing in the Address bar. In addition, users cannot change the Suggestions setting on the Settings charm.
+
+If you disable this policy setting, users do not receive enhanced suggestions while typing in the Address bar. In addition, users cannot change the Suggestions setting on the Settings charm.
+
+If you do not configure this policy setting, users can change the Suggestions setting on the Settings charm.
+
+
+> [!TIP]
+> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
+
+> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
+
+> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
+
+
+ADMX Info:
+- GP English name: *Allow Microsoft services to provide enhanced suggestions as the user types in the Address bar*
+- GP name: *AllowServicePoweredQSA*
+- GP path: *Windows Components/Internet Explorer*
+- GP ADMX file name: *inetres.admx*
+
+
+
+Supported values:
+- 0 - Disabled
+- 1 - Enabled (Default)
+
+
+
+
+
+
+
+
+
+
+
**InternetExplorer/AllowEnterpriseModeFromToolsMenu**
@@ -2713,6 +2811,81 @@ ADMX Info:
+
+**InternetExplorer/DisableActiveXVersionListAutoDownload**
+
+
+
+
+ Home |
+ Pro |
+ Business |
+ Enterprise |
+ Education |
+ Mobile |
+ Mobile Enterprise |
+
+
+  |
+ 6 |
+ 6 |
+ 6 |
+ 6 |
+ |
+ |
+
+
+
+
+
+[Scope](./policy-configuration-service-provider.md#policy-scope):
+
+> [!div class = "checklist"]
+> * User
+> * Device
+
+
+
+
+
+This setting determines whether IE automatically downloads updated versions of Microsoft’s VersionList.XML. IE uses this file to determine whether an ActiveX control should be stopped from loading.
+
+> [!Caution]
+> If you enable this setting, IE stops downloading updated versions of VersionList.XML. Turning off this automatic download breaks the [out-of-date ActiveX control blocking feature](https://docs.microsoft.com/en-us/internet-explorer/ie11-deploy-guide/out-of-date-activex-control-blocking) by not letting the version list update with newly outdated controls, potentially compromising the security of your computer.
+
+If you disable or do not configure this setting, IE continues to download updated versions of VersionList.XML.
+
+
+> [!TIP]
+> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
+
+> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
+
+> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
+
+
+ADMX Info:
+- GP English name: *Turn off automatic download of the ActiveX VersionList*
+- GP name: *VersionListAutomaticDownloadDisable*
+- GP path: *Windows Components/Internet Explorer/Security Features/Add-on Management*
+- GP ADMX file name: *inetres.admx*
+
+
+
+Supported values:
+- 0 - Enabled
+- 1 - Disabled (Default)
+
+
+
+
+
+
+
+
+
+
+
**InternetExplorer/DisableAdobeFlash**
@@ -2904,6 +3077,80 @@ ADMX Info:
+
+**InternetExplorer/DisableCompatView**
+
+
+
+
+ Home |
+ Pro |
+ Business |
+ Enterprise |
+ Education |
+ Mobile |
+ Mobile Enterprise |
+
+
+  |
+ 6 |
+ 6 |
+ 6 |
+ 6 |
+ |
+ |
+
+
+
+
+
+[Scope](./policy-configuration-service-provider.md#policy-scope):
+
+> [!div class = "checklist"]
+> * User
+> * Device
+
+
+
+
+
+This policy setting controls the Compatibility View feature, which allows users to fix website display problems that they may encounter while browsing.
+
+If you enable this policy setting, the user cannot use the Compatibility View button or manage the Compatibility View sites list.
+
+If you disable or do not configure this policy setting, the user can use the Compatibility View button and manage the Compatibility View sites list.
+
+
+> [!TIP]
+> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
+
+> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
+
+> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
+
+
+ADMX Info:
+- GP English name: *Turn off Compatibility View*
+- GP name: *CompatView_DisableList*
+- GP path: *Windows Components/Internet Explorer/Compatibility View*
+- GP ADMX file name: *inetres.admx*
+
+
+
+Supported values:
+- 0 - Disabled (Default)
+- 1 - Enabled
+
+
+
+
+
+
+
+
+
+
+
**InternetExplorer/DisableConfiguringHistory**
@@ -3290,6 +3537,80 @@ ADMX Info:
+
+**InternetExplorer/DisableFeedsBackgroundSync**
+
+
+
+
+ Home |
+ Pro |
+ Business |
+ Enterprise |
+ Education |
+ Mobile |
+ Mobile Enterprise |
+
+
+  |
+ 6 |
+ 6 |
+ 6 |
+ 6 |
+ |
+ |
+
+
+
+
+
+[Scope](./policy-configuration-service-provider.md#policy-scope):
+
+> [!div class = "checklist"]
+> * User
+> * Device
+
+
+
+
+
+This policy setting allows you to choose whether or not to have background synchronization for feeds and Web Slices.
+
+If you enable this policy setting, the ability to synchronize feeds and Web Slices in the background is turned off.
+
+If you disable or do not configure this policy setting, the user can synchronize feeds and Web Slices in the background.
+
+
+> [!TIP]
+> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
+
+> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
+
+> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
+
+
+ADMX Info:
+- GP English name: *Turn off background synchronization for feeds and Web Slices*
+- GP name: *Disable_Background_Syncing*
+- GP path: *Windows Components/RSS Feeds*
+- GP ADMX file name: *inetres.admx*
+
+
+
+Supported values:
+- 0 - Enabled (Default)
+- 1 - Disabled
+
+
+
+
+
+
+
+
+
+
+
**InternetExplorer/DisableFirstRunWizard**
@@ -3424,6 +3745,82 @@ ADMX Info:
+
+**InternetExplorer/DisableGeolocation**
+
+
+
+
+ Home |
+ Pro |
+ Business |
+ Enterprise |
+ Education |
+ Mobile |
+ Mobile Enterprise |
+
+
+  |
+ 6 |
+ 6 |
+ 6 |
+ 6 |
+ |
+ |
+
+
+
+
+
+[Scope](./policy-configuration-service-provider.md#policy-scope):
+
+> [!div class = "checklist"]
+> * User
+> * Device
+
+
+
+
+
+This policy setting allows you to disable browser geolocation support. This prevents websites from requesting location data about the user.
+
+If you enable this policy setting, browser geolocation support is turned off.
+
+If you disable this policy setting, browser geolocation support is turned on.
+
+If you do not configure this policy setting, browser geolocation support can be turned on or off in Internet Options on the Privacy tab.
+
+
+> [!TIP]
+> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
+
+> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
+
+> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
+
+
+ADMX Info:
+- GP English name: *Turn off browser geolocation*
+- GP name: *GeolocationDisable*
+- GP path: *Windows Components/Internet Explorer*
+- GP ADMX file name: *inetres.admx*
+
+
+
+Supported values:
+- 0 - Disabled (Default)
+- 1 - Enabled
+
+
+
+
+
+
+
+
+
+
+
**InternetExplorer/DisableHomePageChange**
@@ -4001,6 +4398,82 @@ ADMX Info:
+
+**InternetExplorer/DisableWebAddressAutoComplete**
+
+
+
+
+ Home |
+ Pro |
+ Business |
+ Enterprise |
+ Education |
+ Mobile |
+ Mobile Enterprise |
+
+
+  |
+ 6 |
+ 6 |
+ 6 |
+ 6 |
+ |
+ |
+
+
+
+
+
+[Scope](./policy-configuration-service-provider.md#policy-scope):
+
+> [!div class = "checklist"]
+> * User
+> * Device
+
+
+
+
+
+This AutoComplete feature suggests possible matches when users are entering Web addresses in the browser address bar.
+
+If you enable this policy setting, users are not suggested matches when entering Web addresses. The user cannot change the auto-complete for web-address setting.
+
+If you disable this policy setting, users are suggested matches when entering Web addresses. The user cannot change the auto-complete for web-address setting.
+
+If you do not configure this policy setting, users can choose to turn the auto-complete setting for web-addresses on or off.
+
+
+> [!TIP]
+> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
+
+> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
+
+> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
+
+
+ADMX Info:
+- GP English name: *Turn off the auto-complete feature for web addresses*
+- GP name: *RestrictWebAddressSuggest*
+- GP path: *Windows Components/Internet Explorer*
+- GP ADMX file name: *inetres.admx*
+
+
+
+Supported values:
+- yes - Disabled (Default)
+- no - Enabled
+
+
+
+
+
+
+
+
+
+
+
**InternetExplorer/DoNotAllowActiveXControlsInProtectedMode**
@@ -12568,6 +13041,83 @@ ADMX Info:
+
+**InternetExplorer/NewTabDefaultPage**
+
+
+
+
+ Home |
+ Pro |
+ Business |
+ Enterprise |
+ Education |
+ Mobile |
+ Mobile Enterprise |
+
+
+  |
+ 6 |
+ 6 |
+ 6 |
+ 6 |
+ |
+ |
+
+
+
+
+
+[Scope](./policy-configuration-service-provider.md#policy-scope):
+
+> [!div class = "checklist"]
+> * User
+> * Device
+
+
+
+
+
+This policy setting allows you to specify what is displayed when the user opens a new tab.
+
+If you enable this policy setting, you can choose which page to display when the user opens a new tab: blank page (about:blank), the first home page, the new tab page or the new tab page with my news feed.
+
+If you disable or do not configure this policy setting, users can select their preference for this behavior.
+
+
+> [!TIP]
+> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
+
+> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
+
+> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
+
+
+ADMX Info:
+- GP English name: *Specify default behavior for a new tab*
+- GP name: *NewTabAction*
+- GP path: *Windows Components/Internet Explorer*
+- GP ADMX file name: *inetres.admx*
+
+
+
+
+Supported values:
+- 0 - NewTab_AboutBlank (about:blank)
+- 1 - NewTab_Homepage (Home page)
+- 2 - NewTab_AboutTabs (New tab page)
+- 3 - NewTab_AboutNewsFeed (New tab page with my news feed) (Default)
+
+
+
+
+
+
+
+
+
+
+
**InternetExplorer/NotificationBarInternetExplorerProcesses**
@@ -16878,14 +17428,53 @@ ADMX Info:
+
+
+
+
+## InternetExplorer policies supported by Windows Holographic
+
+- [InternetExplorer/DisableActiveXVersionListAutoDownload](#internetexplorer-disableactivexversionlistautodownload)
+- [InternetExplorer/DisableCompatView](#internetexplorer-disablecompatview)
+- [InternetExplorer/DisableGeolocation](#internetexplorer-disablegeolocation)
+
+
+
+## InternetExplorer policies supported by Windows Holographic for Business
+
+- [InternetExplorer/DisableActiveXVersionListAutoDownload](#internetexplorer-disableactivexversionlistautodownload)
+- [InternetExplorer/DisableCompatView](#internetexplorer-disablecompatview)
+- [InternetExplorer/DisableGeolocation](#internetexplorer-disablegeolocation)
+
+
+
+## InternetExplorer policies supported by IoT Core
+
+- [InternetExplorer/DisableActiveXVersionListAutoDownload](#internetexplorer-disableactivexversionlistautodownload)
+- [InternetExplorer/DisableCompatView](#internetexplorer-disablecompatview)
+- [InternetExplorer/DisableGeolocation](#internetexplorer-disablegeolocation)
+
+
+
+## InternetExplorer policies supported by IoT Enterprise
+
+- [InternetExplorer/AllowEnhancedSuggestionsInAddressBar](#internetexplorer-allowenhancedsuggestionsinaddressbar)
+- [InternetExplorer/DisableActiveXVersionListAutoDownload](#internetexplorer-disableactivexversionlistautodownload)
+- [InternetExplorer/DisableCompatView](#internetexplorer-disablecompatview)
+- [InternetExplorer/DisableFeedsBackgroundSync](#internetexplorer-disablefeedsbackgroundsync)
+- [InternetExplorer/DisableGeolocation](#internetexplorer-disablegeolocation)
+- [InternetExplorer/DisableWebAddressAutoComplete](#internetexplorer-disablewebaddressautocomplete)
+- [InternetExplorer/NewTabDefaultPage](#internetexplorer-newtabdefaultpage)
+
+
+
-Footnote:
+Footnotes:
- 1 - Added in Windows 10, version 1607.
- 2 - Added in Windows 10, version 1703.
- 3 - Added in Windows 10, version 1709.
- 4 - Added in Windows 10, version 1803.
-
-
-
+- 5 - Added in Windows 10, version 1809.
+- 6 - Added in Windows 10, version 1903.
\ No newline at end of file
From ba046cc060498140ddec69490a6c8a2020520465 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 11:57:29 -0700
Subject: [PATCH 024/156] Create
windows-endpoints-1903-non-enterprise-editions.md
---
...-endpoints-1903-non-enterprise-editions.md | 271 ++++++++++++++++++
1 file changed, 271 insertions(+)
create mode 100644 windows/privacy/windows-endpoints-1903-non-enterprise-editions.md
diff --git a/windows/privacy/windows-endpoints-1903-non-enterprise-editions.md b/windows/privacy/windows-endpoints-1903-non-enterprise-editions.md
new file mode 100644
index 0000000000..44fadd939e
--- /dev/null
+++ b/windows/privacy/windows-endpoints-1903-non-enterprise-editions.md
@@ -0,0 +1,271 @@
+---
+title: Windows 10, version 1809, connection endpoints for non-Enterprise editions
+description: Explains what Windows 10 endpoints are used in non-Enterprise editions.
+keywords: privacy, manage connections to Microsoft, Windows 10, Windows Server 2016
+ms.prod: w10
+ms.mktglfcycl: manage
+ms.sitesec: library
+ms.localizationpriority: high
+audience: ITPro
+author: danihalfin
+ms.author: daniha
+manager: dansimp
+ms.collection: M365-security-compliance
+ms.topic: article
+ms.date: 6/26/2018
+---
+# Windows 10, version 1809, connection endpoints for non-Enterprise editions
+
+ **Applies to**
+
+- Windows 10 Home, version 1809
+- Windows 10 Professional, version 1809
+- Windows 10 Education, version 1809
+
+In addition to the endpoints listed for [Windows 10 Enterprise](manage-windows-1809-endpoints.md), the following endpoints are available on other editions of Windows 10, version 1809.
+
+We used the following methodology to derive these network endpoints:
+
+1. Set up the latest version of Windows 10 on a test virtual machine using the default settings.
+2. Leave the devices running idle for a week (that is, a user is not interacting with the system/device).
+3. Use globally accepted network protocol analyzer/capturing tools and log all background egress traffic.
+4. Compile reports on traffic going to public IP addresses.
+5. The test virtual machine was logged in using a local account and was not joined to a domain or Azure Active Directory.
+6. All traffic was captured in our lab using a IPV4 network. Therefore no IPV6 traffic is reported here.
+
+> [!NOTE]
+> Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
+
+## Windows 10 Family
+
+| **Destination** | **Protocol** | **Description** |
+| --- | --- | --- |
+|\*.aria.microsoft.com*|HTTPS|Microsoft Office Telemetry
+|\*.b.akamai*.net|HTTPS|Used to check for updates to Maps that have been downloaded for offline use
+|\*.c-msedge.net|HTTP|Microsoft Office
+|\*.dl.delivery.mp.microsoft.com*|HTTP|Enables connections to Windows Update
+|\*.download.windowsupdate.com*|HTTP|Used to download operating system patches and updates
+|\*.g.akamai*.net|HTTPS|Used to check for updates to Maps that have been downloaded for offline use
+|\*.login.msa.*.net|HTTPS|Microsoft Account related
+|\*.msn.com*|TLSv1.2/HTTPS|Windows Spotlight
+|\*.skype.com|HTTP/HTTPS|Skype
+|\*.smartscreen.microsoft.com*|HTTPS|Windows Defender Smartscreen
+|\*.telecommand.telemetry.microsoft.com*|HTTPS|Used by Windows Error Reporting
+|*cdn.onenote.net*|HTTP|OneNote
+|*displaycatalog.*mp.microsoft.com*|HTTPS|Used to communicate with Microsoft Store
+|*emdl.ws.microsoft.com*|HTTP|Windows Update
+|*geo-prod.do.dsp.mp.microsoft.com*|TLSv1.2/HTTPS|Enables connections to Windows Update
+|*hwcdn.net*|HTTP|Highwinds Content Delivery Network / Windows updates
+|*img-prod-cms-rt-microsoft-com*|HTTPS|Microsoft Store or Inbox MSN Apps image download
+|*licensing.*mp.microsoft.com*|HTTPS|Licensing
+|*maps.windows.com*|HTTPS|Related to Maps application
+|*msedge.net*|HTTPS|Used by Microsoft OfficeHub to get the metadata of Microsoft Office apps
+|*nexusrules.officeapps.live.com*|HTTPS|Microsoft Office Telemetry
+|*photos.microsoft.com*|HTTPS|Photos App
+|*prod.do.dsp.mp.microsoft.com*|TLSv1.2/HTTPS|Used for Windows Update downloads of apps and OS updates
+|*purchase.md.mp.microsoft.com.akadns.net|HTTPS|Used to communicate with Microsoft Store
+|*settings.data.microsoft.com.akadns.net|HTTPS|Used for Windows apps to dynamically update their configuration
+|*wac.phicdn.net*|HTTP|Windows Update
+|*windowsupdate.com*|HTTP|Windows Update
+|*wns.*windows.com*|TLSv1.2/HTTPS|Used for the Windows Push Notification Services (WNS)
+|*wpc.v0cdn.net*|HTTP|Windows Telemetry
+|arc.msn.com|HTTPS|Spotlight
+|auth.gfx.ms*|HTTPS|MSA related
+|cdn.onenote.net|HTTPS|OneNote Live Tile
+|dmd.metaservices.microsoft.com*|HTTP|Device Authentication
+|e-0009.e-msedge.net|HTTPS|Microsoft Office
+|e10198.b.akamaiedge.net|HTTPS|Maps application
+|evoke-windowsservices-tas.msedge*|HTTPS|Photos app
+|fe2.update.microsoft.com*|TLSv1.2/HTTPS|Enables connections to Windows Update, Microsoft Update, and the online services of Microsoft Store
+|fe3.*.mp.microsoft.com.*|TLSv1.2/HTTPS|Windows Update, Microsoft Update, and Microsoft Store services
+|g.live.com*|HTTPS|OneDrive
+|go.microsoft.com|HTTP|Windows Defender
+|iriscoremetadataprod.blob.core.windows.net|HTTPS|Windows Telemetry
+|login.live.com|HTTPS|Device Authentication
+|msagfx.live.com|HTTP|OneDrive
+|ocsp.digicert.com*|HTTP|CRL and OCSP checks to the issuing certificate authorities
+|officeclient.microsoft.com|HTTPS|Microsoft Office
+|oneclient.sfx.ms*|HTTPS|Used by OneDrive for Business to download and verify app updates
+|onecollector.cloudapp.aria.akadns.net|HTTPS|Microsoft Office
+|ow1.res.office365.com|HTTP|Microsoft Office
+|pti.store.microsoft.com|HTTPS|Microsoft Store
+|purchase.mp.microsoft.com*|HTTPS|Used to communicate with Microsoft Store
+|query.prod.cms.rt.microsoft.com*|HTTPS|Used to retrieve Windows Spotlight metadata
+|ris.api.iris.microsoft.com*|TLSv1.2/HTTPS|Used to retrieve Windows Spotlight metadata
+|ris-prod-atm.trafficmanager.net|HTTPS|Azure traffic manager
+|s-0001.s-msedge.net|HTTPS|Microsoft Office
+|self.events.data.microsoft.com|HTTPS|Microsoft Office
+|settings.data.microsoft.com*|HTTPS|Used for Windows apps to dynamically update their configuration
+|settings-win.data.microsoft.com*|HTTPS|Used for Windows apps to dynamically update their configuration
+|share.microsoft.com|HTTPS|Microsoft Store
+|skypeecs-prod-usw-0.cloudapp.net|HTTPS|Microsoft Store
+|sls.update.microsoft.com*|TLSv1.2/HTTPS|Enables connections to Windows Update
+|slscr.update.microsoft.com*|HTTPS|Enables connections to Windows Update
+|store*.dsx.mp.microsoft.com*|HTTPS|Used to communicate with Microsoft Store
+|storecatalogrevocation.storequality.microsoft.com|HTTPS|Microsoft Store
+|storecatalogrevocation.storequality.microsoft.com*|HTTPS|Used to revoke licenses for malicious apps on the Microsoft Store
+|store-images.*microsoft.com*|HTTP|Used to get images that are used for Microsoft Store suggestions
+|storesdk.dsx.mp.microsoft.com|HTTP|Microsoft Store
+|tile-service.weather.microsoft.com*|HTTP|Used to download updates to the Weather app Live Tile
+|time.windows.com|HTTP|Microsoft Windows Time related
+|tsfe.trafficshaping.dsp.mp.microsoft.com*|TLSv1.2/HTTPS|Used for content regulation
+|v10.events.data.microsoft.com|HTTPS|Diagnostic Data
+|watson.telemetry.microsoft.com|HTTPS|Diagnostic Data
+|wdcp.microsoft.*|TLSv1.2, HTTPS|Used for Windows Defender when Cloud-based Protection is enabled
+|wd-prod-cp-us-west-1-fe.westus.cloudapp.azure.com|HTTPS|Windows Defender
+|wusofficehome.msocdn.com|HTTPS|Microsoft Office
+|www.bing.com*|HTTP|Used for updates for Cortana, apps, and Live Tiles
+|www.msftconnecttest.com|HTTP|Network Connection (NCSI)
+|www.office.com|HTTPS|Microsoft Office
+
+
+## Windows 10 Pro
+
+| **Destination** | **Protocol** | **Description** |
+| --- | --- | --- |
+|\*.cloudapp.azure.com|HTTPS|Azure
+|\*.delivery.dsp.mp.microsoft.com.nsatc.net|HTTPS|Windows Update, Microsoft Update, and Microsoft Store services
+|\*.displaycatalog.md.mp.microsoft.com.akadns.net|HTTPS|Microsoft Store
+|\*.dl.delivery.mp.microsoft.com*|HTTP|Enables connections to Windows Update
+|\*.e-msedge.net|HTTPS|Used by OfficeHub to get the metadata of Office apps
+|\*.g.akamaiedge.net|HTTPS|Used to check for updates to maps that have been downloaded for offline use
+|\*.s-msedge.net|HTTPS|Used by OfficeHub to get the metadata of Office apps
+|\*.windowsupdate.com*|HTTP|Enables connections to Windows Update
+|\*.wns.notify.windows.com.akadns.net|HTTPS|Used for the Windows Push Notification Services (WNS)
+|\*dsp.mp.microsoft.com.nsatc.net|HTTPS|Enables connections to Windows Update
+|\*c-msedge.net|HTTP|Office
+|a1158.g.akamai.net|HTTP|Maps application
+|arc.msn.com*|HTTP / HTTPS|Used to retrieve Windows Spotlight metadata
+|blob.mwh01prdstr06a.store.core.windows.net|HTTPS|Microsoft Store
+|browser.pipe.aria.microsoft.com|HTTPS|Microsoft Office
+|bubblewitch3mobile.king.com|HTTPS|Bubble Witch application
+|candycrush.king.com|HTTPS|Candy Crush application
+|cdn.onenote.net|HTTP|Microsoft OneNote
+|cds.p9u4n2q3.hwcdn.net|HTTP|Highwinds Content Delivery Network traffic for Windows updates
+|client.wns.windows.com|HTTPS|Winddows Notification System
+|co4.telecommand.telemetry.microsoft.com.akadns.net|HTTPS|Windows Error Reporting
+|config.edge.skype.com|HTTPS|Microsoft Skype
+|cs11.wpc.v0cdn.net|HTTP|Windows Telemetry
+|cs9.wac.phicdn.net|HTTP|Windows Update
+|cy2.licensing.md.mp.microsoft.com.akadns.net|HTTPS|Used to communicate with Microsoft Store
+|cy2.purchase.md.mp.microsoft.com.akadns.net|HTTPS|Used to communicate with Microsoft Store
+|cy2.settings.data.microsoft.com.akadns.net|HTTPS|Used to communicate with Microsoft Store
+|dmd.metaservices.microsoft.com.akadns.net|HTTP|Device Authentication
+|e-0009.e-msedge.net|HTTPS|Microsoft Office
+|e10198.b.akamaiedge.net|HTTPS|Maps application
+|fe3.update.microsoft.com|HTTPS|Windows Update
+|g.live.com|HTTPS|Microsoft OneDrive
+|g.msn.com.nsatc.net|HTTPS|Used to retrieve Windows Spotlight metadata
+|geo-prod.do.dsp.mp.microsoft.com|HTTPS|Windows Update
+|go.microsoft.com|HTTP|Windows Defender
+|iecvlist.microsoft.com|HTTPS|Microsoft Edge
+|img-prod-cms-rt-microsoft-com.akamaized.net|HTTP / HTTPS|Microsoft Store
+|ipv4.login.msa.akadns6.net|HTTPS|Used for Microsoft accounts to sign in
+|licensing.mp.microsoft.com|HTTP|Licensing
+|location-inference-westus.cloudapp.net|HTTPS|Used for location data
+|login.live.com|HTTP|Device Authentication
+|maps.windows.com|HTTP|Maps application
+|modern.watson.data.microsoft.com.akadns.net|HTTPS|Used by Windows Error Reporting
+|msagfx.live.com|HTTP|OneDrive
+|nav.smartscreen.microsoft.com|HTTPS|Windows Defender
+|ocsp.digicert.com*|HTTP|CRL and OCSP checks to the issuing certificate authorities
+|oneclient.sfx.ms|HTTP|OneDrive
+|pti.store.microsoft.com|HTTPS|Microsoft Store
+|ris.api.iris.microsoft.com.akadns.net|HTTPS|Used to retrieve Windows Spotlight metadata
+|ris-prod-atm.trafficmanager.net|HTTPS|Azure
+|s2s.config.skype.com|HTTP|Microsoft Skype
+|settings-win.data.microsoft.com|HTTPS|Application settings
+|share.microsoft.com|HTTPS|Microsoft Store
+|skypeecs-prod-usw-0.cloudapp.net|HTTPS|Microsoft Skype
+|slscr.update.microsoft.com|HTTPS|Windows Update
+|storecatalogrevocation.storequality.microsoft.com|HTTPS|Microsoft Store
+|store-images.microsoft.com|HTTPS|Microsoft Store
+|tile-service.weather.microsoft.com/*|HTTP|Used to download updates to the Weather app Live Tile
+|time.windows.com|HTTP|Windows time
+|tsfe.trafficshaping.dsp.mp.microsoft.com|HTTPS|Used for content regulation
+|v10.events.data.microsoft.com*|HTTPS|Microsoft Office
+|vip5.afdorigin-prod-am02.afdogw.com|HTTPS|Used to serve office 365 experimentation traffic
+|watson.telemetry.microsoft.com|HTTPS|Telemetry
+|wdcp.microsoft.com|HTTPS|Windows Defender
+|wusofficehome.msocdn.com|HTTPS|Microsoft Office
+|www.bing.com|HTTPS|Cortana and Search
+|www.microsoft.com|HTTP|Diagnostic
+|www.msftconnecttest.com|HTTP|Network connection
+|www.office.com|HTTPS|Microsoft Office
+
+
+
+## Windows 10 Education
+
+| **Destination** | **Protocol** | **Description** |
+| --- | --- | --- |
+|\*.b.akamaiedge.net|HTTPS|Used to check for updates to maps that have been downloaded for offline use
+|\*.c-msedge.net|HTTP|Used by OfficeHub to get the metadata of Office apps
+|\*.dl.delivery.mp.microsoft.com*|HTTP|Windows Update
+|\*.e-msedge.net|HTTPS|Used by OfficeHub to get the metadata of Office apps
+|\*.g.akamaiedge.net|HTTPS|Used to check for updates to Maps that have been downloaded for offline use
+|\*.licensing.md.mp.microsoft.com.akadns.net|HTTPS|Microsoft Store
+|\*.settings.data.microsoft.com.akadns.net|HTTPS|Microsoft Store
+|\*.skype.com*|HTTPS|Used to retrieve Skype configuration values
+|\*.smartscreen*.microsoft.com|HTTPS|Windows Defender
+|\*.s-msedge.net|HTTPS|Used by OfficeHub to get the metadata of Office apps
+|\*.telecommand.telemetry.microsoft.com*|HTTPS|Used by Windows Error Reporting
+|\*.wac.phicdn.net|HTTP|Windows Update
+|\*.windowsupdate.com*|HTTP|Windows Update
+|\*.wns.windows.com|HTTPS|Windows Notifications Service
+|\*.wpc.*.net|HTTP|Diagnostic Data
+|\*displaycatalog.md.mp.microsoft.com.akadns.net|HTTPS|Microsoft Store
+|\*dsp.mp.microsoft.com|HTTPS|Windows Update
+|a1158.g.akamai.net|HTTP|Maps
+|a122.dscg3.akamai.net|HTTP|Maps
+|a767.dscg3.akamai.net|HTTP|Maps
+|au.download.windowsupdate.com*|HTTP|Windows Update
+|bing.com/*|HTTPS|Used for updates for Cortana, apps, and Live Tiles
+|blob.dz5prdstr01a.store.core.windows.net|HTTPS|Microsoft Store
+|browser.pipe.aria.microsoft.com|HTTP|Used by OfficeHub to get the metadata of Office apps
+|cdn.onenote.net/livetile/*|HTTPS|Used for OneNote Live Tile
+|cds.p9u4n2q3.hwcdn.net|HTTP|Used by the Highwinds Content Delivery Network to perform Windows updates
+|client-office365-tas.msedge.net/*|HTTPS|Office 365 porta and Office Online
+|ctldl.windowsupdate.com*|HTTP|Used to download certificates that are publicly known to be fraudulent
+|displaycatalog.mp.microsoft.com/*|HTTPS|Microsoft Store
+|dmd.metaservices.microsoft.com*|HTTP|Device Authentication
+|download.windowsupdate.com*|HTTPS|Windows Update
+|emdl.ws.microsoft.com/*|HTTP|Used to download apps from the Microsoft Store
+|evoke-windowsservices-tas.msedge.net|HTTPS|Photo app
+|fe2.update.microsoft.com*|HTTPS|Windows Update, Microsoft Update, Microsoft Store services
+|fe3.delivery.dsp.mp.microsoft.com.nsatc.net|HTTPS|Windows Update, Microsoft Update, Microsoft Store services
+|fe3.delivery.mp.microsoft.com*|HTTPS|Windows Update, Microsoft Update, Microsoft Store services
+|g.live.com*|HTTPS|Used by OneDrive for Business to download and verify app updates
+|g.msn.com.nsatc.net|HTTPS|Used to retrieve Windows Spotlight metadata
+|go.microsoft.com|HTTP|Windows Defender
+|iecvlist.microsoft.com|HTTPS|Microsoft Edge browser
+|ipv4.login.msa.akadns6.net|HTTPS|Used for Microsoft accounts to sign in
+|licensing.mp.microsoft.com*|HTTPS|Used for online activation and some app licensing
+|login.live.com|HTTPS|Device Authentication
+|maps.windows.com/windows-app-web-link|HTTPS|Maps application
+|modern.watson.data.microsoft.com.akadns.net|HTTPS|Used by Windows Error Reporting
+|msagfx.live.com|HTTPS|OneDrive
+|ocos-office365-s2s.msedge.net/*|HTTPS|Used to connect to the Office 365 portal's shared infrastructure
+|ocsp.digicert.com*|HTTP|CRL and OCSP checks to the issuing certificate authorities
+|oneclient.sfx.ms/*|HTTPS|Used by OneDrive for Business to download and verify app updates
+|onecollector.cloudapp.aria.akadns.net|HTTPS|Microsoft Office
+|pti.store.microsoft.com|HTTPS|Microsoft Store
+|settings-win.data.microsoft.com/settings/*|HTTPS|Used as a way for apps to dynamically update their configuration
+|share.microsoft.com|HTTPS|Microsoft Store
+|skypeecs-prod-usw-0.cloudapp.net|HTTPS|Skype
+|sls.update.microsoft.com*|HTTPS|Windows Update
+|storecatalogrevocation.storequality.microsoft.com*|HTTPS|Used to revoke licenses for malicious apps on the Microsoft Store
+|tile-service.weather.microsoft.com*|HTTP|Used to download updates to the Weather app Live Tile
+|tsfe.trafficshaping.dsp.mp.microsoft.com|HTTPS|Windows Update
+|v10.events.data.microsoft.com*|HTTPS|Diagnostic Data
+|vip5.afdorigin-prod-ch02.afdogw.com|HTTPS|Used to serve Office 365 experimentation traffic
+|watson.telemetry.microsoft.com*|HTTPS|Used by Windows Error Reporting
+|wdcp.microsoft.com|HTTPS|Windows Defender
+|wd-prod-cp-us-east-1-fe.eastus.cloudapp.azure.com|HTTPS|Azure
+|wusofficehome.msocdn.com|HTTPS|Microsoft Office
+|www.bing.com|HTTPS|Cortana and Search
+|www.microsoft.com|HTTP|Diagnostic Data
+|www.microsoft.com/pkiops/certs/*|HTTP|CRL and OCSP checks to the issuing certificate authorities
+|www.msftconnecttest.com|HTTP|Network Connection
+|www.office.com|HTTPS|Microsoft Office
+
From e936adc1bb432d397f45c9e3aac764d712c1240e Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 12:35:53 -0700
Subject: [PATCH 025/156] Update
windows-endpoints-1903-non-enterprise-editions.md
---
...-endpoints-1903-non-enterprise-editions.md | 20 +++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/windows/privacy/windows-endpoints-1903-non-enterprise-editions.md b/windows/privacy/windows-endpoints-1903-non-enterprise-editions.md
index 44fadd939e..2c3885c711 100644
--- a/windows/privacy/windows-endpoints-1903-non-enterprise-editions.md
+++ b/windows/privacy/windows-endpoints-1903-non-enterprise-editions.md
@@ -1,5 +1,5 @@
---
-title: Windows 10, version 1809, connection endpoints for non-Enterprise editions
+title: Windows 10, version 1903, connection endpoints for non-Enterprise editions
description: Explains what Windows 10 endpoints are used in non-Enterprise editions.
keywords: privacy, manage connections to Microsoft, Windows 10, Windows Server 2016
ms.prod: w10
@@ -7,22 +7,22 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.localizationpriority: high
audience: ITPro
-author: danihalfin
-ms.author: daniha
-manager: dansimp
+author: mikeedgar
+ms.author: v-medgar
+manager: sanashar
ms.collection: M365-security-compliance
ms.topic: article
-ms.date: 6/26/2018
+ms.date: 5/9/2019
---
-# Windows 10, version 1809, connection endpoints for non-Enterprise editions
+# Windows 10, version 1903, connection endpoints for non-Enterprise editions
**Applies to**
-- Windows 10 Home, version 1809
-- Windows 10 Professional, version 1809
-- Windows 10 Education, version 1809
+- Windows 10 Home, version 1903
+- Windows 10 Professional, version 1903
+- Windows 10 Education, version 1903
-In addition to the endpoints listed for [Windows 10 Enterprise](manage-windows-1809-endpoints.md), the following endpoints are available on other editions of Windows 10, version 1809.
+In addition to the endpoints listed for [Windows 10 Enterprise](manage-windows-1903-endpoints.md), the following endpoints are available on other editions of Windows 10, version 1903.
We used the following methodology to derive these network endpoints:
From 455b7236ea01925b0814ebb968321986a6e2f357 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 16:57:41 -0700
Subject: [PATCH 026/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...ating-system-components-to-microsoft-services.md | 13 ++++---------
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 72bb0cefbe..1cd88e5243 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -39,9 +39,6 @@ However, some of the settings reduce the functionality and security configuratio
Make sure you've chosen the right settings configuration for your environment before applying.
You should not extract this package to the windows\\system32 folder because it will not apply correctly.
->[!IMPORTANT]
-> As part of the [Windows Restricted Traffic Limited Functionality Baseline](https://go.microsoft.com/fwlink/?linkid=828887), MDM functionallity is disabled. If you manage devices through MDM, make sure [cloud notifications are enabled](#bkmk-priv-notifications).
-
Applying the Windows Restricted Traffic Limited Functionality Baseline is the same as applying each setting covered in this article.
It is recommended that you restart a device after making configuration changes to it.
Note that **Get Help** and **Give us Feedback** links no longer work after the Windows Restricted Traffic Limited Functionality Baseline is applied.
@@ -56,8 +53,6 @@ The following sections list the components that make network connections to Micr
The following table lists management options for each setting, beginning with Windows 10 Enterprise version 1607.
->[!NOTE]
->For some settings, MDM policies only partly cover capabilities available through Group Policy. See each setting’s section for more details.
| Setting | UI | Group Policy | Registry |
| - | :-: | :-: | :-: |
@@ -268,7 +263,7 @@ On Windows Server 2016 Nano Server:
### 2. Cortana and Search
-Use either Group Policy or MDM policies to manage settings for Cortana. For more info, see [Cortana, Search, and privacy: FAQ](https://go.microsoft.com/fwlink/p/?LinkId=730683).
+Use Group Policies to manage settings for Cortana. For more info, see [Cortana, Search, and privacy: FAQ](https://go.microsoft.com/fwlink/p/?LinkId=730683).
### 2.1 Cortana and Search Group Policies
@@ -558,7 +553,7 @@ To disable the Microsoft Account Sign-In Assistant:
### 13. Microsoft Edge
-Use either Group Policy or MDM policies to manage settings for Microsoft Edge. For more info, see [Microsoft Edge and privacy: FAQ](https://go.microsoft.com/fwlink/p/?LinkId=730682).
+Use Group Policies to manage settings for Microsoft Edge. For more info, see [Microsoft Edge and privacy: FAQ](https://go.microsoft.com/fwlink/p/?LinkId=730682).
### 13.1 Microsoft Edge Group Policies
@@ -1643,7 +1638,7 @@ To disable Windows Defender Smartscreen:
### 25. Windows Spotlight
-Windows Spotlight provides features such as different background images and text on the lock screen, suggested apps, Microsoft account notifications, and Windows tips. You can control it by using the user interface, MDM policy, or through Group Policy.
+Windows Spotlight provides features such as different background images and text on the lock screen, suggested apps, Microsoft account notifications, and Windows tips. You can control it by using the user interface or Group Policy.
If you're running Windows 10, version 1607 or later, you need to:
@@ -1765,7 +1760,7 @@ Windows Update Delivery Optimization lets you get Windows updates and Microsoft
By default, PCs running Windows 10 Enterprise and Windows 10 Education will only use Delivery Optimization to get and receive updates for PCs and apps on your local network.
-Use the UI, Group Policy, MDM policies, or Windows Provisioning to set up Delivery Optimization.
+Use the UI, Group Policy, or Registry Keys to set up Delivery Optimization.
In Windows 10 version 1607 and above you can stop network traffic related to Windows Update Delivery Optimization by setting **Download Mode** to **Bypass** (100), as described below.
From 3c8fc7a4ed6263938d394c3edb28ce1e49d77d37 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 19:08:30 -0700
Subject: [PATCH 027/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...ows-operating-system-components-to-microsoft-services.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 1cd88e5243..e86b33a16f 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -96,7 +96,7 @@ The following table lists management options for each setting, beginning with Wi
| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |
| [18.21 Inking & Typing](#bkmk-priv-ink) |  | |  |
| [19. Software Protection Platform](#bkmk-spp) | |  |  |
-| [20. Storage Health](#bkmk-storage-health) | |  | | |
+| [20. Storage Health](#bkmk-storage-health) | |  |  | |
| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |
| [22. Teredo](#bkmk-teredo) | |  | |  |
| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  | |
@@ -129,7 +129,7 @@ See the following table for a summary of the management settings for Windows Ser
| [18. Settings > Privacy](#bkmk-settingssection) | | | |
| [18.1 General](#bkmk-general) |  |  |  |
| [19. Software Protection Platform](#bkmk-spp) | |  |  |
-| [20. Teredo](#bkmk-teredo) | |  |  |
+| [22. Teredo](#bkmk-teredo) | |  |  |
| [24. Windows Defender](#bkmk-defender) | |  |  |
| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
| [26.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
@@ -1488,7 +1488,7 @@ For Windows 10:
-or-
-- Create a REG_DWORD registry setting named **AllowDiskHealthModelUpdates** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\StorageHealth** with a value of 0.
+- Create a REG_DWORD registry setting named **AllowDiskHealthModelUpdates** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\StorageHealth** with a **value of 0**.
### 21. Sync your settings
From bb3fc68af11c27d207e9b245ab56a43affc54c69 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 19:15:11 -0700
Subject: [PATCH 028/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...perating-system-components-to-microsoft-services.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index e86b33a16f..5964599ef4 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -96,9 +96,9 @@ The following table lists management options for each setting, beginning with Wi
| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |
| [18.21 Inking & Typing](#bkmk-priv-ink) |  | |  |
| [19. Software Protection Platform](#bkmk-spp) | |  |  |
-| [20. Storage Health](#bkmk-storage-health) | |  |  | |
+| [20. Storage Health](#bkmk-storage-health) | |  |  |
| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |
-| [22. Teredo](#bkmk-teredo) | |  | |  |
+| [22. Teredo](#bkmk-teredo) | |  |  |
| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  | |
| [24. Windows Defender](#bkmk-defender) | |  |  |
| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |
@@ -146,7 +146,7 @@ See the following table for a summary of the management settings for Windows Ser
| [6. Font streaming](#font-streaming) |  |  |
| [14. Network Connection Status Indicator](#bkmk-ncsi) |  | |
| [19. Software Protection Platform](#bkmk-spp) |  |
-| [22. Teredo](#bkmk-teredo) |  | |
+| [22. Teredo](#bkmk-teredo) |  |  |
| [24. Windows Defender](#bkmk-defender) |  |  |
| [28. Windows Update](#bkmk-wu) |  |  |
@@ -158,7 +158,7 @@ See the following table for a summary of the management settings for Windows Ser
| - | :-: |
| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) |  |
| [3. Date & Time](#bkmk-datetime) |  |
-| [22. Teredo](#bkmk-teredo) | |
+| [22. Teredo](#bkmk-teredo) |  |
| [28. Windows Update](#bkmk-wu) |  |
### Settings for Windows Server 2019
@@ -206,7 +206,7 @@ See the following table for a summary of the management settings for Windows Ser
| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |
| [18.21 Inking & Typing](#bkmk-priv-ink) | | |  |
| [19. Software Protection Platform](#bkmk-spp) | |  |  |
-| [20. Storage Health](#bkmk-storage-health) | |  | |
+| [20. Storage Health](#bkmk-storage-health) | |  |  |
| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |
| [22. Teredo](#bkmk-teredo) | |  |  |
| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  |  |
From 1000661358f37cf87af06bcba38828acb560e92c Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 19:19:05 -0700
Subject: [PATCH 029/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 5964599ef4..ef98f3c09d 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -99,7 +99,7 @@ The following table lists management options for each setting, beginning with Wi
| [20. Storage Health](#bkmk-storage-health) | |  |  |
| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |
| [22. Teredo](#bkmk-teredo) | |  |  |
-| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  | |
+| [23. Wi-Fi Sense](#bkmk-wifisense) |  |  |  |
| [24. Windows Defender](#bkmk-defender) | |  |  |
| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |
| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |
From 5d4ef5882af406a1993bf5d8aa1175265df89e02 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 19:22:58 -0700
Subject: [PATCH 030/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...ows-operating-system-components-to-microsoft-services.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index ef98f3c09d..af7aace6a4 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -104,7 +104,7 @@ The following table lists management options for each setting, beginning with Wi
| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |
| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |
| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
-| [26.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
+| [26.1 Apps for websites](#bkmk-apps-for-websites) | |  |  |
| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |
| [28. Windows Update](#bkmk-wu) |  |  | |
@@ -132,7 +132,7 @@ See the following table for a summary of the management settings for Windows Ser
| [22. Teredo](#bkmk-teredo) | |  |  |
| [24. Windows Defender](#bkmk-defender) | |  |  |
| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
-| [26.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
+| [26.1 Apps for websites](#bkmk-apps-for-websites) | |  |  |
| [28. Windows Update](#bkmk-wu) | |  |  |
### Settings for Windows Server 2016 Server Core
@@ -214,7 +214,7 @@ See the following table for a summary of the management settings for Windows Ser
| [24.1 Windows Defender Smartscreen](#bkmk-defender-smartscreen) | |  |  |
| [25. Windows Spotlight](#bkmk-spotlight) |  |  |  |
| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
-| [26.1 Apps for websites](#bkmk-apps-for-websites) | | |
+| [26.1 Apps for websites](#bkmk-apps-for-websites) | |  | |
| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |
| [28. Windows Update](#bkmk-wu) | |  |  |
From b6bc7577d870a0007cf4dd4117f29f3f27f4316d Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 19:25:53 -0700
Subject: [PATCH 031/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index af7aace6a4..94c2c9f4dd 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -106,7 +106,7 @@ The following table lists management options for each setting, beginning with Wi
| [26. Microsoft Store](#bkmk-windowsstore) | |  |  |
| [26.1 Apps for websites](#bkmk-apps-for-websites) | |  |  |
| [27. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |
-| [28. Windows Update](#bkmk-wu) |  |  | |
+| [28. Windows Update](#bkmk-wu) | |  |  |
### Settings for Windows Server 2016 with Desktop Experience
From 4b445fe8cf340293684880184d40d5fb096a738e Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 19:36:36 -0700
Subject: [PATCH 032/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 94c2c9f4dd..91ea2a2d0a 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -125,7 +125,7 @@ See the following table for a summary of the management settings for Windows Ser
| [10. Live Tiles](#live-tiles) | |  |  |
| [12. Microsoft Account](#bkmk-microsoft-account) | |  |  |
| [14. Network Connection Status Indicator](#bkmk-ncsi) | |  |  |
-| [16. OneDrive](#bkmk-onedrive) | |  | |
+| [16. OneDrive](#bkmk-onedrive) | |  |  |
| [18. Settings > Privacy](#bkmk-settingssection) | | | |
| [18.1 General](#bkmk-general) |  |  |  |
| [19. Software Protection Platform](#bkmk-spp) | |  |  |
From 2e7a4cf02e2b44f53b2e9bbdbbe64642ad437c6d Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 19:38:28 -0700
Subject: [PATCH 033/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...ndows-operating-system-components-to-microsoft-services.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 91ea2a2d0a..4f37cf4f5a 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -144,8 +144,8 @@ See the following table for a summary of the management settings for Windows Ser
| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) |  |  |
| [3. Date & Time](#bkmk-datetime) |  |  |
| [6. Font streaming](#font-streaming) |  |  |
-| [14. Network Connection Status Indicator](#bkmk-ncsi) |  | |
-| [19. Software Protection Platform](#bkmk-spp) |  |
+| [14. Network Connection Status Indicator](#bkmk-ncsi) |  |  |
+| [19. Software Protection Platform](#bkmk-spp) |  |  |
| [22. Teredo](#bkmk-teredo) |  |  |
| [24. Windows Defender](#bkmk-defender) |  |  |
| [28. Windows Update](#bkmk-wu) |  |  |
From cbac0ad6f2f8e9a057a565e7239504376228330c Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 19:40:59 -0700
Subject: [PATCH 034/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 4f37cf4f5a..01593aa1b1 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -200,7 +200,7 @@ See the following table for a summary of the management settings for Windows Ser
| [18.14 Radios](#bkmk-priv-radios) |  |  |  |
| [18.15 Other devices](#bkmk-priv-other-devices) |  |  |  |
| [18.16 Feedback & diagnostics](#bkmk-priv-feedback) |  |  |  |
-| [18.17 Background apps](#bkmk-priv-background) |  |  | |
+| [18.17 Background apps](#bkmk-priv-background) |  |  |  |
| [18.18 Motion](#bkmk-priv-motion) |  |  |  |
| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |
| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |
From 36d3fb430d2bd55ce4cc1c1c15cf37b35fd07822 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 9 May 2019 19:42:23 -0700
Subject: [PATCH 035/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 01593aa1b1..5a69fa7d6e 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -204,7 +204,7 @@ See the following table for a summary of the management settings for Windows Ser
| [18.18 Motion](#bkmk-priv-motion) |  |  |  |
| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |
| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |
-| [18.21 Inking & Typing](#bkmk-priv-ink) | | |  |
+| [18.21 Inking & Typing](#bkmk-priv-ink) |  | |  |
| [19. Software Protection Platform](#bkmk-spp) | |  |  |
| [20. Storage Health](#bkmk-storage-health) | |  |  |
| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |
From cdecc3168902b9c4de822b9696641cd71f8873e7 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Fri, 10 May 2019 15:25:55 -0700
Subject: [PATCH 036/156] new topic for multiple policies
---
.../TOC.md | 1 +
...s-defender-application-control-policies.md | 43 +++++++++++++++++++
...improvements-in-windows-10-version-1903.md | 25 +----------
3 files changed, 45 insertions(+), 24 deletions(-)
create mode 100644 windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
diff --git a/windows/security/threat-protection/windows-defender-application-control/TOC.md b/windows/security/threat-protection/windows-defender-application-control/TOC.md
index 89a1b3bafb..bdaf9c0a68 100644
--- a/windows/security/threat-protection/windows-defender-application-control/TOC.md
+++ b/windows/security/threat-protection/windows-defender-application-control/TOC.md
@@ -16,6 +16,7 @@
#### [Microsoft recommended block rules](microsoft-recommended-block-rules.md)
### [Audit WDAC policies](audit-windows-defender-application-control-policies.md)
### [Merge WDAC policies](merge-windows-defender-application-control-policies.md)
+### [Deploy multiple WDAC policies](deploy-multiple-windows-defender-application-control-policies.md)
### [Enforce WDAC policies](enforce-windows-defender-application-control-policies.md)
### [Deploy WDAC with a managed installer](use-windows-defender-application-control-with-managed-installer.md)
### [Deploy WDAC with Intelligent Security Graph (ISG)](use-windows-defender-application-control-with-intelligent-security-graph.md)
diff --git a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
new file mode 100644
index 0000000000..a542e82236
--- /dev/null
+++ b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
@@ -0,0 +1,43 @@
+---
+title: Deploy multiple Windows Defender Application Control Policies (Windows 10)
+description: Windows Defender Application Control supports multiple code integrity policies for one device.
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: security
+ms.localizationpriority: medium
+author: jsuther1974
+ms.date: 05/10/2019
+---
+
+# Deploy multiple Windows Defender Application Control Policies
+
+**Applies to:**
+
+- Windows 10
+- Windows Server 2016
+
+>[!IMPORTANT]
+>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
+
+Beginning with Windows 10 version 1903, WDAC supports multiple code integrity policies for one device.
+
+## Precedence
+
+- Multiple base policies: intersection
+ - Only applications allowed by both policies run without generating block events
+- Base + supplemental policy: union
+ - Files that are allowed by the base policy or the supplemental policy are not blocked
+
+## Newly Supported Scenarios
+
+WDAC brings you the ability to support multiple CI policies. Three scenarios are now supported:
+
+1. Enforce and Audit Side-by-Side (Intersection)
+ - To validate policy changes before deploying in enforcement mode, deploy an audit-mode base policy side-by-side with an existing enforcement-mode base policy
+2. Multiple Base Policies (Intersection)
+ - Enforce two or more base policies simultaneously to allow simpler policy targeting for policies with different scope/intent
+ - Ex. Base1 is a corporate standard policy that is relatively loose to accommodate all organizations while forcing minimum corp standards (e.g. Windows works + Managed Installer + path rules). Base2 is a team-specific policy that further restricts what is allowed to run (e.g. Windows works + Managed Installer + corporate signed apps only)
+3. Supplemental Policies (Union)
+ - Deploy a supplemental policy (or policies) to expand a base policy
+ - Ex. The Azure host base policy restricts tightly to just allow Windows and hardware drivers. Can add a supplemental policy to allow just the additional signer rules needed to support signed code from the Exchange team.
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
index b563a2c54f..95d58415d4 100644
--- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
+++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
@@ -7,7 +7,7 @@ ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
author: jsuther1974
-ms.date: 05/06/2018
+ms.date: 05/06/2019
---
# Windows Defender Application Control improvements in Windows 10 version 1903
@@ -61,29 +61,6 @@ Beginning with Windows 10 version 1903, Windows Defender Application Control (WD
Set-RuleOption -o 18 .\policy.xml
```
-## Multiple Policies
-
-Beginning with Windows 10 version 1903, WDAC supports multiple code integrity policies for one device.
-
-### Precedence
-
-- Multiple base policies: intersection
- - Only applications allowed by both policies run without generating block events
-- Base + supplemental policy: union
- - Files that are allowed by the base policy or the supplemental policy are not blocked
-
-### Newly Supported Scenarios
-
-WDAC brings you the ability to support multiple CI policies. Three scenarios are now supported:
-
-1. Enforce and Audit Side-by-Side (Intersection)
- - To validate policy changes before deploying in enforcement mode, deploy an audit-mode base policy side-by-side with an existing enforcement-mode base policy
-2. Multiple Base Policies (Intersection)
- - Enforce two or more base policies simultaneously to allow simpler policy targeting for policies with different scope/intent
- - Ex. Base1 is a corporate standard policy that is relatively loose to accommodate all organizations while forcing minimum corp standards (e.g. Windows works + Managed Installer + path rules). Base2 is a team-specific policy that further restricts what is allowed to run (e.g. Windows works + Managed Installer + corporate signed apps only)
-3. Supplemental Policies (Union)
- - Deploy a supplemental policy (or policies) to expand a base policy
- - Ex. The Azure host base policy restricts tightly to just allow Windows and hardware drivers. Can add a supplemental policy to allow just the additional signer rules needed to support signed code from the Exchange team.
## COM Whitelisting
From 30fc0eb470c713b6033ea489012349cee8376656 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Mon, 13 May 2019 11:31:03 -0700
Subject: [PATCH 037/156] Update TOC.md
---
windows/privacy/TOC.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/windows/privacy/TOC.md b/windows/privacy/TOC.md
index 35561d07af..b687b5bc1b 100644
--- a/windows/privacy/TOC.md
+++ b/windows/privacy/TOC.md
@@ -20,7 +20,9 @@
### [Connection endpoints for Windows 10, version 1709](manage-windows-1709-endpoints.md)
### [Connection endpoints for Windows 10, version 1803](manage-windows-1803-endpoints.md)
### [Connection endpoints for Windows 10, version 1809](manage-windows-1809-endpoints.md)
+### [Connection endpoints for Windows 10, version 1903](manage-windows-1903-endpoints.md)
### [Windows 10, version 1709, connection endpoints for non-Enterprise editions](windows-endpoints-1709-non-enterprise-editions.md)
### [Windows 10, version 1803, connection endpoints for non-Enterprise editions](windows-endpoints-1803-non-enterprise-editions.md)
### [Windows 10, version 1809, connection endpoints for non-Enterprise editions](windows-endpoints-1809-non-enterprise-editions.md)
+### [Windows 10, version 1903, connection endpoints for non-Enterprise editions](windows-endpoints-1903-non-enterprise-editions.md)
## [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
From 7c68158598ccd74ed8ca65bb5ded545479bf40cf Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Tue, 14 May 2019 18:08:00 -0700
Subject: [PATCH 038/156] new pages
---
.../TOC.md | 2 +
.../com-whitelisting.md | 60 ++++++
.../create-path-based-rules.md | 59 +++++
...s-defender-application-control-policies.md | 70 +++++-
...th-windows-defender-application-control.md | 45 +++-
...improvements-in-windows-10-version-1903.md | 201 +-----------------
6 files changed, 237 insertions(+), 200 deletions(-)
create mode 100644 windows/security/threat-protection/windows-defender-application-control/com-whitelisting.md
create mode 100644 windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
diff --git a/windows/security/threat-protection/windows-defender-application-control/TOC.md b/windows/security/threat-protection/windows-defender-application-control/TOC.md
index bdaf9c0a68..5644387f36 100644
--- a/windows/security/threat-protection/windows-defender-application-control/TOC.md
+++ b/windows/security/threat-protection/windows-defender-application-control/TOC.md
@@ -13,11 +13,13 @@
### [Types of devices](types-of-devices.md)
###Use WDAC with custom policies
#### [Create an initial default policy](create-initial-default-policy.md)
+#### [Create path-based rules](create-path-based-rules.md)
#### [Microsoft recommended block rules](microsoft-recommended-block-rules.md)
### [Audit WDAC policies](audit-windows-defender-application-control-policies.md)
### [Merge WDAC policies](merge-windows-defender-application-control-policies.md)
### [Deploy multiple WDAC policies](deploy-multiple-windows-defender-application-control-policies.md)
### [Enforce WDAC policies](enforce-windows-defender-application-control-policies.md)
+### [COM whitelisting](com-whitelisting.md)
### [Deploy WDAC with a managed installer](use-windows-defender-application-control-with-managed-installer.md)
### [Deploy WDAC with Intelligent Security Graph (ISG)](use-windows-defender-application-control-with-intelligent-security-graph.md)
### [Deploy WDAC policies using Group Policy](deploy-windows-defender-application-control-policies-using-group-policy.md)
diff --git a/windows/security/threat-protection/windows-defender-application-control/com-whitelisting.md b/windows/security/threat-protection/windows-defender-application-control/com-whitelisting.md
new file mode 100644
index 0000000000..9cd8ba8357
--- /dev/null
+++ b/windows/security/threat-protection/windows-defender-application-control/com-whitelisting.md
@@ -0,0 +1,60 @@
+---
+title: Windows Defender Application Control path-based rules (Windows 10)
+description: Windows Defender Application Control restricts which applications users are allowed to run and the code that runs in the system core.
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: security
+ms.localizationpriority: medium
+author: jsuther1974
+ms.date: 05/14/2019
+---
+
+# COM Whitelisting
+
+**Applies to:**
+
+- Windows 10
+- Windows Server 2016
+
+>[!IMPORTANT]
+>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
+
+The [Microsoft Component Object Model (COM)](https://docs.microsoft.com/windows/desktop/com/the-component-object-model) is a platform-independent, distributed, object-oriented system for creating binary software components that can interact. COM specifies an object model and programming requirements that enable COM objects to interact with other objects.
+
+Get GUID of application to allow by either:
+- Finding block event in Event Viewer (Application and Service Logs > Microsoft > Windows > AppLocker > MSI and Script) and extracting GUID
+- Creating audit policy (using New-CIPolicy –Audit), potentially with specific provider, and use info from block events to get GUID
+
+### Author setting
+
+Three elements:
+- Provider: platform on which code is running (values are Powershell, WSH, IE, VBA, MSI, or a wildcard “AllHostIds”)
+- Key: GUID for the program you with to run, in the format Key="{33333333-4444-4444-1616-161616161616}"
+- ValueName: needs to be set to "EnterpriseDefinedClsId"
+One attribute:
+- Value: needs to be “true” for allow and “false” for deny
+ Note: without quotation marks
+ Note: deny only works in base policies
+- The setting needs to be placed in the order of ASCII values, first by Provider, then Key, then ValueName
+
+### Examples
+
+```xml
+
+
+ true
+
+
+
+
+ false
+
+
+
+
+ true
+
+
+```
+
diff --git a/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md b/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
new file mode 100644
index 0000000000..852c003dc0
--- /dev/null
+++ b/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
@@ -0,0 +1,59 @@
+---
+title: Windows Defender Application Control path-based rules (Windows 10)
+description: Beginning with Windows 10 version 1903, Windows Defender Application Control (WDAC) policies can contain path-based rules.
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: security
+ms.localizationpriority: medium
+author: jsuther1974
+ms.date: 05/14/2019
+---
+
+# Create Windows Defender Application Control path-based rules
+
+**Applies to:**
+
+- Windows 10
+- Windows Server 2016
+
+>[!IMPORTANT]
+>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
+
+Beginning with Windows 10 version 1903, Windows Defender Application Control (WDAC) policies can contain path-based rules.
+
+- New-CIPolicy parameters
+ - FilePath: create path rules under path \ for anything not user-writeable (at the individual file level)
+ ```powershell
+ New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
+ ```
+ Optionally, add -UserWriteablePaths to ignore user writeability
+
+ - FilePathRule: create a rule where filepath string is directly set to value of \
+ ```powershell
+ New-CIPolicyRule -FilePathRule
+ ```
+ Useful for wildcards like C:\foo\\*
+
+- Usage follows the same flow as per-app rules:
+ ```powershell
+ $rules = New-CIPolicyRule …
+ $rules += New-CIPolicyRule …
+ …
+ New-CIPolicyRule -f .\mypolicy.xml -u
+ ```
+
+- Wildcards supported
+ - Suffix (ex. C:\foo\\*) OR Prefix (ex. *\foo\bar.exe)
+ - One or the other, not both at the same time
+ - Does not support wildcard in the middle (ex. C:\\*\foo.exe)
+ - Examples:
+ - %WINDIR%\\...
+ - %SYSTEM32%\\...
+ - %OSDRIVE%\\...
+
+- Disable default FilePath rule protection of enforcing user-writeability. For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy:
+ ```powershell
+ Set-RuleOption -o 18 .\policy.xml
+ ```
+
diff --git a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
index a542e82236..7408abf167 100644
--- a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
+++ b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
@@ -29,9 +29,9 @@ Beginning with Windows 10 version 1903, WDAC supports multiple code integrity po
- Base + supplemental policy: union
- Files that are allowed by the base policy or the supplemental policy are not blocked
-## Newly Supported Scenarios
+## Newly supported scenarios
-WDAC brings you the ability to support multiple CI policies. Three scenarios are now supported:
+With the ability to support multiple CI policies, three new scenarios are supported:
1. Enforce and Audit Side-by-Side (Intersection)
- To validate policy changes before deploying in enforcement mode, deploy an audit-mode base policy side-by-side with an existing enforcement-mode base policy
@@ -41,3 +41,69 @@ WDAC brings you the ability to support multiple CI policies. Three scenarios are
3. Supplemental Policies (Union)
- Deploy a supplemental policy (or policies) to expand a base policy
- Ex. The Azure host base policy restricts tightly to just allow Windows and hardware drivers. Can add a supplemental policy to allow just the additional signer rules needed to support signed code from the Exchange team.
+
+## PowerShell parameters
+
+New-CIPolicy
+- MultiplePolicyFormat: allows for multiple policies
+
+```powershell
+New-CIPolicy [-FilePath] -Level {None | Hash | FileName | SignedVersion | Publisher | FilePublisher | LeafCertificate | PcaCertificate | RootCertificate | WHQL | WHQLPublisher | WHQLFilePublisher | PFN | FilePath}
+ [-DriverFiles ] [-Fallback {None | Hash | FileName | SignedVersion | Publisher | FilePublisher | LeafCertificate | PcaCertificate | RootCertificate | WHQL | WHQLPublisher | WHQLFilePublisher | PFN | FilePath}]
+ [-Audit] [-ScanPath ] [-ScriptFileNames] [-AllowFileNameFallbacks] [-SpecificFileNameLevel {None | OriginalFileName | InternalName | FileDescription | ProductName | PackageFamilyName | FilePath}] [-UserPEs] [-NoScript]
+ [-Deny] [-NoShadowCopy] [-MultiplePolicyFormat] [-OmitPaths ] [-PathToCatroot ] [] – to generate new policy format(base policy and policy type and policy guid)
+```
+
+Set-CIPolicyIdInfo
+- **SupplementsBasePolicyID**: guid of new supplemental policy
+- **BasePolicyToSupplementPath**: base policy that the supplemental policy applies to
+- **ResetPolicyID**: reset the policy guids back to a random guid
+
+```powershell
+Set-CIPolicyIdInfo [-FilePath] [-PolicyName ] [-SupplementsBasePolicyID ] [-BasePolicyToSupplementPath ] [-ResetPolicyID] [-PolicyId ] []
+```
+
+Add-SignerRule
+- **Supplemental**: provides supplemental signers
+
+```powershell
+Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
+```
+
+Set-RuleOption
+- **Enabled:Allow Supplemental Policies**: makes base policy able to be supplemented
+
+### Examples
+
+**Scenario #1: Creating a new base policy**
+
+```powershell
+New-CiPolicy -MulitplePolicyFormat -foo –bar
+```
+
+- **MultiplePolicyFormat** switch results in 1) random GUIDs being generated for the policy ID and 2) the policy type being specified as base.
+ Can optionally choose to make it supplementable:
+ - Set-RuleOption has a new option **Enabled:Allow Supplemental Policies** to set for base policy
+- For signed policies that are being made supplementable, need to ensure that supplemental signers are defined. Use “Add-SignerRule” to provide supplemental signers.
+ ```powershell
+ Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
+ ```
+
+**Scenario #2: Creating a new supplemental policy**
+
+1. Scan using `New-CiPolicy –MuliplePolicyFormat` to generate a base policy:
+ ```powershell
+ New-CIPolicy -Level PcaCertificate -UserPEs -ScanPath -MultiplePolicyFormat 3> -FilePath
+ ```
+2. Change this new base policy to a supplemental policy
+ - Provide path of base in `Set-CIPolicyIdInfo –BasePolicytoSupplementPath`
+ - Provide GUID of base in `Set-CIPolicyIdInfo –SupplementsBasePolicyID`
+ ```powershell
+ Set-CIPolicyIdInfo -BasePolicyToSupplementPath -SupplementsBasePolicyID -FilePath
+ ```
+ - Can revert the policy back to being a base policy using `-ResetPolicyID`
+
+**Scenario #3: Merging policies**
+
+- When merging, the policy type and ID of the leftmost/first policy specified is used
+ - If the leftmost is a base policy with ID , then regardless of what the GUIDS and types are for any subsequent policies, the merged policy will be a base policy with ID
diff --git a/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md b/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md
index 718fc4a51c..0cac5a2d54 100644
--- a/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md
+++ b/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md
@@ -8,7 +8,7 @@ ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
author: jsuther1974
-ms.date: 05/03/2018
+ms.date: 05/14/2019
---
# Manage packaged apps with Windows Defender Application Control
@@ -48,3 +48,46 @@ Just as there are differences in managing each rule collection, you need to mana
3. Continue to update the WDAC policies as new package apps are introduced into your environment. To do this, see [Merge WDAC policies](merge-windows-defender-application-control-policies.md).
+## Blocking packaged apps
+
+You can use `New-CIPolicyRule -Package $Package -Deny` to block packaged apps:
+
+1. Get the info about an installed package.
+ ```powershell
+ $package = Get-AppxPackage -name
+ ```
+ Dependencies field in output is full Package object, can be accessed and passed directly to New-CIPolicyRule.
+2. Make a rule.
+ ```powershell
+ $Rule = New-CIPolicyRule -Package $package -deny
+ ```
+3. Repeat for other packages you want to block using $rule +=….
+4. Make a policy for just the blocks you created for packages.
+ ```powershell
+ New-CIpolicy -rules $rule -f .\policy.xml -u
+ ```
+5. Merge with allow windows policy, or you could also use examplepolicies\AllowAll.xml.
+ ```powershell
+ Merge-CIPolicy -PolicyPaths .\policy.xml,C:\windows\Schemas\codeintegrity\examplepolicies\DefaultWindows_Audit.xml -o allowWindowsDenyPackages.xml
+ ```
+6. Disable audit mode.
+ ```powershell
+ Set-RuleOption -o 3 -Delete .\allowWindowsDenyPackages.xml
+ ```
+7. Enable invalidate EAs on reboot.
+ ```powershell
+ Set-RuleOption -o 15 .\allowWindowsDenyPackages.xml
+ ```
+8. Compile the policy
+ ```powershell
+ ConvertFrom-CIPolicy .\AllowWindowsDenyPackages.xml C:\compiledpolicy.bin
+ ```
+9. Install the policy withwout restarting.
+ ```powershell
+ Invoke-CimMethod -Namespace root\Microsoft\Windows\CI -ClassName PS_UpdateAndCompareCIPolicy -MethodName Update -Arguments @{FilePath = "C:\compiledpolicy.bin"}
+ ```
+
+After doing this on the next build of Dev3, for the apps that you blocked, already installed apps should fail to launch, and should you put this policy on another machine that hasn’t yet installed the apps, store should block them from being purchased/installed.
+If you wanted to make a rule for an app that isn’t already installed, first make a rule for an app that is. Then for the app you want to actually block take the store URL (from store page click … then share, then copy link to get something like: https://www.microsoft.com/store/productId/9WZDNCRFJ3TJ) and grab the hash code at the end (in bold) then replace the bolded bit below:
+https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9wzdncrfj3tj/applockerdata
+then grab packagefamilyname and replace the one in the xml you got in step 4 with the PFN from the link above, then run through 5-9 again.
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
index 95d58415d4..810e645612 100644
--- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
+++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
@@ -1,16 +1,16 @@
---
-title: Windows Defender Application Control improvements in Windows 10 version 1903 (Windows 10)
-description: Windows Defender Application Control restricts which applications users are allowed to run and the code that runs in the system core.
+title: Windows Defender Application Control Frequently asked questions (Windows 10)
+description: Frequently asked questions.
ms.prod: w10
ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
author: jsuther1974
-ms.date: 05/06/2019
+ms.date: 05/14/2019
---
-# Windows Defender Application Control improvements in Windows 10 version 1903
+# Frequently asked questions
**Applies to:**
@@ -20,199 +20,6 @@ ms.date: 05/06/2019
>[!IMPORTANT]
>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
-This topic covers improvements introduced in Windows 10, version 1903.
-
-## Path-based rules
-
-Beginning with Windows 10 version 1903, Windows Defender Application Control (WDAC) policies can contain path-based rules.
-
-- New-CIPolicy parameters
- - FilePath: create path rules under path \ for anything not user-writeable (at the individual file level)
- ```powershell
- New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
- ```
- Optionally, add -UserWriteablePaths to ignore user writeability
-
- - FilePathRule: create a rule where filepath string is directly set to value of \
- ```powershell
- New-CIPolicyRule -FilePathRule
- ```
- Useful for wildcards like C:\foo\\*
-
-- Usage follows the same flow as per-app rules:
- ```powershell
- $rules = New-CIPolicyRule …
- $rules += New-CIPolicyRule …
- …
- New-CIPolicyRule -f .\mypolicy.xml -u
- ```
-
-- Wildcards supported
- - Suffix (ex. C:\foo\\*) OR Prefix (ex. *\foo\bar.exe)
- - One or the other, not both at the same time
- - Does not support wildcard in the middle (ex. C:\\*\foo.exe)
- - Examples:
- - %WINDIR%\\...
- - %SYSTEM32%\\...
- - %OSDRIVE%\\...
-
-- Disable default FilePath rule protection of enforcing user-writeability. For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy:
- ```powershell
- Set-RuleOption -o 18 .\policy.xml
- ```
-
-
-## COM Whitelisting
-
-• https://docs.microsoft.com/en-us/windows/desktop/com/the-component-object-model
-
-Get GUID of application to allow by either:
-- Finding block event in Event Viewer (Application and Service Logs > Microsoft > Windows > AppLocker > MSI and Script) and extracting GUID
-- Creating audit policy (using New-CIPolicy –Audit), potentially with specific provider, and use info from block events to get GUID
-
-### Author setting
-
-Three elements:
-- Provider: platform on which code is running (values are Powershell, WSH, IE, VBA, MSI, or a wildcard “AllHostIds”)
-- Key: GUID for the program you with to run, in the format Key="{33333333-4444-4444-1616-161616161616}"
-- ValueName: needs to be set to "EnterpriseDefinedClsId"
-One attribute:
-- Value: needs to be “true” for allow and “false” for deny
- Note: without quotation marks
- Note: deny only works in base policies
-- The setting needs to be placed in the order of ASCII values, first by Provider, then Key, then ValueName
-
-### Examples
-
-```xml
-
-
- true
-
-
-
-
- false
-
-
-
-
- true
-
-
-```
-
-## New PowerShell parameters
-
-New-CIPolicy
-- MultiplePolicyFormat: allows for multiple policies
-
-```powershell
-New-CIPolicy [-FilePath] -Level {None | Hash | FileName | SignedVersion | Publisher | FilePublisher | LeafCertificate | PcaCertificate | RootCertificate | WHQL | WHQLPublisher | WHQLFilePublisher | PFN | FilePath}
- [-DriverFiles ] [-Fallback {None | Hash | FileName | SignedVersion | Publisher | FilePublisher | LeafCertificate | PcaCertificate | RootCertificate | WHQL | WHQLPublisher | WHQLFilePublisher | PFN | FilePath}]
- [-Audit] [-ScanPath ] [-ScriptFileNames] [-AllowFileNameFallbacks] [-SpecificFileNameLevel {None | OriginalFileName | InternalName | FileDescription | ProductName | PackageFamilyName | FilePath}] [-UserPEs] [-NoScript]
- [-Deny] [-NoShadowCopy] [-MultiplePolicyFormat] [-OmitPaths ] [-PathToCatroot ] [] – to generate new policy format(base policy and policy type and policy guid)
-```
-
-Set-CIPolicyIdInfo
-- **SupplementsBasePolicyID**: guid of new supplemental policy
-- **BasePolicyToSupplementPath**: base policy that the supplemental policy applies to
-- **ResetPolicyID**: reset the policy guids back to a random guid
-
-```powershell
-Set-CIPolicyIdInfo [-FilePath] [-PolicyName ] [-SupplementsBasePolicyID ] [-BasePolicyToSupplementPath ] [-ResetPolicyID] [-PolicyId ] []
-```
-
-Add-SignerRule
-- **Supplemental**: provides supplemental signers
-
-```powershell
-Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
-```
-
-Set-RuleOption
-- **Enabled:Allow Supplemental Policies**: makes base policy able to be supplemented
-
-### Examples
-
-**Scenario #1: Creating a new base policy**
-
-```powershell
-New-CiPolicy -MulitplePolicyFormat -foo –bar
-```
-
-- **MultiplePolicyFormat** switch results in 1) random GUIDs being generated for the policy ID and 2) the policy type being specified as base.
- Can optionally choose to make it supplementable:
- - Set-RuleOption has a new option **Enabled:Allow Supplemental Policies** to set for base policy
-- For signed policies that are being made supplementable, need to ensure that supplemental signers are defined. Use “Add-SignerRule” to provide supplemental signers.
- ```powershell
- Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
- ```
-
-**Scenario #2: Creating a new supplemental policy**
-
-1. Scan using `New-CiPolicy –MuliplePolicyFormat` to generate a base policy:
- ```powershell
- New-CIPolicy -Level PcaCertificate -UserPEs -ScanPath -MultiplePolicyFormat 3> -FilePath
- ```
-2. Change this new base policy to a supplemental policy
- - Provide path of base in `Set-CIPolicyIdInfo –BasePolicytoSupplementPath`
- - Provide GUID of base in `Set-CIPolicyIdInfo –SupplementsBasePolicyID`
- ```powershell
- Set-CIPolicyIdInfo -BasePolicyToSupplementPath -SupplementsBasePolicyID -FilePath
- ```
- - Can revert the policy back to being a base policy using `-ResetPolicyID`
-
-**Scenario #3: Merging policies**
-
-- When merging, the policy type and ID of the leftmost/first policy specified is used
- - If the leftmost is a base policy with ID , then regardless of what the GUIDS and types are for any subsequent policies, the merged policy will be a base policy with ID
-
-## Packaged App Rules
-
-`New-CIPolicyRule -Package $Package -Deny` to block apps is your best use case, so something like:
-
-1. Get the info about an installed package.
- ```powershell
- $package = Get-AppxPackage -name
- ```
- Dependencies field in output is full Package object, can be accessed and passed directly to New-CIPolicyRule.
-2. Make a rule.
- ```powershell
- $Rule = New-CIPolicyRule -Package $package -deny
- ```
-3. Repeat for other packages you want to block using $rule +=….
-4. Make a policy for just the blocks you created for packages.
- ```powershell
- New-CIpolicy -rules $rule -f .\policy.xml -u
- ```
-5. Merge with allow windows policy, or you could also use examplepolicies\AllowAll.xml.
- ```powershell
- Merge-CIPolicy -PolicyPaths .\policy.xml,C:\windows\Schemas\codeintegrity\examplepolicies\DefaultWindows_Audit.xml -o allowWindowsDenyPackages.xml
- ```
-6. Disable audit mode.
- ```powershell
- Set-RuleOption -o 3 -Delete .\allowWindowsDenyPackages.xml
- ```
-7. Enable invalidate EAs on reboot.
- ```powershell
- Set-RuleOption -o 15 .\allowWindowsDenyPackages.xml
- ```
-8. Compile the policy
- ```powershell
- ConvertFrom-CIPolicy .\AllowWindowsDenyPackages.xml C:\compiledpolicy.bin
- ```
-9. Install the policy withwout restarting.
- ```powershell
- Invoke-CimMethod -Namespace root\Microsoft\Windows\CI -ClassName PS_UpdateAndCompareCIPolicy -MethodName Update -Arguments @{FilePath = "C:\compiledpolicy.bin"}
- ```
-
-After doing this on the next build of Dev3, for the apps that you blocked, already installed apps should fail to launch, and should you put this policy on another machine that hasn’t yet installed the apps, store should block them from being purchased/installed.
-If you wanted to make a rule for an app that isn’t already installed, first make a rule for an app that is. Then for the app you want to actually block take the store URL (from store page click … then share, then copy link to get something like: https://www.microsoft.com/store/productId/9WZDNCRFJ3TJ) and grab the hash code at the end (in bold) then replace the bolded bit below:
-https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9wzdncrfj3tj/applockerdata
-then grab packagefamilyname and replace the one in the xml you got in step 4 with the PFN from the link above, then run through 5-9 again.
-
-## FAQs
**Q:** What uniquely identifies a “file”? SHA1, SHA256, either, both? What is the “Flat hash” vs. normal?
From 457a7c7f478c56f804b0e881de0048bb4d2b13af Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Wed, 15 May 2019 11:08:55 -0700
Subject: [PATCH 039/156] Create
configure-connections-to-microsoft-services-with-mdm.md
---
...nections-to-microsoft-services-with-mdm.md | 122 ++++++++++++++++++
1 file changed, 122 insertions(+)
create mode 100644 windows/privacy/configure-connections-to-microsoft-services-with-mdm.md
diff --git a/windows/privacy/configure-connections-to-microsoft-services-with-mdm.md b/windows/privacy/configure-connections-to-microsoft-services-with-mdm.md
new file mode 100644
index 0000000000..881ce64336
--- /dev/null
+++ b/windows/privacy/configure-connections-to-microsoft-services-with-mdm.md
@@ -0,0 +1,122 @@
+---
+title: Manage connections from Windows operating system components to Microsoft services using Microsoft Intune MDM Server
+description: Use MDM CSPs to minimize connections from Windows to Microsoft services, or to configure particular privacy settings.
+ms.assetid: ACCEB0DD-BC6F-41B1-B359-140B242183D9
+keywords: privacy, manage connections to Microsoft, Windows 10
+ms.prod: w10
+ms.mktglfcycl: manage
+ms.sitesec: library
+ms.localizationpriority: medium
+author: mikeedgar
+ms.author: v-medgar
+ms.date: 3/1/2019
+---
+
+# Manage connections from Windows operating system components to Microsoft services using Microsoft Intune MDM Server
+
+**Applies to**
+
+- Windows 10 Enterprise 1903 version and later
+
+You can use Microsoft InTune with MDM CSPs and custom [OMA URIs](https://docs.microsoft.com/en-us/intune/custom-settings-windows-10) to minimize connections from Windows to Microsoft services, or to configure particular privacy settings. You can configure diagnostic data at the lowest level for your edition of Windows, and also evaluate which other connections Windows makes to Microsoft services you want to turn off in your environment from the list in this article.
+
+To ensure CSPs take priority over Group Policies in case of conflicts, use the [ControlPolicyConflict](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-controlpolicyconflict) policy.
+
+You can configure diagnostic data at the Security/Basic level, turn off Windows Defender diagnostic data and MSRT reporting, and turn off all other connections to Microsoft network endpoints as described in this article to help prevent Windows from sending any data to Microsoft. There are many reasons why these communications are enabled by default, such as updating malware definitions and maintain current certificate revocation lists, which is why we strongly recommend against this. This data helps us deliver a secure, reliable, and more delightful personalized experience.
+
+Note, there is some traffic which is required (i.e. "whitelisted") for the operation of Windows and the Microsoft InTune based management. This traffic includes CRL and OCSP network traffic which will show up in network traces. CRL and OCSP checks are made to the issuing certificate authorities. Microsoft is one of them, but there are many others, such as DigiCert, Thawte, Google, Symantec, and VeriSign. Additional whitelisted traffic specifically for MDM managed devices includes Windows Notification Service related traffic as well as some specific Microsoft InTune and Windows Update related traffic.
+
+For more information on Microsoft InTune please see [Transform IT service delivery for your modern workplace](https://www.microsoft.com/en-us/enterprise-mobility-security/microsoft-intune?rtc=1) and [Microsoft Intune documentation](https://docs.microsoft.com/en-us/intune/).
+
+For detailed information about managing network connections to Microsoft services using Baseline package/registries/Group policies/UI/Command line, see [Manage connections from Windows operating system components to Microsoft services](https://docs.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services).
+
+### Settings for Windows 10 Enterprise edition 1903 and later
+
+The following table lists management options for each setting.
+
+For Windows 10, the following MDM policies are available in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx).
+
+| Setting | MDM Policy | Description |
+| --- | --- | --- |
+| 1. Automatic Root Certificates Update | There is intentionally no MDM available for Automatic Root Certificate Update. | This MDM does not exist since it would prevent the operation and management of MDM management of devices.
+| 2. Cortana and Search | [Experience/AllowCortana](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-experience#experience-allowcortana) | Choose whether to let Cortana install and run on the device.
+| | [Search/AllowSearchToUseLocation](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-search#search-allowsearchtouselocation) | Choose whether Cortana and Search can provide location-aware search results.
Default: Allowed
+| 3. Date & Time | [Settings/AllowDateTime](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-settings#settings-allowdatetime)| Allows the user to change date and time settings.
**0** Not allowed.
1 (default) Allowed.
+| 4. Device metadata retrieval | [DeviceInstallation/PreventDeviceMetadataFromNetwork](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deviceinstallation#deviceinstallation-preventdevicemetadatafromnetwork) | Choose whether to prevent Windows from retrieving device metadata from the Internet
+| 5. Find My Device | [Experience/AllowFindMyDevice](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-experience#experience-allowfindmydevice)| This policy turns on Find My Device.
Set to **0** to disable.
+| 6. Font streaming | [System/AllowFontProviders](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-system#system-allowfontproviders) | Set to 0 to disable font streaming
Set to 1 to enable font streaming
+| 7. Insider Preview builds | [System/AllowBuildPreview](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-system#system-allowbuildpreview) | **0**: users cannot make their devices available for downloading and installing preview software
**1**: users can make their devices available for downloading and installing preview software
**2**: (default) not configured; users can make their devices available for download and installing preview software
+| 8. Internet Explorer | The following Microsoft Internet Explorer MDM policies are available in the [Internet Explorer CSP](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-internetexplorer) |
+| | [InternetExplorer/AllowSuggestedSites](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-internetexplorer#internetexplorer-allowsuggestedsites) | Recommends websites based on the user’s browsing activity.
+| | [InternetExplorer/PreventManagingSmartScreenFilter]( https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-internetexplorer#internetexplorer-preventmanagingsmartscreenfilter) | Prevents the user from managing SmartScreen Filter, which warns the user if the website being visited is known for fraudulent attempts to gather personal information through "phishing," or is known to host malware.
+| | [InternetExplorer/DisableFlipAheadFeature]( https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-internetexplorer#internetexplorer-disableflipaheadfeature) | Determines whether a user can swipe across a screen or click Forward to go to the next pre-loaded page of a website.
+| | [InternetExplorer/DisableHomePageChange]( https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-internetexplorer#internetexplorer-disablehomepagechange) | Determines whether users can change the default Home Page or not.
+| | [InternetExplorer/DisableFirstRunWizard]( https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-internetexplorer#internetexplorer-disablefirstrunwizard) | Prevents Internet Explorer from running the First Run wizard the first time a user starts the browser after installing Internet Explorer or Windows.
+| 9. Live Tiles | [Notifications/DisallowTileNotification](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-notifications)| This policy setting turns off tile notifications. If you enable this policy setting applications and system features will not be able to update their tiles and tile badges in the Start screen. Set value to **1** to disable Tile Notifications.
+| 10. Mail synchronization | [Accounts/AllowMicrosoftAccountConnection](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-accounts#accounts-allowmicrosoftaccountconnection) | **0**: not allowed
**1**: allowed
Does not apply to Microsoft Accounts that have already been configured on the device.
+| 11. Microsoft Account | [Accounts/AllowMicrosoftAccountSignInAssistant](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-accounts#accounts-allowmicrosoftaccountsigninassistant) | Disable the Microsoft Account Sign-In Assistant.
**0**: turned off
**1**: turned on
+| 12. Microsoft Edge | | The following Microsoft Edge MDM policies are available in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). For a complete list of the Microsoft Edge policies, see [Available policies for Microsoft Edge](https://docs.microsoft.com/microsoft-edge/deploy/available-policies).
+| | [Browser/AllowAutoFill](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-browser#browser-allowautofill) | Choose whether employees can use autofill on websites.
Default: Allowed
+| | [Browser/AllowDoNotTrack](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-browser#browser-allowdonottrack) | Choose whether employees can send Do Not Track headers.
Default: Not allowed
+| | [Browser/AllowMicrosoftCompatbilityList](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-browser#browser-allowmicrosoftcompatibilitylist) | Specify the Microsoft compatibility list in Microsoft Edge.
Default: Enabled
+| | [Browser/AllowPasswordManager](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-browser#browser-allowpasswordmanager) | Choose whether employees can save passwords locally on their devices.
Default: Allowed
+| | [Browser/AllowSearchSuggestionsinAddressBar](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-browser#browser-allowsearchsuggestionsinaddressbar) | Choose whether the Address Bar shows search suggestions..
Default: Allowed
+| | [Browser/AllowSmartScreen](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-browser#browser-allowsmartscreen) | Choose whether SmartScreen is turned on or off.
Default: Allowed
+| | [Browser/FirstRunURL](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-browser#browser-firstrunurl) | Choose the home page for Microsoft Edge on Windows Mobile 10.
Default: blank
+| 13. Network Connection Status Indicator | [Connectivity/DisallowNetworkConnectivityActiveTests](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-connectivity#connectivity-disallownetworkconnectivityactivetests) | **1**: turn off NCSI
Note:: After you apply this policy you must restart the device for the policy setting to take effect.
+| 14. Offline maps | [AllowOfflineMapsDownloadOverMeteredConnection](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-maps)|Allows the download and update of map data over metered connections.
**0** Disabled. Force disable auto-update over metered connection.
+| | [EnableOfflineMapsAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-maps#maps-enableofflinemapsautoupdate)|Disables the automatic download and update of map data.
**0** Disabled. Force off auto-update.
+| 15. OneDrive | [DisableOneDriveFileSync](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-system#system-disableonedrivefilesync)| Allows IT Admins to prevent apps and features from working with files on OneDrive.
**1** True (sync disabled).
+| 16. Preinstalled apps | N/A | N/A
+| 17. Privacy settings | | Except for the Feedback & Diagnostics page, these settings must be configured for every user account that signs into the PC.
+| 17.1 General | [TextInput/AllowLinguisticDataCollection](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-textinput#textinput-allowlinguisticdatacollection) | Turn off **Send Microsoft info about how I write to help us improve typing and writing in the future**.
**0**: not allowed
**1**: allowed (default)
+| 17.2 Location | [System/AllowLocation](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-system#system-allowlocation) | Turn off **Location for this device**.
**0**: turned off and the employee can't turn it back on
**1**: turned on but lets the employee choose whether to use it (default)
**2**: turned on and the employee can't turn it off
Note:: You can also set this MDM policy in System Center Configuration Manager using the [WMI Bridge Provider](https://msdn.microsoft.com/library/dn905224.aspx).
+| 17.3 Camera | [Camera/AllowCamera](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-camera#camera-allowcamera) | Turn off **Let apps use my camera**.
**0**: apps can't use the camera
**1** apps can use the camera
Note:: You can also set this MDM policy in System Center Configuration Manager using the [WMI Bridge Provider](https://msdn.microsoft.com/library/dn905224.aspx).
+| 17.4 Microphone | [Privacy/LetAppsAccessMicrophone](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccessmicrophone) | Turn off **Let apps use my microphone**.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.5 Notifications | [Notifications/DisallowCloudNotification](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-notifications#notifications-disallowcloudnotification) | Turn off notifications network usage.
**DO NOT TURN OFF WNS Notifications if you want manage your device(s) using Microsoft InTune**
+| | [Privacy/LetAppsAccessNotifications](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccessnotifications) | Turn off **Let apps access my notifications**.
**0**: user in control
**1**: force allow
**2**: force deny
+| | [Settings/Notifications & actions/AllowOnlineTips]( https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-settings#settings-allowonlinetips) | Disable **AllowOnlineTips** to prevent traffic
+| 17.6 Speech, Inking, & Typing | [Speech/AllowSpeechModelUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-speech#speech-allowspeechmodelupdate) | Turn off updates to the speech recognition and speech synthesis models.
**0**: not allowed (default)
**1**: allowed
+| | [TextInput/AllowLinguisticDataCollection](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-textinput#textinput-allowlinguisticdatacollection)|This policy setting controls the ability to send inking and typing data to Microsoft to improve the language recognition and suggestion capabilities of apps and services running on Windows.
**0**: disallow
**1**: choice deferred to user's preference
+| 17.7 Account info | [Privacy/LetAppsAccessAccountInfo](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccessaccountinfo) | Turn off **Let apps access my name picture and other account info in the UI**.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.8 Contacts | [Privacy/LetAppsAccessContacts](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccesscontacts) | Turn off **Choose apps that can access contacts** in the UI.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.9 Calendar | [Privacy/LetAppsAccessCalendar](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccesscalendar) | Turn off **Let apps access my calendar** in the UI.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.10 Call history | [Privacy/LetAppsAccessCallHistory](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccesscallhistory) | Turn off **Let apps access my call history** in the UI.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.11 Email | [Privacy/LetAppsAccessEmail](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccessemail) | Turn off **Let apps access and send email** in the UI.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.12 Messaging | [Privacy/LetAppsAccessMessaging](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccessmessaging) | Turn off **Let apps read or send messages (text or MMS)** in the UI.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.13 Phone calls | [Privacy/LetAppsAccessPhone](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccessphone) |
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.14 Radios | [Privacy/LetAppsAccessRadios](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccessradios) | Turn off **Let apps control radios** in the UI.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.15 Other devices | [Privacy/LetAppsSyncWithDevices](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappssyncwithdevices) | Turn off **Let apps automatically share and sync info** with wireless devices that don't explicitly pair with your PC, tablet, or phone** in the UI.
**0**: user in control
**1**: force allow
**2**: force deny
+| | [Privacy/LetAppsAccessTrustedDevices](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccesstrusteddevices) | Turn off **Let your apps use your trusted devices** (hardware you've already connected, or comes with your PC, tablet, or phone) in the UI.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.16 Feedback & diagnostics | [System/AllowTelemetry](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-system#system-allowtelemetry) | Change the level of diagnostic and usage data sent when you **Send your device data to Microsoft**.
**0**: maps to the **Security** level
**1**: maps to the **Basic** level
**2**: maps to the **Enhanced** level
**3**: maps to the **Full** level
+| 17.17 Background apps | [Privacy/LetAppsRunInBackground](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsruninbackground) | Turn off **Let apps run in the background** in the UI.
**0**: user in control
**1**: force allow
**2**: force deny
Note: Some apps, including Cortana and Search, might not function as expected if you set **Let apps run in the background** to **Force Deny**.
+| 17.18 Motion | [Privacy/LetAppsAccessMotion](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccessmotion) | Turn off **Let Windows and your apps use your motion data and collect motion history** in the UI.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.19 Tasks | [Privacy/LetAppsAccessTasks](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsaccesstasks) | Turn off the ability to choose which apps have access to tasks.
**0**: user in control
**1**: force allow
**2**: force deny
+| 17.20 App Diagnostics | [Privacy/LetAppsGetDiagnosticInfo](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#privacy-letappsgetdiagnosticinfo) | Turn off the ability to choose which apps have access to diagnostic information.
**0**: user in control
**1**: force allow
**2**: force deny
+| 18. Software Protection Platform | [Licensing/DisallowKMSClientOnlineAVSValidation](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-licensing#licensing-disallowkmsclientonlineavsvalidation) | Opt out of sending KMS client activation data to Microsoft automatically.
**0**: disabled (default)
**1**: enabled
+| 19. Storage Health | [Storage/AllowDiskHealthModelUpdates](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-storage#storage-allowdiskhealthmodelupdates) | Allows disk health model updates.
**0** - Do not allow
+| 20. Sync your settings | [Experience/AllowSyncMySettings](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-experience#experience-allowsyncmysettings) | Control whether your settings are synchronized.
**0**: not allowed
**1**: allowed
+| 21. Teredo | No MDM needed or required|No MDM needed or required
+| 22. Wi-Fi Sense | No MDM needed or required|No MDM needed or required
+| 23. Windows Defender | [Defender/AllowCloudProtection](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-defender#defender-allowcloudprotection) | Disconnect from the Microsoft Antimalware Protection Service.
**0** Not allowed.
**1** (default) Allowed.
+| | [Defender/SubmitSamplesConsent](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-defender#defender-submitsamplesconsent) | Stop sending file samples back to Microsoft.
**0**: always prompt
**1**: send safe samples automatically (default)
**2**: never send
**3**: send all samples automatically
+| 23.1 Windows Defender Smartscreen | [Browser/AllowSmartScreen](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-browser#browser-allowsmartscreen) | Disable Windows Defender Smartscreen.
**0**: turned off
**1**: turned on
+| 23.2 Windows Defender Smartscreen EnableAppInstallControl | [SmartScreen/EnableAppInstallControl](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-smartscreen#smartscreen-enableappinstallcontrol) | Controls whether users are allowed to install apps from places other than the Microsoft Store
**0**: Turns off traffic
**1**: Allows traffic
+| 24. Windows Media Player | N/A | N/A
+| 25. Windows Spotlight | [Experience/AllowWindowsSpotlight](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-experience#experience-allowwindowsspotlight) | Disable Windows Spotlight.
**0**: disabled
+| 26. Microsoft Store | [ApplicationManagement/DisableStoreOriginatedApps](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-applicationmanagement#applicationmanagement-disablestoreoriginatedapps)| Boolean value that disables the launch of all apps from Microsoft Store that came pre-installed or were downloaded.
**0** (default) Enable launch of apps.
**1** Disable launch of apps.
+| | [ApplicationManagement/AllowAppStoreAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-applicationmanagement#applicationmanagement-allowappstoreautoupdate)| Specifies whether automatic update of apps from Microsoft Store are allowed.
**1** (default) Allowed.
**0** Not allowed.
+| 26.1 Apps for websites | [ApplicationDefaults/EnableAppUriHandlers](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-applicationdefaults#applicationdefaults-enableappurihandlers) | This policy setting determines whether Windows supports web-to-app linking with app URI handlers.
**0**: disabled
**1** enabled
+| 27. Windows Update Delivery Optimization | | The following Delivery Optimization MDM policies are available in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx).
+| | [DeliveryOptimization/DODownloadMode](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dodownloadmode) | Lets you choose where Delivery Optimization gets or sends updates and apps.
**0**: turns off Delivery Optimization
**1**: gets or sends updates and apps to PCs on the same NAT only
**2**: gets or sends updates and apps to PCs on the same local network domain
**3**: gets or sends updates and apps to PCs on the Internet
**99**: simple download mode with no peering
**100**: use BITS instead of Windows Update Delivery Optimization
+| | [DeliveryOptimization/DOGroupID](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dogroupid) | Lets you provide a Group ID that limits which PCs can share apps and updates.
Note: This ID must be a GUID.
+| | [DeliveryOptimization/DOMaxCacheAge](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-domaxcacheage) | Lets you specify the maximum time (in seconds) that a file is held in the Delivery Optimization cache.
The default value is 259200 seconds (3 days).
+| | [DeliveryOptimization/DOMaxCacheSize](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-domaxcachesize) | Lets you specify the maximum cache size as a percentage of disk size.
The default value is 20| which represents 20% of the disk.
+| | [DeliveryOptimization/DOMaxUploadBandwidth](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-domaxuploadbandwidth) | Lets you specify the maximum upload bandwidth (in KB/second) that a device uses across all concurrent upload activity.
The default value is 0, which means unlimited possible bandwidth.
+| | [DeliveryOptimization/DODownloadMode](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dodownloadmode)| Specifies the download method that Delivery Optimization can use in downloads of Windows Updates, Apps and App updates. Set to **100** - Bypass mode. Do not use Delivery Optimization and use BITS instead. Added in Windows 10, version 1607.
+| 28. Windows Update | [Update/AllowAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) | Control automatic updates.
**0**: notify the user before downloading the update
**1**: auto install the update and then notify the user to schedule a device restart
**2**: auto install and restart (default)
**3**: auto install and restart at a specified time
**4**: auto install and restart without end-user control
**5**: turn off automatic updates
+
+
+
+
+
From dc813d358459496add78badc5af9efe55f11f663 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Wed, 15 May 2019 12:01:15 -0700
Subject: [PATCH 040/156] Update
configure-connections-to-microsoft-services-with-mdm.md
---
.../configure-connections-to-microsoft-services-with-mdm.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/configure-connections-to-microsoft-services-with-mdm.md b/windows/privacy/configure-connections-to-microsoft-services-with-mdm.md
index 881ce64336..58a96778b5 100644
--- a/windows/privacy/configure-connections-to-microsoft-services-with-mdm.md
+++ b/windows/privacy/configure-connections-to-microsoft-services-with-mdm.md
@@ -7,7 +7,7 @@ ms.prod: w10
ms.mktglfcycl: manage
ms.sitesec: library
ms.localizationpriority: medium
-author: mikeedgar
+author: medgarmedgar
ms.author: v-medgar
ms.date: 3/1/2019
---
From 1bb0e75a6a7e985ce9dce893afcb4b122b4d453b Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Wed, 15 May 2019 12:10:54 -0700
Subject: [PATCH 041/156] Update TOC.md
---
windows/privacy/TOC.md | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/windows/privacy/TOC.md b/windows/privacy/TOC.md
index b687b5bc1b..2b3934e585 100644
--- a/windows/privacy/TOC.md
+++ b/windows/privacy/TOC.md
@@ -17,12 +17,13 @@
### [Windows 10, version 1709 and newer 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)
## Manage Windows 10 connection endpoints
-### [Connection endpoints for Windows 10, version 1709](manage-windows-1709-endpoints.md)
-### [Connection endpoints for Windows 10, version 1803](manage-windows-1803-endpoints.md)
-### [Connection endpoints for Windows 10, version 1809](manage-windows-1809-endpoints.md)
### [Connection endpoints for Windows 10, version 1903](manage-windows-1903-endpoints.md)
-### [Windows 10, version 1709, connection endpoints for non-Enterprise editions](windows-endpoints-1709-non-enterprise-editions.md)
-### [Windows 10, version 1803, connection endpoints for non-Enterprise editions](windows-endpoints-1803-non-enterprise-editions.md)
-### [Windows 10, version 1809, connection endpoints for non-Enterprise editions](windows-endpoints-1809-non-enterprise-editions.md)
+### [Connection endpoints for Windows 10, version 1809](manage-windows-1809-endpoints.md)
+### [Connection endpoints for Windows 10, version 1803](manage-windows-1803-endpoints.md)
+### [Connection endpoints for Windows 10, version 1709](manage-windows-1709-endpoints.md)
### [Windows 10, version 1903, connection endpoints for non-Enterprise editions](windows-endpoints-1903-non-enterprise-editions.md)
+### [Windows 10, version 1809, connection endpoints for non-Enterprise editions](windows-endpoints-1809-non-enterprise-editions.md)
+### [Windows 10, version 1803, connection endpoints for non-Enterprise editions](windows-endpoints-1803-non-enterprise-editions.md)
+### [Windows 10, version 1709, connection endpoints for non-Enterprise editions](windows-endpoints-1709-non-enterprise-editions.md)
## [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
+## [Manage connections from Windows operating system components to Microsoft services using MDM/CSPs](configure-connections-to-microsoft-services-with-mdm.md)
From 6cfd3cb0ee56fda652fac85ef7d25c3298078fce Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Wed, 15 May 2019 12:53:41 -0700
Subject: [PATCH 042/156] Rename
configure-connections-to-microsoft-services-with-mdm.md to
manage-connections-from-windows-operating-system-components-to-microsoft-services-with-MDM.md
---
...operating-system-components-to-microsoft-services-with-MDM.md} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename windows/privacy/{configure-connections-to-microsoft-services-with-mdm.md => manage-connections-from-windows-operating-system-components-to-microsoft-services-with-MDM.md} (100%)
diff --git a/windows/privacy/configure-connections-to-microsoft-services-with-mdm.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-with-MDM.md
similarity index 100%
rename from windows/privacy/configure-connections-to-microsoft-services-with-mdm.md
rename to windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-with-MDM.md
From 0bb2b2f0691e2ada84e3b6953216187311c49cde Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Wed, 15 May 2019 12:54:05 -0700
Subject: [PATCH 043/156] Update TOC.md
---
windows/privacy/TOC.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/TOC.md b/windows/privacy/TOC.md
index 2b3934e585..f1214e7bec 100644
--- a/windows/privacy/TOC.md
+++ b/windows/privacy/TOC.md
@@ -26,4 +26,4 @@
### [Windows 10, version 1803, connection endpoints for non-Enterprise editions](windows-endpoints-1803-non-enterprise-editions.md)
### [Windows 10, version 1709, connection endpoints for non-Enterprise editions](windows-endpoints-1709-non-enterprise-editions.md)
## [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
-## [Manage connections from Windows operating system components to Microsoft services using MDM/CSPs](configure-connections-to-microsoft-services-with-mdm.md)
+## [Manage connections from Windows operating system components to Microsoft services using MDM](configure-connections-to-microsoft-services-with-mdm.md)
From 6d68ad0c7bde63730d6969a632c45281e56ee4a3 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Wed, 15 May 2019 12:55:08 -0700
Subject: [PATCH 044/156] Rename
manage-connections-from-windows-operating-system-components-to-microsoft-services-with-MDM.md
to
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...perating-system-components-to-microsoft-services-using-MDM.md} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename windows/privacy/{manage-connections-from-windows-operating-system-components-to-microsoft-services-with-MDM.md => manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md} (100%)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-with-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
similarity index 100%
rename from windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-with-MDM.md
rename to windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
From 44a8cedab9ee2824824250a667140cdd36f07909 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Wed, 15 May 2019 12:58:52 -0700
Subject: [PATCH 045/156] added path-based rules
---
.../select-types-of-rules-to-create.md | 39 +++++++++++++++++++
1 file changed, 39 insertions(+)
diff --git a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
index 85b9f016f2..ccf9c4559b 100644
--- a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
+++ b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
@@ -103,3 +103,42 @@ As part of normal operations, they will eventually install software updates, or
They could also choose to create a catalog that captures information about the unsigned internal application, then sign and distribute the catalog. Then the internal application could be handled by WDAC policies in the same way as any other signed application. An update to the internal application would only require that the catalog be regenerated, signed, and distributed (no restarts would be required).
+## Create path-based rules
+
+Beginning with Windows 10 version 1903, Windows Defender Application Control (WDAC) policies can contain path-based rules.
+
+- New-CIPolicy parameters
+ - FilePath: create path rules under path \ for anything not user-writeable (at the individual file level)
+ ```powershell
+ New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
+ ```
+ Optionally, add -UserWriteablePaths to ignore user writeability
+
+ - FilePathRule: create a rule where filepath string is directly set to value of \
+ ```powershell
+ New-CIPolicyRule -FilePathRule
+ ```
+ Useful for wildcards like C:\foo\\*
+
+- Usage follows the same flow as per-app rules:
+ ```powershell
+ $rules = New-CIPolicyRule …
+ $rules += New-CIPolicyRule …
+ …
+ New-CIPolicyRule -f .\mypolicy.xml -u
+ ```
+
+- Wildcards supported
+ - Suffix (ex. C:\foo\\*) OR Prefix (ex. *\foo\bar.exe)
+ - One or the other, not both at the same time
+ - Does not support wildcard in the middle (ex. C:\\*\foo.exe)
+ - Examples:
+ - %WINDIR%\\...
+ - %SYSTEM32%\\...
+ - %OSDRIVE%\\...
+
+- Disable default FilePath rule protection of enforcing user-writeability. For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy:
+ ```powershell
+ Set-RuleOption -o 18 .\policy.xml
+ ```
+
From 06af7c649ba56f4b27189cdf662af25eef988a15 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Wed, 15 May 2019 13:08:27 -0700
Subject: [PATCH 046/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 5a69fa7d6e..dc7fcf967a 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1032,7 +1032,7 @@ To turn off **Let apps access my notifications**:
In the **Speech** area, you can configure the functionality as such:
-To turn off streaming audio to Microsoft Speech services,
+To turn off the functionality to do voice dictation, speaking to Cortana and other apps, or sending voice input to Microsoft Speech services:
- Toggle the Settings -> Privacy -> Speech -> **Online speech recognition** switch to **Off**
From a4a15783c649d48c07f91f5e275161660f03c472 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Wed, 15 May 2019 13:10:53 -0700
Subject: [PATCH 047/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index dc7fcf967a..61476e9047 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1032,7 +1032,7 @@ To turn off **Let apps access my notifications**:
In the **Speech** area, you can configure the functionality as such:
-To turn off the functionality to do voice dictation, speaking to Cortana and other apps, or sending voice input to Microsoft Speech services:
+To turn off voice dictation, speaking to Cortana and other apps, or sending voice input to Microsoft Speech services:
- Toggle the Settings -> Privacy -> Speech -> **Online speech recognition** switch to **Off**
From e941711276000903b4978ac40659b3cffe51c617 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Wed, 15 May 2019 13:38:15 -0700
Subject: [PATCH 048/156] renamed faq
---
...ws-defender-application-control-frequently-asked-questions.md} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename windows/security/threat-protection/windows-defender-application-control/{windows-defender-application-control-improvements-in-windows-10-version-1903.md => windows-defender-application-control-frequently-asked-questions.md} (100%)
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-frequently-asked-questions.md
similarity index 100%
rename from windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-improvements-in-windows-10-version-1903.md
rename to windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-frequently-asked-questions.md
From 302daa5ab494993274a9d80b4da54e8246852c39 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Wed, 15 May 2019 13:51:54 -0700
Subject: [PATCH 049/156] renamed com whitelisting topic
---
...egistration-in-windows-defender-application-control-policy.md} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename windows/security/threat-protection/windows-defender-application-control/{com-whitelisting.md => allow-com-object-registration-in-windows-defender-application-control-policy.md} (100%)
diff --git a/windows/security/threat-protection/windows-defender-application-control/com-whitelisting.md b/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
similarity index 100%
rename from windows/security/threat-protection/windows-defender-application-control/com-whitelisting.md
rename to windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
From febe645dd5dc6e20a5b854cb5c6bd9ae88ecc671 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Wed, 15 May 2019 14:22:42 -0700
Subject: [PATCH 050/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...ndows-operating-system-components-to-microsoft-services.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 61476e9047..b86d3299d7 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1550,7 +1550,9 @@ When turned off, the Wi-Fi Sense settings still appear on the Wi-Fi Settings scr
### 24. Windows Defender
-You can disconnect from the Microsoft Antimalware Protection Service.
+You can disconnect from the Microsoft Antimalware Protection Service.
+
+On Windows 10 1903 Client operating systems and newer search on "Tamper Protection" from the Windows search button next to the Start button on the desktop commmand bar. Scroll down to the Tamper Protection toggle and turn it **Off**. This will allow you to modify the Registry key and allow the Group Policy to make the setting. Alternatively, go to Windows Security Settings -> Virus & threat protection, click on Manage settings and then scroll down to the Tamper Protection toggle and set it to **Off**.
- **Enable** the Group Policy **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Windows Defender Antivirus** > **MAPS** > **Join Microsoft MAPS** and then select **Disabled** from the drop down box named **Join Microsoft MAPS**
From 4b7f0fe31f204ee737b1750850cee4d39b65bb76 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Wed, 15 May 2019 15:34:00 -0700
Subject: [PATCH 051/156] renamed toc entries
---
.../windows-defender-application-control/TOC.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/TOC.md b/windows/security/threat-protection/windows-defender-application-control/TOC.md
index 5644387f36..624c07a310 100644
--- a/windows/security/threat-protection/windows-defender-application-control/TOC.md
+++ b/windows/security/threat-protection/windows-defender-application-control/TOC.md
@@ -19,7 +19,7 @@
### [Merge WDAC policies](merge-windows-defender-application-control-policies.md)
### [Deploy multiple WDAC policies](deploy-multiple-windows-defender-application-control-policies.md)
### [Enforce WDAC policies](enforce-windows-defender-application-control-policies.md)
-### [COM whitelisting](com-whitelisting.md)
+### [Allow COM object registration](allow-com-object-registration-in-windows-defender-application-control-policy.md)
### [Deploy WDAC with a managed installer](use-windows-defender-application-control-with-managed-installer.md)
### [Deploy WDAC with Intelligent Security Graph (ISG)](use-windows-defender-application-control-with-intelligent-security-graph.md)
### [Deploy WDAC policies using Group Policy](deploy-windows-defender-application-control-policies-using-group-policy.md)
@@ -37,7 +37,7 @@
### [Sideload Win32 apps on S mode](sideloading-win32-apps-on-windows-10-s-mode-devices.md)
### [Disable WDAC policies](disable-windows-defender-application-control-policies.md)
### [Device Guard and AppLocker](windows-defender-device-guard-and-applocker.md)
-### [Windows Defender Application Control improvements in Windows 10 version 1903](windows-defender-application-control-improvements-in-windows-10-version-1903.md)
+### [FAQs](windows-defender-application-control-frequently-asked-questions.md)
## [AppLocker](applocker\applocker-overview.md)
### [Administer AppLocker](applocker\administer-applocker.md)
From cd3b77704c0515b0cb40d7a8d518759e0fd577ce Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Wed, 15 May 2019 15:36:13 -0700
Subject: [PATCH 052/156] deleted faq
---
.../TOC.md | 1 -
...tion-control-frequently-asked-questions.md | 108 ------------------
2 files changed, 109 deletions(-)
delete mode 100644 windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-frequently-asked-questions.md
diff --git a/windows/security/threat-protection/windows-defender-application-control/TOC.md b/windows/security/threat-protection/windows-defender-application-control/TOC.md
index 624c07a310..075e728710 100644
--- a/windows/security/threat-protection/windows-defender-application-control/TOC.md
+++ b/windows/security/threat-protection/windows-defender-application-control/TOC.md
@@ -37,7 +37,6 @@
### [Sideload Win32 apps on S mode](sideloading-win32-apps-on-windows-10-s-mode-devices.md)
### [Disable WDAC policies](disable-windows-defender-application-control-policies.md)
### [Device Guard and AppLocker](windows-defender-device-guard-and-applocker.md)
-### [FAQs](windows-defender-application-control-frequently-asked-questions.md)
## [AppLocker](applocker\applocker-overview.md)
### [Administer AppLocker](applocker\administer-applocker.md)
diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-frequently-asked-questions.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-frequently-asked-questions.md
deleted file mode 100644
index 810e645612..0000000000
--- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-frequently-asked-questions.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: Windows Defender Application Control Frequently asked questions (Windows 10)
-description: Frequently asked questions.
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype: security
-ms.localizationpriority: medium
-author: jsuther1974
-ms.date: 05/14/2019
----
-
-# Frequently asked questions
-
-**Applies to:**
-
-- Windows 10
-- Windows Server 2016
-
->[!IMPORTANT]
->Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
-
-
-**Q:** What uniquely identifies a “file”? SHA1, SHA256, either, both? What is the “Flat hash” vs. normal?
-
-**A:** Either hash works as a unique identifier, would recommend sha256 though just because lower collision chance.
-
-“Authenticode Hash” is the hash we use, it is calculated in a way that does not change even if the file is embed signed, whereas “flat hash” is just a direct hash on the bytes of the file and changes with signature.
-
-For Scripts/MSIs an embedded hash would use the SIP of the particular script type, while a catalog hash would use the flat hash (since catalogs are only aware of a few select SIPs, particularly the PE exe/dll one), so the 8028/8029 events log the “CatalogHash” as well, in case it differs from the hash used to evaluate against an embedded sig
-
-**Q:** What property of a file is used to map out to a publisher?
-
-**A:** Files are tied to publishers via their signature (either embed signed or catalog signed via a signed catalog containing that files hash), correlate 3089 events in order to get publisher data
-
-**Q:** Can you give a description/enumeration of values for “signing level”?
-
-**A:** Base signing levels are:
-
-```xml
-#define SE_SIGNING_LEVEL_UNCHECKED 0x00000000
-#define SE_SIGNING_LEVEL_UNSIGNED 0x00000001
-#define SE_SIGNING_LEVEL_ENTERPRISE 0x00000002
-#define SE_SIGNING_LEVEL_CUSTOM_1 0x00000003
-#define SE_SIGNING_LEVEL_DEVELOPER SE_SIGNING_LEVEL_CUSTOM_1
-#define SE_SIGNING_LEVEL_AUTHENTICODE 0x00000004
-#define SE_SIGNING_LEVEL_CUSTOM_2 0x00000005
-#define SE_SIGNING_LEVEL_STORE 0x00000006
-#define SE_SIGNING_LEVEL_CUSTOM_3 0x00000007
-#define SE_SIGNING_LEVEL_ANTIMALWARE SE_SIGNING_LEVEL_CUSTOM_3
-#define SE_SIGNING_LEVEL_MICROSOFT 0x00000008
-#define SE_SIGNING_LEVEL_CUSTOM_4 0x00000009
-#define SE_SIGNING_LEVEL_CUSTOM_5 0x0000000A
-#define SE_SIGNING_LEVEL_DYNAMIC_CODEGEN 0x0000000B
-#define SE_SIGNING_LEVEL_WINDOWS 0x0000000C
-#define SE_SIGNING_LEVEL_CUSTOM_7 0x0000000D
-#define SE_SIGNING_LEVEL_WINDOWS_TCB 0x0000000E
-#define SE_SIGNING_LEVEL_CUSTOM_6 0x0000000F
-```
-
-The TL;DR on signing levels is we have collections of certificates+EKUs that we use to define broad “security levels” based on signer, for example SE_SIGNING_LEVEL_WINDOWS generally maps to “signed as part of a production Windows build)
-Some also inherit from others (e.g. signing level Windows is a subset of Microsoft)
-
-**Q:** What is the “SI Signing Scenario”?
-This maps to either kernel or user mode (0 or 1 respectively). CIPolicy lets you configure whitelists for each separately.
-
-**Q:** Can you also provide the “description” for the events?
-
-I know audit/block are each one of two values next to each other, but do they audit/block a specific file type only? Script? Exe?
-
-|-------|--------------------------|
-|Event ID| Description |
-|3076 |Audit for exe/dll generated by CI in the createprocess stack|
-|3077 |Enforced version |
-|3089 |Signing information event correlated with either a 3076/3077 event, contains # of signatures and an index as to which signature it is, one 3089 is generated for each signature of a file (so many 3089 map to one 3076/77). Unsigned files will generate a single 3089 with TotalSignatureCount 0 |
-|8028 |Audit for scripts/msis generated by WLDP being called by the scripthosts themselves (scripthosts opt in to enforcement, so we don’t enforce on 3rd party scripthosts like python/ruby)|
-|8029 |Enforce for scripts|
-
-We don’t currently have signer information in the script events
-
-**Q:** I don’t understand what the “Policy” fields are.
-
-**A:** Code Integrity Policy is at its core an enterprise whitelisting solution. For these events to be generated, customers would have had to generate a policy xml, compile it, and deploy it. PolicyName/PolicyID fields are optional fields customers can add to the policy to get propagated into the events, policy hash is literally the hash of the policy (and policy hash matching guarantees that two events were blocked by the same policy). Since you can have multiple concurrent policies on one system supplementing each other, knowing what policy actually blocked the binary from running is useful
-
-**Q:** Is this purely file based or do I need to worry about the “PackageName” grouping? For example, do I need the packagename to get back to a publisher or are individual files from the package all mapped up directly?
-
-**A:** An event is generated for each individual binary that failed policy. The PackageFamilyName is put in the process token of all binaries loading under an appx and is can be used in rules in policy to attempt to allow an entire package to run rather than whitelisting each individual binary, but we will still generate an individual event for each binary that fails.
-
-
-**Q:** What field in 3089 am I able to join on to map from File to Publisher?
-
-**A:** CorrelationID is actually not in the event templates I sent you and is actually an optional field in the metadata of every eventviewer event. In the XML of the event the correlationID’s path is:
-
-```xml
-
-```
-For comparison, the rest of the fields look like:
-```xml
-valuevalue2…
-```
-
-
-**Q:** 3076/77 don’t seem to include ‘File Path’. Can this be deduced from ‘File Name’? 8028/8029 don’t seem to include ‘File Name’. Can this be deduced from ‘File Path’?
-
-**A:** “File Name” in 3076/77 is actually the path in NT form (\Device\HarddiskVolume3\Windows\System32\myfile.dll), and the “originalfilename” field maps to what would be “File Name” in a file rule in policy XML.
-For 8028/8029, File Path is the C:\ path to the file and you’ll notice a trend where we didn’t bother to include all the same fields we do for the PE files so there is no “originalFileName”.
-
-
From 0c29692554807f296bd38a0ed7d090b9a1541613 Mon Sep 17 00:00:00 2001
From: brbrahm <43386070+brbrahm@users.noreply.github.com>
Date: Wed, 15 May 2019 16:40:39 -0700
Subject: [PATCH 053/156] Some introduction updates to WDAC multiple policies
file
---
...windows-defender-application-control-policies.md | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
index 7408abf167..296060880f 100644
--- a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
+++ b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
@@ -20,9 +20,18 @@ ms.date: 05/10/2019
>[!IMPORTANT]
>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
-Beginning with Windows 10 version 1903, WDAC supports multiple code integrity policies for one device.
+The restriction of only having a single code integrity policy active on a system at any given time has felt limiting for customers in situations where multiple policies with different intents would be useful. Beginning with Windows 10 version 1903, WDAC supports multiple simultaneous code integrity policies for one device in order to light up the following scenarios:
-## Precedence
+1. Enforce and Audit Side-by-Side
+ - To validate policy changes before deploying in enforcement mode, users can now deploy an audit-mode base policy side-by-side with an existing enforcement-mode base policy
+2. Multiple Base Policies
+ - Users can enforce two or more base policies simultaneously in order to allow simpler policy targeting for policies with different scope/intent
+3. Supplemental Policies
+ - Users can deploy one or more supplemental policies to expand a base policy
+ - If two base policies exist on a device, an application has to be allowed by both to run
+ - For supplemental policies, applications that are allowed by either the base policy or its supplemental policy/policies are allowed to run
+
+## How do Base and Supplemental Policies Interact?
- Multiple base policies: intersection
- Only applications allowed by both policies run without generating block events
From 81777d60508c7cae317dd2ccecb826b7953df165 Mon Sep 17 00:00:00 2001
From: brbrahm <43386070+brbrahm@users.noreply.github.com>
Date: Wed, 15 May 2019 21:46:34 -0700
Subject: [PATCH 054/156] Removed duplicate "new supported scenarios" from
multiple policies page
---
...ndows-defender-application-control-policies.md | 15 +--------------
1 file changed, 1 insertion(+), 14 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
index 296060880f..73d0e16c9b 100644
--- a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
+++ b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
@@ -20,7 +20,7 @@ ms.date: 05/10/2019
>[!IMPORTANT]
>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
-The restriction of only having a single code integrity policy active on a system at any given time has felt limiting for customers in situations where multiple policies with different intents would be useful. Beginning with Windows 10 version 1903, WDAC supports multiple simultaneous code integrity policies for one device in order to light up the following scenarios:
+The restriction of only having a single code integrity policy active on a system at any given time has felt limiting for customers in situations where multiple policies with different intents would be useful. Beginning with Windows 10 version 1903, WDAC supports multiple simultaneous code integrity policies for one device in order to enable the following scenarios:
1. Enforce and Audit Side-by-Side
- To validate policy changes before deploying in enforcement mode, users can now deploy an audit-mode base policy side-by-side with an existing enforcement-mode base policy
@@ -38,19 +38,6 @@ The restriction of only having a single code integrity policy active on a system
- Base + supplemental policy: union
- Files that are allowed by the base policy or the supplemental policy are not blocked
-## Newly supported scenarios
-
-With the ability to support multiple CI policies, three new scenarios are supported:
-
-1. Enforce and Audit Side-by-Side (Intersection)
- - To validate policy changes before deploying in enforcement mode, deploy an audit-mode base policy side-by-side with an existing enforcement-mode base policy
-2. Multiple Base Policies (Intersection)
- - Enforce two or more base policies simultaneously to allow simpler policy targeting for policies with different scope/intent
- - Ex. Base1 is a corporate standard policy that is relatively loose to accommodate all organizations while forcing minimum corp standards (e.g. Windows works + Managed Installer + path rules). Base2 is a team-specific policy that further restricts what is allowed to run (e.g. Windows works + Managed Installer + corporate signed apps only)
-3. Supplemental Policies (Union)
- - Deploy a supplemental policy (or policies) to expand a base policy
- - Ex. The Azure host base policy restricts tightly to just allow Windows and hardware drivers. Can add a supplemental policy to allow just the additional signer rules needed to support signed code from the Exchange team.
-
## PowerShell parameters
New-CIPolicy
From df1a051291c22f15ef9ff4ab7f5a5d25d4c0b980 Mon Sep 17 00:00:00 2001
From: brbrahm <43386070+brbrahm@users.noreply.github.com>
Date: Wed, 15 May 2019 21:54:11 -0700
Subject: [PATCH 055/156] Add intro to COM objects page
---
...-windows-defender-application-control-policy.md | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md b/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
index 9cd8ba8357..4131cedc9a 100644
--- a/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
+++ b/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
@@ -22,7 +22,13 @@ ms.date: 05/14/2019
The [Microsoft Component Object Model (COM)](https://docs.microsoft.com/windows/desktop/com/the-component-object-model) is a platform-independent, distributed, object-oriented system for creating binary software components that can interact. COM specifies an object model and programming requirements that enable COM objects to interact with other objects.
-Get GUID of application to allow by either:
+### COM object configurability in WDAC policy
+
+Prior to the Windows 10 1903 update, Windows Defender Application Control (WDAC) enforced a built-in allow list for COM object registration. While this mechanism works for most common application usage scenarios, customers have provided feedback that there are cases where additional COM objects need to be allowed. The 1903 update to Windows 10 introduces the ability to specify allowed COM objects via their GUID in the WDAC policy.
+
+### Get COM object GUID
+
+Get GUID of application to allow in one of the following ways:
- Finding block event in Event Viewer (Application and Service Logs > Microsoft > Windows > AppLocker > MSI and Script) and extracting GUID
- Creating audit policy (using New-CIPolicy –Audit), potentially with specific provider, and use info from block events to get GUID
@@ -32,11 +38,11 @@ Three elements:
- Provider: platform on which code is running (values are Powershell, WSH, IE, VBA, MSI, or a wildcard “AllHostIds”)
- Key: GUID for the program you with to run, in the format Key="{33333333-4444-4444-1616-161616161616}"
- ValueName: needs to be set to "EnterpriseDefinedClsId"
+
One attribute:
- Value: needs to be “true” for allow and “false” for deny
- Note: without quotation marks
- Note: deny only works in base policies
-- The setting needs to be placed in the order of ASCII values, first by Provider, then Key, then ValueName
+ - Note that deny only works in base policies, not supplemental
+- The setting needs to be placed in the order of ASCII values (first by Provider, then Key, then ValueName)
### Examples
From 373c66f301b9ce3488857dfc59ba67f2b0e131a0 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Thu, 16 May 2019 10:29:51 -0700
Subject: [PATCH 056/156] syntax fixes
---
...n-windows-defender-application-control-policy.md | 1 +
.../create-path-based-rules.md | 6 ++++++
...windows-defender-application-control-policies.md | 13 +++++++++++++
.../select-types-of-rules-to-create.md | 6 ++++++
4 files changed, 26 insertions(+)
diff --git a/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md b/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
index 9cd8ba8357..4e19b9193b 100644
--- a/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
+++ b/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
@@ -32,6 +32,7 @@ Three elements:
- Provider: platform on which code is running (values are Powershell, WSH, IE, VBA, MSI, or a wildcard “AllHostIds”)
- Key: GUID for the program you with to run, in the format Key="{33333333-4444-4444-1616-161616161616}"
- ValueName: needs to be set to "EnterpriseDefinedClsId"
+
One attribute:
- Value: needs to be “true” for allow and “false” for deny
Note: without quotation marks
diff --git a/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md b/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
index 852c003dc0..29db07a119 100644
--- a/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
+++ b/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
@@ -24,18 +24,23 @@ Beginning with Windows 10 version 1903, Windows Defender Application Control (WD
- New-CIPolicy parameters
- FilePath: create path rules under path \ for anything not user-writeable (at the individual file level)
+
```powershell
New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
```
+
Optionally, add -UserWriteablePaths to ignore user writeability
- FilePathRule: create a rule where filepath string is directly set to value of \
+
```powershell
New-CIPolicyRule -FilePathRule
```
+
Useful for wildcards like C:\foo\\*
- Usage follows the same flow as per-app rules:
+
```powershell
$rules = New-CIPolicyRule …
$rules += New-CIPolicyRule …
@@ -53,6 +58,7 @@ Beginning with Windows 10 version 1903, Windows Defender Application Control (WD
- %OSDRIVE%\\...
- Disable default FilePath rule protection of enforcing user-writeability. For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy:
+
```powershell
Set-RuleOption -o 18 .\policy.xml
```
diff --git a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
index 7408abf167..2e1842d5c0 100644
--- a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
+++ b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
@@ -34,10 +34,14 @@ Beginning with Windows 10 version 1903, WDAC supports multiple code integrity po
With the ability to support multiple CI policies, three new scenarios are supported:
1. Enforce and Audit Side-by-Side (Intersection)
+
- To validate policy changes before deploying in enforcement mode, deploy an audit-mode base policy side-by-side with an existing enforcement-mode base policy
+
2. Multiple Base Policies (Intersection)
+
- Enforce two or more base policies simultaneously to allow simpler policy targeting for policies with different scope/intent
- Ex. Base1 is a corporate standard policy that is relatively loose to accommodate all organizations while forcing minimum corp standards (e.g. Windows works + Managed Installer + path rules). Base2 is a team-specific policy that further restricts what is allowed to run (e.g. Windows works + Managed Installer + corporate signed apps only)
+
3. Supplemental Policies (Union)
- Deploy a supplemental policy (or policies) to expand a base policy
- Ex. The Azure host base policy restricts tightly to just allow Windows and hardware drivers. Can add a supplemental policy to allow just the additional signer rules needed to support signed code from the Exchange team.
@@ -83,8 +87,11 @@ New-CiPolicy -MulitplePolicyFormat -foo –bar
- **MultiplePolicyFormat** switch results in 1) random GUIDs being generated for the policy ID and 2) the policy type being specified as base.
Can optionally choose to make it supplementable:
+
- Set-RuleOption has a new option **Enabled:Allow Supplemental Policies** to set for base policy
+
- For signed policies that are being made supplementable, need to ensure that supplemental signers are defined. Use “Add-SignerRule” to provide supplemental signers.
+
```powershell
Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
```
@@ -92,18 +99,24 @@ New-CiPolicy -MulitplePolicyFormat -foo –bar
**Scenario #2: Creating a new supplemental policy**
1. Scan using `New-CiPolicy –MuliplePolicyFormat` to generate a base policy:
+
```powershell
New-CIPolicy -Level PcaCertificate -UserPEs -ScanPath -MultiplePolicyFormat 3> -FilePath
```
+
2. Change this new base policy to a supplemental policy
+
- Provide path of base in `Set-CIPolicyIdInfo –BasePolicytoSupplementPath`
- Provide GUID of base in `Set-CIPolicyIdInfo –SupplementsBasePolicyID`
+
```powershell
Set-CIPolicyIdInfo -BasePolicyToSupplementPath -SupplementsBasePolicyID -FilePath
```
+
- Can revert the policy back to being a base policy using `-ResetPolicyID`
**Scenario #3: Merging policies**
- When merging, the policy type and ID of the leftmost/first policy specified is used
+
- If the leftmost is a base policy with ID , then regardless of what the GUIDS and types are for any subsequent policies, the merged policy will be a base policy with ID
diff --git a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
index ccf9c4559b..342163da92 100644
--- a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
+++ b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md
@@ -109,18 +109,23 @@ Beginning with Windows 10 version 1903, Windows Defender Application Control (WD
- New-CIPolicy parameters
- FilePath: create path rules under path \ for anything not user-writeable (at the individual file level)
+
```powershell
New-CIPolicy -f .\mypolicy.xml -l FilePath -s -u
```
+
Optionally, add -UserWriteablePaths to ignore user writeability
- FilePathRule: create a rule where filepath string is directly set to value of \
+
```powershell
New-CIPolicyRule -FilePathRule
```
+
Useful for wildcards like C:\foo\\*
- Usage follows the same flow as per-app rules:
+
```powershell
$rules = New-CIPolicyRule …
$rules += New-CIPolicyRule …
@@ -138,6 +143,7 @@ Beginning with Windows 10 version 1903, Windows Defender Application Control (WD
- %OSDRIVE%\\...
- Disable default FilePath rule protection of enforcing user-writeability. For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy:
+
```powershell
Set-RuleOption -o 18 .\policy.xml
```
From 3b41700ac303962aca1149d250c8aef11c09f49d Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Thu, 16 May 2019 12:43:59 -0700
Subject: [PATCH 057/156] edits to title
---
...tion-in-windows-defender-application-control-policy.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md b/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
index 4e19b9193b..09fb275743 100644
--- a/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
+++ b/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
@@ -1,16 +1,16 @@
---
-title: Windows Defender Application Control path-based rules (Windows 10)
-description: Windows Defender Application Control restricts which applications users are allowed to run and the code that runs in the system core.
+title: Allow COM object registration in a Windows Defender Application Control policy (Windows 10)
+description: You can allow COM object registration in a Windows Defender Application Control policy.
ms.prod: w10
ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
author: jsuther1974
-ms.date: 05/14/2019
+ms.date: 05/16/2019
---
-# COM Whitelisting
+# Allow COM object registration in a Windows Defender Application Control policy
**Applies to:**
From 68ec9c0da46a6f374524b62708afa06ca36ac8a4 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Thu, 16 May 2019 13:38:21 -0700
Subject: [PATCH 058/156] fixed syntax
---
...ith-windows-defender-application-control.md | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md b/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md
index 0cac5a2d54..497501f819 100644
--- a/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md
+++ b/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md
@@ -53,36 +53,52 @@ Just as there are differences in managing each rule collection, you need to mana
You can use `New-CIPolicyRule -Package $Package -Deny` to block packaged apps:
1. Get the info about an installed package.
+
```powershell
$package = Get-AppxPackage -name
```
+
Dependencies field in output is full Package object, can be accessed and passed directly to New-CIPolicyRule.
+
2. Make a rule.
+
```powershell
$Rule = New-CIPolicyRule -Package $package -deny
```
+
3. Repeat for other packages you want to block using $rule +=….
-4. Make a policy for just the blocks you created for packages.
+4. Make a policy for just the blocks you created for packages.
+
```powershell
New-CIpolicy -rules $rule -f .\policy.xml -u
```
+
5. Merge with allow windows policy, or you could also use examplepolicies\AllowAll.xml.
+
```powershell
Merge-CIPolicy -PolicyPaths .\policy.xml,C:\windows\Schemas\codeintegrity\examplepolicies\DefaultWindows_Audit.xml -o allowWindowsDenyPackages.xml
```
+
6. Disable audit mode.
+
```powershell
Set-RuleOption -o 3 -Delete .\allowWindowsDenyPackages.xml
```
+
7. Enable invalidate EAs on reboot.
+
```powershell
Set-RuleOption -o 15 .\allowWindowsDenyPackages.xml
```
+
8. Compile the policy
+
```powershell
ConvertFrom-CIPolicy .\AllowWindowsDenyPackages.xml C:\compiledpolicy.bin
```
+
9. Install the policy withwout restarting.
+
```powershell
Invoke-CimMethod -Namespace root\Microsoft\Windows\CI -ClassName PS_UpdateAndCompareCIPolicy -MethodName Update -Arguments @{FilePath = "C:\compiledpolicy.bin"}
```
From ff61a29b9b9f684de59ba3d1ab6759f555007a4a Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 13:43:10 -0700
Subject: [PATCH 059/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...ponents-to-microsoft-services-using-MDM.md | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
index 58a96778b5..381e5fef6e 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
@@ -16,7 +16,7 @@ ms.date: 3/1/2019
**Applies to**
-- Windows 10 Enterprise 1903 version and later
+- Windows 10 Enterprise 1903 version and newer
You can use Microsoft InTune with MDM CSPs and custom [OMA URIs](https://docs.microsoft.com/en-us/intune/custom-settings-windows-10) to minimize connections from Windows to Microsoft services, or to configure particular privacy settings. You can configure diagnostic data at the lowest level for your edition of Windows, and also evaluate which other connections Windows makes to Microsoft services you want to turn off in your environment from the list in this article.
@@ -30,7 +30,7 @@ For more information on Microsoft InTune please see [Transform IT service delive
For detailed information about managing network connections to Microsoft services using Baseline package/registries/Group policies/UI/Command line, see [Manage connections from Windows operating system components to Microsoft services](https://docs.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services).
-### Settings for Windows 10 Enterprise edition 1903 and later
+### Settings for Windows 10 Enterprise edition 1903 and newer
The following table lists management options for each setting.
@@ -116,7 +116,20 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
| | [DeliveryOptimization/DODownloadMode](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dodownloadmode)| Specifies the download method that Delivery Optimization can use in downloads of Windows Updates, Apps and App updates. Set to **100** - Bypass mode. Do not use Delivery Optimization and use BITS instead. Added in Windows 10, version 1607.
| 28. Windows Update | [Update/AllowAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) | Control automatic updates.
**0**: notify the user before downloading the update
**1**: auto install the update and then notify the user to schedule a device restart
**2**: auto install and restart (default)
**3**: auto install and restart at a specified time
**4**: auto install and restart without end-user control
**5**: turn off automatic updates
-
+### Allowed (aka "Whitelisted") traffic for Microsoft InTune / MDM configurations
+| Endpoint of Allowed traffic |
+| --- |
+|ctldl.windowsupdate.com|
+|cdn.onenote.net|
+|r.manage.microsoft.com|
+|tile-service.weather.microsoft.com|
+|settings-win.data.microsoft.com|
+|client.wns.windows.com|
+|dm3p.wns.windows.com|
+|crl.microsoft.com/pki/crl/*|
+|www.microsoft.com/pkiops/crl/*|
+|activation-v2.sls.microsoft.com/*|
+|ocsp.digicert.com/*|
From de27d90092f80321a0c9a7b3570cecabd5650c63 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 13:44:27 -0700
Subject: [PATCH 060/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...rating-system-components-to-microsoft-services-using-MDM.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
index 381e5fef6e..47198dac47 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
@@ -117,7 +117,8 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
| 28. Windows Update | [Update/AllowAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) | Control automatic updates.
**0**: notify the user before downloading the update
**1**: auto install the update and then notify the user to schedule a device restart
**2**: auto install and restart (default)
**3**: auto install and restart at a specified time
**4**: auto install and restart without end-user control
**5**: turn off automatic updates
### Allowed (aka "Whitelisted") traffic for Microsoft InTune / MDM configurations
-| Endpoint of Allowed traffic |
+
+|**Allowed traffic endpoints** |
| --- |
|ctldl.windowsupdate.com|
|cdn.onenote.net|
From c8b453df2fd9b0083ee15ddbac0fe1017c0608fe Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 13:45:21 -0700
Subject: [PATCH 061/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...ating-system-components-to-microsoft-services-using-MDM.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
index 47198dac47..5b371ce302 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
@@ -117,7 +117,7 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
| 28. Windows Update | [Update/AllowAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) | Control automatic updates.
**0**: notify the user before downloading the update
**1**: auto install the update and then notify the user to schedule a device restart
**2**: auto install and restart (default)
**3**: auto install and restart at a specified time
**4**: auto install and restart without end-user control
**5**: turn off automatic updates
### Allowed (aka "Whitelisted") traffic for Microsoft InTune / MDM configurations
-
+
|**Allowed traffic endpoints** |
| --- |
|ctldl.windowsupdate.com|
@@ -128,7 +128,7 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
|client.wns.windows.com|
|dm3p.wns.windows.com|
|crl.microsoft.com/pki/crl/*|
-|www.microsoft.com/pkiops/crl/*|
+|*microsoft.com/pkiops/crl/*|
|activation-v2.sls.microsoft.com/*|
|ocsp.digicert.com/*|
From 6518bebae843fc8b7d902d20dd57293d7204ef53 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 13:46:38 -0700
Subject: [PATCH 062/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...erating-system-components-to-microsoft-services-using-MDM.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
index 5b371ce302..917e71196f 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
@@ -128,7 +128,7 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
|client.wns.windows.com|
|dm3p.wns.windows.com|
|crl.microsoft.com/pki/crl/*|
-|*microsoft.com/pkiops/crl/*|
+|*microsoft.com/pkiops/crl/**|
|activation-v2.sls.microsoft.com/*|
|ocsp.digicert.com/*|
From efa711233502e9695cf9887f324005da1c7d823d Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 13:47:34 -0700
Subject: [PATCH 063/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...ating-system-components-to-microsoft-services-using-MDM.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
index 917e71196f..5f3cce836a 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
@@ -117,7 +117,9 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
| 28. Windows Update | [Update/AllowAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) | Control automatic updates.
**0**: notify the user before downloading the update
**1**: auto install the update and then notify the user to schedule a device restart
**2**: auto install and restart (default)
**3**: auto install and restart at a specified time
**4**: auto install and restart without end-user control
**5**: turn off automatic updates
### Allowed (aka "Whitelisted") traffic for Microsoft InTune / MDM configurations
-
+
+
+
|**Allowed traffic endpoints** |
| --- |
|ctldl.windowsupdate.com|
From a8272559d158d34bc12cf1844e969a53aa8df09d Mon Sep 17 00:00:00 2001
From: brbrahm <43386070+brbrahm@users.noreply.github.com>
Date: Thu, 16 May 2019 13:47:58 -0700
Subject: [PATCH 064/156] Update
deploy-multiple-windows-defender-application-control-policies.md
---
...s-defender-application-control-policies.md | 80 ++++++-------------
1 file changed, 26 insertions(+), 54 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
index 73d0e16c9b..4484f5fbe6 100644
--- a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
+++ b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
@@ -26,9 +26,10 @@ The restriction of only having a single code integrity policy active on a system
- To validate policy changes before deploying in enforcement mode, users can now deploy an audit-mode base policy side-by-side with an existing enforcement-mode base policy
2. Multiple Base Policies
- Users can enforce two or more base policies simultaneously in order to allow simpler policy targeting for policies with different scope/intent
+ - If two base policies exist on a device, an application has to be allowed by both to run
3. Supplemental Policies
- Users can deploy one or more supplemental policies to expand a base policy
- - If two base policies exist on a device, an application has to be allowed by both to run
+ - A supplemental policy expands a single base policy, and multiple supplemental policies can expand the same base policy
- For supplemental policies, applications that are allowed by either the base policy or its supplemental policy/policies are allowed to run
## How do Base and Supplemental Policies Interact?
@@ -38,68 +39,39 @@ The restriction of only having a single code integrity policy active on a system
- Base + supplemental policy: union
- Files that are allowed by the base policy or the supplemental policy are not blocked
-## PowerShell parameters
+## Creating Multiple Base or Supplemental Policies
-New-CIPolicy
-- MultiplePolicyFormat: allows for multiple policies
+Note that multiple policies will not work on pre-1903 systems.
+### Allow Multiple Policies
+
+In order to allow multiple policies to exist and take effect on a single system, policies must be created using the new Multiple Policy Format. The "MultiplePolicyFormat" switch in New-CIPolicy results in 1) random GUIDs being generated for the policy ID and 2) the policy type being specified as base.
```powershell
-New-CIPolicy [-FilePath] -Level {None | Hash | FileName | SignedVersion | Publisher | FilePublisher | LeafCertificate | PcaCertificate | RootCertificate | WHQL | WHQLPublisher | WHQLFilePublisher | PFN | FilePath}
- [-DriverFiles ] [-Fallback {None | Hash | FileName | SignedVersion | Publisher | FilePublisher | LeafCertificate | PcaCertificate | RootCertificate | WHQL | WHQLPublisher | WHQLFilePublisher | PFN | FilePath}]
- [-Audit] [-ScanPath ] [-ScriptFileNames] [-AllowFileNameFallbacks] [-SpecificFileNameLevel {None | OriginalFileName | InternalName | FileDescription | ProductName | PackageFamilyName | FilePath}] [-UserPEs] [-NoScript]
- [-Deny] [-NoShadowCopy] [-MultiplePolicyFormat] [-OmitPaths ] [-PathToCatroot ] [] – to generate new policy format(base policy and policy type and policy guid)
+New-CIPolicy -MultiplePolicyFormat -foo –bar
```
-Set-CIPolicyIdInfo
-- **SupplementsBasePolicyID**: guid of new supplemental policy
-- **BasePolicyToSupplementPath**: base policy that the supplemental policy applies to
-- **ResetPolicyID**: reset the policy guids back to a random guid
+Optionally, you can choose to make the new base policy supplementable (allow supplemental policies).
+```powershell
+Set-RuleOption -FilePath Enabled:Allow Supplemental Policies
+```
+
+For signed base policies that are being made supplementable, you need to ensure that supplemental signers are defined. Use the "Supplemental" switch in Add-SignerRule to provide supplemental signers.
+ ```powershell
+ Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
+ ```
+
+### Supplemental Policy Creation
+
+In order to create a supplemental policy, begin by creating a new policy in the Multiple Policy Format. From there, use Set-CIPolicyIdInfo to convert it to a supplemental policy and specify which base policy it expands.
+- "SupplementsBasePolicyID": guid of new supplemental policy
+- "BasePolicyToSupplementPath": base policy that the supplemental policy applies to
```powershell
Set-CIPolicyIdInfo [-FilePath] [-PolicyName ] [-SupplementsBasePolicyID ] [-BasePolicyToSupplementPath ] [-ResetPolicyID] [-PolicyId ] []
```
-Add-SignerRule
-- **Supplemental**: provides supplemental signers
+Note that "ResetPolicyId" reverts a supplemental policy to a base policy, and resets the policy guids back to a random guid.
-```powershell
-Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
-```
+### Merging policies
-Set-RuleOption
-- **Enabled:Allow Supplemental Policies**: makes base policy able to be supplemented
-
-### Examples
-
-**Scenario #1: Creating a new base policy**
-
-```powershell
-New-CiPolicy -MulitplePolicyFormat -foo –bar
-```
-
-- **MultiplePolicyFormat** switch results in 1) random GUIDs being generated for the policy ID and 2) the policy type being specified as base.
- Can optionally choose to make it supplementable:
- - Set-RuleOption has a new option **Enabled:Allow Supplemental Policies** to set for base policy
-- For signed policies that are being made supplementable, need to ensure that supplemental signers are defined. Use “Add-SignerRule” to provide supplemental signers.
- ```powershell
- Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
- ```
-
-**Scenario #2: Creating a new supplemental policy**
-
-1. Scan using `New-CiPolicy –MuliplePolicyFormat` to generate a base policy:
- ```powershell
- New-CIPolicy -Level PcaCertificate -UserPEs -ScanPath -MultiplePolicyFormat 3> -FilePath
- ```
-2. Change this new base policy to a supplemental policy
- - Provide path of base in `Set-CIPolicyIdInfo –BasePolicytoSupplementPath`
- - Provide GUID of base in `Set-CIPolicyIdInfo –SupplementsBasePolicyID`
- ```powershell
- Set-CIPolicyIdInfo -BasePolicyToSupplementPath -SupplementsBasePolicyID -FilePath
- ```
- - Can revert the policy back to being a base policy using `-ResetPolicyID`
-
-**Scenario #3: Merging policies**
-
-- When merging, the policy type and ID of the leftmost/first policy specified is used
- - If the leftmost is a base policy with ID , then regardless of what the GUIDS and types are for any subsequent policies, the merged policy will be a base policy with ID
+When merging, the policy type and ID of the leftmost/first policy specified is used. If the leftmost is a base policy with ID , then regardless of what the GUIDS and types are for any subsequent policies, the merged policy will be a base policy with ID .
From 81aaa14e58f21cfaf4659e5593f22e16b0fcc446 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 13:57:32 -0700
Subject: [PATCH 065/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...erating-system-components-to-microsoft-services-using-MDM.md | 2 --
1 file changed, 2 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
index 5f3cce836a..0210fa442d 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
@@ -118,8 +118,6 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
### Allowed (aka "Whitelisted") traffic for Microsoft InTune / MDM configurations
-
-
|**Allowed traffic endpoints** |
| --- |
|ctldl.windowsupdate.com|
From 63a0f2e1345b144a90d55cf8bd623c1e12a9d786 Mon Sep 17 00:00:00 2001
From: brbrahm <43386070+brbrahm@users.noreply.github.com>
Date: Thu, 16 May 2019 14:37:28 -0700
Subject: [PATCH 066/156] Additional content to packaged apps
---
...th-windows-defender-application-control.md | 77 +++++++++++++------
1 file changed, 53 insertions(+), 24 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md b/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md
index 497501f819..d1d521cfb4 100644
--- a/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md
+++ b/windows/security/threat-protection/windows-defender-application-control/manage-packaged-apps-with-windows-defender-application-control.md
@@ -11,23 +11,23 @@ author: jsuther1974
ms.date: 05/14/2019
---
-# Manage packaged apps with Windows Defender Application Control
+# Manage Packaged Apps with Windows Defender Application Control
**Applies to:**
- Windows 10
- Windows Server 2016
-This topic for IT professionals describes concepts and lists procedures to help you manage Packaged apps with Windows Defender Application Control (WDAC) as part of your overall application control strategy.
+This topic for IT professionals describes concepts and lists procedures to help you manage packaged apps with Windows Defender Application Control (WDAC) as part of your overall application control strategy.
-## Understanding Packaged apps and Packaged app installers
+## Understanding Packaged Apps and Packaged App Installers
Packaged apps, also known as Universal Windows apps, are based on a model that ensures all the files within an app package share the same identity. With classic Windows apps, each file within the app could have a unique identity.
With packaged apps, it is possible to control the entire app by using a single WDAC rule.
Typically, an app consists of multiple components: the installer that is used to install the app, and one or more exes, dlls, or scripts. With classic Windows apps, these components don't always share common attributes such as the software’s publisher name, product name, and product version. Therefore, WDAC controls each of these components separately through different rule collections, such as exe, dll, script, and Windows Installer rules. In contrast, all the components of a packaged app share the same publisher name, package name, and package version attributes. Therefore, you can control an entire app with a single rule.
-### Comparing classic Windows apps and packaged apps
+### Comparing classic Windows Apps and Packaged Apps
WDAC policies for packaged apps can only be applied to apps installed on computers running at least Windows Server 2012 or Windows 8, but classic Windows apps can be controlled on devices running at least Windows Server
2008 R2 or Windows 7. The rules for classic Windows apps and packaged apps can be enforced in tandem. The differences between packaged apps and classic Windows apps that you should consider include:
@@ -38,54 +38,55 @@ WDAC policies for packaged apps can only be applied to apps installed on compute
WDAC uses different rule collections to control packaged apps and classic Windows apps. You have the choice to control one type, the other type, or both.
-## Using WDAC to manage packaged apps
+## Using WDAC to Manage Packaged Apps
Just as there are differences in managing each rule collection, you need to manage the packaged apps with the following strategy:
-1. Gather information about which Packaged apps are running in your environment.
+1. Gather information about which packaged apps are running in your environment.
2. Create WDAC rules for specific packaged apps based on your policy strategies. For more information, see [Deploy WDAC policy rules and file rules](select-types-of-rules-to-create.md).
3. Continue to update the WDAC policies as new package apps are introduced into your environment. To do this, see [Merge WDAC policies](merge-windows-defender-application-control-policies.md).
-## Blocking packaged apps
+## Blocking Packaged Apps
-You can use `New-CIPolicyRule -Package $Package -Deny` to block packaged apps:
+You can now use `New-CIPolicyRule -Package $Package -Deny` to block packaged apps.
-1. Get the info about an installed package.
+### Blocking Packaged Apps Which Are Installed on the System
+
+Below are the list of steps you can follow to block one or more packaged apps in the case that the apps are on the system you are using the WDAC PowerShell cmdlets on:
+
+1. Get the app identifier for an installed package
```powershell
- $package = Get-AppxPackage -name
+ $package = Get-AppxPackage -name
```
-
- Dependencies field in output is full Package object, can be accessed and passed directly to New-CIPolicyRule.
-
-2. Make a rule.
+2. Make a rule by using the New-CIPolicyRule cmdlet
```powershell
$Rule = New-CIPolicyRule -Package $package -deny
```
+3. Repeat for other packages you want to block using $rule +=…
-3. Repeat for other packages you want to block using $rule +=….
-4. Make a policy for just the blocks you created for packages.
+4. Make a policy for just the blocks you created for packages
```powershell
New-CIpolicy -rules $rule -f .\policy.xml -u
```
-5. Merge with allow windows policy, or you could also use examplepolicies\AllowAll.xml.
+5. Merge with an existing policy that authorizes the other applications and system components required for your scenario. Here we use the sample Allow Windows policy
```powershell
Merge-CIPolicy -PolicyPaths .\policy.xml,C:\windows\Schemas\codeintegrity\examplepolicies\DefaultWindows_Audit.xml -o allowWindowsDenyPackages.xml
```
-6. Disable audit mode.
+6. Disable audit mode if needed
```powershell
Set-RuleOption -o 3 -Delete .\allowWindowsDenyPackages.xml
```
-7. Enable invalidate EAs on reboot.
+7. Enable invalidate EAs on reboot
```powershell
Set-RuleOption -o 15 .\allowWindowsDenyPackages.xml
@@ -97,13 +98,41 @@ You can use `New-CIPolicyRule -Package $Package -Deny` to block packaged apps:
ConvertFrom-CIPolicy .\AllowWindowsDenyPackages.xml C:\compiledpolicy.bin
```
-9. Install the policy withwout restarting.
+9. Install the policy without restarting
```powershell
Invoke-CimMethod -Namespace root\Microsoft\Windows\CI -ClassName PS_UpdateAndCompareCIPolicy -MethodName Update -Arguments @{FilePath = "C:\compiledpolicy.bin"}
```
+### Blocking Packaged Apps Which Are Not Installed on the System
-After doing this on the next build of Dev3, for the apps that you blocked, already installed apps should fail to launch, and should you put this policy on another machine that hasn’t yet installed the apps, store should block them from being purchased/installed.
-If you wanted to make a rule for an app that isn’t already installed, first make a rule for an app that is. Then for the app you want to actually block take the store URL (from store page click … then share, then copy link to get something like: https://www.microsoft.com/store/productId/9WZDNCRFJ3TJ) and grab the hash code at the end (in bold) then replace the bolded bit below:
-https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9wzdncrfj3tj/applockerdata
-then grab packagefamilyname and replace the one in the xml you got in step 4 with the PFN from the link above, then run through 5-9 again.
+If the app you intend to block is not installed on the system you are using the WDAC PowerShell cmdlets on, then follow the steps below:
+
+1. Create a dummy rule using Steps 1-5 in the Blocking Packaged Apps Which Are Installed on the System section above
+
+2. Navigate to the app you want to block on the Store website
+
+3. Copy the GUID in the URL for the app
+ - Example: the GUID for the Microsoft To-Do app is 9nblggh5r558
+ - https://www.microsoft.com/en-us/p/microsoft-to-do-list-task-reminder/9nblggh5r558?activetab=pivot:overviewtab
+4. Use the GUID in the following REST query URL to retrieve the identifiers for the app
+ - Example: for the Microsoft To-Do app, the URL would be https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9nblggh5r558/applockerdata
+ - The URL will return:
+
+ ```
+ { "packageFamilyName": "Microsoft.Todos_8wekyb3d8bbwe",
+ "packageIdentityName": "Microsoft.Todos",
+ "windowsPhoneLegacyId": "6088f001-776c-462e-984d-25b6399c6607",
+ "publisherCertificateName": "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"
+ }
+ ```
+
+5. Use the value returned by the query URL for the packageFamilyName to replace the package name generated earlier in the dummy rule from Step 1.
+
+## Allowing Packaged Apps
+The method for allowing specific packaged apps is similar to the method outlined above for blocking packaged apps, with the only difference being the parameter to the New-CIPolicyRule cmdlet.
+
+```powershell
+$Rule = New-CIPolicyRule -Package $package -allow
+```
+
+Since a lot of system apps are packaged apps, it is generally advised that customers rely on the sample policies in C:\Windows\schemas\CodeIntegrity\ExamplePolicies to help allow all inbox apps by the Store signature already included in the policies and control apps with deny rules.
From 7f6b20f84cd84c4abc9d848586a0f5ed1ff9875e Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 14:39:26 -0700
Subject: [PATCH 067/156] Update TOC.md
---
windows/privacy/TOC.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/TOC.md b/windows/privacy/TOC.md
index f1214e7bec..3c6f3b4f16 100644
--- a/windows/privacy/TOC.md
+++ b/windows/privacy/TOC.md
@@ -26,4 +26,4 @@
### [Windows 10, version 1803, connection endpoints for non-Enterprise editions](windows-endpoints-1803-non-enterprise-editions.md)
### [Windows 10, version 1709, connection endpoints for non-Enterprise editions](windows-endpoints-1709-non-enterprise-editions.md)
## [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
-## [Manage connections from Windows operating system components to Microsoft services using MDM](configure-connections-to-microsoft-services-with-mdm.md)
+## [Manage connections from Windows operating system components to Microsoft services using MDM](manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md)
From 14f76766db500c66185a878b82f0885271512ac2 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 17:08:21 -0700
Subject: [PATCH 068/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...system-components-to-microsoft-services.md | 54 +++++++++++++++++--
1 file changed, 50 insertions(+), 4 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index b86d3299d7..c6de4234bd 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -8,12 +8,12 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.localizationpriority: medium
audience: ITPro
-author: danihalfin
-ms.author: daniha
-manager: dansimp
+author: medgarmedgar
+ms.author: v-medgar
+manager: sanashar
ms.collection: M365-security-compliance
ms.topic: article
-ms.date: 06/05/2018
+ms.date: 05/16/2019
---
# Manage connections from Windows operating system components to Microsoft services
@@ -95,6 +95,8 @@ The following table lists management options for each setting, beginning with Wi
| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |
| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |
| [18.21 Inking & Typing](#bkmk-priv-ink) |  | |  |
+| [18.22 Activity History](#bkmk-act-history) |  | |  |
+| [18.23 Voice Activation](#bkmk-voice-act) |  | |  |
| [19. Software Protection Platform](#bkmk-spp) | |  |  |
| [20. Storage Health](#bkmk-storage-health) | |  |  |
| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |
@@ -205,6 +207,8 @@ See the following table for a summary of the management settings for Windows Ser
| [18.19 Tasks](#bkmk-priv-tasks) |  |  |  |
| [18.20 App Diagnostics](#bkmk-priv-diag) |  |  |  |
| [18.21 Inking & Typing](#bkmk-priv-ink) |  | |  |
+| [18.22 Activity History](#bkmk-act-history) |  | |  |
+| [18.23 Voice Activation](#bkmk-voice-act) |  | |  |
| [19. Software Protection Platform](#bkmk-spp) | |  |  |
| [20. Storage Health](#bkmk-storage-health) | |  |  |
| [21. Sync your settings](#bkmk-syncsettings) |  |  |  |
@@ -813,6 +817,10 @@ Use Settings > Privacy to configure some settings that may be important to yo
- [18.21 Inking & Typing](#bkmk-priv-ink)
+- [18.22 Activity History](#bkmk-act-history)
+
+- [18.23 Voice Activation(#bkmk-voice-act)
+
### 18.1 General
**General** includes options that don't fall into other areas.
@@ -1424,6 +1432,44 @@ If you're running at least Windows 10, version 1703, you can turn off updates to
- Create a REG_DWORD registry setting named **AllowSpeechModelUpdate** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Speech** with a **value of 0 (zero)**
+
+
+### 18.22 Activity History
+In the **Activity History** area, you can choose turn of tracking of your Activity History.
+
+To turn this Off:
+
+ - Turn **Off** the feature in the UI by going to Settings -> Privacy -> Activity History and **un-checking** the **Store my activity history on this device** AND **unchecking** the **Send my activity History to Microsoft** checkboxes.
+
+-OR-
+
+ - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Enables Activity Feed**.
+
+ -and-
+
+ - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow publishing of User Activities**.
+
+ -and-
+
+ - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow upload of User Activities**
+
+
+-OR-
+
+ - Create a REG_DWORD registry setting named **EnableActivityFeed** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+
+ -and-
+
+ - Create a REG_DWORD registry setting named **PublishUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+
+ -and-
+
+ - Create a REG_DWORD registry setting named **UploadUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+
+
+### 18.23 Voice Activation
+
+
> [!NOTE]
> Releases 1803 and earlier support **Speech, Inking, & Typing** as a combined settings area. For customizing those setting please follow the below instructions. For 1809 and above **Speech** and **Inking & Typing** are separate settings pages, please see the specific section (18.6 Speech or 18.21 Inking and Typing) above for those areas.
From 8a0dd6b4d021f69bcbe844923c43343bf61e1b6a Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 17:11:21 -0700
Subject: [PATCH 069/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...system-components-to-microsoft-services.md | 20 +++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index c6de4234bd..6b2b34cfb1 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -819,7 +819,7 @@ Use Settings > Privacy to configure some settings that may be important to yo
- [18.22 Activity History](#bkmk-act-history)
-- [18.23 Voice Activation(#bkmk-voice-act)
+- [18.23 Voice Activation](#bkmk-voice-act)
### 18.1 General
@@ -1434,40 +1434,40 @@ If you're running at least Windows 10, version 1703, you can turn off updates to
-### 18.22 Activity History
+### 18.22 Activity History
In the **Activity History** area, you can choose turn of tracking of your Activity History.
To turn this Off:
- - Turn **Off** the feature in the UI by going to Settings -> Privacy -> Activity History and **un-checking** the **Store my activity history on this device** AND **unchecking** the **Send my activity History to Microsoft** checkboxes.
+ - Turn **Off** the feature in the UI by going to Settings -> Privacy -> Activity History and **un-checking** the **Store my activity history on this device** AND **unchecking** the **Send my activity History to Microsoft** checkboxes.
-OR-
- - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Enables Activity Feed**.
+ - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Enables Activity Feed**.
-and-
- - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow publishing of User Activities**.
+ - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow publishing of User Activities**.
-and-
- - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow upload of User Activities**
+ - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow upload of User Activities**
-OR-
- - Create a REG_DWORD registry setting named **EnableActivityFeed** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+ - Create a REG_DWORD registry setting named **EnableActivityFeed** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
-and-
- - Create a REG_DWORD registry setting named **PublishUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+ - Create a REG_DWORD registry setting named **PublishUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
-and-
- - Create a REG_DWORD registry setting named **UploadUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+ - Create a REG_DWORD registry setting named **UploadUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
-### 18.23 Voice Activation
+### 18.23 Voice Activation
> [!NOTE]
From 20757790a2a95050ca708859a333673ab2681e01 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 17:14:20 -0700
Subject: [PATCH 070/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...ows-operating-system-components-to-microsoft-services.md | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 6b2b34cfb1..ffd5fd2f7e 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1432,8 +1432,6 @@ If you're running at least Windows 10, version 1703, you can turn off updates to
- Create a REG_DWORD registry setting named **AllowSpeechModelUpdate** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Speech** with a **value of 0 (zero)**
-
-
### 18.22 Activity History
In the **Activity History** area, you can choose turn of tracking of your Activity History.
@@ -1445,11 +1443,11 @@ To turn this Off:
- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Enables Activity Feed**.
- -and-
+ -and-
- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow publishing of User Activities**.
- -and-
+ -and-
- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow upload of User Activities**
From e04b61d04f8c00aa0451e5892f5c539b0a938719 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 17:16:03 -0700
Subject: [PATCH 071/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...ndows-operating-system-components-to-microsoft-services.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index ffd5fd2f7e..9c75815780 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1443,11 +1443,11 @@ To turn this Off:
- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Enables Activity Feed**.
- -and-
+ -and-
- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow publishing of User Activities**.
- -and-
+ -and-
- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow upload of User Activities**
From 41cc5f332b32ad331e10244c2508913fce51868d Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 17:21:50 -0700
Subject: [PATCH 072/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...system-components-to-microsoft-services.md | 23 +++++++++----------
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 9c75815780..2e3498df01 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1437,32 +1437,31 @@ In the **Activity History** area, you can choose turn of tracking of your Activi
To turn this Off:
- - Turn **Off** the feature in the UI by going to Settings -> Privacy -> Activity History and **un-checking** the **Store my activity history on this device** AND **unchecking** the **Send my activity History to Microsoft** checkboxes.
+- Turn **Off** the feature in the UI by going to Settings -> Privacy -> Activity History and **un-checking** the **Store my activity history on this device** AND **unchecking** the **Send my activity History to Microsoft** checkboxes.
-OR-
- - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Enables Activity Feed**.
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Enables Activity Feed**.
- -and-
+ -and-
- - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow publishing of User Activities**.
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow publishing of User Activities**.
- -and-
-
- - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow upload of User Activities**
+ -and-
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow upload of User Activities**
-OR-
- - Create a REG_DWORD registry setting named **EnableActivityFeed** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+- Create a REG_DWORD registry setting named **EnableActivityFeed** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
- -and-
+ -and-
- - Create a REG_DWORD registry setting named **PublishUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+- Create a REG_DWORD registry setting named **PublishUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
- -and-
+ -and-
- - Create a REG_DWORD registry setting named **UploadUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+- Create a REG_DWORD registry setting named **UploadUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
### 18.23 Voice Activation
From 4315924ec2695c645bceedaaa21c10209aa9d0d8 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 17:35:27 -0700
Subject: [PATCH 073/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...system-components-to-microsoft-services.md | 38 +++++++++----------
1 file changed, 17 insertions(+), 21 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 2e3498df01..eee8ddd817 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1433,23 +1433,23 @@ If you're running at least Windows 10, version 1703, you can turn off updates to
### 18.22 Activity History
-In the **Activity History** area, you can choose turn of tracking of your Activity History.
+In the **Activity History** area, you can choose turn Off tracking of your Activity History.
-To turn this Off:
+To turn this Off in the UI:
- Turn **Off** the feature in the UI by going to Settings -> Privacy -> Activity History and **un-checking** the **Store my activity history on this device** AND **unchecking** the **Send my activity History to Microsoft** checkboxes.
-OR-
-- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Enables Activity Feed**.
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **OS Policies** named **Enables Activity Feed**.
-and-
-- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow publishing of User Activities**.
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **OS Policies** named **Allow publishing of User Activities**.
-and-
-- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **App Privacy** > **OS Policies** named **Allow upload of User Activities**
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **OS Policies** > named **Allow upload of User Activities**
-OR-
@@ -1463,36 +1463,32 @@ To turn this Off:
- Create a REG_DWORD registry setting named **UploadUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
-
### 18.23 Voice Activation
+In the **Vocie activation** area, you can choose turn Off apps ability to listen for a Voice keyword.
-> [!NOTE]
-> Releases 1803 and earlier support **Speech, Inking, & Typing** as a combined settings area. For customizing those setting please follow the below instructions. For 1809 and above **Speech** and **Inking & Typing** are separate settings pages, please see the specific section (18.6 Speech or 18.21 Inking and Typing) above for those areas.
+To turn this Off in the UI:
-In the **Speech, Inking, & Typing** area, you can let Windows and Cortana better understand your employee's voice and written input by sampling their voice and writing, and by comparing verbal and written input to contact names and calendar entrees.
+- Turn **Off** the feature in the UI by going to **Settings -> Privacy -> Voice activation** and toggle **Off** the **Allow apps to use voice activation** AND also toggle **Off** the **Allow apps to use voice activation when this device is locked**.
- For more info on how to disable Cortana in your enterprise, see [Cortana](#bkmk-cortana) in this article.
+-OR-
- To turn off the functionality:
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **App Privacy** > named **Let Windows apps activate with voice**.
- - Click the **Stop getting to know me** button, and then click **Turn off**.
+ -and-
- -or-
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **App Privacy** > named **Let Windows apps activate with voice while the system is locked**.
- - Enable the Group Policy: **Computer Configuration** > **Administrative Templates** > **Control Panel** > **Regional and Language Options** > **Handwriting personalization** > **Turn off automatic learning**
- -or-
+-OR-
+
+- Create a REG_DWORD registry setting named **LetAppsActivateWithVoice** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 0 (zero)**.
- - Create a REG_DWORD registry setting named **RestrictImplicitInkCollection** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\InputPersonalization** with a value of 1 (one).
+ -and-
- -or-
+- Create a REG_DWORD registry setting named **PublishUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 0 (zero)**.
- - Create a REG_DWORD registry setting named **AcceptedPrivacyPolicy** in **HKEY_CURRENT_USER\\Software\\Microsoft\\Personalization\\Settings** with a value of 0 (zero).
- -and-
-
- - Create a REG_DWORD registry setting named **HarvestContacts** in **HKEY_CURRENT_USER\\Software\\Microsoft\\InputPersonalization\\TrainedDataStore** with a value of **0 (zero)**.
### 19. Software Protection Platform
From cfa95f5f54a0cef19bbefcea46399ed4d826a154 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 17:38:37 -0700
Subject: [PATCH 074/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...system-components-to-microsoft-services.md | 22 +++++++++----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index eee8ddd817..56ddc526f9 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1437,15 +1437,15 @@ In the **Activity History** area, you can choose turn Off tracking of your Activ
To turn this Off in the UI:
-- Turn **Off** the feature in the UI by going to Settings -> Privacy -> Activity History and **un-checking** the **Store my activity history on this device** AND **unchecking** the **Send my activity History to Microsoft** checkboxes.
+- Turn **Off** the feature in the UI by going to Settings -> Privacy -> Activity History and **un-checking** the **Store my activity history on this device** AND **unchecking** the **Send my activity History to Microsoft** checkboxes
-OR-
-- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **OS Policies** named **Enables Activity Feed**.
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **OS Policies** named **Enables Activity Feed**
-and-
-- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **OS Policies** named **Allow publishing of User Activities**.
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **System** > **OS Policies** named **Allow publishing of User Activities**
-and-
@@ -1453,15 +1453,15 @@ To turn this Off in the UI:
-OR-
-- Create a REG_DWORD registry setting named **EnableActivityFeed** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+- Create a REG_DWORD registry setting named **EnableActivityFeed** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**
-and-
-- Create a REG_DWORD registry setting named **PublishUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+- Create a REG_DWORD registry setting named **PublishUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**
-and-
-- Create a REG_DWORD registry setting named **UploadUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**.
+- Create a REG_DWORD registry setting named **UploadUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\System** with a **value of 0 (zero)**
### 18.23 Voice Activation
@@ -1469,24 +1469,24 @@ In the **Vocie activation** area, you can choose turn Off apps ability to listen
To turn this Off in the UI:
-- Turn **Off** the feature in the UI by going to **Settings -> Privacy -> Voice activation** and toggle **Off** the **Allow apps to use voice activation** AND also toggle **Off** the **Allow apps to use voice activation when this device is locked**.
+- Turn **Off** the feature in the UI by going to **Settings -> Privacy -> Voice activation** and toggle **Off** the **Allow apps to use voice activation** AND also toggle **Off** the **Allow apps to use voice activation when this device is locked**
-OR-
-- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **App Privacy** > named **Let Windows apps activate with voice**.
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **App Privacy** > named **Let Windows apps activate with voice**
-and-
-- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **App Privacy** > named **Let Windows apps activate with voice while the system is locked**.
+- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **App Privacy** > named **Let Windows apps activate with voice while the system is locked**
-OR-
-- Create a REG_DWORD registry setting named **LetAppsActivateWithVoice** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 0 (zero)**.
+- Create a REG_DWORD registry setting named **LetAppsActivateWithVoice** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 0 (zero)**
-and-
-- Create a REG_DWORD registry setting named **PublishUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 0 (zero)**.
+- Create a REG_DWORD registry setting named **PublishUserActivities** in **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows\\AppPrivacy** with a **value of 0 (zero)**
From 15253f3e3a032f457bfe405bf3a5eef2d8e3c035 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 17:40:49 -0700
Subject: [PATCH 075/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 56ddc526f9..13d99f10af 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1425,7 +1425,7 @@ To turn off Inking & Typing data collection (note: there is no Group Policy for
If you're running at least Windows 10, version 1703, you can turn off updates to the speech recognition and speech synthesis models:
- **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Speech** > **Allow automatic update of Speech Data**
+ - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Speech** > **Allow automatic update of Speech Data**
-or-
From e535736d8e846e8dc878783e2f237e5fc49e00ae Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 17:51:51 -0700
Subject: [PATCH 076/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...windows-operating-system-components-to-microsoft-services.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index 13d99f10af..f3912695a7 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1425,7 +1425,7 @@ To turn off Inking & Typing data collection (note: there is no Group Policy for
If you're running at least Windows 10, version 1703, you can turn off updates to the speech recognition and speech synthesis models:
- - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Speech** > **Allow automatic update of Speech Data**
+ - **Disable** the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Speech** > **Allow automatic update of Speech Data**
-or-
From fb799925c329663c180e0d28d7b24b2476b5b147 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Thu, 16 May 2019 20:50:31 -0700
Subject: [PATCH 077/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services.md
---
...ows-operating-system-components-to-microsoft-services.md | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index f3912695a7..11b1cd1dfe 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -170,7 +170,7 @@ See the following table for a summary of the management settings for Windows Ser
| Setting | UI | Group Policy | Registry |
| - | :-: | :-: | :-: |
| [1. Automatic Root Certificates Update](#automatic-root-certificates-update) | |  |  |
-| [2. Cortana and Search](#bkmk-cortana) |  |  |  |  |
+| [2. Cortana and Search](#bkmk-cortana) |  |  |  |
| [3. Date & Time](#bkmk-datetime) |  |  |  |
| [4. Device metadata retrieval](#bkmk-devinst) | |  |  |
| [5. Find My Device](#find-my-device) |  |  |  |
@@ -1104,9 +1104,7 @@ To turn off **Let apps access my calendar**:
-or-
-- Apply the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **App Privacy** > **Let Windows apps access the calendar**
-
- - Set the **Select a setting** box to **Force Deny**.
+- Apply the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **App Privacy** > **Let Windows apps access the calendar**. Set the **Select a setting** box to **Force Deny**.
-or-
From ae42af9fdcb377815e91e8ddbfaf2e70eb99824d Mon Sep 17 00:00:00 2001
From: jaimeo
Date: Fri, 17 May 2019 08:53:09 -0700
Subject: [PATCH 078/156] import of new material on compatibility holds
---
.../update-compliance-feature-update-status.md | 13 +++++++++++++
.../update/update-compliance-perspectives.md | 6 ++++++
2 files changed, 19 insertions(+)
diff --git a/windows/deployment/update/update-compliance-feature-update-status.md b/windows/deployment/update/update-compliance-feature-update-status.md
index 4dbf3ca380..3587c79cbd 100644
--- a/windows/deployment/update/update-compliance-feature-update-status.md
+++ b/windows/deployment/update/update-compliance-feature-update-status.md
@@ -32,3 +32,16 @@ Refer to the following list for what each state means:
* Devices that have failed the given feature update installation are counted as **Update failed**.
* If a device should be, in some way, progressing toward this security update, but its status cannot be inferred, it will count as **Status Unknown**. Devices not using Windows Update are the most likely devices to fall into this category.
+## Compatibility holds
+
+Microsoft usesw diagnostic data to determine whether devices that use Windows Update are ready for an feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *compatibility hold* is generated to delay the device’s upgrade and safeguard the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all compatibility holds on the Windows 10 release information page for any given release.
+
+To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives#deployment-status).
+
+### Opting out of compatibility hold
+
+Microsoft will release a device from a compatibility hold when it has determined it can safely and smoothly install a feature update, but you are ultimately in control of your devices and can opt out if desired. To opt out, set the registry key **HKLM\Software\Microsoft\Windows NT\CurrentVersion\502505fe-762c-4e80-911e-0c3fa4c63fb0** to a name of **DataRequireGatedScanForFeatureUpdates** to a value of **0**.
+
+
+Setting this registry key to **0** will force the device to opt out from *all* compatibility holds. Any other value, or deleting the key, will resume compatibility protection on the device.
+
diff --git a/windows/deployment/update/update-compliance-perspectives.md b/windows/deployment/update/update-compliance-perspectives.md
index f0403b00c8..9f02e47ed0 100644
--- a/windows/deployment/update/update-compliance-perspectives.md
+++ b/windows/deployment/update/update-compliance-perspectives.md
@@ -23,6 +23,8 @@ The first blade is the **Build Summary** blade. This blade summarizes the most i
The second blade is the **Deferral Configurations** blade, breaking down Windows Update for Business deferral settings (if any).
+## Deployment status
+
The third blade is the **Deployment Status** blade. This defines how many days it has been since the queried version has been released, and breaks down the various states in the update funnel each device has reported to be in. The possible states are as follows:
| State | Description |
@@ -30,12 +32,15 @@ The third blade is the **Deployment Status** blade. This defines how many days i
| Update Completed | When a device has finished the update process and is on the queried update, it will display here as Update completed. |
| In Progress | Devices that report they are “In Progress” are one of the various stages of installing an update; these stages are reported in the Detailed Deployment Status blade. |
| Deferred | When a device’s Windows Update for Business deferral policy dictates that the update is not yet applicable due to deferral, it will report as such in this blade. |
+| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status#) |
| Progress stalled | Devices that report as “Progress stalled” have been stuck at “In progress” for more than 7 days. |
| Cancelled | The update was cancelled. |
| Blocked | There is a hard block on the update being completed. This could be that another update must be completed before this one, or some other task is blocking the installation of the update. |
| Unknown | Devices that do not report detailed information on the status of their updates will report Unknown. This is most likely devices that do not use Windows Update for deployment. |
| Update paused | These devices have Windows Update for Business pause enabled, preventing this update from being installed. |
+## Detailed deployment status
+
The final blade is the **Detailed Deployment Status** blade. This blade breaks down the detailed stage of deployment a device is in, beyond the generalized terms defined in Deployment Status. The following are the possible stages a device can report:
| State | Description |
@@ -44,6 +49,7 @@ The final blade is the **Detailed Deployment Status** blade. This blade breaks d
| Update paused | The device’s Windows Update for Business policy dictates the update is paused from being offered. |
| Update offered | The device has been offered the update, but has not begun downloading it. |
| Pre-Download tasks passed | The device has finished all necessary tasks prior to downloading the update. |
+| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status#) |
| Download Started | The update has begun downloading on the device. |
| Download Succeeded | The update has successfully completed downloading. |
| Pre-Install Tasks Passed | Tasks that must be completed prior to installing the update have been completed. |
From f16f0f807ca808e30862da9f76a11a7396b646b9 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Fri, 17 May 2019 09:02:59 -0700
Subject: [PATCH 079/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...ng-system-components-to-microsoft-services-using-MDM.md | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
index 0210fa442d..6dc87da4de 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
@@ -28,7 +28,10 @@ Note, there is some traffic which is required (i.e. "whitelisted") for the opera
For more information on Microsoft InTune please see [Transform IT service delivery for your modern workplace](https://www.microsoft.com/en-us/enterprise-mobility-security/microsoft-intune?rtc=1) and [Microsoft Intune documentation](https://docs.microsoft.com/en-us/intune/).
-For detailed information about managing network connections to Microsoft services using Baseline package/registries/Group policies/UI/Command line, see [Manage connections from Windows operating system components to Microsoft services](https://docs.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services).
+For detailed information about managing network connections to Microsoft services using Registries, Group Policies, or UI see [Manage connections from Windows operating system components to Microsoft services](https://docs.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services).
+
+The endpoints for the “whitelisted” traffic are in the [Whitelisted Traffic](#bkmk-mdm-whitelist).
+
### Settings for Windows 10 Enterprise edition 1903 and newer
@@ -116,7 +119,7 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
| | [DeliveryOptimization/DODownloadMode](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dodownloadmode)| Specifies the download method that Delivery Optimization can use in downloads of Windows Updates, Apps and App updates. Set to **100** - Bypass mode. Do not use Delivery Optimization and use BITS instead. Added in Windows 10, version 1607.
| 28. Windows Update | [Update/AllowAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) | Control automatic updates.
**0**: notify the user before downloading the update
**1**: auto install the update and then notify the user to schedule a device restart
**2**: auto install and restart (default)
**3**: auto install and restart at a specified time
**4**: auto install and restart without end-user control
**5**: turn off automatic updates
-### Allowed (aka "Whitelisted") traffic for Microsoft InTune / MDM configurations
+### Allowed (aka "Whitelisted") traffic for Microsoft InTune / MDM configurations
|**Allowed traffic endpoints** |
| --- |
From 3f3a7ad286e895dc69c2832670c252335344e9af Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Fri, 17 May 2019 09:03:58 -0700
Subject: [PATCH 080/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...erating-system-components-to-microsoft-services-using-MDM.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
index 6dc87da4de..6986ee5ce2 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
@@ -119,7 +119,7 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
| | [DeliveryOptimization/DODownloadMode](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dodownloadmode)| Specifies the download method that Delivery Optimization can use in downloads of Windows Updates, Apps and App updates. Set to **100** - Bypass mode. Do not use Delivery Optimization and use BITS instead. Added in Windows 10, version 1607.
| 28. Windows Update | [Update/AllowAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) | Control automatic updates.
**0**: notify the user before downloading the update
**1**: auto install the update and then notify the user to schedule a device restart
**2**: auto install and restart (default)
**3**: auto install and restart at a specified time
**4**: auto install and restart without end-user control
**5**: turn off automatic updates
-### Allowed (aka "Whitelisted") traffic for Microsoft InTune / MDM configurations
+### Allowed traffic (aka "Whitelisted") for Microsoft InTune / MDM configurations
|**Allowed traffic endpoints** |
| --- |
From 96725bbcd2c005c202f75864c5b395600fa7bb93 Mon Sep 17 00:00:00 2001
From: jaimeo
Date: Fri, 17 May 2019 09:18:13 -0700
Subject: [PATCH 081/156] fixing crosslinks
---
.../update/update-compliance-feature-update-status.md | 2 +-
windows/deployment/update/update-compliance-perspectives.md | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/update/update-compliance-feature-update-status.md b/windows/deployment/update/update-compliance-feature-update-status.md
index 3587c79cbd..f9b26f8340 100644
--- a/windows/deployment/update/update-compliance-feature-update-status.md
+++ b/windows/deployment/update/update-compliance-feature-update-status.md
@@ -36,7 +36,7 @@ Refer to the following list for what each state means:
Microsoft usesw diagnostic data to determine whether devices that use Windows Update are ready for an feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *compatibility hold* is generated to delay the device’s upgrade and safeguard the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all compatibility holds on the Windows 10 release information page for any given release.
-To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives#deployment-status).
+To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives.md#deployment-status).
### Opting out of compatibility hold
diff --git a/windows/deployment/update/update-compliance-perspectives.md b/windows/deployment/update/update-compliance-perspectives.md
index 9f02e47ed0..611b8a05df 100644
--- a/windows/deployment/update/update-compliance-perspectives.md
+++ b/windows/deployment/update/update-compliance-perspectives.md
@@ -32,7 +32,7 @@ The third blade is the **Deployment Status** blade. This defines how many days i
| Update Completed | When a device has finished the update process and is on the queried update, it will display here as Update completed. |
| In Progress | Devices that report they are “In Progress” are one of the various stages of installing an update; these stages are reported in the Detailed Deployment Status blade. |
| Deferred | When a device’s Windows Update for Business deferral policy dictates that the update is not yet applicable due to deferral, it will report as such in this blade. |
-| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status#) |
+| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) |
| Progress stalled | Devices that report as “Progress stalled” have been stuck at “In progress” for more than 7 days. |
| Cancelled | The update was cancelled. |
| Blocked | There is a hard block on the update being completed. This could be that another update must be completed before this one, or some other task is blocking the installation of the update. |
@@ -49,7 +49,7 @@ The final blade is the **Detailed Deployment Status** blade. This blade breaks d
| Update paused | The device’s Windows Update for Business policy dictates the update is paused from being offered. |
| Update offered | The device has been offered the update, but has not begun downloading it. |
| Pre-Download tasks passed | The device has finished all necessary tasks prior to downloading the update. |
-| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status#) |
+| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) |
| Download Started | The update has begun downloading on the device. |
| Download Succeeded | The update has successfully completed downloading. |
| Pre-Install Tasks Passed | Tasks that must be completed prior to installing the update have been completed. |
From 4638ce3016e3234bc51055ab6014308e83f6159f Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Fri, 17 May 2019 09:25:42 -0700
Subject: [PATCH 082/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...g-system-components-to-microsoft-services-using-MDM.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
index 6986ee5ce2..0d87c0498f 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
@@ -111,10 +111,10 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
| | [ApplicationManagement/AllowAppStoreAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-applicationmanagement#applicationmanagement-allowappstoreautoupdate)| Specifies whether automatic update of apps from Microsoft Store are allowed.
**1** (default) Allowed.
**0** Not allowed.
| 26.1 Apps for websites | [ApplicationDefaults/EnableAppUriHandlers](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-applicationdefaults#applicationdefaults-enableappurihandlers) | This policy setting determines whether Windows supports web-to-app linking with app URI handlers.
**0**: disabled
**1** enabled
| 27. Windows Update Delivery Optimization | | The following Delivery Optimization MDM policies are available in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx).
-| | [DeliveryOptimization/DODownloadMode](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dodownloadmode) | Lets you choose where Delivery Optimization gets or sends updates and apps.
**0**: turns off Delivery Optimization
**1**: gets or sends updates and apps to PCs on the same NAT only
**2**: gets or sends updates and apps to PCs on the same local network domain
**3**: gets or sends updates and apps to PCs on the Internet
**99**: simple download mode with no peering
**100**: use BITS instead of Windows Update Delivery Optimization
-| | [DeliveryOptimization/DOGroupID](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dogroupid) | Lets you provide a Group ID that limits which PCs can share apps and updates.
Note: This ID must be a GUID.
-| | [DeliveryOptimization/DOMaxCacheAge](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-domaxcacheage) | Lets you specify the maximum time (in seconds) that a file is held in the Delivery Optimization cache.
The default value is 259200 seconds (3 days).
-| | [DeliveryOptimization/DOMaxCacheSize](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-domaxcachesize) | Lets you specify the maximum cache size as a percentage of disk size.
The default value is 20| which represents 20% of the disk.
+| | [DeliveryOptimization/DODownloadMode](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dodownloadmode)| Lets you choose where Delivery Optimization gets or sends updates and apps.
**0**: turns off Delivery Optimization
**1**: gets or sends updates and apps to PCs on the same NAT only
**2**: gets or sends updates and apps to PCs on the same local network domain
**3**: gets or sends updates and apps to PCs on the Internet
**99**: simple download mode with no peering
**100**: use BITS instead of Windows Update Delivery Optimization
+| | [DeliveryOptimization/DOGroupID](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dogroupid)| Lets you provide a Group ID that limits which PCs can share apps and updates.
Note: This ID must be a GUID.
+| | [DeliveryOptimization/DOMaxCacheAge](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-domaxcacheage)| Lets you specify the maximum time (in seconds) that a file is held in the Delivery Optimization cache.
The default value is 259200 seconds (3 days).
+| | [DeliveryOptimization/DOMaxCacheSize](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-domaxcachesize) | Lets you specify the maximum cache size as a percentage of disk size.
The default value is 20 which represents 20% of the disk.
| | [DeliveryOptimization/DOMaxUploadBandwidth](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-domaxuploadbandwidth) | Lets you specify the maximum upload bandwidth (in KB/second) that a device uses across all concurrent upload activity.
The default value is 0, which means unlimited possible bandwidth.
| | [DeliveryOptimization/DODownloadMode](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dodownloadmode)| Specifies the download method that Delivery Optimization can use in downloads of Windows Updates, Apps and App updates. Set to **100** - Bypass mode. Do not use Delivery Optimization and use BITS instead. Added in Windows 10, version 1607.
| 28. Windows Update | [Update/AllowAutoUpdate](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) | Control automatic updates.
**0**: notify the user before downloading the update
**1**: auto install the update and then notify the user to schedule a device restart
**2**: auto install and restart (default)
**3**: auto install and restart at a specified time
**4**: auto install and restart without end-user control
**5**: turn off automatic updates
From 8ea9ed0bf3385a1a5da6d69634e13d9715edf282 Mon Sep 17 00:00:00 2001
From: Mike Edgar <49731348+medgarmedgar@users.noreply.github.com>
Date: Fri, 17 May 2019 09:26:49 -0700
Subject: [PATCH 083/156] Update
manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
---
...rating-system-components-to-microsoft-services-using-MDM.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
index 0d87c0498f..1169395f22 100644
--- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
+++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-MDM.md
@@ -30,7 +30,8 @@ For more information on Microsoft InTune please see [Transform IT service delive
For detailed information about managing network connections to Microsoft services using Registries, Group Policies, or UI see [Manage connections from Windows operating system components to Microsoft services](https://docs.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services).
-The endpoints for the “whitelisted” traffic are in the [Whitelisted Traffic](#bkmk-mdm-whitelist).
+
+The endpoints for the MDM “whitelisted” traffic are in the [Whitelisted Traffic](#bkmk-mdm-whitelist).
### Settings for Windows 10 Enterprise edition 1903 and newer
From 0452abec2404cb666d908f4130d5010123785001 Mon Sep 17 00:00:00 2001
From: jaimeo
Date: Fri, 17 May 2019 09:39:26 -0700
Subject: [PATCH 084/156] fixing typo
---
.../update/update-compliance-feature-update-status.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/update/update-compliance-feature-update-status.md b/windows/deployment/update/update-compliance-feature-update-status.md
index f9b26f8340..6e0fd2826b 100644
--- a/windows/deployment/update/update-compliance-feature-update-status.md
+++ b/windows/deployment/update/update-compliance-feature-update-status.md
@@ -34,7 +34,7 @@ Refer to the following list for what each state means:
## Compatibility holds
-Microsoft usesw diagnostic data to determine whether devices that use Windows Update are ready for an feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *compatibility hold* is generated to delay the device’s upgrade and safeguard the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all compatibility holds on the Windows 10 release information page for any given release.
+Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for an feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *compatibility hold* is generated to delay the device’s upgrade and safeguard the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all compatibility holds on the Windows 10 release information page for any given release.
To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives.md#deployment-status).
From 4739a22778434a7f6b6d61cc70a8e364dd14cf08 Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Fri, 17 May 2019 10:07:04 -0700
Subject: [PATCH 085/156] edits from Sakib
---
...ows-defender-application-control-policy.md | 47 ++++++++++++-------
.../create-path-based-rules.md | 4 +-
...s-defender-application-control-policies.md | 13 +++--
...win32-apps-on-windows-10-s-mode-devices.md | 25 ++++++++--
4 files changed, 60 insertions(+), 29 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md b/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
index c952c0c184..68a3ab2dcd 100644
--- a/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
+++ b/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy.md
@@ -6,8 +6,8 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
-author: jsuther1974
-ms.date: 05/16/2019
+author: mdsakibMSFT
+ms.date: 05/17/2019
---
# Allow COM object registration in a Windows Defender Application Control policy
@@ -32,7 +32,7 @@ Get GUID of application to allow in one of the following ways:
- Finding block event in Event Viewer (Application and Service Logs > Microsoft > Windows > AppLocker > MSI and Script) and extracting GUID
- Creating audit policy (using New-CIPolicy –Audit), potentially with specific provider, and use info from block events to get GUID
-### Author setting
+### Author policy setting to allow or deny COM object GUID
Three elements:
- Provider: platform on which code is running (values are Powershell, WSH, IE, VBA, MSI, or a wildcard “AllHostIds”)
@@ -46,21 +46,32 @@ One attribute:
### Examples
+Example 1: Allows registration of all COM object GUIDs in any provider
+
```xml
-
-
- true
-
-
-
-
- false
-
-
-
-
- true
-
-
+
+
+ true
+
+
+```
+
+Example 2: Blocks a specific COM object from being registered via Internet Explorer (IE)
+
+```xml
+
+
+ false
+
+
+
+Example 3: Allows a specific COM object to register in PowerShell
+
+```xml
+
+
+ true
+
+
```
diff --git a/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md b/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
index 29db07a119..105f6a46bb 100644
--- a/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
+++ b/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
@@ -6,8 +6,8 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
-author: jsuther1974
-ms.date: 05/14/2019
+author: mdsakibMSFT
+ms.date: 05/17/2019
---
# Create Windows Defender Application Control path-based rules
diff --git a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
index adc318d407..6df51f6694 100644
--- a/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
+++ b/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies.md
@@ -6,8 +6,8 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
-author: jsuther1974
-ms.date: 05/10/2019
+author: mdsakibMSFT
+ms.date: 05/17/2019
---
# Deploy multiple Windows Defender Application Control Policies
@@ -44,19 +44,22 @@ Note that multiple policies will not work on pre-1903 systems.
### Allow Multiple Policies
In order to allow multiple policies to exist and take effect on a single system, policies must be created using the new Multiple Policy Format. The "MultiplePolicyFormat" switch in New-CIPolicy results in 1) random GUIDs being generated for the policy ID and 2) the policy type being specified as base.
+
```powershell
New-CIPolicy -MultiplePolicyFormat -foo –bar
```
Optionally, you can choose to make the new base policy supplementable (allow supplemental policies).
+
```powershell
Set-RuleOption -FilePath Enabled:Allow Supplemental Policies
```
For signed base policies that are being made supplementable, you need to ensure that supplemental signers are defined. Use the "Supplemental" switch in Add-SignerRule to provide supplemental signers.
- ```powershell
- Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
- ```
+
+```powershell
+Add-SignerRule -FilePath -CertificatePath [-Kernel] [-User] [-Update] [-Supplemental] [-Deny] []
+```
### Supplemental Policy Creation
diff --git a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
index 5bbde4033e..25dc3efe37 100644
--- a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
+++ b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
@@ -6,8 +6,8 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
-author: jsuther1974
-ms.date: 05/06/2018
+author: mdsakibMSFT
+ms.date: 05/17/2018
---
# Sideloading Win32 apps on Windows 10 S mode devices
@@ -51,24 +51,37 @@ To allow Win32 apps to run on a Windows 10 device in S mode, admins must ‘unlo
## Creating and Signing a Supplemental Policy
1. Create new base policy using [New-CIPolicy](https://docs.microsoft.com/powershell/module/configci/new-cipolicy?view=win10-ps)
+
```powershell
New-CIPolicy -Level PcaCertificate -UserPEs -ScanPath -MultiplePolicyFormat 3> -FilePath
```
+
2. Change it to a supplemental policy using [Set-CIPolicyIdInfo](https://docs.microsoft.com/powershell/module/configci/set-cipolicyidinfo?view=win10-ps)
+
```powershell
Set-CIPolicyIdInfo -BasePolicyToSupplementPath -SupplementsBasePolicyID 5951A96A-E0B5-4D3D-8FB8-3E5B61030784 -FilePath
```
- Note: ‘5951A96A-E0B5-4D3D-8FB8-3E5B61030784' is the S-mode Base Policy ID.
+
+ >[!NOTE]
+ >‘5951A96A-E0B5-4D3D-8FB8-3E5B61030784' is the S-mode Base Policy ID.
+
3. Put policy in enforce mode using [Set-RuleOption](https://docs.microsoft.com/powershell/module/configci/set-ruleoption?view=win10-ps)
+
```powershell
Set-RuleOption -FilePath -Option 3 –Delete
```
+
This deletes the ‘audit mode’ qualifier.
+
4. Convert to .bin using [ConvertFrom-CIPolicy](https://docs.microsoft.com/powershell/module/configci/convertfrom-cipolicy?view=win10-ps)
+
```powershell
ConvertFrom-CIPolicy -XmlFilePath -BinaryFilePath
```
- Note: PolicyID can be found by inspecting the Supplemental Policy XML. Convert to .bin to sign with DGSS (recommended) or .cip to sign locally.
+
+ >[!NOTE]
+ >PolicyID can be found by inspecting the Supplemental Policy XML. Convert to .bin to sign with DGSS (recommended) or .cip to sign locally.
+
5. To sign using the recommended DGSS option through the Microsoft Store for Business, click **Manage** > **Settings** > **Devices** > **Upload** > **Sign**.
To sign locally using signtool, see [Signing policies with signtool](signing-policies-with-signtool.md).
@@ -76,14 +89,18 @@ To allow Win32 apps to run on a Windows 10 device in S mode, admins must ‘unlo
An admin must generate an app catalog for every deployed app:
1. Use Package Inspector to [create a catalog](https://docs.microsoft.com/microsoft-store/add-unsigned-app-to-code-integrity-policy#a-href-idcreate-catalog-filesacreate-catalog-files-for-your-unsigned-app)
- Start Package Inspector to scan the installer:
+
```console
PackageInspector.exe start C: -path
```
+
- Open the app installer.
- Stop Package Inspector:
+
```console
PackageInspector.exe stop C: -Name -cdfpath
```
+
2. To sign using the recommended DGSS option through the Microsoft Store for Business, click **Manage** > **Settings** > **Devices** > **Upload** > **Sign**.
To sign locally using signtool, see [Signing policies with signtool](signing-policies-with-signtool.md).
From 2717120544bbda0cd6c85afef7db3d58a1f1dd1f Mon Sep 17 00:00:00 2001
From: Justin Hall
Date: Fri, 17 May 2019 10:22:37 -0700
Subject: [PATCH 086/156] removed sideloading apps topic
---
.../TOC.md | 1 -
...win32-apps-on-windows-10-s-mode-devices.md | 109 ------------------
2 files changed, 110 deletions(-)
delete mode 100644 windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
diff --git a/windows/security/threat-protection/windows-defender-application-control/TOC.md b/windows/security/threat-protection/windows-defender-application-control/TOC.md
index 075e728710..ac99737410 100644
--- a/windows/security/threat-protection/windows-defender-application-control/TOC.md
+++ b/windows/security/threat-protection/windows-defender-application-control/TOC.md
@@ -34,7 +34,6 @@
### [Use a Windows Defender Application Control policy to control specific plug-ins, add-ins, and modules](use-windows-defender-application-control-policy-to-control-specific-plug-ins-add-ins-and-modules.md)
### [Use signed policies to protect Windows Defender Application Control against tampering](use-signed-policies-to-protect-windows-defender-application-control-against-tampering.md)
#### [Signing WDAC policies with SignTool.exe](signing-policies-with-signtool.md)
-### [Sideload Win32 apps on S mode](sideloading-win32-apps-on-windows-10-s-mode-devices.md)
### [Disable WDAC policies](disable-windows-defender-application-control-policies.md)
### [Device Guard and AppLocker](windows-defender-device-guard-and-applocker.md)
diff --git a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md b/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
deleted file mode 100644
index 25dc3efe37..0000000000
--- a/windows/security/threat-protection/windows-defender-application-control/sideloading-win32-apps-on-windows-10-s-mode-devices.md
+++ /dev/null
@@ -1,109 +0,0 @@
----
-title: Sideloading Win32 apps on Windows 10 S mode devices (Windows 10)
-description: Windows Defender Application Control restricts which applications users are allowed to run and the code that runs in the system core.
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype: security
-ms.localizationpriority: medium
-author: mdsakibMSFT
-ms.date: 05/17/2018
----
-
-# Sideloading Win32 apps on Windows 10 S mode devices
-
-**Applies to:**
-
-- Windows 10
-- Windows Server 2016
-
->[!IMPORTANT]
->Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
-
-Windows 10 S mode is a locked-down system that only runs Store apps.
-Although it provides tight security and thereby promises reduced management, its application control restrictions make it difficult for some to adopt it widely.
-Sideloading makes S mode a more viable proposition for enterprise and education workloads by allowing critical Desktop apps in addition to Store apps.
-
-## Process Overview
-
-To allow Win32 apps to run on a Windows 10 device in S mode, admins must ‘unlock’ the device so exceptions can be made to S mode policy, and then upload a corresponding signed catalog for each app to Intune. Here are the steps:
-
-1. Unlock S mode devices through Intune
- - Admin uses the Device Guard Signing Service (DGSS) in the Microsoft Store for Business to generate a root certificate for the organization and upload it to Intune
- - Intune will ensure this certificate is included in a device’s unlock token from OCDUS, and any app catalogs which are signed with it will be able to run on the unlocked device
-2. Create a supplemental policy to allow Win32 apps
- - Admin uses Windows Defender Application Control tools to create a supplemental policy
- - Admin uses DGSS to sign their supplemental policy
- - Admin uploads signed supplemental policy to Intune
-3. Allow Win32 app catalogs through Intune
- - Admin creates catalog files (1 for every app) and signs them using DGSS or other certificate infrastructure
- - Admin submits the signed catalog to Intune
- - Intune applies the signed catalog to unlocked S mode device using Sidecar
-
-## Setting up Business Store to use DGSS
-
-1. In the Azure portal, create a new resource of type Azure Active Directory, then create an associated global admin user.
-2. Log in to the Microsoft Store for Business as the global admin then go to **Organization** > **Private Store** and accept.
- This will automatically generate a root certificate for the organization.
-3. To download a root cert or upload policies/catalogs to sign, navigate to **Manage** > **Settings** > **Devices**.
- Note: you can only upload .bin and .cat files.
-
-## Creating and Signing a Supplemental Policy
-
-1. Create new base policy using [New-CIPolicy](https://docs.microsoft.com/powershell/module/configci/new-cipolicy?view=win10-ps)
-
- ```powershell
- New-CIPolicy -Level PcaCertificate -UserPEs -ScanPath -MultiplePolicyFormat 3> -FilePath