Configuration options updating operating system
You can then use these template files to configure or analyze system security using other tools.
If you select Propagate inheritable permissions to all subfolders and files, normal Windows 2000 ACL inheritance procedures are in effect.If you are not using the common infrastructure, you need to make the appropriate changes to this document.The most current information about hardware requirements and compatibility for servers, clients, and peripherals is available at the Product Compatibility Web site (Note: If you installed Windows 2000 in a different drive and/or directory, that path will display instead of C:\WINNT.) However, in this guide you are going to modify the predefined secure workstation or server template (Securews.inf) that is included with Windows 2000.To view the settings defined by Securews.inf: A Restricted Group Policy allows you to define who should and should not belong to a specific group.This guide assumes that you have run the procedures in the two-part "Step by Step Guide to A Common Infrastructure for Windows 2000 Server Deployment"
The common infrastructure documents specify a particular hardware and software configuration.
Local security policy is exposed through the Security Settings extension to Group Policy.
Local security policy includes the Account Policy and Local Policy areas only.
Effective policy describes the combined local, domain, and organizational unit policies for each setting.
This distinction is made because local policy settings can be overwritten by domain or OU policy settings.
Choosing the option: Do not allow permissions on this file or folder to be replaced for an object in a template makes sense only if an ancestor of that object is configured to overwrite children.