All printers that are created by Management Center on central print servers, send their print jobs (with the help of ThinPrint Engine) to devices on which a ThinPrint Client is installed. For the addressing of the ThinPrint Clients you can choose from three protocols:
- TCP/IP
if ThinPrint Clients are accessed via their IP address
- Connection Service
if ThinPrint Clients on ThinPrint Gateways or local print servers cannot be accessed directly via their IP addresses or if firewall settings require a reversal in the direction of communication (additional licensing is necessary, see the ThinPrint Connection Service manual)
- ICA or RDP
if ThinPrint Clients on workstations or Thin Clients cannot be accessed directly via their IP addresses (with VMware also PCoIP instead of RDP)
In the Management Center configuration console you have to configure the selected print protocol in several places:
- Protocol settings in the Locations menu:
- for TCP/IP and Connection Service
- for ICA or RDP
- Protocol settings in a ThinPrint Client’s Printers menu:
- for ICA or RDP
- Protocol settings in the Connections menu:
- for TCP/IP and Connection Service
- for ICA or RDP
You also need to consider the required print protocol in the Dynamic
Printer Matrix of AutoConnect:
- Protocol settings in the Dynamic Printer Matrix of AutoConnect:
- for TCP/IP and Connection Service
- for ICA or RDP
If ThinPrint Client is not already integrated into the firmware of a device, then install – if possible – the compatible ThinPrint Client (TCP/IP type, ICA type
or RDP type). Or select another, appropriate device, on which a ThinPrint Client can be installed. For example, you can use a local print server or a Gateway Appliance, if you don’t want to install ThinPrint Client on every workstation.