Stop users installing keylog software

A business colleague mentioned that they had discovered an employee at their
firm installing keylogging software on a client PC, which numerous people
logged on it. They now wanted to prevent any user from installing any
program.

I assume that the way to stop this is to reduce the User to a 'Restricted
User' on each 2000/XP Client PC. Is this right, and would it have any
repercussions SBS-wise?

Thanks

SuperGumby
Thu Apr 29 05:53:55 CDT 2004

A better way to handle this problem is to get the user to sign a computer
usage agreement.

You are allowed to use our computer.
Keep in mind that it is our computer.
If you abuse this privelage you will no longer be our employee.



"jann" <jann@dial.pipex.com> wrote in message
news:Os2RyXdLEHA.1264@TK2MSFTNGP12.phx.gbl...
> A business colleague mentioned that they had discovered an employee at
their
> firm installing keylogging software on a client PC, which numerous people
> logged on it. They now wanted to prevent any user from installing any
> program.
>
> I assume that the way to stop this is to reduce the User to a 'Restricted
> User' on each 2000/XP Client PC. Is this right, and would it have any
> repercussions SBS-wise?
>
> Thanks
>
>

jann
Thu Apr 29 09:03:55 CDT 2004

Well, they could be dismissed anyway under the normal terms of their
contract.

However given the havoc that they could wreak if they do get an important
logon password etc., it is no good us acting after the event. We need to
make sure that it doesn't happen in the first place.

Any ideas anyone?

Thanks

Bob
Thu Apr 29 09:31:14 CDT 2004

jann,

You might want to install keylogger detection software. I use PestPatrol
which also removes all other non-viral "pests". You can dounload a trial
at http://pestpatrol.com/downloads/eval/download.asp And here is a 25% off
coupon code COMP-W619 for PestPatrol.

Bob

"jann" <jann@dial.pipex.com> wrote in message
news:%23inRqKfLEHA.2624@TK2MSFTNGP09.phx.gbl...
> Well, they could be dismissed anyway under the normal terms of their
> contract.
>
> However given the havoc that they could wreak if they do get an important
> logon password etc., it is no good us acting after the event. We need to
> make sure that it doesn't happen in the first place.
>
> Any ideas anyone?
>
> Thanks
>
>

jann
Thu Apr 29 12:26:46 CDT 2004

Thanks, very interesting