Can I map a IGEL OS 10.5 UDC device to a Windows Print Q that is using ThinPrint driver virtualization?

Hi – Is it possible to map a 10.5 UDC device to a Windows Print Q that is using ThinPrint driver virtualization? I can’t find any documentation on this…

Learn more, read the entire thread inside the IGEL Community o Slack

Hi, basically yes but not sure to have understood you right, but I assume you already walked through this doc:

i did see that but interpreted it to be for UDC’s 10.5 hosting a printer that a WIndows Printer server wants to map to.

(i’m really green with the IGEL and ThinPrint though)

From MHO, it shouldn‘t make a difference, still, not sure to get the question right. Let‘s see if some thinprint guru wants to join…

this is what i’m trying to accomplish. Basically this is how we do printing today with Windows 10 converted into a ‘thin like configuration’. In order to minimize disruption to exiting process we would like to replicate this setup using IGEL and ThinPrint.

If your printserver is reachable from the Citrix environment I would map the printers directly into the sessions, without going trough the IGEL endpoints.

yeah thats a huge change for us, one we were trying to avoid

we figured with printer driver virtualization we could keep the existing printer model

so is deploying printers on IGEL devices not possible in this manner?

I may ask a dumb question, but is this config you could achieve on Windows with Thinprint?

yes, easily

i’m actually running it in my lab right now

we are a large healthcare organization with about 15-20k workstations, printing has always been configured on the endpoint and passed through to the citrix session. The introduction of Thin Clients will be painful enough without having to translate endpoint configured printers into session assigned printers spanning tons of different xenapp server silos.

So, the the thinprint client is able to do that… Ok. Did you found something on the thinprint linux side?

so the goal is to ease implementation and make it ‘like for like’ as possible to maintain the existing printer deployment pattern.

no, where would i look for that?

i was kind of hoping/expecting these features out of the box.

ThinPrint Client Linux

would be my first thought

okay thats sort of what i’m looking for, how is that achieved using IGEL printer policies?

That’s what the article describes, or am I wrong? I can only tell how to deal with the local Thinrpint installation of printer, I’m not aware of how it looks like on the Thinprint Server

The thnuclnt.conf is created by the Igel Setup or UMS Profile and then rest should be dealt on Terminal-/VDI-/Thinprint Server

yeah i’m thinking there definitely needs to be some sort of ‘printing gateway’ setup because IGEL isn’t going to do SMB like a windows workstation would when mapping a printer via UNC.

the Connector looks logically like its a fit, not having any luck with it in my lab though.

i just emailed the ThinPrint rep to see what he has to say.

Ok, great. Please keep us in the loop if help is needed or if you found a solution that may be suitable for other members!

for sure! i’ll make sure to keep everyone up to date!! 🙂

well i got my answer, ThinPrint universal driver doesn’t work in Linux so virtualizing the print path between IGEL UDC and Windows Print server is not possible due to Linux print architecture.

looks like its going to have to be server assigned printing!

Continue reading and comment on the thread ‘Can I map a IGEL OS 10.5 UDC device to a Windows Print Q that is using ThinPrint driver virtualization?’.  Not a member? Join Here!

Learn more, search the IGEL Knowledge Base

Ask a question or comment on the above message thread?

Join or log in to the IGEL Community to ask us anything and meet other IGEL customers, partners, and EUC enthusiasts.

Submit a question, or Join Today!

Popular Message Threads

Categories & Tags: