There's still built-in security groups.
I'm just referring to it as a policy setting
because that's how they're applied in instances like this.
They are security groups though,
and they cannot be altered inside of your MMC console
as far as the users and groups is concerned.
Let me show you.
In our Windows 10 lab system here,
I just wanted to point this out real quick.
I have local users and groups running inside of MMC.
So that way we can take a look at what's going on.
And as you can see,
you don't see any of those two actually being shown
for all applications and such.
They are still security groups
and you can add them to other files and folders.
Taking a look at the LZ folder.
I'm sorry, James.
LZ folder on the desktop of Windows 10.
Well, I'm inside the permissions for it for security
and I'm adding the all application packages.
And I don't even have to do that.
I can just click on advanced and go into find now
for all the users and groups
that are actually on the system.
I'll expand this a little bit
and then zoom in for you right here.
You can see here that we have all application packages
listed right there.
Still cannot be modified.
And it is a security group on the system.
You can tell by the icon,
but it's just not something you can view inside
of the actual MMC console when you have local users groups.
This is set by default through policy,
but is a security group.
And I'll put this code PowerShell code below.
You can see I goofed it up a little bit from the top.
But what we did here was verify the existence
of the actual security group,
all application packages as an example
to display the actual group ID inside of PowerShell.
You can see that it's S1-15-2-1.
So it is a group, you just don't see it normally
and it's very well hidden.
And identified to be applied in local security policy
covertly to things like services.
So, but you can't add normal users
or other groups inside of something
like all application packages
because it is a very unique type of security group.