WorkSpace On-Demand 2.0 Feature for Windows ... - IBM Redbooks

2.5.1.2 System policy files
In addition to the user profiles described above, an administrator can also
make use of system policy file to control the user environment. A system
policy file can be implemented on the domain controller so that all users that
log on will have these restrictions or settings applied.
Since the desktop logon and network access settings are stored, for the most
part, in the computer’s registry database, system policy files for users
overwrite settings in the current user area of the registry, and system policy
for computers overwrites the current local machine area of the registry. This
allows you to control user actions (user profiles) as well as computer actions
for users and groups.
The default system policy file contains a default user setting and a default
computer setting. Use the System Policy Editor to manage the user desktop
by changing the default user settings and manage the logon and network
settings by changing the Default Computer settings.
All systems loging on to a domain with system policy files implemented will
use the same uniform policy defined by the system policy file.
When a user logs on to the OS/2 Warp Server Domain, the operating system
looks in the NETLOGON SHARE to see if there is an NTConfig.pol file
present for Windows NT or a Config.pol file present for Windows 9x. If the file
is found, the contents of the file are copied to the local computer’s registry
and is used to overwrite the current user and local machine portions of the
registry.
With the Feature for Windows Clients, there are three System Policy files: one
for administrators, one for a sandbox machine, and one for all other IBM
WorkSpace On-Demand 2.0 Feature for Windows Clients. The location for
each of these is shown in Figure 13.
Feature for Windows Clients architecture 47