RE: [ EXTERNAL ]Re: Possible to send a HOLD at PRINTER job from i?

Thanks to you all for your input thus far.

Vernon, your idea was something akin to what I was thinking along the lines of. Sending the print job to a CUPS (common unix printing system) Server that is connected to each of the printers, having the needed printer drivers living on that CUPS server and having the CUPS act as a user with a specific code, this could be printer specific but most of these jobs aren't 'for their eyes only' so even a generic code would work.

Need to pass your idea and mine over to the Network team to see if it's possible or I'm just blowing smoke.

Ken

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of VERNON HAMBERG Owner via MIDRANGE-L
Sent: Tuesday, July 30, 2024 6:46 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: VERNON HAMBERG Owner <vhamberg@xxxxxxxxxxxxxxx>; midrange-l@xxxxxxxxxxxxxxxxxx
Subject: [ EXTERNAL ]Re: Possible to send a HOLD at PRINTER job from i?

We have a similar setup to yours, Charles - we have Konica-Minlota BizHubs in departments - at least, we have 4 of them on this floor. No local printers on anyone's desk at all now. And we do what you do.


Now it's been awhile, but I believe it is possible to map an IBM i user profile as an alias in Active Directory. A print device on the i would point to some IP address on the network for the managed printing, so things queue up. And the alias makes the IBM i stuff come up under your Windows user.

Of course, there's work to be done to set it up. Probably not much in the way of device descriptions, though, necessarily.


We don't have much actual printing done now - we use Robot Reports for users, which converts things to PDF or ??? and puts them on a network file share or some such.


We've not yet given users the ability to use the Printer Output action of ACS - I believe there are ways to limit what people can do with that, so maybe that's an option.


HTH
Vern


On Tue, 30 Jul, 2024 at 3:12 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:


To: midrange systems technical discussion

Probably going to depend on _how_ this is being accomplished for your Windows printing.

It seems likely to be some combination of the printer hardware and some software package.

For instance, I don't see our network attached printers in Windows. All I see is "My Company Secure Print" as a printer.

After printing to that, I can walk to a printer, swipe my badge and get my printout.

I'd suspect that in order for your IBM i to participate, you're going to
- have to be using SSO/Kerberos, so that there's a single "user"
- possibly have to redefine the printers on your IBM i. (and use SNMP or IPP as a protocol)

Just some thoughts off the top of my head.

HTH,
Charles

On Tue, Jul 30, 2024 at 1:20 PM Ken Meade via MIDRANGE-L < midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>> wrote:

All,

Like a lot of companies we are looking at minimizing the number of
printers we have, but one of our concerns is that print jobs will pile
up at the printer.
I know that I can set up a driver configuration on my local Windows
machine to do a HOLD at the printer and I enter a code at the printer
to get my jobs when I'm ready for them.
In fact that is what we plan on doing for all users as we set up their
local machines and primary printers.
We'd like to replicate this same thing for jobs that come from our i,
is this even possible?

Thanks,
Ken

Ken Meade | Director of Information Technology and Infrastructure
kmeade@xxxxxxxxxxxxxxxxx<mailto:kmeade@xxxxxxxxxxxxxxxxx>
<mailto:kmeade@xxxxxxxxxxxxxxxxx<mailto:kmeade@xxxxxxxxxxxxxxxxx>> |
(603)
444-3570
[cid:image001.png@01DAE293.F2FEB6A0]
Littleton Coin Company, Inc.
1309 Mt Eustis Rd, Littleton NH 03561
http://www.l/
ittletoncoin.com%2F&data=05%7C02%7Ckmeade%40littletoncoin.com%7Cee55ff
7129974e94b3d408dcb0e958f5%7Cf671045cabcb483e800849f5e77d0a0d%7C0%7C0%
7C638579763520569222%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQI
joiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=dRy5MUONd
Sqom58FmLHQ0a3K%2FxqPxuclfLisxtlpUJ4%3D&reserved=0<https://nam12.safel/
inks.protection.outlook.com/?url=http%3A%2F%2Fwww.littletoncoin.com%2F
&data=05%7C02%7Ckmeade%40littletoncoin.com%7Cee55ff7129974e94b3d408dcb
0e958f5%7Cf671045cabcb483e800849f5e77d0a0d%7C0%7C0%7C63857976352057748
2%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6
Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=pmoeU4bkx5jP4QRkdu7HKFQNgwhB
bGjrCH11l72tOr4%3D&reserved=0><https://nam12.safelinks.protection.outl/
ook.com/?url=http%3A%2F%2Fwww.littletoncoin.com%2F&data=05%7C02%7Ckmea
de%40littletoncoin.com%7Cee55ff7129974e94b3d408dcb0e958f5%7Cf671045cab
cb483e800849f5e77d0a0d%7C0%7C0%7C638579763520583276%7CUnknown%7CTWFpbG
Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
3D%7C0%7C%7C%7C&sdata=rEbsenMQbJQ%2BRafxM2biKGLGKmCJH9BO9xbSgPZlSU8%3D
&reserved=0><https://nam12.safelinks.protection.outlook.com/?url=http%25
3A%2F%2Fwww.littletoncoin.com%2F&data=05%7C02%7Ckmeade%40littletoncoin
.com%7Cee55ff7129974e94b3d408dcb0e958f5%7Cf671045cabcb483e800849f5e77d
0a0d%7C0%7C0%7C638579763520587530%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w
LjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sd
ata=YWjJ2Xp3mTgGM9JLg%2B4lb1GBAVHV6NN0PI%2BR9fNgcxg%3D&reserved=0>>


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://list/
s.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C02%7Ckmeade
%40littletoncoin.com%7Cee55ff7129974e94b3d408dcb0e958f5%7Cf671045cabcb
483e800849f5e77d0a0d%7C0%7C0%7C638579763520591770%7CUnknown%7CTWFpbGZs
b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
%7C0%7C%7C%7C&sdata=q1emeVAIaWNxIU8cN7XdLHPrRws3aDK2VnCK6UJY6z0%3D&res
erved=0 or email:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@lists.
midrange.com> Before posting, please take a moment to review the
archives at
https://archive.midrange.com/midrange-l.

Please contact
support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.