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
- Management Services • Overview
- Management Services • Installation
- Management Services • Practice
- Management Services • Cmdlets • Part 1
- Management Services • Cmdlets • Part 2
- Management Services • ScriptRunner
- Management Services • Appendix
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
  - Logging
  - Factory reset
ThinPrint Hub Remote Management
- Cloud management
  - Managing Hubs in the cloud
  - Connecting printers to the cloud
- On-premises remote management
FAQs
Troubleshooting
- Mapping issues
  - Duplicate Printers Map
- Encryption and certificate issues
  - Troubleshooting – Encryption & Certificates
- Fonts and formatting issues
  - Solving font problems
- 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

Technical requirements for Tracking

Your architecture must meet the following requirements for running ThinPrint Tracking:

ThinPrint Engine + ThinPrint Tracking Service:
See ThinPrint Engine on print servers: Technical requirements.
The SQL serveradditionally requires:
- Microsoft SQL Server 2005 Express and later
The ThinPrint Tracking Report Engine can be run on the following servers (as a web server):
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2 SP1

Here, the following is required:

Microsoft .NET Framework 3.5 SP 1
ASP .NET (can be enabled as a Windows component or installed as a part of the .NET Framework)
Internet Information Services (IIS) 5.1 or later. Port 80 is used by default. The IIS Default Web Site needs to be bound to TCP port 80. Make sure that no other programs are using this port.

Note! Please note with ThinPrint Tracking, that data printed via a ThinPrint Port is collected.

Administrator permissions are required for all installation and configuration procedures.