Scenario 1: Editing the Local GPO Using ADMX Files
This scenario shows you how to edit local Group Policy using ADMX files.
Editing the Administrative Template Policy Settings of the Local GPO Using ADMX Files
You must use a Windows Vista–based computer to edit local GPOs using ADMX files.
To edit administrative template policy settings using ADMX files
To open Group Policy Object Editor on a Windows Vista machine, press the Windows logo key + R, and then type GPEDIT.msc.
Group Policy Object Editor will automatically read all ADMX files stored in the %systemroot%\PolicyDefinitions\ folder.
Locate the policy setting you wish to edit and open it.
- You can still remove and add ADM files to the GPO using the Add/Remove Templates menu option. There is no user interface for adding or removing ADMX files in Windows Vista.To add ADMX files to the Group Policy editing session, copy the ADMX files to the %systemroot%\PolicyDefinitions\ folder and restart Group Policy Object Editor.
- Policy settings from ADMX files will be displayed under the Administrative Template node. Policy settings from ADM files will be displayed under the Classic Administrative Templates (ADM) node.
- Group Policy Object Editor will continue to recognize custom ADM files you have in your existing environment, but will not consume any ADM file that has been superseded by ADMX files. If you have edited any of the following ADM files to modify existing or create new policy settings, they will not be consumed by the Windows Vista–based Group Policy Object Editor: System.adm, Inetres.adm, Conf,adm, Wmplayer.adm, and Wuau.adm.