From b1148fab9b9994ac373b9f8b1e91e9cb67f90ab0 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 24 Mar 2020 15:00:42 -0700 Subject: [PATCH] Formatting --- windows/client-management/mdm/policy-csp-restrictedgroups.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-restrictedgroups.md b/windows/client-management/mdm/policy-csp-restrictedgroups.md index 77dbb8f681..0c768e2b75 100644 --- a/windows/client-management/mdm/policy-csp-restrictedgroups.md +++ b/windows/client-management/mdm/policy-csp-restrictedgroups.md @@ -81,9 +81,9 @@ For example, you can create a Restricted Groups policy to allow only specified u > [!CAUTION] > Attempting to remove the built-in administrator from the Administrators group will result in failure with the following error: -> | Error Code in Hex | Error Code in Dec| Symbolic Name | Error Description | Header | +> | Error Code | Symbolic Name | Error Description | Header | > |----------|----------|----------|----------|----------| -> |0x55b|1371|ERROR_SPECIAL_ACCOUNT|Cannot perform this operation on built-in accounts.|winerror.h| +> |0x55b (Hex)
1371 (Dec)|ERROR_SPECIAL_ACCOUNT|Cannot perform this operation on built-in accounts.|winerror.h| Starting in Windows 10, version 1809, you can use this schema for retrieval and application of the RestrictedGroups/ConfigureGroupMembership policy. A minimum occurrence of 0 members when applying the policy implies clearing the access group and should be used with caution.