OMRF-ISG Archives

OMRF's Information Support Group


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Jerrod Howard <[log in to unmask]>
Reply To:
OMRF's Information Support Group <[log in to unmask]>
Mon, 19 Apr 2004 08:29:32 -0500
text/plain (36 lines)
We may have to go that route, but I am not a script writer (though I may yet
have to become one). Thanks for the advice.

-----Original Message-----
From: Alan Shields [mailto:[log in to unmask]]
Sent: Friday, April 16, 2004 6:21 PM
To: [log in to unmask]
Subject: Re: Program specific access security program

On Fri, Apr 16, 2004 at 03:52:11PM -0500, Jerrod Howard wrote:
> We are looking for a program to control and log access to specific
> on a windows 2000 computer (for example, o control access to a specifc
> executable or program while also logging the date used and the duration of
> time used on that date). The problem we're having is as people come in to
> use our imaging equipment, we need to track the person who used it as well
> as the duration of time they used it for. I would like to be able to pull
> an audit or access log at the end of the month and looks at usage times
> user for billing purposes.

This is a cheap trick, and not necessarily suitable for a hostile
environment, but you could move the program being run, and have the
program instead be a script that logs entrance and exit from the
program, and kicks off the original.

This logging could be done to a remote server, or just to a file.

Small script to assemble usage information from that log file, and you'd
be done.

Just a thought,