If they are 'non Technical Users', then would
they know what/how to do their job. Would
they understand what it is they are looking at?
How would they know if something is truely
wrong or OK? You'll end up doing the job
indirectly, because they'll be calling all the time
for explainations and false alarms.
There are thousands of things that could go
wrong. Of those, there are a thousand
exceptions.
Sounds like you had an email problem. Mgt
then decided the helpdesk must have access
so they can determine when theres an issue.
Give them access to the fw status program and
let them stare at that until you can get the
management setup to email/page/etc. the
Helpdesk personnel(of course you'll be included
in that too. Just put a sleep 300 to give yourself a
head start :)
Best of Luck!
Robert
(p.s. I like Peters idea. But if the first lie doesn't
work, come up with a better one!)
- -
Robert P. MacDonald, Network Engineer
e-Business Infrastructure
G o r d o n F o o d S e r v i c e
Voice: +1.616.261.7987 email: [EMAIL PROTECTED]
>>> Peter Goodridge <[EMAIL PROTECTED]> 7/14/00 2:08:11 PM >>>
>
>The safest way is to lie, and say it would violate the
>license.
>
>If you can't get away with that enable secure shell
>and set up an account that goes straight into a menu
>driven script. Stay away from telnet.
>
>HTH,
>Pete Goodridge
>
>--- khalid Ameziane <[EMAIL PROTECTED]> wrote:
>>
>> Hi All,
>>
>> i was asked to give the "the Checkpoint Firewall"
>> for non Technical Users ,
>> to check the status
>> of the system ressources, the status of the queued
>> emails ..things like that
>> .....
>>
>> what would be the SAFEST way to do it , without
>> really give them the access
>> to the command line ??
>>
>>
>> Thanks .
>> Khalid.
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
