Re: Securing Terminal Server
- From: "Vera Noest [MVP]" <Vera.Noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 02 Jun 2006 06:26:14 -0700
A combination of restrictive GPOs and NTFS permissions is what you
need.
278295 - How to lock down a Windows Server 2003 or Windows 2000
Terminal Server session
http://support.microsoft.com/?kbid=278295
Windows Server 2003 Terminal Server Security White Paper
http://www.microsoft.com/downloads/details.aspx?FamilyID=402A0CD1-
9E4D-4007-8EAF-C30623E71250&displaylang=en
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
=?Utf-8?B?VG9tIFdhbGw=?= <TomWall@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 02 jun 2006:
How can I can secure Windows Terminal Server? I have a client.
which wants a Terminal Server with thin clients connecting to it
in a number of locations. The environment is a classroom
environment, but the students are not to be trusted and the
system is to be locked down as much as possible. Please point
me to resources.
- Prev by Date: Re: Can not log into my terminal server - logon error
- Next by Date: Re: Multiple instances of RDP client and resource redirection
- Previous by thread: Re: Default printer settings in Windows 2003 T/S
- Next by thread: Re: Securing Terminal Server
- Index(es):
Relevant Pages
|
