Auditing Print Jobs

In a Windows 2000 or later domain, is it possible to audit when specific files are printed?

Unfortunately, no. The OS knows when an application opens a printer object and starts pumping in data to be printed, but it can't determine that the data source is a particular file. In the Security log, you can track whenever someone prints to an object by enabling the Audit object access events policy and then enabling auditing under the printer's Properties. However, Windows can tell you—through event ID 560 (Object Open)—only that a user opened the printer for print access, nothing more.

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering System Center 2012

During over 6 hours of training you can join John Savill from your computer as he will walk you through the key components and capabilities of System Center 2012, what’s involved in using the components, and the benefit they can bring to your environment.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.