Re: General Question re Terminal Services
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 29 May 2007 07:05:25 -0700
If with "data folder" you mean home directory, that's something
that you set for each user account. You can do that in a number of
places, one of them being in the properties of their AD account.
About locking down your Terminal Server, that's a bit more
complicated. It's achieved with a combination of Group Policies and
NTFS permissions. Here are some guidelines to start with:
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 respond in newsgroup, NOT by private email ___
=?Utf-8?B?R2F2aW4gRW1lcnNvbg==?=
<GavinEmerson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 29 maj 2007 in
microsoft.public.windows.terminal_services:
I feel I'm missing something in a big way regarding terminal.
service.
I have set the role on my test server & am ready to get a thin
client device logged in over remote desktop.
I'm wanting each RD user to have their own data folder, & be
tied down as to a) what they can see on the server & b) what
they can do on the server.
Where is this set up ? I understand this may be a very obvious
one for most using this board.
Regards, Gavin.
- Prev by Date: Re: deny access to all but 1 folder
- Next by Date: Re: scripted logon
- Previous by thread: Re: Set font size (theme) with GPO for terminal sessions
- Next by thread: COM1 poor performance
- Index(es):
Relevant Pages
|
