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

Enabling strong cryptography for Tpms

If you want to restrict the encryption of communication between your Tpms.Service and Tpms.Agent to TLS 1.2 or higher you may have to enable strong cryptography for .NET separately. Otherwise it tries to establish the connection with TLS 1.0 and will fail.

You have to set the following registry values on the Tpms machines and then restart them.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727] "SystemDefaultTlsVersions" = dword:00000001 "SchUseStrongCrypto" = dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions" = dword:00000001 "SchUseStrongCrypto" = dword:00000001

English