Microsoft Windows NT 4.0 - Manual (Page 48)

40 Microsoft Windows NT Server White Paper
4. Browse to locate the directory x:\Admin\Apptools\Poledit\ (where x is drive
A through Z) on the Windows 95 compact disc.
5. Select both Group Policies and the System Policy Editor, and then click
OK to Install.
It is important that you run the setup program as described above. Undesir-
able results will occur if you merely copy the Policy Editor and related files to
the Windows 95-based computer.
To install the System Policy Editor from a Windows NT 4.0 Server:
1. Copy the Poledit.exe file from the Windows NT Server 4.0 to the \windows
directory of the Windows 95-based machine.
2. Copy the Common.adm and Windows.adm files from the Windows NT 4.0-
based server to the \windows directory of the Windows 95-based machine.
3. Create a shortcut to the System Policy Editor executable (Poledit.exe,
located in the \windows directory of the Windows 95-based computer).
Updating the Registry with the System Policy Editor
The System Policy Editor allows you to easily update the registry settings to
generate the correct environment for a particular user or group of users. You
can use the System Policy Editor in two ways:
•
You can open the local registry through the System Policy Editor, and
change the settings for the local user and computer.
•
You can modify an existing policy file or create a new one to contain the
settings that you want to enforce on a per user, per computer, or com-
bined user/computer basis.
When you open the System Policy Editor in registry mode, you can modify
the registry of the local computer without having to use Regedt32.exe or Re-
gedit.exe. However, you can modify only those values exposed by the
templates; the System Policy Editor does not give you access to the entire
registry.
System Policy Editor Template (.Adm) Files
The System Policy Editor uses administrative (.adm) files to determine which
registry settings can be modified. An .adm file is a hierarchical template, and
consists of categories and subcategories that dictate which settings are avail-
able through the user interface. An .adm file contains the registry locations
where changes should be made for a particular selection, additional options for
a particular selection, restrictions, and in some cases, the default value for a
selection.
When you run the System Policy Editor and select Policy Template from
the Options menu, a window similar to the one shown below appears. This
window displays the names of the .adm files that are currently being used. If
you need to make changes to custom applications, for example, you can add a
template to this list. To ensure that the system uses the latest administrative
information, the System Policy Editor reads the custom .adm files each time it
starts.
For detailed instructions when creating .adm files, see the section “Creating