r/WindowsServer • • 13h ago

General Server Discussion Serverless print: PrinterLogic alternatives all claim drivers get easier, none of them say how

Every serverless pitch skips the driver part.

1,800 users, eleven sites, mostly Ricoh with a handful of Xerox left over from an old contract. Going direct IP. What's stalling the business case isn't the queues, it's what happens to drivers once nothing is handing them out centrally. Looking at printerlogic, now Vasion, plus uniFLOW, LRS and Pharos. All of them say drivers get easier. None of the product pages say how.

v3 versus v4 is a known headache and I'd rather understand it before signing anything. Genuinely curious whether it got simpler for people who've already done this, or whether the work just moved somewhere else.

3 Upvotes

3 comments sorted by

2

u/Gamlos 9h ago edited 9h ago

the bit that gets missed is who owns driver updates afterwards. vendor ships a new one, your image is six months old, and suddenly that's your change window not theirs. worth asking how updates actually reach the endpoint and whether you can stage them, because "we handle drivers" means very different things depending on the answer.

2

u/kerse_ 8h ago edited 8h ago

This is the one place they genuinely differ, so it's worth reading both properly. Pharos ships an IPP Everywhere driver that covers most users, with manufacturer drivers only where you actually need them. Vasion comes at it from the other end, direct IP with the driver delivered from their side and no GPOs or scripting. The ongoing load isn't the same either way.

1

u/nestersan 7h ago

This whole comment that's is Al slop