Welcome to our comprehensive video guide on troubleshooting Active Directory Group Policies like a pro! We're finishing the remaining tests in the PowerShell module “GPOZaurr”. This powerful module walks us through the fundamentals of GPO troubleshooting. We will cover 12 more subjects that make up critical aspects of correct GPO: Permissions, Ownership, Blocked Inheritance, CNF conflict, GPO links, GPOs and Ous with valid users and computers, NetLogon Permissions, and an opportunity to document your GPOs and files on SYSVOL and NetLogon Shares. Dive into the world of Group Policy Objects (GPOs), a critical component for network administrators in managing and automating the configuration of Windows environments. But what happens when things don't go as planned? That's where we come in. Armed with 'GPOZaurr', also known as the 'PowerShell Eater', we're going to show you how to effectively troubleshoot GPOs, transforming complex problems into manageable solutions. This powerful PowerShell module is your secret weapon for diagnosing and resolving those tricky Group Policy issues that can often leave you scratching your head. Whether you're a seasoned IT professional or just starting out, our step-by-step process will guide you through the nuances of identifying and fixing common and not-so-common Group Policy errors and problems. By the end of this video, you'll have a deeper understanding of how GPOs work, and more importantly, how to tackle issues when they arise. So, let's get started and master the art of Group Policy troubleshooting with GPOZaurr!
"Everybody can be great... because anybody can serve. You don't have to have a college degree to serve. You don't have to make your subject and verb agree to serve. You only need a heart full of grace. A soul generated by love." Martin Luther King Jr.
We are on Group Policy Troubleshooting Part 2. In Part 1, I introduced a marvelous PowerShell module
called GPO ZAURR. He gives it a name of Group Policy Eater. This PowerShell module is so
comprehensive and is so well designed that I decided to use it as a framework to show you
how you can troubleshoot group policies. There's a total of 15 different fundamental principles
that this PowerShell module goes after to analyze, give you a report on, and then show you how to fix
those 15 different problems. Now, in the first video, I spent all my time really walking you
through the HTML reports that the PowerShell module gives you, how to tackle each and every section,
how to analyze it, how to look at your report, how to repair. All of that, I took a great deal
of time just so that you are comfortable with what the PowerShell module does and how to use it.
So, in this second video, we're going to quickly go through those last 12 and hopefully you are
now comfortable with how to approach troubleshooting and have a better understanding of some of the
major issues that can cause you problems with group. Now, I've ran my Group Policy Eater
module commands and you can see it's run the analysis. I now have an HTML report. We're going
to start with GPO permissions consistency. What do we mean when we talk about GPO permission
consistency? When I, as a domain administrator, create a group policy, I am putting data in the
Active Directory domain partition. There's going to be GPO metadata that goes in there.
There's going to be ACLs, Access Control Lists, that are going to be in that metadata. I'm also
going to put files and folders on the sysvol account. There's going to be a good folder that
represents that GPO. There's going to be a top-level ACL that's on that GPO and all the
files and folders that are inside, do they inherit that top-level permission set so that we don't
have permissions in the metadata different than what the ACLs that are going to be on the sysvol
account. So, notice the graph on the right. If you have red in your chart, you've got inconsistencies.
You've got either inherited rights not being the same as top-level or whatever. So, you need to
look at your report and help determine what is the problem and where do you need to focus on.
So, here in my spreadsheet view, I see that my GPOs over here on the left and I see my ACL
consistency is all true and green. My ACL consistency inside is all true and green.
If it wasn't, then I would have the steps to solve those problems. I could prepare a report,
go next, start using some of these permissions that will allow me to repair some inconsistencies,
go next, and here are some of the inheritance. Now, here it says this step is manual until some
kind of automation is developed. So, here you would have to try to figure out your inheritance issue
if this was where you had the problem. This check just makes sure that you don't get out of sync
between your ACLs on metadata and your SysVol count. Keep in mind in the repair step, always
leave the what if parameter in until you're ready and feel comfortable to remove it and then go ahead
and execute it. Our next test is the duplicate CNF group policy. So, CNF stands for conflict.
It simply means that you had two domain administrators who are modifying this GPO
at the same time on two different domain controllers. AD does not overwrite this
if it doesn't, if it hasn't had a chance to replicate. Instead, it renames one of the objects
and appends it by giving it the CNF and it allows you to go in manually and fix this conflict.
Again, the repair step has the what if parameter in. You can run it and take a look at it before
you go ahead and remove the dash what if parameter. Since GPOs and OUs are really the heart
and soul of group policies, and group policies want to see either users in an OU or computers
in an OU or both in an OU, GPOs will not impact anything in an OU if it's not a computer and it's
not a user. Do you have GPOs that are linked to OUs and there's nothing in them? That can happen.
Over time, your Active Directory can get messy and this gives you that option to really clean up,
make sure that you have GPOs attached to OUs that have either computers or users inside.
So this test is going to be looking at those policies. This is a great cleanup operation
on your Active Directory and your GPOs to make sure that you don't have these type of situations.
If you look in the right pane of the HTML report, he makes some cautions. He says,
unlinking GPOs from OUs that have no computers or users inside is a fairly safe exercise.
Removing an OU requires a bit more deep dive and should only be executed if you know what
you're doing. If you'll notice in this report, this spreadsheet, I've got a highlighted OU
and that OU I created is called no GPO and it's an OU that I can drag and drop a user or a computer
in and I don't have any group policies assigned to it. So if I've got something going on in my
environment and I'm suspecting it's a GPO problem, one of the ways I can do is grab that user,
grab that computer and throw them in my no GPO OU, reboot the computer and see now that all
GPOs have been relinquished from that computer, is it acting normal again? That's just my own
decision to have that and you can see it's letting me know it doesn't like it. It's not a problem.
You can do this. Just be aware it's highlighting the fact that I've got an OU with no GPO.
And of course the repair, this command will then execute, it runs a cleanup procedure that
unleaks all group policies from organizational units that have no users or computer objects.
And so again, it has the dash what if, so do that first before you remove that what if.
Our next test is called group policy summary. This is kind of cleanup part two. So every time
an administrator adds more and more group policies as business requirements change due
to either neglect or thinking it may serve a purpose later, a lot of group policies just
have no value at all. Either the GPO is not linked to anything or just stays unlinked forever or the
GPO is linked but the link are disabled or the GPO is totally disabled. There can be group policies
that are targeting certain groups or persons and that group has been removed leaving the GPO doing
nothing. So this is looking at kind of the overall. You can see I got a lot of red in mine. Mine's a
training domain. So I've got like eight group policies that are not optimized. I've got three
that are not valid. My report card is not good here. What does it mean that my group policies
are not optimized? So here under group policy object node, I'm going to go to one of my group
policies. I was actually preparing this GPO for one of my videos and it's concerning BitLocker.
Well, it's a computer only group policy. It does not impact users and if I right mouse click and
I look at GPO status, it is enabled. It's not doing anything which is one of my bad report card
elements but I should have said user configuration settings disabled because it's not going to impact
any users and I've got it set to do so. All the configurations are strictly for computer,
not for user. So by doing that, notice my status is that the user configuration settings are
disabled. It will actually run faster. So that's what it means by optimized. Pay attention to this
test, this analysis of your group policies. Make sure you clean up as many of these problems as you
can. If you have these non-optimized GPOs, it'll actually help the performance of log-ons for your
users. As you get to the repair section, make sure you do a backup. This is one place I would make
sure I do a backup before I move forward and fix some of these issues. In the repair section of
this test, lots of good information. Make sure you do your reading and due diligence. Any
information highlighted in red, I would read that. He provides scripts not only for a single domain
but multi-domain situations. Again, be careful. Make sure you read carefully the information
supplied by this module before you execute anything. Now our next test is group policy
links and allows you to look at your group policies and see how many OUs you have linked
to this particular GPO. You can see in my spreadsheet view, I have a default domain
policy and it's linked only to the domain. Then my remote event viewer and RPC firewall GPO
is linked to five OUs. And then I have some of my GPOs that are linked to six OUs. So it's a great
way to look at your GPOs. How many OUs are you linked to? Are those links enabled or are they
disabled? So you want to look at that. That's a great way to look at your GPO strategy to see
your link, your link enabled and your link disabled. The next test is group policy passwords.
I don't have any such scenario. So mine is blank. We're now looking at group policy permission
analysis. When GPOs are created, there's a handful of standard permissions and those are
anti-authority, authenticated users, domain administrators and enterprise admins with
edit, delete and modify permission. And then of course, a system account with edit,
delete and modify permission. If this is not standard in your GPO structure,
you're going to have problems. So when you run the report, you're going to get your graph showing you
your visible permissions, overall permissions, administrative, authenticated users, system
permissions. And then if there's any unknown permissions in your group policy structure,
it's going to highlight those. So again, if you're missing authenticated users or admin groups or
system, the scripts are there so that you can add those groups, get them back to default status in
terms of permissions. He even provides a script that will allow any unknown permissions from your
structure. So you just run it. Again, always use the what if, and then go ahead and remove it and
get rid of those unknown permissions. The next test that he runs is called the SysVol file list.
It really isn't a diagnostic, but it is a nice spreadsheet analysis of what you have on your
SysVol folder. So here you can see my spreadsheet view of all my SysVol files.
You can export that out in Excel, CVS, PDF. Nice, nice features, especially if you want
for some documentation. This is a great way to pull that information off. It shows you that
this particular policy is based on an ADMX template. It gives you attributes,
gives you creation time, last access time, and last write time. A lot of great information,
especially for documentation. Before we leave this SysVol, NetLogon file list, just be aware,
this is every file on those two shares on your domain controller, SysVol and your NetLogon.
Here is my domain controller. You always have a NetLogon share and a SysVol share. And this
test or this documentation shows you every file you have on your NetLogon share
and your SysVol share. You might be surprised how many you have. The spreadsheet is busy and the
font is very small, but you do have a lot of information here. I'm going to come down. I've
got over 447 entries into this spreadsheet. I'm up to 436 of 447. So I'm almost to the end of my
files. And you can see things are starting to change. This particular file belongs to a GPO.
If you go back to my first list of files, this file doesn't belong to a GPO. So just be aware,
notice the file extensions. POL, that is going to be a policy that edits the registry because it's a
.pol extension. I see a .inf. I know that's a security policy. There's a lot of information
in here that I can glance at. But just be aware, this is a great way of documenting
what's on your NetLogon, your SysVol, gives you enormous amount of great information.
You might want to pop through it. In my case, I've got 447 entries. It's going to be many pages if I
print it. Our next test that we run is a look at our policies to see are any of them being blocked
via inheritance. Naturally, we have inheritance invoked. So if we set a policy at the domain
level, it should be inherited by OUs below it. This is going to reveal, do we have any of those?
And you can see mine is boring. There's no blocked inheritance in my structure. Let me go ahead and
turn on blocked inheritance. We'll come back and run this test and you'll see my report will look
different. So let's take a look. Here's my group policy management. I'm going to come to an OU,
right mouse click, and notice I have the option to block inheritance. Notice I get an icon here.
I'm going to come to a couple. Let's go to Home Labs, Block Inheritance, and Home PCs,
Block Inheritance. This prevents anything at the domain level from automatically coming down into
those OUs. This can get you in trouble. This is an approach that is appropriate for certain
applications but also can create security problems. Let's run a report again and let's
take a look at it. Okay, this is a fresh report. I'm going to come up to Group Policies, Blocked
Inheritance. Voila, you can see there's a lot of change. So now it has paid attention to the fact
that I've blocked inheritance. Group policies at the domain level may or may not come down
to certain OUs and it's letting me see that clearly here. So blocking group policies being
inherited by sub-OUs is not bad, it just has to be done very carefully. Here's the normal
way that group policies work. Let's say the root here in this graphic is our domain and I've set
a password policy, A, and I've also set an Internet Explorer setting, we'll call that C.
This sub-OU has a firewall policy called B. Now these sub-OUs, user and computer,
now because of inheritance, now have a group policy of A, B, and C. They've inherited from
the domain, the parent, the process of inheritance has pushed each of those policies down to OUs
that are in the hierarchical structure of that domain. Here's the same thing. So if I have a
domain policy, and here's my domain, and I decide at sales to block this policy up here from my
managers, from my sales reps, and from my sales admin, it stops it from being inherited. This is
appropriate for certain scenarios, but it also can add security risks. Again, to block inheritance,
you just go to an OU, right mouse click, and check the block inheritance. You will get an
icon indicating so you can clearly see when inheritance is being blocked. Okay, Mr. B,
you've made it sound pretty bad. No, let's take a look at some of the reasons for blocking
inheritance. You have a specialized security requirement on an OU that's different from the
rest of the domain. There's one way you would block inheritance. You have a different software
configuration for an OU that's different from the parent OU. You had a testing development
environment. User-specific policies, password policies would also allow you to block inheritance,
say from the overall domain. In a multinational corporation is location-based policies. Policies
that you set in your European environment may be very different than in your Asian environment.
Temporary policy changes, you could stop inheritance just for some testing reason
or to avoid disruption. You could have an educational training environment OU in which
you're going to block certain inherited group policies. You could have compliance where because
of compliance, you've got point of sale that are under PCI compliance. So because of those point
of sale devices, you have to block inherited GPOs. And then legacy systems, because of their need,
but their legacy, you may want to block certain. So there are justified reasons for blocking
inheritance. We have three more tests. Let's wrap this up. The next one is called group policy
content. It's really not analysis. It has no repair features. It basically shows you all the types of
policies that you have set up right now and gives you a ton of information. In my case, I do have an
audit group policy, BitLocker group policy. You can come through here and see all the different
various types. I've got a Windows update. I've got a couple Windows PowerShell. I've got some
firewall rules. So it's just showing you all the types of group policies you have. And it breaks
down all the information about each of those. Again, you can export that in Excel, CVS, PDF,
and again, build documentation. The group policy content is simply great for documentation. It
allows you to really get a lot of information about your GPOs, export them into any format
you want, and build again that great reporting. Our next test is NetLogon owners. Remember,
NetLogon is a share on a domain controller. It's used by group policy objects. Keep in mind,
the ownership should be the built-in administrator. Anybody owns files or is the owner of files that's
outside of the built-in administrator, that needs to be changed. This report is going to highlight
it. It's going to let you know, and it's going to give you the scripts to repair it. Now, our last
test covers NetLogon permissions. Now, this is not ownership. This is just the permissions assigned
to the files on the NetLogon share. These can vary. You want to pay attention to what permissions are
applied to those files so that the wrong users or groups don't have modify rights or write permissions
or all those disastrous type of permissions on your domain controller group policy NetLogon share.
This, again, is just going to analyze, report it, and give you some scripts to fix it.
All right, Mr. Interpol, are all my troubles and problems with GPOs covered in this two video
series? Absolutely not. But you did get some solid, good foundational steps and procedures to follow
when you set up your group policies so that you'll find you're much more consistent,
fewer errors, fewer problems, especially if you're inheriting a company, you're brought in as an
administrator, there's been six administrators before you, and here you sit with 400 GPOs,
and you don't have a clue of what you've got there. This is a great way to analyze those,
clean up any messes or inconsistencies, get things in order. Just a quick reminder,
if what we produce here at Tech Savvy Productions on our YouTube channel is beneficial to you,
I encourage you, join the channel. It's $2.99 a month. It's less than a cup of coffee a month,
but your membership really helps support the costs that are required to make this channel.
We encourage you, no matter whether you're a member or not, put in comments, feedback
in our comment section, take advantage of our notes, our PowerPoints.