Group policy settings are presented as GP always in ADT as user interface tools but the GPO is actually
two components a group policy container and a group policy template.
The group policy container in an edit is object let is stored in the group policy objects contained
within the domain name context of the directory similar to all ADT as objects.
Each group policy container includes a globally unique identifier or grid attributes that uniquely identifies
the object within 80 days the group policy container defiance.
Basic attributes of the GPO.
The settings are contained in the group policy template which is a collection of files stored in the
Source Wall of each domain controller in the sense of all domain policies GPO grid path where GPO grid
is a grid of the group policy container.
When you make changes to the sentence of a GPO the changes are saved to group policy the template of
the domain controller from which the GPO was opened which by default is a domain controller that holds
the primary domain controller emulator operations master role or PDC by default one group policy refresh
secures the client site extensions apply sets in a GPO only if the GPO has been updated the group policy
client service can identify an updated GPO by its version number each GPO has a version number that
increments each time a change is made the version number is stored to the group policy container attribute
and in a text file named Jupiter that any in the group policy template folder group policy client knows
the version number of each GPO it has previously applied.
If you're in group policy a refresh group policy client discovers that the version number of the group
policy container has been changed the client site extensions are informed that the GPO is updated.
Now some reports about GPL replication group policy containers and group policy templates are both replicated
between all domain controllers in a single domain in a tedious.
However different replication mechanisms are used for these two items.
The group policy container in aided is replicates by using a director application agent a directory
replication agent uses a topology generated by knowledge consistency checker which you can define or
refine manually.
The result of the group policy continuous replicated within seconds to all domain controllers inside
and also is replicated between sides based on the interim site application configuration.
The group follows a template in the system all replicates by using one of the following two technologies
the file replication service or f IRS replicates sis role in domains that are run and Windows Server
2000 eight two thousand eight hour to 2003 and 2000 server if all domain controllers are on and Windows
Server 2008 or higher.
You should configure this follow replication by using distributed file system replication or D F as
R So before 2000 eight server you use file replication service and after Server 2008 you use distributed
file system replication which is more efficient and reliable mechanism.
It is recommended that you use DFS SA because f far is now deprecated now because the group policy container
and group policy template replicate separately.
It is possible for them to become out of synchronisation for a short time.
Typically when this happens the group policy container replicates the Domain Controller files systems
that obtained their order list of GPO orders from the Domain Controller identifies the new group policy
container attempt to download the group policy template and notice that the version numbers are not
the same.
A policy process an error is then recorded in the event logs.
If the reverse happens and group policy template replicates to a domain controller before the group
policy container then clients obtain in their order list of GPO was from the domain controller are not
notified of the new GPO until the group policy container replicates.