1. The Group Policy Object Editor will launch, and it will be focused on the selected GPO. Under the GPO name, you see two nodes: Computer Configuration and User Configuration | 1. The Group Policy Object Editor will launch and it will be focused on the selected GPO. Under the GPO name you see two nodes Computer Configuration and User Configuration. To demonstrate administrative templates let s focus on the User Settings. Expand the User Configuration node then expand the Administrative Templates node. You ll see a tree of folders representing the available areas for administrative template controls Fig. . Figure The Group Policy Object Editor focused on the Default Domain Policy 2. What you see is a graphical representation of the ADM files that are loaded by this particular GPO. The ADM files dictate which folders registry keys and values are presented here. Each folder such as Control Panel Network and System represents ADM categories. Within each category are sets of policies that you can specify. For example if you expand the System folder you will see a subfolder named Power Management. After you expand a specific subfolder the right pane of the Group Policy Object Editor window will expose the list of all available registry limitations that can be set in relation to the selected feature. For example the Power Management folder contains the Prompt for password on resume from hibernate suspend policy. When you configure this policy the appropriate setting will be created or modified in registry. 3. To configure a specific policy simply double-click it to open the respective Properties window Fig. . Previously in this section when discussing the ADM file structure I pointed out the new keywords appearing with each new Windows version. Now notice the effect they have on the GPO Editor user interface. For example the EXPLAIN keyword appears in the Properties window s Explain tab which you can click to read Help text associated with the selected policy item. Also notice the Supported on At least Windows XP Professional. string at the bottom of this dialog. It appeared because the SUPPORTED statement was included in the .
