Re: locking down command.com
From: Eric Chamberlain (eric_james_chamberlain_at_hotmail.com)
Date: 07/26/03
- Next message: 281 cu. in.: "Re: kill messenger"
- Previous message: Eric Chamberlain: "Re: To IPSec Packet Filter OR Not To IPSec Packet Filter - that is the question"
- In reply to: nathan: "locking down command.com"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 25 Jul 2003 19:52:43 -0700
You can also set permissions on command.com so the students, assuming they
are not administrators, can not read or execute the file.
"nathan" <nathanh@mtannancc.nsw.edu.au> wrote in message
news:udOtrEmUDHA.1004@TK2MSFTNGP12.phx.gbl...
> I have some students using command.com to net send anoying messages to
> staff. How do i disable it.
> Students are all users. I have denied access to command prompt in GP (but
it
> only works on cmd.exe)
> Because we don't really use the messenger service i have set it to manual
in
> GP on student machines.
> However they are going to winnt\system32\command.com and are able to even
> start the messenger service back up again using net start. Is this
normal???
> How can i stop this from happening?
>
> cheers,
>
> nathan
>
>
- Next message: 281 cu. in.: "Re: kill messenger"
- Previous message: Eric Chamberlain: "Re: To IPSec Packet Filter OR Not To IPSec Packet Filter - that is the question"
- In reply to: nathan: "locking down command.com"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
