Uh oh! You may have noticed a big difference between the previous two screenshots. When I was pulling ADMX files from my local hard drive, I had a bunch of settings in there. Now that I have changed over to using the Central Store for ADMX files, my Administrative Templates folder is empty!

This is because the new folders we created are also empty. We simply need to populate our new Central Store folders with the existing ADMX and ADML files. They are still sitting on the hard drive of my Domain Controller, so go ahead and make the following file copies on a Domain Controller:

• Copy %systemroot%PolicyDefinitions to %systemroot%SYSVOLsysvolmydomain.localPoliciesPolicyDefinitions.
• Copy %systemroot%PolicyDefinitionsen-US to %systemroot%SYSVOLsysvolmydomain.localPoliciesPolicyDefinitionsen-US.

Looking inside GPMC, we now have all of our Administrative Templates back in the console, and can also see that they are still being pulled from the Central Store:

I have left my DirectAccess Connectivity Assistant ADMX/ADML out purposefully, so that we can prove that in the future, whenever you need to import a new ADMX/ADML file combination, the only thing you have to do is copy them into their corresponding folders inside the Central Store's SYSVOL. After copying the files into their Central Store folders, those new template settings will then be available to access from any GPMC inside your domain. If I re-copy my DCA's ADMX/ADML files into their corresponding SYSVOL folders, opening up GPMC from LAPTOP1 immediately shows me those new settings: