Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

Re: Admin Rights required on Terminal Services

Subject: Re: Admin Rights required on Terminal Services
Date: 22 Mar 2005 11:21:18 -0000
In-Reply-To: <423F47FF.6040304@ucw.com.au>


From: Security <security@ucw.com.au>


With the TS config for a custom writen prog, if you cannot give admin 
rights to everyone (fair enough), one thing you could do is start 
security "failure" auditing for everything on the TS box.

Somthing similar was proposed in a previous post, will try to do this (if time 
permits ;)

However does not seem to be a 'clean' and 'professional' way to make this thing 
work

Or,
Why not give admin access to users and use group policy to remove any 
icons or access paths to any sensitive areas.

This is what we have decided to do in the meantime, give user admin rights, and 
restrict 'all' his access, at least accesses that he won't need: remove command 
prompt, control panel, disable right-click, remove access to local disk (will 
be moving to a thin client environment), all everything else available in the 
Group Policy

I am very interested in the outcome of this thread. Please continue to 
post ideas.

Me too! Yeah please post new ideas

<Prev in Thread] Current Thread [Next in Thread>