diff --git a/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md b/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md index 622d2739af..75c2d3f601 100644 --- a/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md +++ b/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md @@ -213,11 +213,11 @@ Requirements: 4. Rename the extracted Policy Definitions folder to **PolicyDefinitions**. -5. Copy PolicyDefinitions folder to **C:\Windows\SYSVOL\domain\Policies**. +5. Copy PolicyDefinitions folder to **\\contoso.com\SYSVOL\contoso.com\policies\PolicyDefinitions**. If this folder does not exist, then be aware that you will be switching to a [central policy store](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra) for your entire domain. -6. Restart the Domain Controller for the policy to be available. +6. Wait for the SYSVOL DFSR replication to be completed and then restart the Domain Controller for the policy to be available. This procedure will work for any future version as well. @@ -297,4 +297,4 @@ To collect Event Viewer logs: - [Windows 10 Administrative Templates for Windows 10 November 2019 Update 1909](https://www.microsoft.com/download/details.aspx?id=100591) - [Windows 10 Administrative Templates for Windows 10 May 2019 Update 1903](https://www.microsoft.com/download/details.aspx?id=58495) -- [Windows 10 Administrative Templates for Windows 10 October 2018 Update 1809](https://www.microsoft.com/download/details.aspx?id=57576) \ No newline at end of file +- [Windows 10 Administrative Templates for Windows 10 October 2018 Update 1809](https://www.microsoft.com/download/details.aspx?id=57576) diff --git a/windows/client-management/mdm/policy-configuration-service-provider.md b/windows/client-management/mdm/policy-configuration-service-provider.md index 97803c60b7..64caa2be1e 100644 --- a/windows/client-management/mdm/policy-configuration-service-provider.md +++ b/windows/client-management/mdm/policy-configuration-service-provider.md @@ -57,12 +57,12 @@ The following diagram shows the Policy configuration service provider in tree fo

Supported operation is Get. -**Policy/Config/***AreaName* +**Policy/Config/_AreaName_**

The area group that can be configured by a single technology for a single provider. Once added, you cannot change the value.

Supported operations are Add, Get, and Delete. -**Policy/Config/***AreaName/PolicyName* +**Policy/Config/_AreaName/PolicyName_**

Specifies the name/value pair used in the policy.

The following list shows some tips to help you when configuring policies: @@ -81,12 +81,12 @@ The following diagram shows the Policy configuration service provider in tree fo

Supported operation is Get. -**Policy/Result/***AreaName* +**Policy/Result/_AreaName_**

The area group that can be configured by a single technology independent of the providers.

Supported operation is Get. -**Policy/Result/***AreaName/PolicyName* +**Policy/Result/_AreaName/PolicyName_**

Specifies the name/value pair used in the policy.

Supported operation is Get. @@ -102,31 +102,31 @@ The following diagram shows the Policy configuration service provider in tree fo > [!NOTE] > The OPAX settings that are managed by the Microsoft Office Customization Tool are not supported by MDM. For more information about this tool, see [Office Customization Tool](/previous-versions/office/office-2013-resource-kit/cc179097(v=office.15)). -

ADMX files that have been installed by using ConfigOperations/ADMXInstall can later be deleted by using the URI delete operation. Deleting an ADMX file will delete the ADMX file from disk, remove the metadata from the ADMXdefault registry hive, and delete all the policies that were set from the file. The MDM server can also delete all ADMX policies that are tied to a particular app by calling delete on the URI, ./Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/{AppName}. +

ADMX files that have been installed by using **ConfigOperations/ADMXInstall** can later be deleted by using the URI delete operation. Deleting an ADMX file will delete the ADMX file from disk, remove the metadata from the ADMXdefault registry hive, and delete all the policies that were set from the file. The MDM server can also delete all ADMX policies that are tied to a particular app by calling delete on the URI, ./Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/{AppName}.

Supported operations are Add, Get, and Delete. -**Policy/ConfigOperations/ADMXInstall/***AppName* +**Policy/ConfigOperations/ADMXInstall/_AppName_**

Added in Windows 10, version 1703. Specifies the name of the Win32 or Desktop Bridge app associated with the ADMX file.

Supported operations are Add, Get, and Delete. -**Policy/ConfigOperations/ADMXInstall/***AppName*/Policy +**Policy/ConfigOperations/ADMXInstall/_AppName_/Policy**

Added in Windows 10, version 1703. Specifies that a Win32 or Desktop Bridge app policy is to be imported.

Supported operations are Add, Get, and Delete. -**Policy/ConfigOperations/ADMXInstall/***AppName*/Policy/*UniqueID* +**Policy/ConfigOperations/ADMXInstall/_AppName_/Policy/_UniqueID_**

Added in Windows 10, version 1703. Specifies the unique ID of the app ADMX file that contains the policy to import.

Supported operations are Add and Get. Does not support Delete. -**Policy/ConfigOperations/ADMXInstall/***AppName*/Preference +**Policy/ConfigOperations/ADMXInstall/_AppName_/Preference**

Added in Windows 10, version 1703. Specifies that a Win32 or Desktop Bridge app preference is to be imported.

Supported operations are Add, Get, and Delete. -**Policy/ConfigOperations/ADMXInstall/***AppName*/Preference/*UniqueID* +**Policy/ConfigOperations/ADMXInstall/_AppName_/Preference/_UniqueID_**

Added in Windows 10, version 1703. Specifies the unique ID of the app ADMX file that contains the preference to import.

Supported operations are Add and Get. Does not support Delete. @@ -8611,4 +8611,4 @@ The following diagram shows the Policy configuration service provider in tree fo ## Related topics -[Configuration service provider reference](configuration-service-provider-reference.md) \ No newline at end of file +[Configuration service provider reference](configuration-service-provider-reference.md)