Locking down a Desktop

[Taishi]

What are ways to limit the amount of damage a user can
do to his/her system (i.e. deleting config files, installing bad
applications, etc)?

Regards,
T

 

[Tergiversative]

What are ways to limit the amount of damage a user can
do to his/her system (i.e. deleting config files, installing bad
applications, etc)?

Regards,
T

Easiest: make them a Guest. They can't install most apps (although
there are old ones that can be gotten 'round), can't change driver
configs, can't delete most important files, etc. Most of what they can
do is merely damage their own data. The tricky part will be getting
*certain* apps to run for them; you might have to tweak registry
permissions or give them access to specific programs folders, if a
program is not really designed to properly install in XP.

BTW, please do not cross-post; it serves no purpose and often annoys
people trying to assist. Pick the best group for the question and post
it there; someone will answer it, and often the same people read
various groups so they may be irked at being asked 3 times what belongs
in only one place.

 

[Ronnie Vernon MVP]

What are ways to limit the amount of damage a user can
do to his/her system (i.e. deleting config files, installing bad
applications, etc)?

Regards,

Taishi

MVP Doug Knox has created a slick little utility that easily restricts
access to just about any program or setting that you wish. Very intuitive,
easy to use and it works on XP Pro as well as XP Home version. This utility
works on a per user basis. Take a look at it here.

Doug's Windows® XP Security Console
http://www.dougknox.com/xp/utils/xp_securityconsole.htm

--
Ronnie Vernon
Microsoft MVP
Windows Shell/User

Please reply to the newsgroup so all may benefit.

 

[Kevin Boyle]

I haven't installed this utility yet but this sounds like exactly the kind
of thing I am looking for, I dont know why Microsoft haven't included
something like this in their Windows deployment tools.

And, before it is suggested, I have looked into Group Policy Objects and
they seem quite ineffective and not suited to single workstation setup.

 

[Ronnie Vernon MVP]

I haven't installed this utility yet but this sounds like exactly the
kind of thing I am looking for, I dont know why Microsoft haven't
included something like this in their Windows deployment tools.

And, before it is suggested, I have looked into Group Policy Objects
and they seem quite ineffective and not suited to single workstation
setup.

Kevin

Do look into it. You are right about gpedit, it only applies to groups and
not single users.

Doug's utility allows you to select a user directly from the accounts on a
given system. It is a real relief for the folks who have XP Home installed,
since they do not have an easy way to set this type of security options.
Parents are going to love it too.

--
Ronnie Vernon
Microsoft MVP
Windows Shell/User

Please reply to the newsgroup so all may benefit.