The information in this article applies to:
SUMMARYThis article describes the location of ADM files while they are a component of a Group Policy Object (GPO), and the location of additional ADM template files. MORE INFORMATION
Administrative (ADM) Templates are files that define the settings the administrator can configure through the Group Policy utility.
Active Directory Group Policy ObjectsWhen you create Group Policy Objects using the Active Directory Users and Computers or Active Directory Sites and Services utilities, you have data in the Active Directory and in SYSVOL (an automatically replicated folder used by domain controllers of the same domain). In SYSVOL, each Group Policy Object has an associated folder to store files that are components of the Group Policy. The template files used by a given GPO are stored in an "ADM" folder. For example, if the GUID (Globally Unique Identifier) associated with the "Default Domain Policy" GPO is {31B2F340-016D-11D2-945F-00C04FB984F9}, the local path to the ADM folder associated with this GPO would be the following path<SYSVOL Location>\Domain Name\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Admwhere <SYSVOL Location> is the location of the SYSVOL folder. The ADM folder within the associated GPO folder does not exist until the Group Policy Object has been opened for the first time and you click either the Computer or User configuration node. When you create a GPO in the Active Directory and a User or Computer configuration node is selected, the Inetres.adm and System.adm files are copied from the %SystemRoot%\Inf folder on the client computer to the appropriate ADM folder for the GPO in SYSVOL. When an administrator adds an ADM template to a Group Policy Object that exists in the Active Directory, the ADM file is copied from the location the user specified into the ADM folder of the associated Group Policy Object in SYSVOL. In either case, when the File Replication Service (FRS) discovers the changed file (in this case, a new file), it replicates that file to other domain controllers in the same domain. When another administrator opens the Group Policy Object, the ADM file is present to be loaded along with the Group Policy Object which allows the available settings to be displayed in the Group Policy utility. If the ADM file is not there, the settings remains in the Group Policy Object, but is not visible using the user interface. For more information about how to identify the directory in SYSVOL associated with a Group Policy Object, please refer to the following Knowledge Base article: Q216359 How to Identify Group Policy Objects in the Active Directory and SYSVOL Local Group Policy Objects (LGPO)Windows 2000 creates the Local Group Policy Object automatically. The administrator of the computer can use the LGPO to define settings of their own, but GPO's at the domain can override the local settings.When you create an LGPO, you create the following folder: %SystemRoot%\SYSTEM32\GroupPolicyWhen you use the "Administrative Template" settings for the first time, the Inetres.adm and System.adm files are copied from the INF folder on the local computer to the appropriate ADM folder under the GroupPolicy folder. When an ADM template is added to a Local Group Policy Object (LGPO), the ADM file from the location the user specified is copied to this folder. When the administrator opens the Local Group Policy Object again, the ADM file loads from the ADM folder under the GroupPolicy folder. Additional query words:
Keywords : kbenv ntdomain |
|
Last Reviewed: December 29, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |