Using Printer PIN Numbers

[evillarreal]

I need to know how to change the Ownerid/User Acct info on a print job that is submitted via a webpage. We want to use Pin numbers for our users who print jobs to the same printer. The problem we are having is that when you have 30 people routing print to the same printer, the print gets mixed. We can successfully define a printer from a server locally to each workstation and set the Pin Number option on each workstation and route the separate print jobs to the same printer. The setup assigns the users USERID and Pin Number to uniquely identify each print job. The users are then able to retrieve the print jobs using their assigned Pin Numbers. However, when they attempt to select print jobs on a website using the same print on the same server, the process assigns the Web application process Owner ID to the job. Hence, when the 30 users print via the web, all of the print will print immediately, not giving the users the option to retrieve their respective jobs using their Pin Numbers. So, I need to know if I can somehow change the Owner ID to the users Userid at the time the print is selected to print from the webpage. If the web app cannot automatically determine the user who submits a print request from the webpage, we could place a drop-down list box with the users ID's. They could then select their userid and the printer name and with that info, maybe we could somehow change the web app OwnerID/Userid to what they entered and route it to the printer. They could at this point use the Pin Number feature to selectively retrieve their print jobs. If anyone could provide some insight into this process, I would appreciate it. Thanks.

[evillarreal]

Does anyone know of a 3rd party app that can change the print driver owner id? See the response below to the original request:

I think the biggest problem you are facing here is impersonation. The "Owner" in this dialog is actually the NT account that requested the print. The problem is that the user requesting the print job is actually the app.adobe.u account (the web app is impersonating as this user). In the world of NT authentication (NTLM, anyway), there is not a good way to impersonate the requesting user to the printer. If we were using Kerberos, this would be a snap, but I do not think we will be getting there anytime soon (especially considering the length of time it is taking just to get us on a Win2k domain).

I am not sure about how the Print Job dialog pulls the Owner information. If it is part of a raw print job request, then you may be able to actually write a component to form this request appropriately (you would likely need Ethereal, or some other packet sniffer to see this communication). There may be existing components that we can acquire to do this as well, as I am sure we are not the first people to stumble across this problem.

I wish I had a magic bullet for this issue, but I am afraid I do not. The best/easiest route may be to look for a 3rd party component that can do this already, as I do not believe that this is a trivial problem.

[Bothware]

If you can change the code that actually sends the print jobs, then you could use "runas" e.g.
shell_execute('runas /user:username@domain.example.com "printingprog.exe -doc=filename.ext"')


Please note I have not tried this, but "runas" is a command built into Windows for executing things as different users.