You are not logged in.
My company just announced that they will no longer support direct printing to printers that are "network enabled" (had badge scanners added to them). They are going completely to "cloud printing," where you print your document to a print queue, then go to the printer of your choosing, scan a badge, and your document is printed.
Does anyone have experience with this on Linux? Just wondering if I'll have to reboot to Windows every time I want to print. I can dig up more information if that would be helpful?
- I know the name of the cloud printing "virtual printing device" (at least that's what I'd call it -- it appears as a printer to print to, but obviously it works with any printer, so... virtual print device?)
- Perhaps HP has a particular protocol I could research?
- If someone has previous experience and could help answer that I *won't* be able to to do this definitively, that's appreciated as well to save me time fiddling with it.
For example, I'm a bit curious about how the badge interaction will work. Are the badges just telling it my username? If so, I might have a chance. If there's some user ID on Windows that's being sent, however, I'm not sure I'll be able to replicate that if it's some sort of encrypted key or something belonging to a badge/Username database that my company keeps track of an has installed to the printers.
Just out of my league with how this all works and looking for tips.
Thanks!
John
Offline
I think this question can be answered best by those people who implement the new printing solution for your company. And even if they have no idea about linux, they might at least tell you what you need to send to the server together with your print job so you can find and actually print it later on. Once you know how it is meant to work, we can try and implement that.
Offline
I don't know how many times I've asked questions like this on the forums and gotten the same response... and somehow I still keep forgetting the obvious choice of asking my IT group at work. When I encounter an issue like this, I reflexively wonder if some other Arch user has already experienced something like it. Thanks for the reminder, and I'll explore that route.
Offline