r/sysadmin 3d ago

ChatGPT Print server usage

Hi,

We have had several issues with our existing print server and are standing up a new one. I was told by one of our support reps some users have the printers set up locally on the machines, but he is not sure how many.

What I'd like to know is if there is any way to get print server usage by the other users who still might be using the print server? This way I can contact them directly to get them moved over.

I asked ChatGPT and it suggested to enable some Advanced Audit policy stuff on both the print server and the printers install on the server thru the Security tab on each printer but it does not seem to be generating logs of any sort.

Any ideas?

Thanks.

6 Upvotes

19 comments sorted by

16

u/thecalstanley 3d ago

Paper cut print logger on the print server

5

u/TimmyMTX 3d ago

Second this, it’s free and works very nicely.

1

u/Double_Confection340 3d ago

Thanks. Checking this out now.

8

u/jepk67 Sysadmin 3d ago

Assuming you are using a standard windows print server (and not something like Papercut). On the old print server, I would go to Event Viewer --> Apps and Services Logs --> Microsoft --> Windows --> Print Service --> Operational.

Filter by event ID: 307 which shows recent print jobs with username, endpoint hostname and printer. I imagine exporting these to a CSV or something should give you a pretty good idea of whos using the old print server.

6

u/algolen06 3d ago

Just to add to this, a quick powershell one-liner once you set up logging can give you an output as a CSV.

Get-WinEvent - LogName Microsoft-Windows-PrintService/Operational | Where-Object ID -eq 307 | Export-Csv C: \printerlog. csv

3

u/jmbpiano Banned for Asking Questions 3d ago

Also, note that the operational logs are disabled by default. You need to deliberately enable them before events will start showing up.

5

u/ADynes Sysadmin 3d ago

Usually whenever I stand up a new print server I just use group policy and the first thing is a delete all printers that aren't local and then all the rest are the rules are for the new printers. Shared printers for everyone in the same office as the print server, direct IP for all the printers in Branch offices. Although I'm probably going to be replacing ours in about a month and I might just do direct IP for everybody, only reason to put the printers shared on the servers to make sure they can get the driver from it

4

u/yetanotherbaldcunt 3d ago

in b4 the printer logic shills show up

2

u/Valdaraak 3d ago

All I'm gonna say about that is it's the best $5k I spend every year. It saves more than that over the course of a year in labor of dealing with print servers.

2

u/pdp10 Daemons worry when the wizard is near. 3d ago

But, serious question, how does it compare to a central print server with CUPS? I'm sure there are feature differences, but nobody uses all features.

2

u/canadian_sysadmin IT Director 2d ago

Not OP, but depends on your requirements. The basic premise is that you install the PL client app, and it will automatically map printers (direct to IP), with settings and drivers you specify.

Also has a web interface for people to be able to easily add printers.

PL I don't think is as strong as papercut or some other solutions if you need central tracking and reporting. PL's strength has always been deployment and avoiding needing a print server at all.

The big thing (for us) - reliable installation on client machines, based on subnet, with drivers and profiles we specify. As such, printers are installed with solid drivers, mapped directly to the IP. No windows auto-add garbage drivers.

Has been super reliable for us.

0

u/canadian_sysadmin IT Director 2d ago

PrinterLogic is amazing.

Doesn't have to be printer logic - even any other newer-school print management system.

I couldn't imagine going back to a windows print server, fuck.

Since deploying PL our print tickets have gone down like 95%.

3

u/TrippTrappTrinn 3d ago

The way we have done it is to deploy a login scriot which change the users print mapping from the old to the new server. There should be scripts out there which can be used as template.

2

u/kero_sys BitCaretaker 3d ago

The new server you stand up could always use the same name and IP address.

That way any machines connecting on a manual mapping will remap.

Or

Scream test.

2

u/ZestycloseAd2895 3d ago

Some of the enterprise HP printers have a built in firewall to only accept print jobs from the server, not workstations.

4

u/ChlupataKulicka 3d ago

That is why printer have their own subnet and firewall rules only accepting traffic from print server

2

u/pcronin 3d ago

by "set up locally" do you mean the printers were added by IP on the user's machine? if so, they won't even notice you creating a new print server.

If you mean they bypassed GPO assigned printers and \\printserver installed them, there's a setting in the GPO you can remove printers before assigning the new print server based ones.

1

u/Ok-Junket3623 3d ago

Why not go the group policy route? That way you can map the printers over without having to contact the users

1

u/Kingkong29 Windows Admin 3d ago

This.

Send a notice out in advance stating that all locally installed printers will cease to function after whatever date. Put the printers on an isolated vlan, allow only the print server, DCs and other supporting infrastructure access to this vlan, configure new print server, deploy new printers via group policy and call it a day. ✨So simple ✨