From 210cf9c3eb5bef2a98047d7c1bb02ecf5cd5c320 Mon Sep 17 00:00:00 2001 From: Ricardo Cabral Date: Sat, 12 Jan 2019 11:07:45 +0000 Subject: [PATCH] Confusion For me this part is confusion: "In Windows 10, version 1809, Delete command and setting the value to be 0 again if it was previously set to 1 will be supported." Suggestion: In Windows 10, version 1809, will be support the Delete command and setting set value to 0 again, if it was previously been set to 1. --- .../client-management/mdm/policy-csp-controlpolicyconflict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/policy-csp-controlpolicyconflict.md b/windows/client-management/mdm/policy-csp-controlpolicyconflict.md index 5369a3d16d..dbbd120bb4 100644 --- a/windows/client-management/mdm/policy-csp-controlpolicyconflict.md +++ b/windows/client-management/mdm/policy-csp-controlpolicyconflict.md @@ -68,7 +68,7 @@ Added in Windows 10, version 1803. This policy allows the IT admin to control wh > 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. The default value is 0. The MDM policies in Policy CSP will behave as described if this policy value is set 1. -Note: 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. In Windows 10, version 1809, Delete command and setting the value to be 0 again if it was previously set to 1 will be supported. +Note: 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. In Windows 10, version 1809, will be support the Delete command and setting set value to 0 again, if it was previously been set to 1. The following list shows the supported values: