Papercut Script - allow specific user to print specfic filenames only

[LeightonJames]

Hi all

 

Currently using Papercut to manage print queues and track print usage.

 

We have a user account that is abusing the print system, unable to identify the actual user as it's a generic account used for first aid incidents, and printing things they shouldn't be.

 

What I would like to do is delete any jobs sent by this user that don't match a specific filename.

 

I'm hoping this is possible

[MatthewL]

Does it need to print? Can you not disable printing for said user or you could look in the log and see which PC name they are coming from and trace them that way?

[mullet_man]

Does it need to print? Can you not disable printing for said user or you could look in the log and see which PC name they are coming from and trace them that way?

 

Yeah that’s what I thinking, are they printing lots of documents? Check the logs and narrow the PC, printer used and times you should be able to find out who’s taking liberties from that information?

[LeightonJames]

I did think of that and the Head has spoken to staff however we can't prove one way or the other who it was which is why I was looking into using a script to delete anything that falls outside of the specified filename for this particular user.

 

The school has 2 laptops which are used for the firstaid login. These 2 machines are used by multiple people to record the first aid incidents.

 

The document that they SHOULD be printing is titled XRIncidentReportForm and this never changes irrespective of the number that is printed. As the user that we have setup for the first aid system has no network drive access the staff are printing from USB Drives that they are connecting to the laptop.

 

 

If it's not possible I will look into alternative methods of control regarding this user.

[Steve21]

You can do it with a print script on the printer, that basically looks at user then file.

 

But personally I think it's the wrong way to do it, as if they really want to abuse it they'll just rename a file to the "allowed" one and it'll print

 

Steve

[gds64]

How about setting the user (in PaperCut) to be an unauthenticated user, enable "Print account selection" with standard account selection as the selected option, but then only enable "Allow user to perform printing as another user "? Run the PaperCut client on the laptops and it'll force the user to login with their own Windows account each time they submit a job. Would that do what you need?

[PotNoodleTech]

In the logs it should show the PC the user is actually using to print each job - should be able to trace the user via the PC name?

 

The best option by far is to not use generic users. Have an Account called First Aid and then add each specific user that will need to print first aid stuff into that account. That way you can go into the first aid account and see exactly who printed what and from what PC. No more generic'ness and no way for the staff member to get away with it. If they need to print, they'll be printing identified to the system from their own login account.

[LeightonJames]

Thanks for all the suggestions.

 

After discussing it with the Head we have implemented the script after all (used the code snippets to create it) and it works.

 

Thanks again though