Skip to content
Tutorials Center
My learning

Topics

Lesson 20 of 38 ยท Group Policy and Management

Group Policy Objects and Processing Order

Learn what a Group Policy Object is, how computer and user settings are applied, the LSDOU processing order and how often policy refreshes in an Active Directory domain.

Group Policy is how an Active Directory administrator configures thousands of computers and users from one place. Instead of walking to each machine to set a password rule, map a drive or lock down a setting, you write the rule once in a Group Policy Object (GPO) and attach it to part of the directory. Every machine and user under that part picks it up automatically.

This lesson explains what a GPO is made of, how the two halves (computer and user) work, the order in which policies are applied, and how often clients check for changes. The Windows tools are described in words, because they cannot run on this site. The runnable examples are small Python stand-ins that model the same rules, so you can experiment with ordering and timing yourself.

What a GPO actually is

A GPO is not a single object. It is a pair of linked pieces:

  • The Group Policy Container (GPC) is an object in the directory under CN=Policies,CN=System,DC=example,DC=com. It holds the GPO name, its GUID, its version number and a few flags. It replicates with the rest of Active Directory.
  • The Group Policy Template (GPT) is a folder in the SYSVOL share, for example \\example.com\SYSVOL\example.com\Policies\{GUID}. It holds the actual settings: registry-based policy files (Registry.pol), security templates, scripts and preferences. It replicates with DFS Replication.

Because the two halves travel by different routes, they can get out of sync. A GPO whose container says version 5 but whose folder is still at version 4 behaves oddly. This is one of the commonest root causes of "my policy does not apply", and the troubleshooting lesson shows how to check it.

A GPO does nothing until it is linked to a site, a domain or an organizational unit (OU). The link is stored on the container (the gPLink attribute of that site, domain or OU), not on the GPO itself. One GPO can be linked in many places.

Computer settings and user settings

Every GPO has two independent halves:

Half Applies to When it applies Typical content
Computer Configuration The computer account At startup, then in the background Security options, services, firewall, software, startup scripts
User Configuration The user account At sign-in, then in the background Desktop, folder redirection, drive maps, logon scripts

The computer half follows the computer object in the directory, and the user half follows the user object. If the computer account sits in OU=Workstations and the user sits in OU=Staff, the computer receives policies linked on the path to the first OU, and the user receives those on the path to the second. If you only need one half, you can disable the unused half of a GPO, which also speeds processing.

The LSDOU processing order

Policies are applied in a fixed order, and the last one applied wins when two disagree:

  1. Local: the local group policy on the machine itself.
  2. Site: GPOs linked to the Active Directory site the computer is in.
  3. Domain: GPOs linked to the domain root.
  4. OU: GPOs linked to OUs, from the outermost parent down to the OU that directly contains the object. Inside a single container, links are processed from the highest link order number to the lowest-numbered link, so link order 1 is applied last and wins.
flowchart LR
  L["Local policy"] --> S["Site GPOs"]
  S --> D["Domain GPOs"]
  D --> P["Parent OU GPOs"]
  P --> C["Child OU GPOs"]
  C --> R["Effective settings"]

Later boxes override earlier ones when a setting conflicts. Settings that do not conflict accumulate.

Two rules deserve emphasis. First, only settings that are configured take part. A policy that leaves a setting as Not Configured never overrides anything. Second, non-conflicting settings add up. If the domain GPO sets a wallpaper and the OU GPO sets a screen saver timeout, the user gets both.

Python LSDOU resolver (Python stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice that ScreenSaverTimeout is set in three layers and the deepest OU wins, while Wallpaper simply accumulates.

When policy is refreshed

Policy is not applied once. After the first application, clients re-check on a schedule:

  • Workstations and member servers: every 90 minutes, plus a random offset of up to 30 minutes, so a thousand machines do not hit the domain controller at the same moment.
  • Domain controllers: every 5 minutes.
  • At computer startup and user sign-in, regardless of the timer.
  • On demand with gpupdate /force, which re-applies every setting, or plain gpupdate, which applies only what changed.

Some settings need a restart or a new sign-in because the system reads them only at those times, for example software installation and folder redirection.

Python When will a client pick up my change?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The numbers are modelled on the documented defaults, but the actual wait also depends on when the client last refreshed. The worst case is 120 minutes.

Common mistakes

  • Editing the Default Domain Policy for everything. Keep it for the few settings it is meant for (password and Kerberos policy) and create separate GPOs for other settings, so you can disable or back up each one on its own.
  • Linking user settings to an OU that contains only computers. User settings follow the user object, so they never apply. (Loopback processing, described in filtering and loopback, is the deliberate exception.)
  • Forgetting replication. A change made on one domain controller reaches others only after replication, which depends on sites and topology.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Where are the actual settings of a GPO stored?

    The container (GPC) in the directory holds metadata such as version and name, while the template (GPT) in SYSVOL holds the setting files.
  2. 2. Two GPOs set the same value. One is linked to the domain and one to a child OU. Which one wins?

    LSDOU applies the domain first and the OU afterwards, so the OU setting overrides it.
  3. 3. What is the default background refresh interval for a workstation?

    Workstations refresh every 90 minutes with a random 0 to 30 minute offset; domain controllers refresh every 5 minutes.
  4. 4. A GPO that leaves a setting as Not Configured will:

    Only configured settings take part in conflict resolution, so Not Configured never overrides anything.

Summary

  • A GPO is a container in the directory plus a template folder in SYSVOL, and does nothing until it is linked.
  • Each GPO has a computer half and a user half that apply to different objects at different times.
  • Order is Local, Site, Domain, then OUs from parent to child; the last applied setting wins and unconfigured settings do not conflict.
  • Workstations refresh every 90 to 120 minutes, domain controllers every 5, and gpupdate forces a refresh.

Next: GPO Links, Inheritance and Precedence