Now,
it's important that you understand the order of
precedence and application with Group Policy.
I'm not doing a full introduction rundown on Group Policy
here; instead, I'm going to punt to my friend,
Darren Mar‑Elia. He has a course that's a few years old, but then again,
Group Policy hasn't changed much in the last 20 years.
So as far as I'm concerned,
Darren's Pluralsight course on Group Policy Fundamentals is
just as valid today in 2022 as it was in 2015.
So check the exercise files, and I'll link to Darren's course.
He will definitely sort you out if you're newer to Group Policy.
But in terms of that layered effect where you can have
multiple GPOs applying to a user and a computer,
this is the order right here, L‑S‑D‑O‑U, or LS‑DOU, as I like to say. In
other words, the workstation or server system first will apply its own
Group Policy settings, and then, in order, if there are Group Policy
objects linked to the Active Directory site,
those settings will be applied, then the domain, and then the
organizational unit. Now in the event of a conflict, a level
closer to the computer or a level closer to the user settings
will be the effective setting.
So if we have a setting here on the local machine that gets overridden,
say, in the domain GPO, the domain GPO setting will be the current one.
Now,
I always say as a systems architect, try to keep your Group
Policy infrastructure as simple as you can get it.
In fact,
I'll end this lesson with some Group Policy‑proven practices that you might find useful in your real life work.