 |
|
|
| Using a system policy is very easy for changing Windows NT's registry entries. For example if you want to restrict user access to the display properties, you will have to know which registry entry to change and you will have to know how to change it. With a system policy, it's very easy because all you will have to do is check a box and the System Policy Editor will do the appropriate changes for you. Another advantage is that you can refine your changes to be applied to users, group of users or computers. |
|
|
|
|
| A system policy file is a collection of user, group and computer policies. By default this file does not exist, you have to create it using the System Policy Editor. After you create it you have to save it to the NETLOGON share in all domain controllers so that computers will read the file when users are logging on to the domain. NETLOGON is the sharing name of the "c:\winnt\system32\Repl\import\scripts" folder. |
|
|
|
|
| The default system policies do not exist by default like its name may suggest. It is created when you create the system policy file. When you first create a system policy file it contains only two policies: the default computer policy and the default user policy. These two default system policies are applied when there is no individual user or computer policies. |
|
|
|
|
| The user's roaming or local profile is first applied and then the system policy is applied. System policy takes precedence and is applied in the following order: If the user has an individual user policy it is applied. If not and the user is member of a group that has a system policy, the group policy is applied. If not, the default user policy is applied. Then if the computer the user logs on to has an individual computer policy, it is applied. If not the default computer policy is applied. |
|
United States
(change country or region)