deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 05:47:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
windows-itpro-docs/windows/client-management/mdm/policy-csp-controlpolicyconflict.md
MariciaAlforque 4d134ff4f6 replaced nickbrower authorname with MariciaAlforque
2018-05-11 10:45:43 -07:00

3.9 KiB
Raw Blame History

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 - ControlPolicyConflict Policy CSP - ControlPolicyConflict maricia article w10 windows MariciaAlforque 03/12/2018

Policy CSP - ControlPolicyConflict

ControlPolicyConflict policies

ControlPolicyConflict/MDMWinsOverGP

ControlPolicyConflict/MDMWinsOverGP

Home Pro Business Enterprise Education Mobile Mobile Enterprise
cross mark check mark4 check mark4 check mark4 check mark4 cross mark cross mark

Scope:

[!div class = "checklist"]

  • Device

Added in Windows 10, version 1803. This policy allows the IT admin to control which policy will be used whenever both the MDM policy and its equivalent Group Policy (GP) are set on the device.

Note

MDMWinsOverGP only applies to policies in Policy CSP. It does not apply to other MDM settings with equivalent GP settings that are defined on other configuration service providers.

This policy is used to ensure that MDM policy wins over GP when same setting is set by both GP and MDM channel. This policy doesn’t support Delete command. This policy doesn’t support setting the value to be 0 again after it was previously set 1. The default value is 0. The MDM policies in Policy CSP will behave as described if this policy value is set 1.

The following list shows the supported values:

  • 0 (default)
  • 1 - The MDM policy is used and the GP policy is blocked.

The policy should be set at every sync to ensure the device removes any settings that conflict with MDM just as it does on the very first set of the policy. This ensures that:

  • GP settings that correspond to MDM applied settings are not conflicting
  • The current Policy Manager policies are refreshed from what MDM has set
  • Any values set by scripts/user outside of GP that conflict with MDM are removed

The Policy DDF contains the following tags to identify the policies with equivalent GP:

  • <MSFT:ADMXBacked>
  • <MSFT:ADMXMapped>
  • <MSFT:GPRegistryMappedName>
  • <MSFT:GPDBMappedName>

For the list MDM-GP mapping list, see Policies supported by GP .

The MDM Diagnostic report shows the applied configurations states of a device including policies, certificates, configuration sources, and resource information. The report includes a list of blocked GP settings because MDM equivalent is configured, if any. To get the diagnostic report, go to Settings > Accounts > Access work or school > and then click the desired work or school account. Scroll to the bottom of the page to Advanced Diagnostic Report and then click Create Report.

The following list shows the supported values:

  • 0 (default)
  • 1 - The MDM policy is used and the GP policy is blocked.

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.