No ThinPrint specific configuration is available on
the thin clients. Thus to be able to use ThinPrint, users must first
set up their printers according to the user documentation, and then
configure ThinPrint on the thin client using the Printer Setup dialog
box.
To configure the ThinPrint, use the following guidelines:
Use the Printer Identification field to enter a printer class (you can change the printer name as
needed).
Printer IDs are assigned (depending
on the physical port) as follows:
COM1 = 1
COM2 = 2
LPT1 = 3 — USB printers are detected
automatically on LPT1
LPT2 = 4
LPD0 = 5– The LPD Queue name is transmitted
as the printer name; the Printer Identification as class
LPD1 = 6 — The LPD Queue name is
transmitted as the printer name; the Printer Identification as class
LPD2 = 7 — The LPD Queue name is transmitted
as the printer name; the Printer Identification as class
LPD3 = 8 — The LPD Queue name is
transmitted as the printer name; the Printer Identification as class
SMB1 = 9 — In the form \\host\printershare
SMB2 = 10
SMB3 = 11
SMB4 = 12
To install the relevant ThinPrint product on the server
use the following guidelines:
Printer Objects Created Manually
by the Administrator — After you install.print Engine, create
a printer object on the server to use the native driver and ThinPort
as a printer port. You can use any protocol (TCP, RDP or ICA) because
ThinOS has.print clients for all of the protocols. The printer object
needs to observe ThinPrint naming conventions, for example, HPLJ5#_:2, in which case print jobs are sent to the local printer that has
ID number .2 by referring to.print client port ID. If no ID
number is present, the.print client sends the print job to the printer
set as current.
Printer Objects Created Automatically
by ThinPrint AutoConnect — When using ThinPrint AutoConnect, the
thin client identifies with the thin client ID number 84 and thus
is recognized as a thin client without a local spooler. You can also
set up a template on the server that uses a native driver example, HPLJ5) and ThinPort, and then name this template as you want
in the form _#AnyName.
You can then make sure that
the rules on ThinPrint Autoconnect [1] have been set to assign the
desired local printers to use this server template. The assigned printer
will then be shown in the user session using the HPLJ5 driver and
ThinPort; it is named automatically according to ThinPrint naming
convention with the printer name from the client side included. Alternatively,
you can also define a template name according to the client printer
name (replace.AnyName. with printer name 4. and 5. above for example, _#HP Laserjet 5 so that the local printer object.HP Laserjet
5. is mapped to this template without any rules defined on the ThinPrint
Autoconnect.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\