Thin OS print settings

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #956
    AvatarAnthonyP69
    Member
    • Total Post: 15
    • Regular Joe
    • ★★

    Could someone help explain all the different tabs and their settings for the printer settings on the Thin OS.

    I want to look at all the possible ways you can use the Thin OS and printers. Unfortunitly the User & Admin manuals are just useless on explaining these settings.

    I have been able to setup a V10 to act as a LPD print server (no brainer that one) for a locally attached printer, but I want to know more. What is the need for LPD or SMB tabs if they only allow you to share out a locally attached printer, making the Thin Client a very expensive Network Print server???

    Anything on this would be greatly appreciated.

    Anthony

    #11820
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi Anthony,

    I just checked and the admin guide does not mention printers, you are right! (strange hey?)

    Fortunately a quick search in the Wyse knowledge base turned up a good doc that explains setting up a mapping to Unix and Windows print servers from WTOS.

    Go to the knowledge base and search for solution number 10824 or just search with the keyword “print”

    http://www.wyse.com/serviceandsupport/support/kbase.asp

    (The artical is called “Wyse Thin O/S – How to set up Printers”)

    Cheers,
    -TT

    #11825
    AvatarAnthonyP69
    Member
    • Total Post: 15
    • Regular Joe
    • ★★

    Thanks TT for the reply.

    I do believe I have read this document, but not quite sure where they are going with this.

    So on the ports tab we can define a locally attached printer (on LPT1 or USB etc) with a name, Printer identification (which I believe would be the name of the windows printer driver used on the Citrix server etc) printer class, which I am not sure why you would need to define this if all the device does is pass data out the necessary port to the printer. Enable device is straight forward and LPD service I know allows for devices to use the thin client as a network print server to send their printing data to.

    The question I have is what do you use the other LPD and SMB tabs for?

    Is this so you can allow a Citrix session using client printer mappings, to pass the print data through the client and then out to either a LPD print server or a SMB print server?

    If this is the case, then how would you configure the Citrix Session to handle this? Currently I am using UPD to win32 clients to setup client printing. Can I do something very similar to the Thin Client?

    This would be nice as I can then remove more printer drivers from my Citrix farm and add more thin clients to print via a local Windows Servers without needing logon scripts to map over the WAN (which is very slow)

    Thanks
    Anthony

    #11827
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi Anthony,

    You are correct, these tabs are for connecting the Thin Client to a print server.

    LPD – Line Printer Daemon – this is a Unix based print protocol
    SMB – Server Message Blocks – Used to connect to Microsoft Print Servers

    Now you can use the UPD2 but not the UPD3. This will allow you to lower your driver base. Take a look at this article here on setting this up:

    http://www.freewysemonkeys.com/site/modules.php?name=Downloads&d_op=viewdownloaddetails&lid=30&ttitle=Universal_Print_Driver_Exclude_Winterms_v1_.pdf

    This would be nice as I can then remove more printer drivers from my Citrix farm and add more thin clients to print via a local Windows Servers without needing logon scripts to map over the WAN (which is very slow)

    Yes this is a slow way of doing this, I would recommend you place a print server next to the Citrix servers and import the print ques via the Citrix console. You can then use Citrix policies to assign the printers to users rather than a log in script. You will find this much faster. Be aware that you are sending spooled jobs over the WAN so make sure you have some policy mapping on the routers on port 1494 or the sessions will slow down.

    There are now two new ways you can test printing to see what works for you! Of course if you do map printers on the clients use the WNOS.INI and do not manually create them if you can avoid it,

    Cheers,
    -TT

    #11831
    ConfGenConfGen
    Keymaster
    • Total Post: 11002
    • Jedi Master
    • ★★★★★★★

    Hi Anthony,

    So on the ports tab we can define a locally attached printer (on LPT1 or USB etc) with a name, Printer identification (which I believe would be the name of the windows printer driver used on the Citrix server etc) printer class, which I am not sure why you would need to define this if all the device does is pass data out the necessary port to the printer. Enable device is straight forward and LPD service I know allows for devices to use the thin client as a network print server to send their printing data to.

    As a small summary:
    – Printer Name=just a name, which is displayed in the session
    – Printer ID=Windows Printer Driver Name
    – Printer Class=used for ThinPrint

    All the other things are perfectly answered by TT

    Cheers
    CG

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.