5.11 Managing Administrative Template Files

Administrative template (ADM) files are unicode‑formatted text files that Group Policy uses to describe the location of registry‑based policy settings in the Windows Vista and Windows 7 registry. ADMX files are XML‑based administrative template files, which were introduced with Microsoft Windows Vista Service Pack 1 and are used instead of ADM files.

ADM files are no longer supported. On a computer running Microsoft Windows Vista Service Pack 1 or later, GPA ignores the following default ADM files and only uses the corresponding ADMX files:

  • system.adm

  • inetres.adm

  • conf.adm

  • wmplayer.adm

  • wuau.adm

You need to apply any changes you make to custom ADM files to the corresponding ADMX files. GPA neither displays nor applies new policy settings and modifications you make on ADM files if there is a corresponding ADMX file. For more information about ADM and ADMX files, see the Microsoft Windows documentation.

5.11.1 Understanding ADMX Files

ADMX files are XML‑based administrative template files, which were introduced with Microsoft Windows Vista Service Pack 1 and used instead of ADM files. ADMX files are language‑neutral and support multilingual display of policy settings. The file structure comprises a language‑neutral (.admx) file and a language‑specific (.adml) resource file. Multilingual support allows administrators in different countries to work with the same ADMX files and see the descriptions of the Group Policy settings in the local language. You can only manage ADMX file‑based Group Policy settings on computers running Microsoft Windows Vista Service Pack 1 or later. You can create and edit ADMX files using any XML‑compatible editor.

Microsoft Windows manages ADMX files from the central store that is a central location in the domain. Before you install the GPA Console on a computer running Microsoft Windows Vista Service Pack 1 or later, manually create a central store on the domain controller. The central store enables you to read ADMX files from a single domain‑level location on the domain controller. You cannot manage ADMX files if you do not create a central store. For more information about creating the central store, see the Microsoft Windows documentation.

The ADMX and ADML files are available in the default local policy definition folder, %systemroot%\PolicyDefinitions. When you install the GPA Console on a computer running Microsoft Windows Vista Service Pack 1 or later, the installation process replaces the default local policy definition folder with a local folder, \installDir\Local GPOs\domain name\, and redirects all future ADMX files to the local folder. GPA uses this local folder to temporarily store and work with ADMX files.

NOTE:

  • If you did not configure the central store before installing the GPA Console, you can retrieve the default ADMX and ADML files from the %systemroot%\Windows\PolicyDefinitions_old path folder.

  • After installing the GPA Console, synchronize the ADMX and ADML files from the central store. For more information about synchronizing ADMX and ADML files from the central store, see Section 5.11.3, Synchronizing or Exporting ADMX Files from the Central Store. After synchronizing the ADMX and ADML files, run the GPO Settings report on any GPO in the GP Repository to ensure tools using the local ADMX and ADML files can correctly display the administrative templates policies. For more information about running the GPO Settings Report, see Section 7.2, Viewing GPO Setting Information.

5.11.2 Working with ADMX Files in the GP Repository

While administering domain‑based GPOs, you can use ADMX files available in the GP Repository. You can also share custom ADMX files with other Group Policy administrators in a domain by adding these files to the GP Repository.

In the GPA Console, you can perform the following tasks:

  • Add ADMX files

  • Remove ADMX files

  • Approve ADMX files

  • Unapprove ADMX files

  • Synchronize ADMX files from the central store

  • Export ADMX files to the central store

NOTE:You can perform these tasks only on computers running Microsoft Windows Vista Service Pack 1 or later.

To add or remove ADMX files:

  1. Log on to the GPA Console computer with an account that has Create GPO permissions (for adding an ADMX file) or Delete GPO permissions (for removing an ADMX file).

  2. Start the GPA Console in the Group Policy Administrator program group.

  3. In the left pane, expand GP Repository, and then select the GP Repository.

  4. Select the domain.

  5. On the Action Menu, click Properties.

  6. On the domain Properties dialog box, click the Repository ADMX tab.

  7. Complete one of the following steps:

    • Click Add, and Browse to and select the .admx file you want to add, and then click OK.

    • Select the ADMX file you want to remove, and then click Remove.

You can add ADMX files from any folder to any domain in the GP Repository. All corresponding .adml files should be in the culture subfolders before you add .admx files into the domain in the GP Repository. The culture subfolders are available under the folder where .admx files are available. When you add ADMX files into the domain in the GP Repository, GPA automatically scans the culture subfolders for the language‑specific .adml files.

NOTE:You can add ADMX files without adding the corresponding ADML files. However, GPA does not allow you to edit the settings available in ADMX files until the corresponding ADML files are available in the culture subfolders.

You can select and remove ADMX files from any domain in the GP Repository. Removing .admx files from the GP Repository also removes corresponding .adml files from the GP Repository culture subfolder.

NOTE:If you delete any domain and its corresponding GPOs, you need to manually delete the related ADMX files from the \installDir\Local GPOs\domain name\ folder on all computers running Microsoft Windows Vista Service Pack 1 or later and the GPA Console.

5.11.3 Synchronizing or Exporting ADMX Files from the Central Store

When you install or upgrade GPA, the GP Repository does not contain any ADMX files. To add the default ADMX files provided by Microsoft Windows Vista Service Pack 1 or later, you need to synchronize these files from the central store to the GP Repository. You can also synchronize new or modified ADMX files from the central store to the GP Repository. You need to ensure the central store is available at all times. For more information about the central store, see the Microsoft Windows documentation.

When you synchronize ADMX files from the central store to the GP Repository, the GP Repository contains the central store version of ADMX files. If you create a custom ADMX file with the same name as the central store version of the ADMX file, and then add this file from any folder on your local computer to the GP Repository, GPA overwrites the central store version of the ADMX file in the GP Repository.

Users with Export GPO permissions can export ADMX files into the central store. If the same ADMX file exists in the central store, you have the option to either overwrite the existing file or skip exporting the specific ADMX file and export the remaining ADMX files.

To synchronize or export ADMX files:

  1. Log on to the GPA Console computer with an account that has Import GPO from AD permissions (for synchronizing ADMX files) or Export GPO to AD and Modify Export Status permissions (for exporting ADMX files).

  2. Start the GPA Console in the Group Policy Administrator program group.

  3. In the left pane, expand GP Repository, and then select the GP Repository.

  4. Select the domain.

  5. On the Action Menu, click Properties.

  6. On the domain Properties dialog box, click the Repository ADMX tab.

  7. Perform one of the following tasks:

    • Click Sync from Central Store to synchronize ADMX files.

    • Click Export to export all approved ADMX files.

    NOTE:Changes you make to ADMX files you exported to the central store will be available in the GPO Settings report after you close and re-open the GPA Console.

  8. Click OK.

The AdmxSyncCentralStoreReport.log file provides a report that lists the ADMX files GPA has and has not synchronized from the central store. The AdmxSyncCentralStoreReport.log file is available on the local computer in the \installDir\Log files folder.

The ADMXExport_SummaryReport.log file provides the list of ADMX files that GPA did not export. It is available on the local computer in the \installDir\Log file folder.