Avatar of Line One
Line One
 asked on

Group policy not applying Server 2008 Terminal Server

I'm having issues with GPOs on a 2008 R2 Terminal server on a 2008 domain.
I have 2 GPOs at the Terminal Server OU level. These have user configuration settings, and they apply ok.
I have added another GPO at the users Ou level. This has some user configuration settings enabled.

WhenI I check the applied GPOs using gpresult, there is no mention at all of the new GPO. It's not showing as applied or filtered.
Any ideas?
Windows Server 2008Active Directory

Avatar of undefined
Last Comment
Line One

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Mike Kline

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Line One

ASKER
Loopback is enalbed on the Default Machine Policy, which is linked to the terminal server OU. It's set to replace.
However GPresult shows this GPO as filtered out for users:

The following GPOs were not applied because they were filtered out
-------------------------------------------------------------------
    Local Group Policy
        Filtering:  Not Applied (Empty)

    Default Machine Policy
        Filtering:  Disabled (GPO)
Line One

ASKER
Hang on, I think I've got it now.
The Default Machine policy scope was for Authenticated users only.
When I removed this security filtering, it seemed to work.
I would have thought the user counted as an authenticated user, seeing as they logged on successfully?
Mike Kline

You removed it and what did you add, just authenticated users should have been ok
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
Line One

ASKER
I didn't add anything. So the security filtering section is now blank.
My understanding is that it will apply to all users if no filtering is present?
Greg Jacknow

Yes having authenticated users on a policy that you wanted to have apply to machines might be an issue.  As the machine section is not per user it authenticates per login as the computers account.
Mike Kline

Authenticated users does include computers.

Check the ACL on the GPO to see what the exact permissions are.

Thanks

Mike
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Line One

ASKER
Hi Mike,
I checked the ACL, and authenticated users is added with read access. They are added authomatically when i add auth users to the security filtering.
However, I still get
 Default Machine Policy
     Filtering:  Disabled (GPO)

Any ideas? I would prefer to get it working logically as it should, rather than using work arounds.