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

Keep users of shared printer from seeing what others send to the same printer

We are using shared printers from a 2008R2 print server, and would like for our users to not be able to see what other users pass to the print queue.

Today any user that has the print queue window open, can see the file- and username of print jobs being passed to the printer.
In a student environment this is not very desirable.

Any ideas how to prevent everyone from seeing all other users' print job information?

regards,
Skjalg
Print-job-information.jpg
0
itavdelingen
Asked:
itavdelingen
  • 2
  • 2
3 Solutions
 
viki2000Commented:
This is "Print Management Step-by-Step Guide for Windows Server 2008"
http://technet.microsoft.com/en-us/library/cc753109%28v=ws.10%29.aspx
but there is no specific reference to your request, or I do not see it.

Using an external software seems possible:
http://www.papercut.com/kb/Main/HideDocumentNameOnWindowsPrinters
http://www.youtube.com/watch?v=sXRdzvXJNOM
0
 
viki2000Commented:
Somebody else gave the next answer here:
http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/079c8fbd-ae9a-47b9-bc8c-18c1b65faee4/

"
It is impossible and the solution is not achievable in a single print queue. Also, please note that if users can print to the queue, then they can see the contents of the queue. If users have no access to a print queue, then they won’t even see the queue.
 
Please refer to the following suggestions as workaround.

1. Creating a print queue for each user (or set of users), with permissions only for that user/users.
2. Monitoring job submission (via FindNextPrinterChangeNotification) and changing the document name to something generic. This still leaves a small window where the 'real' name is visible.
"
0
 
deroodeCommented:
In our student environment we use a separate printserver (not connected to a domain) to handle our printing. We have Pcounter (http://www.andtechnologies.com/) installed on this server, for accounting and direct-pay purposes.

In our setup we've disabled direct connections (SMB) to this server, but have made it accessible through the LPD protocol. This setup has the advantage that anyone can print to the printer (the pcounter program tags a printjob with a username and password) and additional printjobs aren't visible anymore once they are submitted to the queue.

If you leave out the pcounter (but you'll probably have some other accounting mechanism for your students) just create a setup with LPD on the server and clients.

The downside of this setup is that you must install LPD/LPR (Add/remove programs - Windows Components - Other Network file and print services - Print services for Unix) on your server and clients, and that you have to install a Local printer on your clients. (the settings of which cannot be centrally managed)
0
 
deroodeCommented:
Ping;

Did you have a chance to try the LPD route?
(Install Print services for Unix on your server and clients, configure a local printer on the client that prints to the LPD queue on the server)
0
 
hdhondtCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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