diff --git a/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md b/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md index 7cdc026046..f462eeaba0 100644 --- a/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md +++ b/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md @@ -4,7 +4,7 @@ description: Learn more about the ADMX_MicrosoftDefenderAntivirus Area in Policy author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/10/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -3239,7 +3239,12 @@ This policy setting allows you to configure heuristics. Suspicious detections wi - + +This policy setting allows you to configure scanning for packed executables. It's recommended that this type of scanning remain enabled. + +- If you enable or don't configure this setting, packed executables will be scanned. + +- If you disable this setting, packed executables won't be scanned. @@ -3256,7 +3261,6 @@ This policy setting allows you to configure heuristics. Suspicious detections wi - [!INCLUDE [ADMX-backed policy note](includes/mdm-admx-policy-note.md)] **ADMX mapping**: @@ -3264,6 +3268,11 @@ This policy setting allows you to configure heuristics. Suspicious detections wi | Name | Value | |:--|:--| | Name | Scan_DisablePackedExeScanning | +| Friendly Name | Scan packed executables | +| Location | Computer Configuration | +| Path | Windows Components > Microsoft Defender Antivirus > Scan | +| Registry Key Name | Software\Policies\Microsoft\Windows Defender\Scan | +| Registry Value Name | DisablePackedExeScanning | | ADMX File Name | WindowsDefender.admx | diff --git a/windows/client-management/mdm/policy-csp-admx-terminalserver.md b/windows/client-management/mdm/policy-csp-admx-terminalserver.md index 845fe646f5..690350461f 100644 --- a/windows/client-management/mdm/policy-csp-admx-terminalserver.md +++ b/windows/client-management/mdm/policy-csp-admx-terminalserver.md @@ -4,7 +4,7 @@ description: Learn more about the ADMX_TerminalServer Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/10/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -2457,6 +2457,9 @@ Per Device licensing mode requires that each device connecting to this RD Sessio - If you enable this policy setting, the Remote Desktop licensing mode that you specify is honored by the Remote Desktop license server and RD Session Host. - If you disable or don't configure this policy setting, the licensing mode isn't specified at the Group Policy level. + +> [!NOTE] +> AAD Per User mode is deprecated on Windows 11 and above. diff --git a/windows/client-management/mdm/policy-csp-fileexplorer.md b/windows/client-management/mdm/policy-csp-fileexplorer.md index 8c51b03f44..75e9fb777f 100644 --- a/windows/client-management/mdm/policy-csp-fileexplorer.md +++ b/windows/client-management/mdm/policy-csp-fileexplorer.md @@ -4,7 +4,7 @@ description: Learn more about the FileExplorer Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/29/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -145,7 +145,7 @@ When This PC location is restricted, give the user the option to enumerate and n -Turning off files from Office.com will prevent File Explorer from requesting recent cloud file metadata and displaying it in the Quick access view. +Turning off this setting will prevent File Explorer from requesting cloud file metadata and displaying it in the homepage and other views in File Explorer. Any insights and files available based on account activity will be stopped in views such as Recent, Recommended, Favorites, etc. @@ -177,7 +177,7 @@ Turning off files from Office.com will prevent File Explorer from requesting rec | Name | Value | |:--|:--| | Name | DisableGraphRecentItems | -| Friendly Name | Turn off files from Office.com in Quick access view | +| Friendly Name | Turn off account-based insights, recent, favorite, and recommended files in File Explorer | | Location | Computer Configuration | | Path | WindowsComponents > File Explorer | | Registry Key Name | Software\Policies\Microsoft\Windows\Explorer | diff --git a/windows/client-management/mdm/policy-csp-filesystem.md b/windows/client-management/mdm/policy-csp-filesystem.md index 98bb86e6a8..57ec3f91e0 100644 --- a/windows/client-management/mdm/policy-csp-filesystem.md +++ b/windows/client-management/mdm/policy-csp-filesystem.md @@ -4,7 +4,7 @@ description: Learn more about the FileSystem Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/29/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -40,7 +40,10 @@ ms.topic: reference - + +Dev drive is a drive optimized for performance considering developer scenarios and by default no file system filters are attached to it. Filters listed in this setting will be allowed to attach even on a dev drive. + +A reboot is required for this setting to take effect. @@ -57,7 +60,6 @@ ms.topic: reference - [!INCLUDE [ADMX-backed policy note](includes/mdm-admx-policy-note.md)] **ADMX mapping**: @@ -65,6 +67,10 @@ ms.topic: reference | Name | Value | |:--|:--| | Name | DevDriveAttachPolicy | +| Friendly Name | Dev drive filter attach policy | +| Location | Computer Configuration | +| Path | System > Filesystem | +| Registry Key Name | System\CurrentControlSet\Policies | | ADMX File Name | filtermanager.admx | @@ -90,7 +96,14 @@ ms.topic: reference - + +Dev drive or developer volume is a volume optimized for performance of developer scenarios. A developer volume allows an administrator to choose file system filters that are attached on the volume. + +Disabling this setting will disallow creation of new developer volumes, existing developer volumes will mount as regular volumes. + +If this setting isn't configured the default policy is to enable developer volumes while allowing antivirus filter to attach on a deveveloper volume. Further, if not configured, a local administrator can choose to not have antivirus filter attached to a developer volume. + +A reboot is required for this setting to take effect. @@ -107,7 +120,6 @@ ms.topic: reference - [!INCLUDE [ADMX-backed policy note](includes/mdm-admx-policy-note.md)] **ADMX mapping**: @@ -115,6 +127,11 @@ ms.topic: reference | Name | Value | |:--|:--| | Name | EnableDevDrive | +| Friendly Name | Enable dev drive | +| Location | Computer Configuration | +| Path | System > Filesystem | +| Registry Key Name | System\CurrentControlSet\Policies | +| Registry Value Name | FsEnableDevDrive | | ADMX File Name | refs.admx | diff --git a/windows/client-management/mdm/policy-csp-humanpresence.md b/windows/client-management/mdm/policy-csp-humanpresence.md index e0cc0d9db0..6584e6372b 100644 --- a/windows/client-management/mdm/policy-csp-humanpresence.md +++ b/windows/client-management/mdm/policy-csp-humanpresence.md @@ -4,7 +4,7 @@ description: Learn more about the HumanPresence Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/10/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -38,8 +38,8 @@ ms.topic: reference - -Determines whether Allow Adaptive Dimming When External Display Connected checkbox is forced checked/unchecked by the MDM policy. The user won't be able to change this setting and the checkbox in the UI will be greyed out. + +Determines whether Allow Adaptive Dimming When Battery Saver On checkbox is forced checked/unchecked by the MDM policy. The user won't be able to change this setting and the checkbox in the UI will be greyed out. @@ -72,7 +72,12 @@ Determines whether Allow Adaptive Dimming When External Display Connected checkb | Name | Value | |:--|:--| | Name | ForceAllowDimWhenExternalDisplayConnected | -| Path | Sensors > AT > WindowsComponents > HumanPresence | +| Friendly Name | Force Allow Dim When External Display Connected | +| Location | Computer Configuration | +| Path | Windows Components > Human Presence | +| Registry Key Name | Software\Policies\Microsoft\HumanPresence | +| Registry Value Name | ForceAllowDimWhenExternalDisplayConnected | +| ADMX File Name | Sensors.admx | @@ -97,8 +102,8 @@ Determines whether Allow Adaptive Dimming When External Display Connected checkb - -Determines whether Allow Lock on Leave When External Display Connected checkbox is forced checked/unchecked by the MDM policy. The user won't be able to change this setting and the checkbox in the UI will be greyed out. + +Determines whether Allow Lock on Leave When Battery Saver On checkbox is forced checked/unchecked by the MDM policy. The user won't be able to change this setting and the checkbox in the UI will be greyed out. @@ -131,7 +136,12 @@ Determines whether Allow Lock on Leave When External Display Connected checkbox | Name | Value | |:--|:--| | Name | ForceAllowLockWhenExternalDisplayConnected | -| Path | Sensors > AT > WindowsComponents > HumanPresence | +| Friendly Name | Force Allow Lock When External Display Connected | +| Location | Computer Configuration | +| Path | Windows Components > Human Presence | +| Registry Key Name | Software\Policies\Microsoft\HumanPresence | +| Registry Value Name | ForceAllowLockWhenExternalDisplayConnected | +| ADMX File Name | Sensors.admx | @@ -156,7 +166,7 @@ Determines whether Allow Lock on Leave When External Display Connected checkbox - + Determines whether Allow Wake on Approach When External Display Connected checkbox is forced checked/unchecked by the MDM policy. The user won't be able to change this setting and the checkbox in the UI will be greyed out. @@ -190,7 +200,12 @@ Determines whether Allow Wake on Approach When External Display Connected checkb | Name | Value | |:--|:--| | Name | ForceAllowWakeWhenExternalDisplayConnected | -| Path | Sensors > AT > WindowsComponents > HumanPresence | +| Friendly Name | Force Allow Wake When External Display Connected | +| Location | Computer Configuration | +| Path | Windows Components > Human Presence | +| Registry Key Name | Software\Policies\Microsoft\HumanPresence | +| Registry Value Name | ForceAllowWakeWhenExternalDisplayConnected | +| ADMX File Name | Sensors.admx | @@ -215,7 +230,7 @@ Determines whether Allow Wake on Approach When External Display Connected checkb - + Determines whether Disable Wake on Approach When Battery Saver On checkbox is forced checked/unchecked by the MDM policy. The user won't be able to change this setting and the checkbox in the UI will be greyed out. @@ -249,7 +264,12 @@ Determines whether Disable Wake on Approach When Battery Saver On checkbox is fo | Name | Value | |:--|:--| | Name | ForceDisableWakeWhenBatterySaverOn | -| Path | Sensors > AT > WindowsComponents > HumanPresence | +| Friendly Name | Force Disable Wake When Battery Saver On | +| Location | Computer Configuration | +| Path | Windows Components > Human Presence | +| Registry Key Name | Software\Policies\Microsoft\HumanPresence | +| Registry Value Name | ForceDisableWakeWhenBatterySaverOn | +| ADMX File Name | Sensors.admx | diff --git a/windows/client-management/mdm/policy-csp-multitasking.md b/windows/client-management/mdm/policy-csp-multitasking.md index 3fd43b32c1..c12b74e90f 100644 --- a/windows/client-management/mdm/policy-csp-multitasking.md +++ b/windows/client-management/mdm/policy-csp-multitasking.md @@ -4,7 +4,7 @@ description: Learn more about the Multitasking Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/10/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -37,9 +37,9 @@ ms.topic: reference -This setting controls the inclusion of Microsoft Edge tabs into Alt+Tab. +This setting controls the inclusion of app tabs into Alt+Tab. -This can be set to show all tabs, the most recent 3 or 5 tabs, or no tabs from Microsoft Edge. +This can be set to show the most recent 3, 5 or 20 tabs, or no tabs from apps. If this is set to show "Open windows only", the whole feature will be disabled. @@ -82,7 +82,7 @@ This policy only applies to the Alt+Tab switcher. When the policy isn't enabled, | Name | Value | |:--|:--| | Name | BrowserAltTabBlowout | -| Friendly Name | Configure the inclusion of Microsoft Edge tabs into Alt-Tab | +| Friendly Name | Configure the inclusion of app tabs into Alt-Tab | | Element Name | Pressing Alt + Tab shows. | | Location | User Configuration | | Path | Windows Components > Multitasking | diff --git a/windows/client-management/mdm/policy-csp-notifications.md b/windows/client-management/mdm/policy-csp-notifications.md index 10ce383407..1f7b42377a 100644 --- a/windows/client-management/mdm/policy-csp-notifications.md +++ b/windows/client-management/mdm/policy-csp-notifications.md @@ -4,7 +4,7 @@ description: Learn more about the Notifications Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/10/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -38,8 +38,16 @@ ms.topic: reference - -This policy allows you to prevent Windows from displaying notifications to Microsoft account (MSA) and local users in Start (user tile). Notifications include getting users to: reauthenticate; backup their device; manage cloud storage quotas as well as manage their Microsoft 365 or XBOX subscription. If you enable this policy setting, Windows won't send account related notifications for local and MSA users to the user tile in Start. + +This policy allows you to prevent Windows from displaying notifications to Microsoft account (MSA) and local users in Start (user tile). + +Notifications include getting users to: reauthenticate; backup their device; manage cloud storage quotas as well as manage their Microsoft 365 or XBOX subscription. + +- If you enable this policy setting, Windows won't send account related notifications for local and MSA users to the user tile in Start. + +- If you disable or don't configure this policy setting, Windows will send account related notifications for local and MSA users to the user tile in Start. + +No reboots or service restarts are required for this policy setting to take effect. @@ -71,7 +79,12 @@ This policy allows you to prevent Windows from displaying notifications to Micro | Name | Value | |:--|:--| | Name | DisableAccountNotifications | -| Path | AccountNotifications > AT > WindowsComponents > AccountNotifications | +| Friendly Name | Turn off account notifications in Start | +| Location | User Configuration | +| Path | Windows Components > Account Notifications | +| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\AccountNotifications | +| Registry Value Name | DisableAccountNotifications | +| ADMX File Name | AccountNotifications.admx | @@ -318,12 +331,16 @@ No reboots or service restarts are required for this policy setting to take effe - + This policy setting turns on multiple expanded toast notifications in action center. - If you enable this policy setting, the first three notifications of each application will be expanded by default in action center. -- If you disable or don't configure this policy setting, only the first notification of each application will be expanded by default in action center. Windows 10 only. This will be immediately deprecated for Windows 11. No reboots or service restarts are required for this policy setting to take effect. +- If you disable or don't configure this policy setting, only the first notification of each application will be expanded by default in action center. + +Windows 10 only. This will be immediately deprecated for Windows 11. + +No reboots or service restarts are required for this policy setting to take effect. @@ -355,7 +372,12 @@ This policy setting turns on multiple expanded toast notifications in action cen | Name | Value | |:--|:--| | Name | ExpandedToastNotifications | -| Path | WPN > AT > StartMenu > NotificationsCategory | +| Friendly Name | Turn on multiple expanded toast notifications in action center | +| Location | User Configuration | +| Path | Start Menu and Taskbar > Notifications | +| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\PushNotifications | +| Registry Value Name | EnableExpandedToastNotifications | +| ADMX File Name | WPN.admx | diff --git a/windows/client-management/mdm/policy-csp-privacy.md b/windows/client-management/mdm/policy-csp-privacy.md index 5102bebb64..b272736200 100644 --- a/windows/client-management/mdm/policy-csp-privacy.md +++ b/windows/client-management/mdm/policy-csp-privacy.md @@ -4,7 +4,7 @@ description: Learn more about the Privacy Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/10/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -2946,8 +2946,20 @@ If an app is open when this Group Policy object is applied on a device, employee - -This policy setting specifies whether Windows apps can access the human presence sensor. + +This policy setting specifies whether Windows apps can access presence sensing. + +You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting. + +If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access presence sensing by using Settings > Privacy on the device. + +If you choose the "Force Allow" option, Windows apps are allowed to access presence sensing and employees in your organization can't change it. + +If you choose the "Force Deny" option, Windows apps aren't allowed to access presence sensing and employees in your organization can't change it. + +If you disable or don't configure this policy setting, employees in your organization can decide whether Windows apps can access presence sensing by using Settings > Privacy on the device. + +If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app. @@ -2980,8 +2992,12 @@ This policy setting specifies whether Windows apps can access the human presence | Name | Value | |:--|:--| | Name | LetAppsAccessHumanPresence | -| Path | AppPrivacy > AT > WindowsComponents > AppPrivacy | -| Element Name | LetAppsAccessHumanPresence_Enum | +| Friendly Name | Let Windows apps access presence sensing | +| Element Name | Default for all apps. | +| Location | Computer Configuration | +| Path | Windows Components > App Privacy | +| Registry Key Name | Software\Policies\Microsoft\Windows\AppPrivacy | +| ADMX File Name | AppPrivacy.admx | @@ -3006,8 +3022,20 @@ This policy setting specifies whether Windows apps can access the human presence - -List of semi-colon delimited Package Family Names of Microsoft Store Apps. Listed apps are allowed access to the human presence sensor. This setting overrides the default LetAppsAccessHumanPresence policy setting for the specified apps. + +This policy setting specifies whether Windows apps can access presence sensing. + +You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting. + +If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access presence sensing by using Settings > Privacy on the device. + +If you choose the "Force Allow" option, Windows apps are allowed to access presence sensing and employees in your organization can't change it. + +If you choose the "Force Deny" option, Windows apps aren't allowed to access presence sensing and employees in your organization can't change it. + +If you disable or don't configure this policy setting, employees in your organization can decide whether Windows apps can access presence sensing by using Settings > Privacy on the device. + +If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app. @@ -3030,8 +3058,11 @@ List of semi-colon delimited Package Family Names of Microsoft Store Apps. Liste | Name | Value | |:--|:--| | Name | LetAppsAccessHumanPresence | -| Path | AppPrivacy > AT > WindowsComponents > AppPrivacy | -| Element Name | LetAppsAccessHumanPresence_ForceAllowTheseApps_List | +| Friendly Name | Let Windows apps access presence sensing | +| Location | Computer Configuration | +| Path | Windows Components > App Privacy | +| Registry Key Name | Software\Policies\Microsoft\Windows\AppPrivacy | +| ADMX File Name | AppPrivacy.admx | @@ -3056,8 +3087,20 @@ List of semi-colon delimited Package Family Names of Microsoft Store Apps. Liste - -List of semi-colon delimited Package Family Names of Microsoft Store Apps. Listed apps are denied access to the human presence sensor. This setting overrides the default LetAppsAccessHumanPresence policy setting for the specified apps. + +This policy setting specifies whether Windows apps can access presence sensing. + +You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting. + +If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access presence sensing by using Settings > Privacy on the device. + +If you choose the "Force Allow" option, Windows apps are allowed to access presence sensing and employees in your organization can't change it. + +If you choose the "Force Deny" option, Windows apps aren't allowed to access presence sensing and employees in your organization can't change it. + +If you disable or don't configure this policy setting, employees in your organization can decide whether Windows apps can access presence sensing by using Settings > Privacy on the device. + +If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app. @@ -3080,8 +3123,11 @@ List of semi-colon delimited Package Family Names of Microsoft Store Apps. Liste | Name | Value | |:--|:--| | Name | LetAppsAccessHumanPresence | -| Path | AppPrivacy > AT > WindowsComponents > AppPrivacy | -| Element Name | LetAppsAccessHumanPresence_ForceDenyTheseApps_List | +| Friendly Name | Let Windows apps access presence sensing | +| Location | Computer Configuration | +| Path | Windows Components > App Privacy | +| Registry Key Name | Software\Policies\Microsoft\Windows\AppPrivacy | +| ADMX File Name | AppPrivacy.admx | @@ -3106,8 +3152,20 @@ List of semi-colon delimited Package Family Names of Microsoft Store Apps. Liste - -List of semi-colon delimited Package Family Names of Microsoft Store Apps. The user is able to control the human presence privacy setting for the listed apps. This setting overrides the default LetAppsAccessHumanPresence policy setting for the specified apps. + +This policy setting specifies whether Windows apps can access presence sensing. + +You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting. + +If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access presence sensing by using Settings > Privacy on the device. + +If you choose the "Force Allow" option, Windows apps are allowed to access presence sensing and employees in your organization can't change it. + +If you choose the "Force Deny" option, Windows apps aren't allowed to access presence sensing and employees in your organization can't change it. + +If you disable or don't configure this policy setting, employees in your organization can decide whether Windows apps can access presence sensing by using Settings > Privacy on the device. + +If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app. @@ -3130,8 +3188,11 @@ List of semi-colon delimited Package Family Names of Microsoft Store Apps. The u | Name | Value | |:--|:--| | Name | LetAppsAccessHumanPresence | -| Path | AppPrivacy > AT > WindowsComponents > AppPrivacy | -| Element Name | LetAppsAccessHumanPresence_UserInControlOfTheseApps_List | +| Friendly Name | Let Windows apps access presence sensing | +| Location | Computer Configuration | +| Path | Windows Components > App Privacy | +| Registry Key Name | Software\Policies\Microsoft\Windows\AppPrivacy | +| ADMX File Name | AppPrivacy.admx | diff --git a/windows/client-management/mdm/policy-csp-settingssync.md b/windows/client-management/mdm/policy-csp-settingssync.md index 7a792dc92c..954bbaeaf2 100644 --- a/windows/client-management/mdm/policy-csp-settingssync.md +++ b/windows/client-management/mdm/policy-csp-settingssync.md @@ -4,7 +4,7 @@ description: Learn more about the SettingsSync Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/10/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -101,7 +101,14 @@ If you don't set or disable this setting, syncing of the "accessibility" group i - + +Prevent the "language preferences" group from syncing to and from this PC. This turns off and disables the "languages preferences" group on the "Windows backup" settings page in PC settings. + +If you enable this policy setting, the "language preferences", group won't be synced. + +Use the option "Allow users to turn language preferences syncing on" so that syncing is turned off by default but not disabled. + +If you don't set or disable this setting, syncing of the "language preferences" group is on by default and configurable by the user. @@ -118,7 +125,6 @@ If you don't set or disable this setting, syncing of the "accessibility" group i - [!INCLUDE [ADMX-backed policy note](includes/mdm-admx-policy-note.md)] **ADMX mapping**: @@ -126,6 +132,11 @@ If you don't set or disable this setting, syncing of the "accessibility" group i | Name | Value | |:--|:--| | Name | DisableLanguageSettingSync | +| Friendly Name | Do not sync language preferences settings | +| Location | Computer Configuration | +| Path | Windows Components > Sync your settings | +| Registry Key Name | Software\Policies\Microsoft\Windows\SettingSync | +| Registry Value Name | DisableLanguageSettingSync | | ADMX File Name | SettingSync.admx | diff --git a/windows/client-management/mdm/policy-csp-start.md b/windows/client-management/mdm/policy-csp-start.md index c3738fcb56..a62fd83d3f 100644 --- a/windows/client-management/mdm/policy-csp-start.md +++ b/windows/client-management/mdm/policy-csp-start.md @@ -4,7 +4,7 @@ description: Learn more about the Start Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/29/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -1506,8 +1506,8 @@ To validate this policy, do the following steps: - -This policy setting allows you to hide the personalized websites in the recommended section of the Start Menu. If you enable this policy setting, the Start Menu will no longer show personalized website recommendations in the recommended section of the start menu. + +Remove Personalized Website Recommendations from the Recommended section in the Start Menu. @@ -1539,7 +1539,12 @@ This policy setting allows you to hide the personalized websites in the recommen | Name | Value | |:--|:--| | Name | HideRecommendedPersonalizedSites | -| Path | StartMenu > AT > StartMenu | +| Friendly Name | Remove Personalized Website Recommendations from the Recommended section in the Start Menu | +| Location | Computer and User Configuration | +| Path | Start Menu and Taskbar | +| Registry Key Name | Software\Policies\Microsoft\Windows\Explorer | +| Registry Value Name | HideRecommendedPersonalizedSites | +| ADMX File Name | StartMenu.admx | diff --git a/windows/client-management/mdm/policy-csp-system.md b/windows/client-management/mdm/policy-csp-system.md index 58708cd210..700b3d03f2 100644 --- a/windows/client-management/mdm/policy-csp-system.md +++ b/windows/client-management/mdm/policy-csp-system.md @@ -4,7 +4,7 @@ description: Learn more about the System Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/10/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -111,6 +111,8 @@ This policy is only supported up to Windows 10, Version 1703. Please use 'Manage +This policy is deprecated and will only work on Windows 10 version 1809. Setting this policy will have no effect for other supported versions of Windows. + AllowCommercialDataPipeline configures an Azure Active Directory joined device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the Product Terms at< https://go.microsoft.com/fwlink/?linkid=2185086>. To enable this behavior: @@ -120,7 +122,7 @@ To enable this behavior: Windows diagnostic data is collected when the Allow Telemetry policy setting is set to value 1 - Required or above. Configuring this setting doesn't change the Windows diagnostic data collection level set for the device. -If you disable or don't configure this setting, Microsoft will be the controller of the Windows diagnostic data collected from the device and processed in accordance with Microsoft's privacy statement at unless you have enabled policies like 'Allow Update Compliance Processing' or 'Allow Desktop Analytics Processing". +If you disable or don't configure this setting, Microsoft will be the controller of the Windows diagnostic data collected from the device and processed in accordance with Microsoft's privacy statement at unless you have enabled policies like 'Allow Update Compliance Processing' or 'Allow Desktop Analytics Processing'. See the documentation at for information on this and other policies that will result in Microsoft being the processor of Windows diagnostic data. @@ -189,6 +191,8 @@ See the documentation at for i +This policy is deprecated and will only work on Windows 10 version 1809. Setting this policy will have no effect for other supported versions of Windows. + This policy setting, in combination with the Allow Telemetry and Configure the Commercial ID, enables organizations to configure the device so that Microsoft is the processor for Windows diagnostic data collected from the device, subject to the Product Terms at< https://go.microsoft.com/fwlink/?linkid=2185086>. To enable this behavior: @@ -751,6 +755,8 @@ If you disable or don't configure this policy setting, the device will send requ +This policy is deprecated and will only work on Windows 10 version 1809. Setting this policy will have no effect for other supported versions of Windows. + This policy setting, in combination with the Allow Telemetry and Configure the Commercial ID, enables organizations to configure the device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the Product Terms at< https://go.microsoft.com/fwlink/?linkid=2185086>. To enable this behavior: @@ -876,6 +882,8 @@ Specifies whether to allow the user to factory reset the device by using control +This policy is deprecated and will only work on Windows 10 version 1809. Setting this policy will have no effect for other supported versions of Windows. + This policy setting configures an Azure Active Directory joined device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the Product Terms at< https://go.microsoft.com/fwlink/?linkid=2185086>. To enable this behavior: diff --git a/windows/client-management/mdm/policy-csp-webthreatdefense.md b/windows/client-management/mdm/policy-csp-webthreatdefense.md index 06336a8d08..a5834287ac 100644 --- a/windows/client-management/mdm/policy-csp-webthreatdefense.md +++ b/windows/client-management/mdm/policy-csp-webthreatdefense.md @@ -4,7 +4,7 @@ description: Learn more about the WebThreatDefense Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/10/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -40,8 +40,14 @@ ms.topic: reference - -Automatically collect website or app content when additional analysis is needed to help identify security threats. + +This policy setting determines whether Enhanced Phishing Protection can collect additional information-such as content displayed, sounds played, and application memory-when your users enter their work or school password into a suspicious website or app. This information is used only for security purposes and helps SmartScreen determine whether the website or app is malicious. + +- If you enable this policy setting, Enhanced Phishing Protection may automatically collect additional content for security analysis from a suspicious website or app when your users enter their work or school password into that website or app. + +- If you disable this policy setting, Enhanced Phishing Protection won't collect additional content for security analysis when your users enter their work or school password into a suspicious site or app. + +- If this policy isn't set, Enhanced Phishing Protection automatic data collection will honor the end user's settings. @@ -73,7 +79,12 @@ Automatically collect website or app content when additional analysis is needed | Name | Value | |:--|:--| | Name | AutomaticDataCollection | -| Path | WebThreatDefense > AT > WindowsComponents > WebThreatDefense | +| Friendly Name | Automatic Data Collection | +| Location | Computer Configuration | +| Path | Windows Components > Windows Defender SmartScreen > Enhanced Phishing Protection | +| Registry Key Name | Software\Policies\Microsoft\Windows\WTDS\Components | +| Registry Value Name | CaptureThreatWindow | +| ADMX File Name | WebThreatDefense.admx | diff --git a/windows/client-management/mdm/policy-csp-windowsai.md b/windows/client-management/mdm/policy-csp-windowsai.md index 3eda0ccc64..5d7b09569f 100644 --- a/windows/client-management/mdm/policy-csp-windowsai.md +++ b/windows/client-management/mdm/policy-csp-windowsai.md @@ -4,7 +4,7 @@ description: Learn more about the WindowsAI Area in Policy CSP. author: vinaypamnani-msft manager: aaroncz ms.author: vinpa -ms.date: 08/29/2023 +ms.date: 08/30/2023 ms.localizationpriority: medium ms.prod: windows-client ms.technology: itpro-manage @@ -38,7 +38,7 @@ ms.topic: reference - + This policy setting allows you to turn off Windows Copilot. - If you enable this policy setting, users won't be able to use Copilot. The Copilot icon won't appear on the taskbar either. @@ -75,7 +75,12 @@ This policy setting allows you to turn off Windows Copilot. | Name | Value | |:--|:--| | Name | TurnOffWindowsCopilot | -| Path | WindowsCopilot > AT > WindowsComponents > WindowsCopilot | +| Friendly Name | Turn off Windows Copilot | +| Location | User Configuration | +| Path | Windows Components > Windows Copilot | +| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\WindowsCopilot | +| Registry Value Name | TurnOffWindowsCopilot | +| ADMX File Name | WindowsCopilot.admx |