You are all pretty much right on... this isn't an easy thing to do. If possible at all.

Now here's why... On our Citrix servers we have recently started using Uniprint. With uniprint when you click file/print you get one option "Uniprint". You click ok and it then shows the printers you have on the local PC. When you then print it wraps the job into a PDF and sends it to the PC so you don't have to have print drivers on the Citrix servers.

That's great but so what...

Well... with WYSE thin clients there is no local Uniprint client that the server can redirect print jobs to and if you use the "Uniprint" print queue it'll cause problems as there's nowhere for the job to go. SO... Uniprint has a Gateway Spool server that basically looks like a traditional print server to the session and you can mount print queues like with any other print server.

Also great but so what...

Well the problem is that the generic local "Uniprint" queue is always there and seems to always stay as the default no matter how you tell the connected queue to be default. Even if I can figure out how to not make it default it's dangerous to have in the list cause if it's used it'll crash... but only from a Thin Client.

So... I need a way to suppress the "Uniprint" local print queue for anyone launching a session from a Thin Client and yet be available if they then launch a session from a PC (which would have the Uniprint client).

Holy Cow if that makes sense to you then you win!

Really it's a third party app issue (Uniprint) that I'm trying to work around \:\)
_________________________
Chris Fricke
Clackamas County