In this chapter: |
---|
To understand the structure of Group Policy, you first need to understand the structure of Active Directory®. Active Directory has both physical and logical components. The heart of Active Directory’s physical architecture is an extensible storage engine (ESE) for reading and writing information to the Active Directory data store. The ESE uses an object-based hierarchy to represent information in the data store. The data store is essentially a database with a primary data file, working files for maintaining the state of the data file, and transaction logs for recording changes. Within Group Policy, there is a logical and physical representation of every Group Policy object (GPO) as well. The logical component of a GPO is a Group Policy container (GPC), which is stored in Active Directory. The physical component is a Group Policy template (GPT), which is stored on the file systems of domain controllers. The way these logical and physical components are handled depends largely on the Group Policy processing configuration.
Related Information
For essential background on Group Policy, see Chapter 1 and Chapter 2.
For more information on the Active Directory architecture, see "Active Directory Physical Architecture" and "Active Directory Logical Architecture" in Chapter 32 of Windows Server 2003 Inside Out (Microsoft Press, 2003).
For more information about Group Policy inheritance and processing, see "Managing Group Policy Inheritance" and "Managing Group Policy Processing and Refresh" in Chapter 3.