GeologyETH
asked on
Document attributes in windows print log
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.
ASKER
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.
ASKER
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?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
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?
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?
ASKER
I hooked the copy process on the event 805, but a copied .spl file no content. Ideas?
ASKER
Works with hooking on id 801.
great!
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.