Is there any way to forensically recover data of printed jobs directly from the printer memory?
RAM impossible.
Off drum image, real maybe.
Built in hard drive – yup.
Is it a network printer? Logs on the server will help here-definitely on Win, linux I'm not sure-you could check that easily.
Is it a network printer? Logs on the server will help here-definitely on Win, linux I'm not sure-you could check that easily.
Elmurado,
Are you talking about the Windows server event logs? If yes, I would be interested in the event ids. Is there any other log in windows which could tell me wht was printed?
This is a great free tool from MS.
http//
And here's a link to how to use it-the first link on this page is what you might want
http//
I've used this for giving reports to HR showing that users have been printing cookery books at work in the past!
Formats very nicely.
Otherwise for eyeballing the logs, check under the system events for print jobs. Usually event id 10 but there may be others too. Depending on what auditing you have turned on you can find out a fair amount of info.
Check here for auditing info
http//
This is a great free tool from MS.
http//www.microsoft.com/downloads/details.aspx?familyid=890cd06b-abf8-4c25-91b2-f8d975cf8c07&displaylang=en And here's a link to how to use it-the first link on this page is what you might want
http//www.logparser.com/Repository.htm
I've used this for giving reports to HR showing that users have been printing cookery books at work in the past!Formats very nicely.
Otherwise for eyeballing the logs, check under the system events for print jobs. Usually event id 10 but there may be others too. Depending on what auditing you have turned on you can find out a fair amount of info.Check here for auditing info
http//www.windowsnetworking.com/articles_tutorials/Securing-Printer-Usage-Windows-Server-2003-Part3.html
Hi can you explain how you used it as the link is not working now.