Learning about group policy and updating administrative templates
A GPO can be used to filter objects based on security group membership, which allows administrators to manage computers and users in either a centralized or a de-centralized manner.
To do this, administrators can use filtering based on security groups to define the scope of Group Policy management, so that Group Policy can be applied centrally at the domain level, or in a decentralized manner at the OU level, and can then be filtered again by security groups.
Please use this instruction set to begin to understand how Group Policy works and begin to think about how your organization might use Group Policy to reduce its TCO.
A GPO can be associated with more than one Active Directory container or multiple containers can be linked to a single GPO.
Administrative Templates are registry-based policy settings that appear in the Local Group Policy Editor under the Administrative Templates node of both the Computer and User Configuration nodes.
This hierarchy is created when the Local Group Policy Editor reads XML-based Administrative Template files (.admx).
No association with any real company, organization, product, person, or event is intended or should be inferred.
This common infrastructure is designed for use on a private network.