Discussion:
Terminal service security on client
(too old to reply)
Nick Trenary
2004-12-29 17:10:10 UTC
Permalink
I am very wet behind the ears on Terminal Services so bear with me. I am
looking at using thin clients for internet stations at our library, about
10-12 total. I have a thin client and TS installed on a 2k server for
testing purposes. My question is about exiting an rdp session. How can I
secure the thin client so that a use doesn't exit session? A user could
then potentially open rdp again and change the settings. Am I overlooking
something?

Thanks,
Nick
Vera Noest [MVP]
2004-12-30 15:05:44 UTC
Permalink
Most thin clients allow you to password protect the rdp settings. You
preconfigure the default rdp settings in the setup menu and users can
only start it, not modify it. How this is done exactly depends on the
manufacturer. Check their website for instructions.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
Post by Nick Trenary
I am very wet behind the ears on Terminal Services so bear with
me. I am looking at using thin clients for internet stations at
our library, about 10-12 total. I have a thin client and TS
installed on a 2k server for testing purposes. My question is
about exiting an rdp session. How can I secure the thin client
so that a use doesn't exit session? A user could then
potentially open rdp again and change the settings. Am I
overlooking something?
Thanks,
Nick
Steve Stirling
2005-01-04 17:11:01 UTC
Permalink
You can also, through group policy, remove the LOG OFF button from the start
menu of their Terminal Server profile
Post by Nick Trenary
I am very wet behind the ears on Terminal Services so bear with me. I am
looking at using thin clients for internet stations at our library, about
10-12 total. I have a thin client and TS installed on a 2k server for
testing purposes. My question is about exiting an rdp session. How can I
secure the thin client so that a use doesn't exit session? A user could
then potentially open rdp again and change the settings. Am I overlooking
something?
Thanks,
Nick
Loading...