Windows – Logging and Reporting on W2k3 print server printing

There is no built-in mechanism to disable printer redirection for only specific printers.

I'd consider doing the following (it's convoluted as all get out, but it should give you what you want):

• "Share" the printers on each client computer that should be available to the Terminal Server.

• Add the "TCP/IP Print Server" service to each client computer (marking the service for automatic startup and opening port 515 in the local Windows Firewall on each client computer, if applicable).

• Create local printers on the Terminal Server (or other server computer) corresponding to each printer attached to client computers. These printers should use "Standard TCP/IP" ports configured for LPR, with the "Queue Name" set to the share name specified on the client comptuer for each given printer, and with the "LPR Byte Counting Enabled" check-box checked.

You have control of the print queue name using this method such that you can make the name appear as you'd like. You can set permissions on the queues to prevent users from sending jobs to the wrong printers if you so desire. You can completely disable client printer redirection, as well.

(I do the whole "TCP/IP Print Server" dance, as described above, rather than using "Local Ports" naming UNCs. Some people do the "Local Ports" but I've found throughout the years that I have severe reliability problems doing it that way. My method basically makes the PC act like a really expensive "JetDirect" box...)

I've managed to fix this by using following procedure:

1. Server Manager -> Diagnostics -> Event Views (or compmgmt.msc => Event Viewer)
2. Applications and Service Logs -> Microsoft
3. Windows -> PrintServer -> Operational
4. Right click on the right side under Actions "Enable Log"

And then you can monitor who printed what. You can create Custom View out of it for convenience using Event ID 307 to monitor just printed jobs.