How to Set Up Locally-Based System Policies

 Last reviewed: December 11, 1997
Article ID: Q168579
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SUMMARY

Windows NT system policies are designed for when a user logs on to a domain account database. There are times, however, that it is necessary to have policies on a Windows NT workstation or server computer that is not participating in a domain or when you need a different policy for users who are logged on to the local account database.

MORE INFORMATION

There are two basic ways to set up locally-based system policies. To use these on a workstation or server running Windows NT 4.0 (not a domain controller), follow one of the following procedures:

Automatic Update Method

  1. Share the Winnt\System32\Repl\Import\Scripts folder (where Winnt is the name of your Windows directory) as Netlogon.

  2. Grant the group Everyone "Read" Permissions and the group Administrators "Full Control" to this share.

  3. Start System Policy Editor (Poledit.exe) and make the changes for your policy. Start with something simple such as "Remove Run command from Start Menu" from Shell/Restrictions in the Users Properties window.

  4. Double-click Local Computer, double-click Network, double-click System Policies Update, and then click Remote Update so that it is selected.

  5. In the Update Mode box, click Automatic (Use Default Path), and then click OK.

  6. Save your policy to the location listed above as Ntconfig.pol.

NOTE: This configuration will allow you to use both a local and a domain-wide system policy, depending on which user account database the user logs on to.

Remote Update Method

  1. Start System Policy Editor(Poledit.exe) and make the changes for your policy.

  2. Double-click Local Computer, double-click Network, double-click System Policies Update, and then click Remote Update so that it is selected.

  3. In the Update Mode box, click Manual (Use Specific Path), and then click OK.

  4. Type a path name in the Path for Manual Update dialog box (for example, c:\winnt\ system32\repl\import\scripts\Ntconfig.pol).

  5. Save your policy to the location listed above as Ntconfig.pol. While using the Manual Update, you may name the policy file anything you would like; just be sure to enter it into the path in step 4 above.

TIP: Every person or computer that logs on after a policy is in place is subject to the policy. Therefore, it is a good idea to not edit the default user or computer until you are familiar with System Policies. A good idea to use is to make a test user/group account in "User Manager" and then make a specific policy for this user/group in System Policy Editor. After you have the policy working properly you can then transfer the policy to the production environment. 
Keywords          : ntdomain NTSrvWkst kbenv kbtool
Version           : WinNT:4.0
Platform          : winnt
Issue type        : kbhowto

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.