Where Are Group Policy Templates Stored On A Domain Controller

The Group Policy Key Store is located in the SYSVOL directory on the domain controllers, replicated between them, and used to store ADMX/ADML GPO template files used to manage Active Directory domain clients. In this article, we'll show how to create a GPO Central Store, copy administrative (admx) templates to it, and update the template files to support the latest Windows versions.

If you have not created a Primal Store for Group Policy files, the list of administrative templates is loaded from the C:\Windows\PolicyDefinitions folder on a local reckoner when you run the domain GPO editor (gpmc.msc – Grouping Policy Management Console). Then you volition see the post-obit bulletin side by side to the Authoritative Templates section of your GPO editor: Policy definitions (ADMS files) retrieved from the local computer.

By default, the domain GPO editor first tries to load ADMX templates from the Cardinal Store, and if it is not available, the local PolicyDefinitions folder is used.

If you desire to strength your GPO editor to use local administrative templates from the electric current computer, create a REG_DWORD parameter with the name EnableLocalStoreOverride and value 1 under the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows registry key.

gpo editor: Policy definitions (ADMS files) retrieved from the local computer

Each computer or server may take different ADMX file versions (for example, depending on Windows version and build). Appropriately, some GPO settings may not exist available to the administrator on some computers. To address this issue, the Grouping Policy administrative templates fundamental repository (GPO Central Shop) was developed.

By default, the GPO Key Store in Active Directory is non created. To create a repository, copy the local PolicyDefinitions folder from any domain controller to the \\woshub.com\SYSVOL\woshub.com\Policies folder.

copy policydefinitions folder to GPO Central Store

Both administrative template (*.admx) and localization files (*.adml) will appear in the PolicyDefinitions binder in SYSVOL. If y'all want to see policy or section names in the GPO editor in German language, copy locale subdirectories with ADML files for all languages that will be used by Group Policy administrators (for example, de_DE and en_US folders).

I recommend using only English ADML files for GPOs (en-US folder), even if you are using the Deutsch Windows version.

Copy administrative template language ADML files to the GPO Central Store

Then update ADMX templates in the Key Shop to the latest Windows version available in your domain environment. The template files in the Central Store are replicated to all domain controllers. Learn more about how to install and update ADMX templates.

Important! Before updating ADMX files in the Grouping Policy Cardinal Store, it is strongly recommended to create a backup copy of this directory.

In my instance, I will copy the PolicyDefinitions folder from Windows 10 to the GPO Central Shop.

You can copy the files using PowerShell:

$Destination = "\\woshub.com\SysVol\woshub.com\Policies\PolicyDefinitions" $Source = "C:\Windows\PolicyDefinitions" Copy-Item -Path $Source\* -Destination $Destination –Recurse –Forcefulness –PassThru

copy PolicyDefinitions admx templates to the sysvol using powershell

You tin can download GPO authoritative templates for all new Windows versions hither: https://docs.microsoft.com/en-us/troubleshoot/windows-client/group-policy/create-and-manage-key-store.

You lot can also copy other ADMX templates to GPO Central Shop. For example, at that place may be administrative templates for Microsoft Office, Microsoft Security Baseline, Firefox, Chrome, LAPS, Java settings, Adobe Reader, etc.

Note. If yous are using legacy ADM template files, they cannot be used in the GPO central repository.

Of import! Always use the latest version of the Grouping Policy Editor (gpedit.msc) to forbid conflicts between Group Policy versions and Administrative Template settings. To practice it, an administrator should work with GPO objects from a computer with the latest Windows version (many administrators adopt editing Group Policies direct from the domain controllers only), or from a estimator that has the latest RSAT package version installed.

Open the Group Policy Management Editor and make sure that there is the message Policy Definitions (ADMX files) retrieved from the primal shop next to Administrative Templates. Local authoritative templates are ignored in this case.

Policy Definitions (ADMX files) retrieved from the central store

Now yous tin can configure your GPOs, and apply new Group Policy settings on the clients.

In some cases, after updating the Central Store you may see multiple errors like shown below when y'all start the GPO editor:

Administrative Templates Resource xxxx referenced in attribute xxxx could not be institute.File \\thirty\SysVol\ 30 \Policies\PolicyDefinitions\30.admx, line 175, column 331

Then make sure that you have updated GPO language files (*.adml) in en-US, de-DE, etc. folders. If the problem persists, restore the PolicyDefinitions directory from a backup folder (or a domain controller backup image).

To brand the new authoritative templates bachelor on all domain controllers, look for the file replication service to copy the changes to other DCs.