Capturing Data from each Print Job

  • Thread starter Thread starter JohnNews
  • Start date Start date
J

JohnNews

Folks:


I have a Print Server that provides service for 25 network printers and 100
users.

For every print job that passes through the print server I would like to
capture as much statistical information (about THAT print job) as possible.
For example, I am interested in: USER, TIME, DATE, # PAGES, ETC, ETC,
ETC. How best can I accomplish this goal ?

* Is there a DOS command (or VB script, Jscript) that I can use to
capture this type of information for each print job ?
* Would the existence of Active Directory provide any assistance towards
achieving my goal of gathering data for each print job crossing the print
server ?
*

My goal is to archive this information to a database/spreadsheet for
later analysis.




Thanks,
John.
 
JohnNews said:
Folks:


I have a Print Server that provides service for 25 network printers and 100
users.
Click to expand...

How could that have anything even remotely to do with Windows Millenium
Edition OS ? Hire a support tech.
For every print job that passes through the print server I would like to
capture as much statistical information (about THAT print job) as possible.
For example, I am interested in: USER, TIME, DATE, # PAGES, ETC, ETC,
ETC. How best can I accomplish this goal ?
Click to expand...

By RTFMing on your print server software ?


Rick
 
There is a utility in the Resource Kit (applicable
resource kit for your OS) that can be used and set up to
capture Event Log information (such as successful print
jobs) that can then be dumped into a text file (hence the
name DumpEL -- Dump contents of Event Log). You can read
the help contents of the utility for syntax to use. You
also will need an event code to search. Basically, you
will be interested in event code 10, as this is the code
for the successful processing of a print job.

Cheers!
 
Turn On your Print logging so that the EventLog captures as much printing
information as possible. When you have enough info for a certain period,
save the EventLog as a text file (comma delimited or tab delimited) & then
sort it.

To sort it, I feed it through a Perl script.

Albert C. Pang
Klohn Crippen
 
check out Print Audit Analysis and Print Audit 4

These programs get the data for each job prior to the job
reaching the printer server - they are fully client based
solutions - therefore the most accurate.

Low network traffic, will not crash server or ever miss
print jobs.
Roll out the Print Audit "client" module only (never more
than 2 mb of code) to all computers in minutes using log
on scripts inbedded in software and is centrally
administered.

Create custom reports based on any criteria you wish -
institute quota, declining balance and or max pages for
printers. Configure to pop up and prompt user to enter
user pin codes or client code or track silentl. Both
programs capture by default the user log in identity.

Server based solutions can miss jobs when overwhelmed by
traffic, possibly crash systems and can't capture direct
to ip or local printers with out a client module.
visit www.printaudit.com for a free trial - or call 877-
412-8348 in North America or 403-685-4932 for more
information.
 
The 3rd party application Print Audit 4 and Print Audit
Analysis will allow you to capture data for all print
jobs regardless of whether it is local, networked or
direct to ip printing. This is the most accurate and easy
to use solution on the market. It is the only fully
client based solution - very light on your network. Of
course you may also set max pages for printers and quotas
for users. Will by default capture the user based on
their log in identity. Can also assign pin codes for
users if they are sharing computers. Free trials
available at: www.printaudit.com or call for more
information 877-41AUDIT we offer free support during the
evaluation stage and for the life of the software. We can
offer support free of charge because our solution simply
works very well.
 
Back
Top