36 KiB
title, description, ms.author, ms.topic, ms.prod, ms.technology, author, ms.date
| title | description | ms.author | ms.topic | ms.prod | ms.technology | author | ms.date |
|---|---|---|---|---|---|---|---|
| Policy CSP - System | Policy CSP - System | maricia | article | w10 | windows | nickbrower | 03/12/2018 |
Policy CSP - System
System policies
- System/AllowBuildPreview
- System/AllowEmbeddedMode
- System/AllowExperimentation
- System/AllowFontProviders
- System/AllowLocation
- System/AllowStorageCard
- System/AllowTelemetry
- System/AllowUserToResetPhone
- System/BootStartDriverInitialization
- System/DisableEnterpriseAuthProxy
- System/DisableOneDriveFileSync
- System/DisableSystemRestore
- System/FeedbackHubAlwaysSaveDiagnosticsLocally
- System/LimitEnhancedDiagnosticDataWindowsAnalytics
- System/TelemetryProxy
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
 |
 |
|
|
|
|
[!div class = "checklist"]
- Device
Note
This policy setting applies only to devices running Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education, Windows 10 Mobile, and Windows 10 Mobile Enterprise.
This policy setting determines whether users can access the Insider build controls in the Advanced Options for Windows Update. These controls are located under "Get Insider builds," and enable users to make their devices available for downloading and installing Windows preview software.
If you enable or do not configure this policy setting, users can download and install Windows preview software on their devices. If you disable this policy setting, the item "Get Insider builds" will be unavailable.
ADMX Info:
- GP English name: Toggle user control over Insider builds
- GP name: AllowBuildPreview
- GP path: Data Collection and Preview Builds
- GP ADMX file name: AllowBuildPreview.admx
The following list shows the supported values:
- 0 – Not allowed. The item "Get Insider builds" is unavailable, users are unable to make their devices available for preview software.
- 1 – Allowed. Users can make their devices available for downloading and installing preview software.
- 2 (default) – Not configured. Users can make their devices available for downloading and installing preview software.
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
[!div class = "checklist"]
- Device
Specifies whether set general purpose device to be in embedded mode.
Most restricted value is 0.
The following list shows the supported values:
- 0 (default) – Not allowed.
- 1 – Allowed.
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
[!div class = "checklist"]
- Device
Note
This policy is not supported in Windows 10, version 1607.
This policy setting determines the level that Microsoft can experiment with the product to study user preferences or device behavior.
Most restricted value is 0.
The following list shows the supported values:
- 0 – Disabled.
- 1 (default) – Permits Microsoft to configure device settings only.
- 2 – Allows Microsoft to conduct full experimentations.
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
2 |
2 |
2 |
2 |
2 |
2 |
[!div class = "checklist"]
- Device
Added in Windows 10, version 1703. Boolean policy setting that determines whether Windows is allowed to download fonts and font catalog data from an online font provider. If you enable this setting, Windows periodically queries an online font provider to determine whether a new font catalog is available. Windows may also download font data if needed to format or render text. If you disable this policy setting, Windows does not connect to an online font provider and only enumerates locally-installed fonts.
This MDM setting corresponds to the EnableFontProviders Group Policy setting. If both the Group Policy and the MDM settings are configured, the group policy setting takes precedence. If neither is configured, the behavior depends on a DisableFontProviders registry value. In server editions, this registry value is set to 1 by default, so the default behavior is false (disabled). In all other editions, the registry value is not set by default, so the default behavior is true (enabled).
This setting is used by lower-level components for text display and fond handling and has not direct effect on web browsers, which may download web fonts used in web content.
Note
Reboot is required after setting the policy; alternatively you can stop and restart the FontCache service.
ADMX Info:
- GP English name: Enable Font Providers
- GP name: EnableFontProviders
- GP path: Network/Fonts
- GP ADMX file name: GroupPolicy.admx
The following list shows the supported values:
- 0 - false - No traffic to fs.microsoft.com and only locally-installed fonts are available.
- 1 - true (default) - There may be network traffic to fs.microsoft.com and downloadable fonts are available to apps that support them.
To verify if System/AllowFontProviders is set to true:
- After a client machine is rebooted, check whether there is any network traffic from client machine to fs.microsoft.com.
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
[!div class = "checklist"]
- Device
Specifies whether to allow app access to the Location service.
Most restricted value is 0.
While the policy is set to 0 (Force Location Off) or 2 (Force Location On), any Location service call from an app would trigger the value set by this policy.
When switching the policy back from 0 (Force Location Off) or 2 (Force Location On) to 1 (User Control), the app reverts to its original Location service setting.
For example, an app's original Location setting is Off. The administrator then sets the AllowLocation policy to 2 (Force Location On.) The Location service starts working for that app, overriding the original setting. Later, if the administrator switches the AllowLocation policy back to 1 (User Control), the app will revert to using its original setting of Off.
ADMX Info:
- GP English name: Turn off location
- GP name: DisableLocation_2
- GP path: Windows Components/Location and Sensors
- GP ADMX file name: Sensors.admx
The following list shows the supported values:
- 0 – Force Location Off. All Location Privacy settings are toggled off and greyed out. Users cannot change the settings, and no apps are allowed access to the Location service, including Cortana and Search.
- 1 (default) – Location service is allowed. The user has control and can change Location Privacy settings on or off.
- 2 – Force Location On. All Location Privacy settings are toggled on and greyed out. Users cannot change the settings and all consent permissions will be automatically suppressed.
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
[!div class = "checklist"]
- Device
Controls whether the user is allowed to use the storage card for device storage. This setting prevents programmatic access to the storage card.
Most restricted value is 0.
The following list shows the supported values:
- 0 – SD card use is not allowed and USB drives are disabled. This setting does not prevent programmatic access to the storage card.
- 1 (default) – Allow a storage card.
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
[!div class = "checklist"]
- User
- Device
Allow the device to send diagnostic and usage telemetry data, such as Watson.
The following tables describe the supported values:
Windows 8.1 Values:
- 0 - Not allowed.
- 1 – Allowed, except for Secondary Data Requests.
- 2 (default) – Allowed.
Windows 10 Values:
- 0 – Security. Information that is required to help keep Windows more secure, including data about the Connected User Experience and Telemetry component settings, the Malicious Software Removal Tool, and Windows Defender. Note: This value is only applicable to Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile Enterprise, Windows 10 IoT Core (IoT Core), and Windows Server 2016. Using this setting on other devices is equivalent to setting the value of 1.
- 1 – Basic. Basic device info, including: quality-related data, app compatibility, app usage data, and data from the Security level.
- 2 – Enhanced. Additional insights, including: how Windows, Windows Server, System Center, and apps are used, how they perform, advanced reliability data, and data from both the Basic and the Security levels.
- 3 – Full. All data necessary to identify and help to fix problems, plus data from the Security, Basic, and Enhanced levels.
Important
If you are using Windows 8.1 MDM server and set a value of 0 using the legacy AllowTelemetry policy on a Windows 10 Mobile device, then the value is not respected and the telemetry level is silently set to level 1.
Most restricted value is 0.
ADMX Info:
- GP English name: Allow Telemetry
- GP name: AllowTelemetry
- GP element: AllowTelemetry
- GP path: Data Collection and Preview Builds
- GP ADMX file name: DataCollection.admx
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
[!div class = "checklist"]
- Device
Specifies whether to allow the user to factory reset the phone by using control panel and hardware key combination.
Most restricted value is 0.
The following list shows the supported values: orted values:
- 0 – Not allowed.
- 1 (default) – Allowed to reset to factory default settings.
System/BootStartDriverInitialization
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
[!div class = "checklist"]
- Device
This policy setting allows you to specify which boot-start drivers are initialized based on a classification determined by an Early Launch Antimalware boot-start driver. The Early Launch Antimalware boot-start driver can return the following classifications for each boot-start driver:
- Good: The driver has been signed and has not been tampered with.
- Bad: The driver has been identified as malware. It is recommended that you do not allow known bad drivers to be initialized.
- Bad, but required for boot: The driver has been identified as malware, but the computer cannot successfully boot without loading this driver.
- Unknown: This driver has not been attested to by your malware detection application and has not been classified by the Early Launch Antimalware boot-start driver.
If you enable this policy setting you will be able to choose which boot-start drivers to initialize the next time the computer is started.
If you disable or do not configure this policy setting, the boot start drivers determined to be Good, Unknown or Bad but Boot Critical are initialized and the initialization of drivers determined to be Bad is skipped.
If your malware detection application does not include an Early Launch Antimalware boot-start driver or if your Early Launch Antimalware boot-start driver has been disabled, this setting has no effect and all boot-start drivers are initialized.
Tip
This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.
You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to 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.
ADMX Info:
- GP English name: Boot-Start Driver Initialization Policy
- GP name: POL_DriverLoadPolicy_Name
- GP path: System/Early Launch Antimalware
- GP ADMX file name: earlylauncham.admx
System/DisableEnterpriseAuthProxy
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
3 |
3 |
3 |
3 |
|
|
[!div class = "checklist"]
- Device
This policy setting blocks the Connected User Experience and Telemetry service from automatically using an authenticated proxy to send data back to Microsoft on Windows 10. If you disable or do not configure this policy setting, the Connected User Experience and Telemetry service will automatically use an authenticated proxy to send data back to Microsoft. Enabling this policy will block the Connected User Experience and Telemetry service from automatically using an authenticated proxy.
ADMX Info:
- GP English name: Configure Authenticated Proxy usage for the Connected User Experience and Telemetry service
- GP name: DisableEnterpriseAuthProxy
- GP element: DisableEnterpriseAuthProxy
- GP path: Data Collection and Preview Builds
- GP ADMX file name: DataCollection.admx
System/DisableOneDriveFileSync
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
2 |
2 |
2 |
2 |
|
|
[!div class = "checklist"]
- Device
Added in Windows 10, version 1703. Allows IT Admins to prevent apps and features from working with files on OneDrive. If you enable this policy setting:
- Users cannot access OneDrive from the OneDrive app or file picker.
- Microsoft Store apps cannot access OneDrive using the WinRT API.
- OneDrive does not appear in the navigation pane in File Explorer.
- OneDrive files are not kept in sync with the cloud.
- Users cannot automatically upload photos and videos from the camera roll folder.
If you disable or do not configure this policy setting, apps and features can work with OneDrive file storage.
ADMX Info:
- GP English name: Prevent the usage of OneDrive for file storage
- GP name: PreventOnedriveFileSync
- GP path: Windows Components/OneDrive
- GP ADMX file name: SkyDrive.admx
The following list shows the supported values:
- 0 (default) – False (sync enabled).
- 1 – True (sync disabled).
To validate on Desktop, do the following:
- Enable policy.
- Restart machine.
- Verify that OneDrive.exe is not running in Task Manager.
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
[!div class = "checklist"]
- Device
Allows you to disable System Restore.
This policy setting allows you to turn off System Restore.
System Restore enables users, in the event of a problem, to restore their computers to a previous state without losing personal data files. By default, System Restore is turned on for the boot volume.
If you enable this policy setting, System Restore is turned off, and the System Restore Wizard cannot be accessed. The option to configure System Restore or create a restore point through System Protection is also disabled.
If you disable or do not configure this policy setting, users can perform System Restore and configure System Restore settings through System Protection.
Also, see the "Turn off System Restore configuration" policy setting. If the "Turn off System Restore" policy setting is disabled or not configured, the "Turn off System Restore configuration" policy setting is used to determine whether the option to configure System Restore is available.
Tip
This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.
You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to 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.
ADMX Info:
- GP English name: Turn off System Restore
- GP name: SR_DisableSR
- GP path: System/System Restore
- GP ADMX file name: systemrestore.admx
System/FeedbackHubAlwaysSaveDiagnosticsLocally
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
| 4 |
4 |
4 |
4 |
4 |
[!div class = "checklist"]
- Device
Added in Windows 10, version 1803. When filing feedback in the Feedback Hub, diagnostic logs are collected for certain types of feedback. We now offer the option for users to save it locally, in addition to sending it to Microsoft. This policy will allow enterprises to mandate that all diagnostics are saved locally for use in internal investigations.
The following list shows the supported values:
- 0 (default) - False. The Feedback Hub will not always save a local copy of diagnostics that may be created when a feedback is submitted. The user will have the option to do so.
- 1 - True. The Feedback Hub should always save a local copy of diagnostics that may be created when a feedback is submitted.
System/LimitEnhancedDiagnosticDataWindowsAnalytics
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
3 |
3 |
3 |
3 |
3 |
3 |
[!div class = "checklist"]
- Device
This policy setting, in combination with the System/AllowTelemetry policy setting, enables organizations to send Microsoft a specific set of diagnostic data for IT insights via Windows Analytics services.
To enable this behavior you must complete two steps:
- Enable this policy setting
- Set Allow Telemetry to level 2 (Enhanced)
When you configure these policy settings, a basic level of diagnostic data plus additional events that are required for Windows Analytics are sent to Microsoft. These events are documented here: Windows 10, version 1709 enhanced telemetry events and fields used by Windows Analytics.
Enabling enhanced diagnostic data in the System/AllowTelemetry policy in combination with not configuring this policy will also send the required events for Windows Analytics, plus additional enhanced level telemetry data. This setting has no effect on computers configured to send full, basic or security level diagnostic data to Microsoft.
If you disable or do not configure this policy setting, then the level of diagnostic data sent to Microsoft is determined by the System/AllowTelemetry policy.
ADMX Info:
- GP English name: Limit Enhanced diagnostic data to the minimum required by Windows Analytics
- GP name: LimitEnhancedDiagnosticDataWindowsAnalytics
- GP element: LimitEnhancedDiagnosticDataWindowsAnalytics
- GP path: Data Collection and Preview Builds
- GP ADMX file name: DataCollection.admx
| Home | Pro | Business | Enterprise | Education | Mobile | Mobile Enterprise |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
[!div class = "checklist"]
- Device
Allows you to specify the fully qualified domain name (FQDN) or IP address of a proxy server to forward Connected User Experiences and Telemetry requests. The format for this setting is <server>:<port>. The connection is made over a Secure Sockets Layer (SSL) connection. If the named proxy fails, or if there is no proxy specified when this policy is enabled, the Connected User Experiences and Telemetry data will not be transmitted and will remain on the local device.
If you disable or do not configure this policy setting, Connected User Experiences and Telemetry will go to Microsoft using the default proxy configuration.
ADMX Info:
- GP English name: Configure Connected User Experiences and Telemetry
- GP name: TelemetryProxy
- GP element: TelemetryProxyName
- GP path: Data Collection and Preview Builds
- GP ADMX file name: DataCollection.admx
Footnote:
- 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.