• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 103
  • Last Modified:

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.
0
GeologyETH
Asked:
GeologyETH
  • 5
  • 4
1 Solution
 
NiabingiCommented:
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.
0
 
GeologyETHAuthor 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?
0
 
NiabingiCommented:
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.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
GeologyETHAuthor 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?
0
 
NiabingiCommented:
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
0
 
GeologyETHAuthor 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?
0
 
GeologyETHAuthor Commented:
I hooked the copy process on the event 805, but a copied .spl file no content. Ideas?
0
 
GeologyETHAuthor Commented:
Works with hooking on id 801.
0
 
NiabingiCommented:
great!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now