Controlling policy in Windows Server 2008 Terminal Server

Our organization just got its first Server 2008 terminal server for hosting applications.  Previously we've been using 2003 which worked great but we updated a few other servers to Server 2008 (file server, mail server) and I really enjoyed 2008 so when it came to upgrade I went with that Server OS.  

I'm having problems figuring out how to control the Terminal Server's user policies though.  When our users log in (they are Domain Users only, not admins) they can see the Server Manager, Command Prompt, and Administrative Tools link in the Start Menu.  Of course I do not want them to see any of this.  The only thing they should need is the applications being hosted (Outlook, Quickbooks Enterprise, Adobe Reader).  I don't recall having this issue with Server 2003.  

Does this have to managed through a group policy? I looked in Local Security Policy for the machine but couldn't find anything.  I also tried editing the Default Profile but that got me no where.

Thank you,
LVL 1
DrPcKenAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lacrewgaCommented:
Create an OU (Organization Unit) in Active DIrectory for users and edit, drill down to set the options that you want. Reply if need help.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DrPcKenAuthor Commented:
I failed to mention that the Domain Controller is still running Server 2003 (this is my next server to push to 2008 :) ).  

Is an OU really the way to handle this for a terminal server?  The only users that are allowed to login to the Terminal Server have to be part of a Security Group I created in AD called Terminal Users.  Users that aren't in that group cannot access the Terminal Server.
0
lacrewgaCommented:
I don't have boxes in front of me, but I am thinking that you can create policies for that security group by right clicking, and then Properties. You should be able to choose inheritance or not.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

DrPcKenAuthor Commented:
I'm not doubting you, but in my experience this policy would be in effect no matter which machine their user account is logged in under.  I would only want this policy to be in effect for the Terminal Server.
0
lacrewgaCommented:
Do you have people that use TS and log on locally? If not, the simplest thing to do would be to add an OU and place those users that remote into that group.
0
DrPcKenAuthor Commented:
My users log on to their machines locally, and then access the terminal server when needed (like when they are traveling).
0
DrPcKenAuthor Commented:
Ok so I would create an OU for the terminal server computer object, not the users right?  Would I create a loopback policy as defined here?

http://www.virtualizationadmin.com/articles-tutorials/terminal-services/general/managing-terminal-services-group-policy.html
0
lacrewgaCommented:
0
DrPcKenAuthor Commented:
Great! I got the OU and policy created and it seems to be working.  But users (non-admins) are still seeing things I don't want them to (Server Manager, Admin Tools, etc..).  Is there a way to block these items?
0
lacrewgaCommented:
From memory... drill down and you will find a policy that will allow you to set only the programs that you want to enable for them to run. Just  add your exe file names and that should lock it down.
0
lacrewgaCommented:
Note: From memory... I did not have a machine in front of me, I recalled from memory. Didnt want to confuse you.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.