Terminal server lockdown doesn't work

[gsomlai51]

Hello,

I wanted to lockdown a recently installed single Terminal server (Win2003 R2).
The server is alone is a separate OU. I created a GPO according to the whitepaper from
Microsoft titled "Locking Down Windows Server 2003 Terminal Server Sessions" I did
everything according to this document, I used GPO loopback processing in replace mode
rebooted the server after this setting was done, and linked the lockdown GPO to this
OU.
However user logging on with RDP to the server, they don't get the policy.
I tried to use security filtering and added the Terminal server, but it didn't help.
Do I have to add authenticated users as well? Or did I miss something else?
I'm quite new on the GPO usage area....
Any help is appreciated.

Kind regards
Gabor

[vmotzney]

Not sure if you still need help, but this what I did:

I created a group specific for Terminal Services and added that group to the filtering, along with the TS Server. All users using TS added to that group. The OU for the Terminal Server is set for blocked inheritence.

hope that helps.