The area group that can be configured by a single technology for a single provider. If a configuration source wants to query the result of conflict resolution (for example, if Exchange and MDM both attempt to set a value,) the configuration source can use the Policy/Result path to retrieve the resulting value. One policy can be configured by multiple configuration sources. The configuration source can use this path to set policy values and later query any policy value that it previously set. Node for grouping all policies configured by one source. The root node for the Policy configuration service provider.

The following diagram shows the Policy configuration service provider in tree format as used by both Open Mobile Alliance Device Management (OMA DM) and OMA Client Provisioning. Vendor/MSFT/Policy/Result/ AreaName/PolicyName to get the result. Vendor/MSFT/Policy/Config/ AreaName/PolicyName to configure the policy. Device/Vendor/MSFT/Policy/Result/ AreaName/PolicyName to get the result.įor device wide configuration the Device/ portion may be omitted from the path, deeming the following paths respectively equivalent to the paths provided above: Device/Vendor/MSFT/Policy/Config/ AreaName/PolicyName to configure the policy. User/Vendor/MSFT/Policy/Result/ AreaName/PolicyName to get the result. User/Vendor/MSFT/Policy/Config/ AreaName/PolicyName to configure the policy. To configure a policy under a specific scope (user vs. The allowed scope of a specific policy is represented below its table of supported Windows editions. Other policies can be configured at the user level, meaning the policy will only take effect for that user. Some policies can only be configured at the device level, meaning the policy will take effect independent of who is logged into the device. Policy scope is the level at which a policy can be configured.

Windows 10 csp