Skip to main content

Auditing Printers in Windows Server 2012

By

If your organization has a need for auditing the use of printers, you can accomplish this with the Windows Event Logs.

Step 1: Configure Auditing.

Auditing can be configured through several means.  Group Policy is the most effective because it is a centrally managed system and users are not able to turn it off.  To enable auditing on the client/servers where the printer is managed, scope a GPO with these settings:

image

Expand Computer Configuration \ Policies \ Windows Settings Security Settings \ Local Policies \ Audit Policies.

Configure Audit object access to log success.

Close the GPO editor.  You must make sure that this GPO is scoped for the target client and the policy is applied.

 

Step 2: Configure audit settings on the printer.

On your Windows 2012 or Windows 8 client, press the (Windows) key to bring up the start menu.  For Windows Server 2008/7, click Start.

Type Printers and click Settings.

Click Devices and Printers.

image

Right click the printer that you want to perform auditing on and click Printer Properties.

Select the Sharing tab.  You need to list this shared printer in Active Directory to enable Auditing. 

Click Change Sharing Options and elevate your privileges if necessary,

Check List in the directory and then click Apply.

Click the Security tab and then click Advanced.

Click the Auditing tab.

Now click Add and the click Select a principal.

From here you can select the user or group that you want to audit. If you just want to audit who is sending print jobs to this printer, just audit for Print. 

Click OK 3 times.

A word of caution.  This will fill your security log very quickly.  In testing, 35 events were generated from printing 1 page from Notepad.  Consult your printer manufacture to see if they have management software for their product that will achieve your goals.  Here is a link to the KB article warning you about this same issue.  The information that is of value to you; username, printer, and document are located in multiple events in the message portion of the event.  This is not something that you can easily scan through so a third party solution may be required.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more