Document attributes in windows print log

GeologyETH
GeologyETH used Ask the Experts™
on
The event log provides some information about print jobs, e.b. user, document etc. This can be read, e.g. with log parser. The question is how to get more details about a printed document, i.e. the documents attributes as e.g. color, b&w, duplex etc.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
look in the folder on the server or PC if not using a print server, C:\Windows\System32\spool\PRINTERS
copy the .spl file and open it with notepad, there you can see what tray is been called and whether duplex is on or not for that job.

Author

Commented:
Thanks for info. I've found a .spl on a PC, but not on the server. The printer are connected via TCP/IP port to the server and then shared. Any clue?
to capture that .spl file you will need pause the printer on the server and send the job then go to the folder and copy the file so you can examine it. when working correctly the file get delete once the job is printed so that is why you have to pause printing, then resume to make the job print.
Why Diversity in Tech Matters

Kesha Williams, certified professional and software developer, explores the imbalance of diversity in the world of technology -- especially when it comes to hiring women. She showcases ways she's making a difference through the Colors of STEM program.

Author

Commented:
that worked, thanks. But this information source is only very shortly available. The question is how to save such information about the print jobs permanently. Is there e.g. a possibility to enhance the information written into the log or another way to write it out into a file?
you can create a batch file and add it to a task to run and copy the files you may have to set it to run every 1 min to copy all files.

robocopy "C:\Windows\System32\spool\PRINTERS"  "C:\new_location"

pause
exit

Author

Commented:
Thanks, I'll try it. But I think an at job running every minute might not catch all print related files, i.e. some prints can happen in between? Maybe, the script can be triggered by the print job?
But then I've the copied files. In the end I need only the details about the printed documents. The log parser is a convenient tool for analyzing the log. But, details about the printed documents are not stored there. Is there a possibility to customize the logs by such information?

Author

Commented:
I hooked the copy process on the event 805, but a copied .spl file no content. Ideas?

Author

Commented:
Works with hooking on id 801.
great!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial