Windows Server 2008 and Windows Vista : Using .adm Template Language (part 4) - Syntax for Updating the GPME Interface - POLICY

4.3 POLICY

The POLICY syntax is used to identify a policy setting that the user can modify within the GPME. The POLICY syntax generates the “policy settings displayed” list of policies in the details pane of the GPME, under the folders, which are created by the CATEGORY syntax.

If you want different registry paths and values to appear under a single policy within the GPME, use the POLICY syntax followed by the KEYNAME syntax. However, if multiple registry paths and values that fall under the same KEYNAME must be placed under the same policy, the KEYNAME syntax must precede the POLICY syntax.

An example of the KEYNAME statement followed by the POLICY statement containing multiple registry values is shown here:

CLASS USER
CATEGORY "Microsoft Custom ADM Entries"
   POLICY "Controls hidden files."
   KEYNAME "SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced"
     PART "Do you want to see hidden files?" TEXT
     END PART
     PART "Hidden Files and Folders:" DROPDOWNLIST
     VALUENAME Hidden
        ITEMLIST
        NAME "Yes" VALUE Numeric 1
        NAME "No" VALUE Numeric 2
        END ITEMLIST
     END PART
     PART "Do you want to see Super Hidden files?" TEXT
     END PART
     PART "Super Hidden" DROPDOWNLIST
     VALUENAME Showsuperhidden
        ITEMLIST
        NAME "Yes" VALUE Numeric 1
        NAME "No" VALUE Numeric 0
        END ITEMLIST
     END PART
  END POLICY
END CATEGORY

					  

Note

The POLICY syntax requires an END POLICY to tell the GPME when to stop grouping the settings together. Additional syntax that you can use in conjunction with POLICY includes KEYNAME, ITEMLIST, VALUENAME, VALUEON, VALUEOFF, POLICY, PART, END, ACTIONLISTON, ACTIONLISTOFF, and CLIENTTEXT.

This .adm snippet generates the interface in the GPME, as shown in Figure 2.

Figure 2. Shown is an example of the GPME configuration that results from having multiple registry values in the same .adm template.