Article ID: 269799
Article Last Modified on 10/31/2006
APPLIES TO
- Microsoft Windows 2000 Professional Edition
This article was previously published under Q269799
SUMMARY
You can use a Windows-based computer in a non-domain environment to use local group policies to secure the workstation. This implementation is not designed to secure a Windows-based computer for individual users who log on to the computer.
You can, however, configure a Windows-based computer to use system policies. This allows administrators to configure policies on Windows-based computers for individual users who log on to the computer.
You can configure Windows to use system policies. This allows administrators to configure policies on a Windows-based computer for each individual user.
To create the system policy, use the Poledit.exe file that is located on the Windows CD-ROM or contact Microsoft Product Support for the PolEdit.exe file and the supporting files. The following table lists the files that you need and the location to which they must be copied.
| File name | Location |
|---|---|
| Poledit.exe | %SystemRoot% |
| Common.adm | %SystemRoot%\Inf |
| Winnt.adm | %SystemRoot%\Inf |
| Poledit.chm | %SystemRoot%\Help |
Implementing System Policies
- Start System Policy Editor (Poledit.exe) and make the changes for your policy.For additional information about system policies, click the article number below to view the article in the Microsoft Knowledge Base:
161334 Guide To Windows NT 4.0 Profiles and Policies (Part 1 of 6)
- On the File menu, click Save As, and then save the policy file on your hard disk. For example, save the file in the Ntconfig.pol folder.
- On the File menu, click Open Registry.
- Double-click Local Computer, double-click Network, double-click System Policies Update, and then click to select the Remote Update check box.
- In the Update Mode box, click Manual (use the specific path), type a path name in the Path for Manual Update dialog box (for example, type c:\ntconfig.pol), and then click OK.
- Save your policy to the Ntconfig.pol folder, and then quit Policy Editor.
- Restart your computer for the changes to the policy to take effect.
WARNING: Every person or computer that logs on to the computer 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. You may want to make a test user account in Local Users and Computers, and then make specific policy for this user in System Policy Editor. After the policy is working properly, you can transfer the policy to the production environment.
back to the top
Keywords: kbenv kbhowto kbhowtomaster KB269799
