Central print server with ThinPrint Engine (scenario 1)
Terminal server with ThinPrint Engine (scenario 2)
Central print server with ThinPrint Engine (scenario 1)
For all the preparations you need to make on a central print server (on which a ThinPrint Engine is installed) as well as on the terminal servers and XenDesktop templates, refer to ThinPrint installation and configuration.
Terminal server with ThinPrint Engine (scenario 2)
On the terminal server or remote desktop, you can make an entry in the AutoConnect table so that the Mac printer will be mapped into the terminal session – without creating a template.
- When configuring AutoConnect, enter an additional line into Dynamic Printer Matrix, in order to map printers without templates, e. g.:
TPPS!ThinPort:
Legend:
| Column x | applies to Mac OS X clients, and others |
| Column I | applies only for the ICA protocol |
| Column R | applies only for the RDP protocol |
| Column T | applies only for the TCP/IP protocol |
| TPPS | the PostScript driver TP Output Gateway PS |
| ! | separator |
| ThinPort: | name of the ThinPrint Port with which the session printers are to be connected (one line is needed per ThinPrint Port). For TCP/IP, the print protocol of the port must be set as TCP/IP (sockets), and for ICA or RDP as Virtual Channel Protocol (ICA or RDP). |
The PostScript driver TP Output Gateway PS (see TPPS in the Target column of Illus.) enables AutoConnect to transfer the driver properties from the Mac to the session printers.
