ThinPrint Engine • Getting Started
ThinPrint Engine Components
- High Availability and Load Balancing
- Printer Self Service
  - Using the Self Service
  - Windows Registry entries of ThinPrint Self Service
- ThinPrint Group Policies
- Connection Service aka Secure Tunnel
- ThinPrint Tracking
ThinPrint Clients
- ThinPrint Client Windows
- ThinPrint Client for VMware Horizon
- ThinPrint Client Mac
- ThinPrint Client Linux
- ThinPrint Client for HP Printers
ThinPrint Management Services
Personal Printing
- Personal Printing • Introduction
  - About Personal Printing
  - How it works
- Installing Personal Printing
- Configuring Personal Printing server
- Personal Printing Release Station
- User self registration & JobViewer
- Smartphone authentication
- Personal Printing clients on network printers
- Options and supplemental information
Licensing, Certificates and Diagnostics
- ThinPrint licensing
- License server
- License server's PowerShell module
- Enterprise Portal
- Creating and installing certificates
- Ports
  - TCP ports used by ThinPrint
- ThinPrint Diagnostic Utility
ThinPrint Hub
- Intended use and safety information
  - Intended use, conformities and Dual-Use Regulation
  - Safety information
- Quickstart with ThinPrint Hub
- Hub web console
- ThinPrint Hub Finder
- Updating the Hub
  - Downloading and installing a firmware update
  - Firmware versions
- Hub PowerShell module
- Hub cmdlets • Part 1
- Hub cmdlets • Part 2
- Hub cmdlets • Part 3
- Hub cmdlets • Part 4
- Managing certificates on the Hub
- Logging and reset
  - Hub logging
  - Factory reset
ThinPrint Hub Remote Management
- Cloud management
  - Managing Hubs in the cloud
  - Connecting printers to the cloud
- On-premises remote management (no support)
FAQs
Troubleshooting
- Printing issues
  - "Error While Opening Virtual Channel" When Printing
- Mapping issues
- Encryption and certificate issues
  - Troubleshooting – Encryption & Certificates
- Fonts and formatting issues
  - Solving font problems
  - Issues with Zebra and SATO Label Printer
- Management Services issues
  - Troubleshooting of Management Services
- ThinPrint Client issues
  - Troubleshooting of ThinPrint Client Mac
  - Troubleshooting of HP and Xerox printers
- ThinPrint Hub issues
  - ThinPrint Hub troubleshooting

Remote desktop scenarios

Remote desktops – Printing via TCP/IP

Remote desktops – Printing via ICA, RDP or PCoIP

The following example scenarios illustrate typical environments in which ThinPrint can be deployed. The depicted scenarios can also be combined – flexibility in mixed environments is one of the strengths of ThinPrint.

Remote desktops – Printing via TCP/IP

Workstations and terminals (thin clients) communicate with the remote desktops (terminal servers or VDI) via the Citrix protocol ICA, via the Microsoft protocol RDP (with Citrix XenApp/Xen Desktop or Microsoft Terminal Services/Remote Desktop Session Hosts) or via the VMware VDI protocol PCoIP. With ThinPrint, though, they are able to print via TCP/IP in either case. The print jobs are then sent directly to the client computer or network printer, circumventing the remote desktop session (separation of the data streams). This improves performance during printing, since available bandwidth can be utilized better.

Furthermore, each user can use all printers in the network which are accessible via TCP/IP – regardless of whether he is using a workstation (rich client), a thin client, or any other type of client.

ThinPrint printing with terminal servers over TCP/IP

Remote desktops – Printing via ICA, RDP or PCoIP

The Citrix protocol ICA, the Microsoft protocol RDP and the VMware protocol PCoIP enable print jobs to be sent to a user of a remote desktop session through the virtual channels of the session communication (ICA, RDP or PCoIP). This ThinPrint print mode is also possible to clients in masked networks. Further information can be found starting in Example configuration.

ThinPrint printing with terminal servers over ICA, RDP or PCoIP