There’s one last step after installing and configuring the ThinPrint Engine: setting up printers on the ThinPrint Ports.
If you are working with several ThinPrint Ports, each with a different protocol, then check port configuration before printer installation to see which ThinPrint Port supports which protocol.
Please also refer to the following information when adding printers to the server manually (without Management Center or Management Services).
For simplicity’s sake, only standard addressing is considered here; reversed addressing can be found in the chart in Naming convention, and addressing ThinPrint Connection Service Ports is explained in detail in ThinPrint Connection Service. On this, see also the section Address information in the Registry (below).
It is irrelevant to a ThinPrint printer name whether the object represents a traditional (native) printer driver or the Output Gateway “printer driver”. The ThinPrint printer name is composed according to the network protocol in use:
|Network protocol||names of printer objects|
Example: Kyocera FS-850#client1:3
Example: Kyocera FS-850#126.96.36.199:3
|Use Virtual Channel Gateway (RDP/ICA/PCoIP)||Either: printer_name#user_name:printer_ID
Example: Kyocera FS-850#administrator:3
Example: Kyocera FS-850#:3
Example: Kyocera FS-850#printer1
Example: Kyocera FS-850#188.8.131.52
Client name with TCP/IP and LPD means the real name of the client in the network (= host name). Alternatively, the client’s IP address can be used; this is especially necessary when there are difficulties with the name resolution.
Note! With TCP/IP it is possible to send print data to any client computer running a ThinPrint Client – independent of a session (on a terminal server or virtual desktop).
At the client (i. e., a workstation, a thin client or terminal, a gateway appliance or a local print server), the ThinPrint Client automatically assigns every installed printer an ID. The printer_ID can be omitted if
- there is only one printer installed on the client
- printing should take place on the ThinPrint Client’s current printer
- if, firstly, all the print jobs are sent via Virtual Channel Gateway and, secondly, the share name entered in Dynamic Printer Matrix’ Target Printer column and the printer name on the client machine match (= if the variable %LCPRN% can be used in the Target Printer column).
The printer name can be anything you like. It is nonetheless recommended that it is the same as the printer name at the client machine.
ThinPrint Client assigned this printer ID 2
Lexmark T644 # client1:2
Lexmark T644 # 192.168.1.17:2
Print protocol ICA, RDP or PCoIP
With the Use Virtual Channel Gateway protocol type, it is possible to print from print servers via RDP, ICA or PCoIP. Print jobs are then sent via TCP/IP from the ThinPrint Engine installed on the print server to the Virtual Channel Gateway on the terminal server or virtual desktop and from there via RDP, ICA or PCoIP to the client. The naming convention for the printers on the print server is the same as for RDP, ICA or PCoIP.
The RDP, ICA and PCoIP protocol assumes all communication with the client, including the client’s unambiguous identification. The printer name is composed of:
Description of the Printer and the Printer ID
Example: Kyocera FS-850 is to be printed via ThinPrint using RDP. If multiple printers are installed and ID 3 was assigned to the printer by the ThinPrint Client, the printer name could be: Kyocera#:3 (# before :) or Kyocera FS-850#_:3 (underline before :) If Kyocera FS-850 is ThinPrint Client’s Current Printer or the Dynamic Printer Matrix is in use (and share name and client printer name match), this name is sufficient: Kyocera FS-850
Note! With the RDP, ICA or PCoIP protocol print data is sent automatically to the client from whose session the print data was created.
Address information in the Registry
If you use unique printer names in your print environment, you can alternatively store the address information in the Windows registry. To do this, write the address of the ThinPrint Client to:
and the printer ID to:
Pooling printer ports with ThinPrint means you can attach printer objects to several ThinPrint Ports – also known as printer pooling. This has the following advantages:
- Improved performance
- Little chance of blockage from very large or “hanging” print jobs
- Fewer printer ports on the server (because multiple printers can be connected to a few ports)
- Bandwidth limitation is more clearly defined
ThinPrint Port pooling is supported by:
- ThinPrint Ports
- Output Gateway
- Virtual Channel Gateway
- Connection Service
- Management Center
- Management Services
Port pooling is mainly used to improve print performance. It should be remembered though, that all ThinPrint Ports in a pool should have the same settings – this can be done automatically using the Management Center or Management Services. Port pooling with ThinPrint Ports in combination with Output Gateways, Management Center/Services and AutoConnect, however, brings more than maximum performance; it also makes administration particularly easy and convenient.
When setting bandwidth, note that the bandwidths of a pool are added to each other when all ThinPrint Ports print simultaneously. Detailed information can be found in the technical description ThinPrint Ports.