Re: Restricting / Locking Down Terminal Services
From: Vera Noest [MVP] (Vera.Noest_at_remove-this.hem.utfors.se)
Date: 08/02/04
- Next message: Adrian Moseley: "Win2k3 Server Remote Services"
- Previous message: Vera Noest [MVP]: "Re: TCP lost over time"
- In reply to: Timothy: "Restricting / Locking Down Terminal Services"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 02 Aug 2004 06:49:49 -0700
You'll have to use a combination of Group Policies and NTFS
permissions.
278295 - How to Lock Down a Windows 2000 Terminal Services Session
http://support.microsoft.com/?kbid=278295
231287 - Loopback Processing of Group Policy
http://support.microsoft.com/?kbid=231287
--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
webmaster@equity.co.uk (Timothy) wrote in
news:f3717c39.0408020456.2affb413@posting.google.com:
> We have just setup a Windows 2000 Terminal Services Server and
> we are looking to now get this set up for all our users.
>
> We don't want our users being able to play with all the settings
> but I am unsure which is the best way of locking the server
> down. Has anyone got any good tips or guide for doing this?
>
> Thanks in advance,
>
> Timothy.
- Next message: Adrian Moseley: "Win2k3 Server Remote Services"
- Previous message: Vera Noest [MVP]: "Re: TCP lost over time"
- In reply to: Timothy: "Restricting / Locking Down Terminal Services"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|