Руководство Администратора для Cisco Cisco Virtualization Experience Client 2212
C-3
Cisco Virtualization Experience Client 2112/2212 ICA Administration Guide for WTOS 7.0_214
OL-215152-01
Appendix C Local System Administration
Configuring ThinPrint
If the zero client is configured for Dial-up access, there must be an RAS server answering the configured
telephone number. Otherwise, the zero client will require factory attention to recover it.
telephone number. Otherwise, the zero client will require factory attention to recover it.
Configuring ThinPrint
No ThinPrint-specific configuration is available on the zero 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 zero client (by clicking on the desktop background, selecting System Setup from the menu to
open the Network Setup dialog box, and then clicking Printer to open and use the printer
configurations).
users must first set up their printers according to the user documentation, and then configure ThinPrint
on the zero client (by clicking on the desktop background, selecting System Setup from the menu to
open the Network Setup dialog box, and then clicking Printer to open and use the printer
configurations).
Use the following guidelines:
•
Use the Printer Identification field to enter a printer class (you can change the printer name as
needed).
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)
as class)
–
LPD1 = 6 (The LPD Queue name is transmitted as the printer name; the Printer Identification
as class)
as class)
–
LPD2 = 7 (The LPD Queue name is transmitted as the printer name; the Printer Identification
as class)
as class)
–
LPD3 = 8 (The LPD Queue name is transmitted as the printer name; the Printer Identification
as class)
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 Object(s) 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 WTOS 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 will be 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 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 WTOS 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 will be 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 Object(s) Created Automatically by ThinPrint AutoConnect—When using ThinPrint
AutoConnect, the zero client identifies with the zero client ID number 84 (and thus is recognized as
a zero client without a local spooler). You can also set up a template on the server that uses a native
driver (for 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 will be named automatically according
AutoConnect, the zero client identifies with the zero client ID number 84 (and thus is recognized as
a zero client without a local spooler). You can also set up a template on the server that uses a native
driver (for 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 will be named automatically according