Okay.
And now let's let's look at this concept of targeting of computers and user users on a real system.
So I'm back on my server box and I'm an Active Directory users and computers.
I've got this little voice structure called sales.
Underneath sales.
I have a client, so you and the users owe you and they contain a computer account and a user account
respectively.
So if I come back to AMC, you'll see that same structure.
And what I want to do is I want to create a GPO and link it to that client.
So you and I'm going to call it sales computer policy, and I'm going to create one called Sales User
Policy and I'm going to link that to the users.
Oh, you under sales.
So now if I go in and edit this GPO because I'm on the client, so you the only stuff that I can really
configure that is going to affect the objects within this.
So you are the stuff under computer configuration, remember?
In the clients view, I only have computer objects.
I don't have any users object user objects.
And that's that's on purpose.
That's how I broken up my ADD structure.
So if I come back under the policy, the computer configuration policy section, anything I define here
will be essentially applied to the pole dash, to the computer objects.
And so what I'm going to do is just pick any policy here.
Unwilling to enable to display highly detailed status messages policy.
And that policy will then apply to all of the computer objects in the client's O.U.
Now, if I come in here under sales user policy and I create, let's say I want to create a drive mapping
for the users in sales.
So if I'm going to come up here to drive maps and I'm going to say create a new map drive.
And I'm going to just pointed at a share where the sales organization has.
A public drive, so to speak, and I am going to call it the yes drive for sales.
And I am going to go ahead and click.
Okay.
So now I've got an S drive being mapped to the sales share on the Sd1 server.
And that means that any users within the users o you under sales will process this policy because it's
on the user configuration side.
And they will successfully map that s drive to that share.
So that's kind of the key point here is you've got an ad structure and in that ad structure, you've
got users in some containers and computers in other containers, and you have to target your GPOs accordingly.
Now, you might have a situation where you have an O u that contains both users and computers and that
can get a little bit complicated.
But the point there is that anything you define under computer configuration will be processed by the
computer objects and that, oh, you and anything you define under user configuration will be processed
by the user objects.
And that O.U.
Hopefully that brings the point home around this kind of bifurcated existence of the group policy object
and how it applies each to computers and users.