1. technology and computing
2. hardware
3. computer peripherals
4. printers, copiers and fax
5. printers

ThinPrint Engine on terminal servers
ThinPrint version 10.6
Manual
ThinPrint GmbH
Alt-Moabit 91 a
10559 Berlin
Germany / Alemania
Cortado, Inc.
7600 Grandview Avenue
Suite 200
Denver, Colorado 80002
USA / EEUU
Cortado Pty. Ltd.
Level 20, The Zenith Centre,
Tower A
821 Pacific Highway
Chatswood, NSW 2067
Australia
E-Mail: info@cortado.com
Web: www.thinprint.com
Issued: March 30, 2015 (v79)
Notes
© Copyright
This document is the intellectual property of ThinPrint GmbH. This document may be copied in whole or
in part, provided this Copyright notice is included in every copy.
® Registered trade marks
All hardware and software names mentioned in this document are the registered trademarks of their
respective companies or should be regarded as such.
Safety warning
All ThinPrint products are pure software solutions. Please note the safety warnings in the technical documentation from your hardware vendor and from the manufacturer of each device and component.
Before beginning installation, we recommend closing all windows and applications and deactivating any
virus scanner.
© ThinPrint GmbH 2015
2
Manual
Contents
Introduction
................................................................................................................ 6
What is ThinPrint? .......................................................................................................... 6
The technology ..........................................................................................................
Server components ....................................................................................................
Driver Free Printing ....................................................................................................
Print data compression ...............................................................................................
Client component ......................................................................................................
6
6
7
7
7
Package contents ........................................................................................................... 7
Licenses ........................................................................................................................ 8
Terminal server scenarios ................................................................................................ 8
Terminal server(s) – Printing via TCP/IP ....................................................................... 8
Terminal server(s) – Printing via ICA/RDP .................................................................... 9
Installation
.................................................................................................................. 9
Technical requirements ................................................................................................... 9
ThinPrint Engine ...................................................................................................... 10
Cortado License Server ............................................................................................. 10
ThinPrint Client ....................................................................................................... 10
Installing ThinPrint Engine (per terminal server) ............................................................... 11
Installation with installation wizard ............................................................................ 11
New printer object ................................................................................................... 13
Example configuration .......................................................................................... 14
Installing ThinPrint Clients ............................................................................................. 15
Configuring thin client .............................................................................................. 15
Configuring local print server ..................................................................................... 18
client2: RDP type of ThinPrint Client Windows on a workstation ................................... 19
Server configuration ...................................................................................................... 19
ThinPrint Ports ........................................................................................................ 19
Configuring AutoConnect .......................................................................................... 23
Printing ....................................................................................................................... 23
© ThinPrint GmbH 2015
If you still can't print • Checklist .................................................................................... 25
Manual
3
Contents
Configuring ThinPrint
........................................................................................... 27
Global settings ............................................................................................................. 27
ThinPrint Configuration console .................................................................................
Cortado License Server .............................................................................................
Print spooler events .................................................................................................
Tracking .................................................................................................................
ThinShare ...............................................................................................................
27
28
29
29
32
ThinPrint Ports ............................................................................................................. 33
How to create new ThinPrint Ports? ...........................................................................
Configure tab ..........................................................................................................
Advanced tab ..........................................................................................................
Job Statistics tab .....................................................................................................
Distributing port configuration ...................................................................................
33
34
35
36
37
Creating printers and templates ...................................................................................... 41
Templates ............................................................................................................... 42
Manually created printers ......................................................................................... 43
Port pooling ............................................................................................................ 45
LPR/LPD printing with Linux, Mac or Windows CE clients ................................................ 46
Preparations on the server ........................................................................................ 47
ThinPrint Output Gateway ............................................................................................. 48
Paper formats and trays ...........................................................................................
Presettings on the server (administrators only) ............................................................
Settings in a terminal session ....................................................................................
Printing with preview ...............................................................................................
Finishing options .....................................................................................................
Open my printing preferences ....................................................................................
Changing Output Gateway print dialogue’s language ....................................................
49
49
53
54
56
56
57
PostScript version of ThinPrint Output Gateway ............................................................... 58
Encrypting print data .................................................................................................... 59
Importing SSL certificates on the servers .................................................................... 59
Importing SSL certificates on the clients ..................................................................... 63
AutoConnect ................................................................................................................ 65
4
Manual
65
66
66
66
67
68
71
76
76
78
© ThinPrint GmbH 2015
AutoConnect features ...............................................................................................
Basic constellation ...................................................................................................
Templates and ports ................................................................................................
Template permissions ..............................................................................................
AutoConnect configuration ........................................................................................
Settings ..................................................................................................................
Dynamic Printer Matrix .............................................................................................
Variables ................................................................................................................
Script control ..........................................................................................................
Map additional printers ............................................................................................
Contents
Send, export and import the configuration .................................................................. 79
Cloud printing .............................................................................................................. 80
Overview of Cloud Printing ........................................................................................ 80
Setup ..................................................................................................................... 82
Printing .................................................................................................................. 85
Appendix .................................................................................................................... 87
Customer service and technical support .......................................................................... 87
Server roles and custom setup ....................................................................................... 87
Session-in-Session ........................................................................................................ 88
Update and uninstallation ............................................................................................. 90
Update from ThinPrint version 9.0 to 10.0 or from 9.0 to 10.6 .................................... 90
Update from older ThinPrint versions ......................................................................... 90
Uninstallation .......................................................................................................... 91
Disabling Windows printer mapping ............................................................................... 91
Windows registry .......................................................................................................... 94
ThinPrint Engine: ThinPrint Ports and ThinPrint Connection Service Ports ...................... 94
AutoConnect ........................................................................................................... 95
Additional resources ..................................................................................................... 97
Glossary ...................................................................................................................... 97
© ThinPrint GmbH 2015
Abbreviations and acronyms ........................................................................................ 104
Manual
5
Introduction
Introduction
What is ThinPrint?
The ThinPrintt product line offers premium print management for all IT environments.
No matter whether server-based, virtualized or distributed PC architecture, with
homogeneous or heterogeneous hardware and operating features, with an integrated
print server or not. Mobile employees, home employees, as well as complete branch
offices can be easily integrated into the existing corporate IT infrastructure without
any printing restrictions with regard to flexibility, performance or comfort. Thanks to
the high levels of print data compression, secure SSL-encryption, connection-oriented bandwidth control, dynamic printer deployment and technology such as Driver
Free Printing and V-Layer, ThinPrint fully meets the requirements for professional
print management.
The technology
ThinPrint consists of two servers as well as a client component, i.e. ThinPrint
Engine, Cortado License Server and ThinPrint Client (Illus. 1).
Illus. 1
Illus. 1
Using ThinPrint with server and client components
Server components
The server component ThinPrint Engine is the core of the ThinPrint framework. It provides complete printer driver management including Driver Free Printing.
ThinPrint Engine performs the following main functions:
•
•
•
•
6
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Bandwidth controlled transmission of print jobs
Print data compression and streaming
Print data SSL/TLS encryption
Provision of the virtual printer driver TP Output Gateway (enables a radical
reduction of printer drivers on printing computers = Driver Free Printing).
• Auto-created client printers are created by AutoConnect, a component of the
product ThinPrint Engine.
Introduction
Driver Free Printing
Thanks to TP Output Gateway, time-consuming server-side installation and administration of printer drivers under Windows is no longer necessary. Printer driver conflicts
on terminal servers (or Remote Desktop Session Hosts) are also a thing of the past.
The printer drivers are only installed on the client PCs or on local print servers. That
means that any type of printer can be used on any printer port; e.g., multifunctional
devices (printer, fax, copier, and scanner in one device) on a USB interface or a laser
printer on a bidirectional interface.
For ThinPrint Clients on non-Windows computers, the generic PostScript driver
TP Output Gateway PS is applied. Or you install a central print server additionally
where you can use the V-Layer (refer to ThinPrint Engine on print servers manual,
Page 97).
Print data compression
The compression of ThinPrint print data can be influenced as follows:
• With Driver Free Printing mode, on the one hand you can choose the Advanced
Adaptive Compression level using Output Gateway templates (Page 37). This
method analyzes the individual components of a print job and compresses each
with the corresponding best algorithm before transmitting the data. Additionally, user errors that can occur when inserting pictures in a document are corrected. Thereby reducing data volume by up to 98%. On the other hand you
can influence the compression in the port configuration (Page 34).
• With Native Printing mode – i.e. using templates with native drivers –, the compression can only be influenced in the port configuration (Page 34).
Client component
On the client side, ThinPrint Client is generally responsible for receiving print data,
decompressing it, and sending it to the print device. There are many ThinPrint Clients
available for different end devices and types of use: for all Windows versions, for
Mac OS and Linux as well as for both internal and external print servers of network
printers. Please note that there are different ThinPrint Client types for the protocols
RDP, ICA and TCP/IP – the last one as both an application and a Windows service.
ThinPrint Clients can be downloaded from ThinPrint’s website (see Page 97). The
website also includes a list of information on devices which are already embedded
with ThinPrint Clients. If you require a ThinPrint Client which is not listed on the website, please send an e-mail to info@cortado.com.
Package contents
© ThinPrint GmbH 2015
The ThinPrint Engine product ZIP contains amongst other components:
•
•
•
•
•
The License Server installer
The ThinPrint Engine installer
The installer for both License Server and ThinPrint Engine
A quick installation guide for installation on terminal servers
A quick installation guide for installation on print servers
ThinPrint Engine on terminal servers.fm
Manual
7
Introduction
Licenses
The ThinPrint Engine is licensed user-based. The License Server installer can install
a demo license key. But for productive purposes you should have received license
keys from your reseller; these are also installed on the License Server (Illus. 1). There
are license keys from the following types:
TLUS-0750-10...
TPUD-0745-10...
TPUS-0745-10...
annual ThinPrint Engine Premium license (ALM)
perpetual ThinPrint Engine license
perpetual ThinPrint Engine Premium license
The third block of the key indicates the number of licensed named users (here: 10).
More information about ThinPrint licensing can be found in the Licensing and in the
Licenses Server manual.
Premium licenses
Premium licenses contain the following components or products additionally:
•
•
•
•
•
•
Mobile Print
Print job tracking
Host Integration Service
Connection Service
Management Center (only relevant for print server installation)
Cluster support (only relevant for print server installation)
Note! In case License Server and one of the components Host Integration Service or Connection Service are installed on different machines, the license keys
of ThinPrint Engine Premium (TLUS or TPUS) are to be installed on the
License Server but those of the other components on the respective computer:
TPHS on the Host Integration Service machine
THCG on the Connection Service machine
Terminal server scenarios
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.
Terminal server(s) – Printing via TCP/IP
1
8
with Microsoft Terminal Services/Remote Desktop Session Hots or Citrix XenApp
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
PCs and terminals (thin clients) communicate with the terminal server1 via the Citrix
protocol ICA or the Microsoft protocol RDP (Illus. 2). 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 terminal 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,
Installation
or any other type of client. Further information can be found starting in Example configuration on Page 14.
Illus. 2
Illus. 2
ThinPrint printing with terminal servers over TCP/IP
Terminal server(s) – Printing via ICA/RDP
Both the Citrix protocol ICA and the Microsoft protocol RDP enable print jobs to be
sent to a user of a terminal session through the virtual channels of terminal server
communication (ICA or RDP). This ThinPrint print mode is also possible to clients in
masked networks 2 (Illus. 3). Further information can be found starting in Example
configuration on Page 14.
Illus. 3
Illus. 3
ThinPrint printing with terminal servers over ICA or RDP
Installation
Technical requirements
© ThinPrint GmbH 2015
Be sure that the TCP ports for printing via TCP/IP are not being blocked by another
program or by a server-side or client-side firewall. Default ports are:
• License Server inbound: 4004 and 4005
• ThinPrint Engine outbound: 4000 for printing, 4005 to the License Server and
– if needed – 443 to the cloud
• Connection Service inbound: 4000 and 4001
2
Networks behind routers with Network Address Translation (NAT)
ThinPrint Engine on terminal servers.fm
Manual
9
Installation
IPv4 has to be enabled for each involved machine (IPv6 should be disabled).
ThinPrint Engine
Supported server operating systems
• Windows Server 2012 R2
• Windows Server 2012
• Windows Server 2008 R2
• Windows Server 2008
Also required:
• .NET Framework version 3.5
For Windows 2012, please install .NET Framework 3.5 additionally.
• For Windows 8 Modern UI applications: Feature Release 1 (FR1) of ThinPrint
Output Gateway 9.0 if it is to support finishing options additionally
• With Windows Server 2008 SP1: Microsoft Hotfixes KB958741 (Print Job
Owner) and KB958656 (Client Side Rendering)
• With Windows Server 2008 R2: Microsoft Hotfix KB2493115
• For Session-in-Session (Page 88) to a XenApp server or XenDesktop:
Citrix ICA Client v10.0 or later
• If necessary: Microsoft SQL Server 2005 Express or later for the Tracking database
ThinPrint Engine can be installed together with the following ThinPrint components
on the same server (provided it’s supported by the respective operating system):
•
•
•
•
License Server
Mobile Print
Connection Service
Host Integration Service
Cortado License Server
Supported server operating systems
• Windows Server 2012 R2
• Windows Server 2012
• Windows Server 2008 R2
• Windows Server 2008
ThinPrint Client
• Workstations or local print servers: Windows 8.1, 8, 7, XP, 2012 R2, 2012,
2008 R2, 2008, 2003 SP2
• Apple MacIntosh, Linux, Windows 2000, NT 4, Vista, ME, 98, 95 with
Windows-Installer version 2.0 and later
• Thin Clients with embedded ThinPrint Client (see Page 97).
For all stages of installation and configuration, you will need a normal domain user
account with local administrator permissions:
– To install and configure the software, set up a normal user account in the AD
(Active Directory). LicService used here as an example.
– Then give this account local administrator permissions on the license server.
10
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Administrator
permissions
Installation
Installing ThinPrint Engine (per terminal server)
License Server
Make sure that a Cortado License Server is already installed. For this, see the
manuals Cortado License Server and ThinPrint Engine on terminal servers • Quick
installation.
Unattended
installation
Unattended installation and licensing are also possible; refer to the technical description Unattended installation of ThinPrint Engine components.
Installation with installation wizard
Install ThinPrint Engine according to the scenarios depicted in illustrations 2 and 3.
Note! Before beginning installation, we recommend closing all windows and
applications and deactivating any virus scanner. Also be aware that after installation ThinPrint Engine will only become functional after a Windows restart.
A detailed installation with all screenshots is shown in the ThinPrint Engine on terminal servers: Quick Installation manual.
1. Start the installation program, e.g. Setup_ThinPrint_10.6_Complete_x64.exe
or Setup_ThinPrintEngine_x64.exe.
2. Select Intall ThinPrint Engine if you use the bundle installer Setup_ThinPrint_10.6_Complete_x64.exe.
Note! With Windows Server 2003, a reboot is required if Windows Installer
4.5 was not installed before installation (in this case, Windows Installer 4.5
will be installed automatically).
© ThinPrint GmbH 2015
3. Select one of the following languages: English, German, French, or Spanish.
4. Click NEXT to confirm the Welcome window.
5. Read the license agreement, accept it and click NEXT to confirm.
6. The menu shown in Illus. 4 will open. Select TERMINAL SERVER.
ThinPrint Engine on terminal servers.fm
Manual
11
Installation
Illus. 4
Illus. 4
Select the TERMINAL SERVER role
For assistance selecting the role, read Server roles and custom setup on Page 87.
Print Server
This option only applies if you install ThinPrint Engine on a central print server. In
that case, consult ThinPrint Engine on print servers manual.
Terminal Server
Extension
Select TERMINAL SERVER EXTENSION, if you use a central print server in your terminal
server environment (Remote Desktop Session Host). In this case only AutoConnect,
Virtual Channel Gateway and Output Gateway are installed, but ThinPrint Engine is
not3.
Administration
Tools
Select this option if you want to configure ThinPrint Engine remotely from this computer. In this case only the necessary MMC components will be installed. System
requirements for the workstation on which you wish to install Administration Tools:
Windows 8 Classic, 7 SP1, Vista SP2 or XP Professional x64 SP2 or the server operating systems mentioned in Technical requirements on Page 10.
Custom Setup
Here you can specifically select individual ThinPrint components, e.g. Session-in-Session. See Server roles and custom setup on Page 87.
12
ThinPrint Engine will be installed on the print server.
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
3
Installation
7. In the next dialogue box you can specify the Address of Cortado License Server
or select ENTER ADDRESS LATER (Illus. 5). Click NEXT to continue.
Illus. 5
Illus. 5
License Server address
8. In the next Window, specify the installation path and confirm with NEXT.
9. Click on INSTALL in the next dialogue box to start the actual installation process.
Click FINISH to close the last window.
Note! Be aware that after installation ThinPrint Engine will only become functional after a Windows restart.
New printer object
After installation, the _#ThinPrint Output Gateway (template) printer can be found
in the server’s printers folder (Illus. 6).
Illus. 6
© ThinPrint GmbH 2015
Illus. 6
Template ThinPrint
Output Gateway
_#ThinPrint Output Gateway printer template in server’s printers folder
This printer is a template for auto-created client printers. In other words, when a user
establishes a connection to the terminal server, a printer is created (mapped) for
them in the ICA or RDP session; this printer inherits all settings (e.g., compression
level, the transmission protocol, and the TP Output Gateway printer driver) from the
template (Illus. 7).
ThinPrint Engine on terminal servers.fm
Manual
13
Example configuration
Illus. 7
Illus. 7
Further information
Printer in a terminal session: “TP Output Gateway” printer driver inherited
from a template (example)
ThinPrint Clients must be installed on the client machines to receive ThinPrint print
data (see Installing ThinPrint Clients on Page 15).
The TP Output Gateway is used as a universal printer driver for Windows devices.
Alternatively you can use the generic PostScript driver TP Output Gateway PS for
Non-Windows devices.
For more information about creating and configuring printers and templates, see
the sections Templates and ThinPrint Output Gateway (Pages 42 and 48).
By default, ThinPrint Engine automatically creates client printers in every terminal
session. To simplify the selection of a ThinPrint printer within a session, the Windows
automatic printer mapping function could be disabled. Read more about disabling
Windows printer mapping on Page 91.
Example configuration
The installation wizards for both the ThinPrint Engine server and the ThinPrint Client
Windows client components are preconfigured so that it is possible to print immediately after installation is completed, with no further configuration – provided you
install either the RDP ThinPrint Client Windows or the ICA ThinPrint Client Windows
for supporting the respective RDP or ICA connection types.
This plug-and-play installation cannot be used in every scenario. One reason is
that it requires a Windows workstation as client. So only the main configuration
options are illustrated here, using a example scenario as example. The following
descriptions refer to the example scenario below.
© ThinPrint GmbH 2015
14
Manual
ThinPrint Engine on terminal servers.fm
Example configuration
Illus. 8
Illus. 8
Example scenario with client and user names
Our scenario attempts to combine a couple of typical client and connection types in
a terminal server environment. Clients are a workstation and a thin client as well as
a local print server.
The following table describes the print environment used in the example configuration (Illus. 8).
Machine
name
User
name
client1
Printer
ThinPrint Client type
Print mode
user1
Samsung
ML-2525
TCP/IP type of ThinPrint Client Linux
with native printer
driver
ps06
—
Lexmark
T644
ThinPrint Client Service Windows
(TCP/IP)
Driver Free Printing
client2
user2
HP Color
LaserJet
RDP type of ThinPrint Client Windows
Driver Free Printing
The ICA protocol can also be used as an alternative to RDP. In that case, all RDP
specific installations and configurations must be replaced with those for ICA.
Installing ThinPrint Clients
Configuring thin client
© ThinPrint GmbH 2015
client1: ThinPrint Client Linux (TCP/IP) on a thin client
1. For this example scenario, choose a thin client with an embedded ThinPrint
Client (see Page 97).
2. Open the configuration of the thin client (here: Igel Linux) and firstly, create a
printer under PRINTER→ CUPS→ PRINTERS (Caution: not under ThinPrint), see
the arrow on the left in Illus. 9.
3. Select ADD (click on the asterisk, see right arrow in Illus. 9).
4. Create a printer name (no spaces) select a printer port if necessary, and click
on the button DETECT DEVICES (middle arrows in Illus. 9)
ThinPrint Engine on terminal servers.fm
Manual
15
Example configuration
5. This opens the window, SELECT AVAILABLE DEVICE (Illus. 9 below), where you can
select the printer.
Illus. 9
Illus. 9
Thin Client Igel Linux: Creating CUPS printer
6. Illus. 10 shows the successfully created printer under CUPS.
Illus. 10
Illus. 10
Thin Client Igel Linux: Created CUPS printer
7. Now go to THINPRINT→ PRINTER (left arrow in Illus. 11).
8. Click on ADD (asterisk) and enter the printer name. You can use spaces here.
9. Click on the button DETECT DEVICES.
© ThinPrint GmbH 2015
16
Manual
ThinPrint Engine on terminal servers.fm
Example configuration
10. This opens the window SELECT AVAILABLE DEVICE, where you can select your
printer as CUPS printer (Illus. 11).
Illus. 11
Illus. 11
Thin Client Igel Linux: creating CUPS printer in ThinPrint
11. Enable this ThinPrint printer (arrow in Illus. 12).
Illus. 12
Illus. 12
Thin Client Igel Linux: activate ThinPrint printer
© ThinPrint GmbH 2015
Illus. 13. shows the result. The printer is now set up for ThinPrint.
ThinPrint Engine on terminal servers.fm
Manual
17
Example configuration
Illus. 13
Illus. 13
Thin Client Igel Linux: successfully set up ThinPrint printer
More information about thin client settings can be found in LPR/LPD printing with
Linux, Mac or Windows CE clients on Page 46.
Configuring local print server
ps06: ThinPrint Client Service Windows on a local print server
1. For the example scenario, install a Lexmark T644 printer (Illus. 14).
Illus. 14
Illus. 14
Printer installed on local print server ps06
2. Install ThinPrint Client Service Windows; please refer to the ThinPrint Client
Windows manual.
3. Open the ThinPrint Client Manager. Determine the Lexmark T644 printer ID
from the ASSIGNMENT tab (Illus. 15).
Illus. 15
18
Printer ID of the Lexmark T644 (here: 1)
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Illus. 15
Example configuration
client2: RDP type of ThinPrint Client Windows on a workstation
Requirement: An RDP client must be installed. The scenario in Illus. 8 (Page 15)
applies.
1. For the example scenario, install an HP Color LaserJet printer (Illus. 16).
2. Install RDP type of ThinPrint Client Windows; please refer to the ThinPrint Client Windows manual.
ThinPrint Client is started automatically with the RDP session. It does not need
to be configured for the example installation.
Illus. 16
Illus. 16
Printer installed locally on client2
Server configuration
All settings made for server configuration must be performed on each terminal server
in a server farm (for import/export and sending configuration see Page 37).
Requirement: ThinPrint Engine must already be installed (Page 11). The scenario
in Illus. 8 (Page 15) applies.
ThinPrint Ports
1. Open the ThinPrint configuration (Illus. 17).
© ThinPrint GmbH 2015
Illus. 17
Illus. 17
ThinPrint Engine on terminal servers.fm
Opening ThinPrint Configuration
Manual
19
Example configuration
2. Click ADD (Illus. 18, right arrow) for each remote ThinPrint Engine to be configured and then specify the computer address. For the local ThinPrint Engine,
click THINPRINT ENGINE in the console tree (Illus. 18, left arrow).
Illus. 18
Illus. 18
Open the configuration console for server components
3. Select: THINPRINT→ THINPRINT ENGINE→ PORT MANAGER (Illus. 19, left arrow).
Illus. 19
Illus. 19
ThinPrint Port(s) in the configuration console (= Port Manager)
4. Create the following ThinPrint Port by clicking the NEW THINPRINT PORT icon
(upper arrow in Illus. 19) and set the protocol (Illus. 20 and 21):
Port name
Port type (protocol)
RDP1:
VCP = VIRTUAL CHANNEL PROTOCOL (ICA OR RDP)
© ThinPrint GmbH 2015
20
Manual
ThinPrint Engine on terminal servers.fm
Example configuration
Illus. 20
Illus. 20
Selecting port type for port “RDP1:”; click APPLY
Illus. 21
A new ThinPrint Port
Illus. 21
5. To enable AutoConnect to create a corresponding printer for each client printer
in a terminal session and also so that the printer can print across different
connections, create the following printer templates (Illus. 22) in the server’s
printers folder:
ThinPrint Port
Printer driver
_#Samsung ML-2525
ThinPort:
Samsung ML-2525W Series
_#RDP
RDP1:
TP Output Gateway
© ThinPrint GmbH 2015
Printer name
ThinPrint Engine on terminal servers.fm
Manual
21
Example configuration
Illus. 22
Illus. 22
Two new printer objects as templates
6. Under PROPERTIES→ SECURITY, assign permissions to the two printer templates,
_#Samsung ML-2525 and _#RDP:
• Delete all users and groups except for administrators and all application
packages, if applicable.
• Add SYSTEM and allow full control.
7. Change to the port configuration and check that the new printers have been
assigned correctly to the ThinPrint Ports (Illus. 23; if necessary, press F5 to
refresh).
Illus. 23
Illus. 23
The new templates (right) assigned to the ThinPrint Ports (left)
© ThinPrint GmbH 2015
22
Manual
ThinPrint Engine on terminal servers.fm
Example configuration
Configuring AutoConnect
8. Select DYNAMIC PRINTER MATRIX in the Console Tree (Illus. 24, left). To enable
AutoConnect to create the printers from client1 and client2 for the sessions of
user1 and user2, add the following entries to the first two lines:
IP Range
Client
Name
Printer
Name
User/Group
Target
*
*
*
\\ourdomain\user1
Samsung ML-2525
*
*
*
\\ourdomain\user2
RDP
Notes:
• Double-click in the gray area to change to the edit mode.
• AutoConnect processes the Dynamic Printer Matrix from top to bottom, for
each printer activated in ThinPrint Client (on a workstation). When a
matching entry is found, AutoConnect stops searching the table and the target
printer of the matching line is being created in the user’s session. So, lower
lines will only be executed if the conditions of the upper lines don’t match for
this client printer.
Illus. 24
Illus. 24
Creating a printer
manually
Dynamic Printer Matrix
– Create the following printer object in the terminal server’s printers folder for the
printer in Illus. 14 and 15:
Lexmark T644#ps06:1
© ThinPrint GmbH 2015
Attach it to the ThinPort: printer port.
Printing
– Establish a Remote Desktop Connection from each client machine to the terminal server farm; as shown in our example, logging on as user1 and user2, respectively. The printers in Illus. 25 and 26 appear in the printers folder in the
two sessions.
– Open an application and print with each of these printers.
ThinPrint Engine on terminal servers.fm
Manual
23
Example configuration
Illus. 25
Illus. 25
Printers from user1 in an terminal session as in the example
Illus. 26
Printers from user2 in an terminal session as in the example
Illus. 26
Print jobs will be received from the ThinPrint Clients and forwarded to the printers as
follows:
Client name
(User name)
Print
protocol
Addressed
printer ID
ws2776 (user1)
RDP
2
HP Color LaserJet 3600
ps06 (user1 + user2)
TCP/IP
1
Lexmark T644
ws2307 (user2)
TCP/IP
2
Samsung ML-2525
Target printer
Please note which printers in terminal sessions use a native driver and which use the
TP Output Gateway (see the MODEL column in Illus. 25 and 26).
© ThinPrint GmbH 2015
24
Manual
ThinPrint Engine on terminal servers.fm
Example configuration
If you still can't print • Checklist
© ThinPrint GmbH 2015
If AutoConnect does not create the desired printers or if printing itself fails to work
properly, please check the following before contacting ThinPrint support (Page 87).
• If you run Windows Server 2008 (x64) SP1: Did you install the Microsoft Hotfixes KB958741 (Print Job Owner) and KB958656 (Client Side Rendering)?
(Page 10)
• Is the same protocol selected for the ThinPrint Client, the ThinPrint Port, and
AutoConnect? Example for RDP:
• Is the RDP type of the ThinPrint Client installed on the client machine?
(Page 19)
• To which type of ThinPrint Port is the specified printer template connected?
VIRTUAL CHANNEL PROTOCOL (ICA OR RDP); must be enabled in the port configuration (Illus. 20).
• For AutoConnect, either VIRTUAL CHANNEL (ICA OR RDP) or AUTO must be set
as connection protocol (Illus. 81), and the respective column in the Dynamic
Printer Matrix has to be set to enabled (here R for RDP).
• Is TP AUTOCONNECT SERVICE running on each terminal server?
• If TCP/IP is the selected protocol:
• Are the TCP port numbers the same on server and client (see port configuration in MMC – Illus. 38 – and ThinPrint Client Manager)?
• Are you sure that the TCP port number is not being blocked by the firewall or
by another program?
• Is the client in a masked network (NAT)? If so, you must select either RDP or
ICA (and client-side use the respective ThinPrint Client), or additionally install
the ThinPrint Connection Service (see also the ThinPrint Connection Service
manual).
• If a printer was created manually (see Page 23), check the naming convention
of the ThinPrint Port (see port configuration in MMC, Illus. 39).
• If you selected USE ENCRYPTION on the server (Illus. 75), continue reading the
section Encrypting print data for further information (Page 59), or disable
encryption for now.
• Are the correct templates used when AutoConnect starts (see Illus. 22)? For
each template, there must be an appropriate printer name, printer class, or
entry in the Dynamic Printer Matrix (see ThinPrint Client Manager, Illus. 15,
and AutoConnect, Illus. 87). Check that AutoConnect is working by starting it
manually: Open the Command Prompt in a terminal session, change to the
AutoConnect’s program directory – e.g. C:\Program Files\Common Files\ThinPrint – and enter the following to create the session printers:
tpautoconnect –d
tpautoconnect -v
(tpautoconnect -d removes existing autocreated printers and ends the
AutoConnect application in the session)
If the session printers can be created manually by entering TPAutoConnect
in the command line but are not automatically created when the terminal session is started, check all AutoConnect settings in MMC (Illus. 81 to 93).
• Testing the TCP/IP connection: For printing via TCP/IP, there must exist between
server and client a TCP/IP connection which allows direct communication with
the ThinPrint Client and its TCP port. Masked client networks (NAT) can often
ThinPrint Engine on terminal servers.fm
Manual
25
Example configuration
cause difficulties in this situation. Test to see if the connection exists by trying
a telnet from the server to the client’s TCP port.4 To do this, enter the following at the server’s Command Prompt:
telnet IP port (blank space between IP address and TCP port number)
IP is the client machine’s IP address; port is the TCP port the ThinPrint Client
is using. (See also the ThinPrint Client manuals.)
Example 1: telnet 192.168.131.224 4000
After executing this command, a telnet window should open without error
message. If so, the connection is OK.
• If you are using Driver Free Printing but, even though the printers are created in
the terminal session with AutoConnect, printer options such as paper formats
and sources are unavailable, check whether the following functions have been
• enabled:
• ENABLE SENDING PROPERTIES in the ThinPrint Client Manager (Illus. 15)
• INHERIT CLIENT PRINTER SETTINGS in the AutoConnect configuration (Illus. 84)
• Session-in-Session: Check whether ThinPrint Engine is installed on the
machine that you want to run the second session on. The Session-in-Session
component must be installed on the “middle” computer (see Page 88). Check
here:
• Whether the required Registry value SISACTIVE (REG_DWORD) is present and
set to 1 (0=inactive, 1=active). Path: hkey_local_machine\software\ThinPrint\TPClnRdp (or \TPClnIca)
• Whether the ThinPrint component TPClnICA.dll is present in the ICA Client’s
(also: Citrix XenApp Plugin for Hosted Apps) directory – e.g.: C:\Program Files
(x86)\Citrix\ICA Client. If not, copy it from the ThinPrint program directory –
e.g.: C:\Program Files\ThinPrint Engine – to this directory.
Please also note the section Citrix ICA Client later installed (Page 90).
26
A ThinPrint Client (TCP/IP type) is necessary on the respective client machine.
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
4
Configuring ThinPrint
Configuring ThinPrint
Global settings
ThinPrint Configuration console
– Open the THINPRINT CONFIGURATION console (Illus. 27).
Illus. 27
Illus. 27
Start Configuration
The ThinPrint Engine console appears (Illus. 28).
Illus. 28
Illus. 28
ThinPrint Engine console
© ThinPrint GmbH 2015
Here, you will find all events generated by ThinPrint components. Additionally you
can display and filter print spooler events as well as manage the ThinPrint services
and the print spooler.
Note! Note that saved server settings will only be effective after a spooler
restart. With Windows Server 2008 R2 or later, spooler events cannot be
shown here at present.
ThinPrint Engine on terminal servers.fm
Manual
27
Configuring ThinPrint
– Scroll down and select EDIT SETTINGS (Illus. 29).
Illus. 29
Illus. 29
ThinPrint Configuration: Select EDIT SETTINGS
Cortado License Server
– In the CORTADO LICENSE SERVER tab (Illus. 30), you can:
• change the license server address (hostname, FQDN or IP address)
and the TCP port
• open the license server’s configuration website by clicking its link
• change the address of the configuration website by clicking EDIT
Illus. 30
28
© ThinPrint GmbH 2015
Illus. 30
License Server settings
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Print spooler events
– In the PRINT SPOOLER EVENTS tab, you can select which print spooler events from
the Windows event viewer are to be displayed (Illus. 31).
Illus. 31
Illus. 31
Which print spooler events are to be displayed?
Tracking
Overview
The Tracking Service is included in the ThinPrint Engine installer software (ThinPrint
Engine Premium license is needed). Its setup is described in the Tracking manual.
Print job tracking gathers information about print activities using ThinPrint Engine.
With it, print related data is gathered on the server and forwarded to an SQL server
(Illus. 32).
Print job tracking has the following components:
• ThinPrint Engine (sends data to the Tracking Service)
• Tracking Service (receives data and writes it to an SQL database)
• Tracking Report Engine (web component for clear analysis, summary, and graphic report of tracking results)
© ThinPrint GmbH 2015
Note! The SQL server is not included in the ThinPrint Engine. Tracking Report
Engine and SQL server have to be set up separately (see the Tracking manual).
ThinPrint Engine on terminal servers.fm
Manual
29
Configuring ThinPrint
Illus. 32
Illus. 32
Example for using Tracking
See also the section Job Statistics tab (Page 36).
Tracking Service
You can gather information about the print jobs sent with the ThinPrint Engine for
your statistics (tracking). To do so, you must set up a Microsoft SQL server. The
ThinPrint Engine sends tracking data to this server via the Tracking Service. Print data
available for tracking is:
–
–
–
–
–
–
Tracking Report
Engine
Author of a print job
Printer used
Settings used
Print job compression
Number of pages printed
Information on any errors
The Tracking Report Engine makes it possible to display data from the SQL database
as an overview in a web browser. All significant information on print jobs can be summarized by various criteria, sorted, and graphically displayed (Illus. 33).
© ThinPrint GmbH 2015
30
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Illus. 33
Illus. 33
Preparing ThinPrint Engine and
Tracking Service
Analyzing SQL data in a web browser (example)
To prepare the ThinPrint Engine for sending data of sent print jobs to the Tracking
Service, you must make the following changes to the configuration of the ThinPrint
Engine:
© ThinPrint GmbH 2015
1. Open configuration with START→ THINPRINT CONFIGURATION.
2. Mark the respective ThinPrint Engine node and select EDIT SETTINGS (Illus. 29).
3. Enter the following settings in the TRACKING tab (Illus. 34):
• ENABLE TRACKING
• SQL server’s address and name
• SQL server or Windows authentication: an account (specified with Tracking
Database installer) which has write permissions for your database
• Encryption settings if the data are to be sent encrypted to the SQL server
• Name of the Tracking database (created using its installer)
ThinPrint Engine on terminal servers.fm
Manual
31
Configuring ThinPrint
4. Click OK to confirm. The Result is shown in Illus. 35.
Illus. 34
Illus. 34
Enable Tracking and enter settings
Illus. 35
Print job tracking enabled
Illus. 35
For details, see ThinPrint Tracking manual.
ThinShare
32
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
The settings in the THINSHARE tab (Illus. 36) are intended for the compression with
printing to shared Output Gateway printer objects. This is described in the ThinPrint
Engine on print servers manual.
Configuring ThinPrint
Illus. 36
Illus. 36
ThinShare: provided for print server installations
ThinPrint Ports
ThinPrint prints with its own printer ports (ThinPrint Ports) which will be automatically created during installation. Note that Cloud printing also uses specific printer
ports (Page 80). ThinPrint does not affect printing with conventional ports as Standard TCP/IP Ports.
The Port Manager (Illus. 37) offers the following options for ThinPrint Ports:
•
•
•
•
Add a ThinPrint Port – local and remote
Configure a ThinPrint Port – local and remote
Delete a ThinPrint Port – local and remote
Send port configuration to other Windows machines on which a ThinPrint
Engine is installed
• Export and import port properties
• Encryption settings
General information about ThinPrint Ports can also be found in the technical description ThinPrint Ports.
© ThinPrint GmbH 2015
How to create new ThinPrint Ports?
To create new ports use the buttons in MMC’s menu bar (Illus. left) NEW THINPRINT
PORT or NEW THINPRINT CONNECTION SERVICE PORT (Illus. 37). Choose the port settings: port type (protocol), bandwidth and/or encryption.5
5
Recommended: 600 ThinPrint Ports with 800 active printer queues (Windows Server 2003 with
3 GHz Dual Xeon processor, 2 GB RAM, and SCASII ultra3 disk array) or 1500 queues with
Windows Server 2008 R2
ThinPrint Engine on terminal servers.fm
Manual
33
Configuring ThinPrint
Note! In principle, there is no limit to the length of printer port names. Some
applications, however, only support port names with a length of four or six
characters; if longer port names are used, this could cause problems (printer
is not visible in the application, etc.).
Configuration
5. To configure ports, select PORT MANAGER on the left (Illus. 37).
Illus. 37
Illus. 37
ThinPrint Ports in Port Manager
6. Double clicking a port name (right arrow in Illus. 37) will open the port configuration (Illus. 38).
Configure tab
Illus. 38
34
Port settings: CONFIGURE tab
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Illus. 38
Configuring ThinPrint
The ThinPrint Ports can be configured as follows:
USE ENCRYPTION
BANDWIDTH
Enables SSL/TLS encryption; a valid and corresponding certificate must be available on both ThinPrint Engine and ThinPrint
Client machine (not for LPD; see also Page 59).
• ENABLE: Bandwidth control on
• Max. bandwidth available for printing with ThinPrint; minimum: 1 kbit/s, default: unlimited
CONTROL
Print protocol
• TCP/IP (sockets)
• ICA / RDP (Virtual Channel Protocol)
• LPD (Unix print protocol LPR/LPD)
• USE VIRTUAL CHANNEL GATEWAY
This function isn not relevant here. IT’s for printing from print
servers via ICA, RDP or PCoIP.
MINIMUM
• Enabled: always highest compression
• Disabled: transfer rate optimized compression – depends on
bandwidth settings
PRINT DATA
VOLUME
You can also select the TCP port (default: 4000) for the TCP/IP print protocols. The
TCP ports of the ThinPrint Clients must be the same as those of the ThinPrint Ports.
For LPD printing, see the technical description ThinPrint Port configuration for
bandwidth controlled printing via LPR/LPD.
Advanced tab
© ThinPrint GmbH 2015
Illus. 39
Illus. 39
ThinPrint Engine on terminal servers.fm
Port settings: ADVANCED tab
Manual
35
Configuring ThinPrint
Under ADVANCED are the options:
CLIENT CONTROL: BANDWIDTH
If this option is enabled, each client user can set his own bandwidth value
(in the ThinPrint Client Manager). Client bandwidth settings must be lower than
server-side settings; otherwise, ThinPrint Port settings are applied. This function is only available if bandwidth control (see Illus. 38 above right) has been
enabled.
CONNECTION RETRIES (TCP/IP and LPD only)
Enter the number of times ThinPrint Engine should attempt to establish a
connection to the client.
NET SEND SERVICE
Net Send Service is used to notify users if ThinPrint experiences print errors.
If this box is checked (= default), ThinPrint Engine will send error messages to
the relevant account.
Note: This function can become irksome if several users are logged on using the
same account.
NAMING CONVENTION
You can select for each ThinPrint Port whether the address information is at the
beginning or the end of the printer name. Examples:
Default addressing
Reversed addressing
TCP/IP
Lexmark T644 PS3#192.168.1.100
Lexmark T644 PS3#192.168.1.100:1
HP LaserJet 1200 PCL#client1
HP LaserJet 1200 PCL#client1:2
192.168.1.100#Lexmark T644 PS3
192.168.1.100:1#Lexmark T644 PS3
client1#HP LaserJet 1200 PCL
client1:2#HP LaserJet 1200 PCL
ICA / RDP
HP LaserJet 1200 PCL#
Lexmark T644 PS3#:1
HP LaserJet 1200 PCL
:1#Lexmark T644 PS3
Example for auto-created printers (AutoConnect):
HP LaserJet 1200 PCL#user1:2
user1:2#HP LaserJet 1200 PCL
LPD
Lexmark T630#192.168.1.101
Lexmark T630#networkprinter3
192.168.1.101#Lexmark T630
networkprinter3#Lexmark T630
Job Statistics tab
Print statistics must be activated per port.
36
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
– Select the relevant ThinPrint Port; click PROPERTIES→ JOB STATISTICS and then
High (every second), Normal (every 10 seconds), Low (every 30 seconds),
No update, or Statistics off (default) under UPDATE SPEED as in Illus. 40.
Configuring ThinPrint
Note! Use this function only part-time, as it may affect print performance. See
also Tracking (Page 29).
Illus. 40
Illus. 40
Port settings: JOB
STATISTICS
tab
Distributing port configuration
The following strategies are available for creating the same configuration for ThinPrint
Ports on multiple servers:
•
•
•
•
– Open the ThinPrint Engine configuration console.
– Mark a port in a server’s Port Manager (e.g. TS01 in Illus. 41) and select COPY
from the context menu.
– Mark the Port Manager of a target server (e.g. TS02 in Illus. 42) and select
PASTE from the context menu.
© ThinPrint GmbH 2015
Copy-and-Paste
Remote configuration of ThinPrint Ports
Copying port properties with “copy-and-paste” (see below)
Export to an .xml file and import to target servers (see below)
Sending port configuration to target servers (see below)
ThinPrint Engine on terminal servers.fm
Manual
37
Configuring ThinPrint
Illus. 41
Illus. 41
Copy a port on a server
Illus. 42
Paste the port on another server
Illus. 42
Export/Import
The following export and import functions are available:
EXPORT PORT CONFIGURATION
Exports the selected ThinPrint Port to an .xml
file (Illus. 41)
IMPORT /EXPORT→ EXPORT
PORT CONFIGURATION
Exports all ThinPrint Ports to an .xml file if no
port is selected (Illus. 43)
IMPORT /EXPORT→ IMPORT
PORT CONFIGURATION
Imports ThinPrint Ports from an .xml file
(Illus. 43)
© ThinPrint GmbH 2015
38
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Illus. 43
Illus. 43
Sending
port configuration
Exporting, importing, or sending all ThinPrint Ports
The SEND PORT CONFIGURATION function sends ThinPrint Ports to other servers or server groups. There are various modes:
SEND PORT CONFIGURATION
(OVERWRITE)
Sends the selected ThinPrint Port; ports with
the same name on the target system will be
overwritten (Illus. 41)
SEND PORT CONFIGURATION
(ADD ONLY)
Sends the selected ThinPrint Port; ports with
the same name on the target system will not be
overwritten (Illus. 41)
IMPORT /EXPORT→ SEND PORT
CONFIGURATION (OVERWRITE)
Send all ThinPrint Ports (bottom arrow in; ports
with the same name on the target system will
be overwritten (Illus. 43)
IMPORT /EXPORT→ SEND PORT
CONFIGURATION (ADD ONLY)
Send all ThinPrint Ports (bottom arrow in; ports
with the same name on the target system will
not be overwritten (Illus. 43)
ThinPrint Ports on the target computer which do not exist on the on the sending computer remain unchanged.
© ThinPrint GmbH 2015
Procedure
when sending
Selecting the send option will open the dialog in Illus. 44.
Illus. 44
Illus. 44
ThinPrint Engine on terminal servers.fm
Dialog for sending properties
Manual
39
Configuring ThinPrint
– To improve clarity, first select OBJECT TYPES (upper arrow in Illus. 44), and disable GROUPS (Illus. 45). Click OK to confirm.
– Select ADVANCED (lower arrow in Illus. 44) and then FIND NOW (Illus. 46).
Illus. 45
Illus. 45
Limiting the selection to computers
Illus. 46
Finding target servers
Illus. 46
– Mark all target servers and click OK to confirm (Illus. 47).
Caution! You are influencing the configuration of remote computers. Check
once more that you really want to send the configured ThinPrint Ports to the
selected servers. A confirmation prompt allows you to cancel the process.
© ThinPrint GmbH 2015
40
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Illus. 47
Illus. 47
Selecting target servers
Note! If you receive an error message when sending, create a connection with
the MMC to the target computer via the relevant ThinPrint Engine node for
remote configuration and repeat the send process from the source computer
while keeping the console open (Illus. 48).
Illus. 48
Illus. 48
Create a connection to the target computer with the MMC (here: arrow to
TS66) and repeat send process from source computer (here: TS55)
© ThinPrint GmbH 2015
Creating printers and templates
General information about creating ThinPrint printers can be found in the technical
descriptions ThinPrint addressing and ThinPrint Ports.
There’s one last step after installing and configuring the ThinPrint Engine on the
terminal servers: setting up printers on the ThinPrint Ports.
ThinPrint Engine on terminal servers.fm
Manual
41
Configuring ThinPrint
Which protocol?
Simplification(s)
If you are working with several ThinPrint Ports, each with a different protocol, then
check port configuration (Illus. 37) before printer installation to see which ThinPrint
Port supports what protocol.
• ThinPrint Output Gateway (Page 48)
• AutoConnect (Page 65)
Templates
What are templates?
With ThinPrint, a template is a printer in the server’s printers folder from which the
client or session printers created with AutoConnect inherit their properties (see AutoConnect, Page 65).
The _#ThinPrint Output Gateway template appears in the server’s printers folder
after installation of ThinPrint Engine (Illus. 54, Page 48).
Which properties
are inherited?
Among other things, client printers that are created by AutoConnect in the terminal
session’s printers folder inherit the following properties from templates:
• Number of copies, orientation, preview options, compression settings and page
adjustment (scale to fit or adjust margins); these are inherited always from the
templates.
• The other properties (e.g., paper trays, paper format, color, print resolution, and
print on both sides (duplex) are retrieved from the ThinPrint Client. These will
be also inherited from the templates if sending properties from the ThinPrint Client to the ThinPrint Engine is disabled.
• (Native) printer driver or Driver Free Printing (TP Output Gateway)
• Printer port and thus:
• Bandwidth
• Print protocol (TCP/IP, ICA, RDP)
• Printing with or without the ThinPrint Connection Service
• Printing with or without print data encryption
• Port pooling
• Naming convention for ThinPrint printers
© ThinPrint GmbH 2015
42
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Template
denominations
Network protocol
Names of printer objects (for templates)
TCP/IP, ICA, RDP
Either:
_#printer
Example:
_#Kyocera FS-850
Or:
_#class
Example:
_#HPLaser
Printers can be connected via a template with a specific name (e.g., _#printer) if their printer name or
class name corresponds with the template name (after
the #). Using class names is sensible if printers with
different names shall use the same template (this is
possible if the driver in the template is appropriate for
the different client printers). The underscore (“_”)
marks the template as such and is replaced with client-specific information for the automatically created
printers.
Manually created printers
If you let AutoConnect automatically create all client printers in the sessions, then
you only need to create templates and select the naming convention in the port configuration (see Page 35) once. If you also want to create printers on the server manually, though, please also refer to the following information.
For simplicity’s sake, only standard addressing is considered here; reversed
addressing can be found in the chart on Page 36, and addressing THINPRINT CONNECTION SERVICE PORTS is explained in detail in the ThinPrint Connection Service
manual. It is irrelevant to a ThinPrint printer name whether the object represents a
traditional (native) printer driver or the Output Gateway “printer driver”. The ThinPrint printer name is composed according to the network protocol in use:
© ThinPrint GmbH 2015
Printer names
Network protocol
Names of printer objects
TCP/IP
Either:
Example:
Or:
Example:
printer_name#client_name:printer_ID
Kyocera FS-850#client1:3
printer_name#IP_address:printer_ID
Kyocera FS-850#191.168.1.17:3
ICA/RDP
Either:
Example:
Or:
Example:
printer_name#user_name:printer_ID
Kyocera FS-850#administrator:3
printer_name#:printer_ID
Kyocera FS-850#:3
LPD
Either:
Example:
Or:
Example:
printer_name#client_name
Kyocera FS-850#printer1
printer_name#IP_address
Kyocera FS-850#191.168.1.18
ThinPrint Engine on terminal servers.fm
Manual
43
Configuring ThinPrint
client_name
Client name with TCP/IP and LPD 6 means the real name of the client in the network
(= host name). Alternatively, the client’s IP address can be used; this is especially
necessary when there are difficulties with name resolutions
Note! With TCP/IP it is possible to send print data to any client computer running a ThinPrint Client – independent of the terminal session.
printer_ID
At the client 7, the ThinPrint Client automatically assigns every installed printer an ID
(see Illus. 15, Page 18). The printer_ID can be omitted if there is only one printer
installed on the client, or if printing should take place on the ThinPrint Client’s current printer.
printer_name
The printer name can be anything you like. It is nonetheless recommended that it is
the same as the printer name at the client.
Example 2:
Client
Client name
client1
IP Address
192.168.1.17
Printer
HP LaserJet 1200 PCL
ThinPrint Client assigned this printer ID 2.
Server
HP LaserJet 1200 PCL#client1:2
Or
HP LaserJet 1200 PCL#192.168.1.17:2
The ICA and the RDP protocols assume all communication with the client, including
the client’s unambiguous identification. The printer name is composed of:
Description of the Printer and the Printer ID
Note! With the ICA/RDP protocol print data is sent automatically to the client
from whose terminal session the print data was created.
See the technical description ThinPrint Port configuration for bandwidth controlled printing via
LPR/LPD.
7
i.e., a Workstation, a thin client (terminal), a gateway appliance or a local print server
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
44
6
Configuring ThinPrint
Port pooling
Pooling printer ports with ThinPrint means you can attach printer objects to several
ThinPrint Ports (Illus. 49 and 50) – also known as printer pooling. This has the following advantages:
• Improved performance
• Little chance of blockage from very large or “hanging” print jobs
• Fewer printer ports on the server (because multiple printers can be connected
to a few ports)
• Bandwidth limitation is more clearly defined
Illus. 49
Illus. 49
Port pooling increases the availability of printers
ThinPrint Port pooling is supported by:
•
•
•
•
ThinPrint Ports
Output Gateway
AutoConnect
Connection Service
© ThinPrint GmbH 2015
Port pooling is mainly used to improve print performance. It should be considered,
though, that all ThinPrint Ports in a pool should have the same settings. Port pooling
with ThinPrint Ports in combination with Output Gateways and AutoConnect, however, brings more than maximum performance; it also makes administration particularly easy and convenient.
When setting bandwidth, note that the bandwidths of a pool are added to each
other when all ThinPrint Ports print simultaneously. Detailed information can be
found in the technical description ThinPrint Ports.
ThinPrint Engine on terminal servers.fm
Manual
45
Configuring ThinPrint
Illus. 50
Illus. 50
Enabling port pooling (example)
LPR/LPD printing with Linux, Mac or Windows CE clients
Linux, Mac OS and Windows CE clients are capable of forwarding print jobs to LPD
devices. The ThinPrint Client Linux, Mac or WinCE is installed on a thin client or
workstation and can then receive ThinPrint print jobs (via TCP/IP, ICA or RDP) and
send them directly to internal or external print servers of network printers (via
LPR/LPD, Illus. 51).
ThinPrint Clients for Linux, Mac and Windows CE operating systems support
LPR/LPD printing.
Note! For more information on sending print jobs directly via LPR/LPD with
ThinPrint Engine, see also the technical description ThinPrint Port configuration for bandwidth controlled printing via LPR/LPD.
Illus. 51
46
LPR/LPD printing via Linux, Mac or Windows CE clients
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Illus. 51
Configuring ThinPrint
Preparations on the server
– Set up a new template on the server (e.g. #Samsung ML-2525, left arrow in
Illus. 52) and attach it to a ThinPrint Port (e.g. ThinPort:, Illus. 19 on
Page 20). Use a native printer driver to do this (e.g. Samsung ML-2580 Series
PCL6, right arrow in Illus. 52, or TP Output Gateway PS).
Illus. 52
Illus. 52
Preparing a template for LPD printing with thin clients (example)
– Make sure that the printers completely spool the print data on the hard drive
before sending. To do so, open the template’s printer properties and select
GENERAL. Select START PRINTING AFTER LAST PAGE IS SPOOLED (Illus. 53). Additionally disable the ADVANCED PRINTING FEATURES. Click OK to confirm.
– Select the appropriate settings in AutoConnect to ensure that the relevant
Windows-CE, Mac OS or Linux clients’ printers operate with the new template
(_#HPLaser) in the terminal sessions. Refer to the configuration example on
Page 23 or to the section AutoConnect on Page 65.
© ThinPrint GmbH 2015
Illus. 53
Illus. 53
ThinPrint Engine on terminal servers.fm
Recommended settings for client-side LPD printing on the server
Manual
47
Configuring ThinPrint
ThinPrint Output Gateway
TP Output Gateway is a virtual printer driver (see the MODEL column in Illus. 54) that
makes it possible to render print data on a remote machine (workstation or print server) using the native printer driver which is installed there. Because no other printer
driver is required on the machine on which the applications run, this print method is
called Driver Free Printing. In this sense, of course, “Driver Free” only refers to the
terminal server (Illus. 55).
The user interface of Output Gateway is available in 16 languages, see Page 57.
Illus. 54
Illus. 54
“TP Output Gateway” driver in the server’s printers folder
With Driver Free Printing, print data is sent from the terminal server to the client
machine in Windows’ own EMF data format – bandwidth controlled, compressed,
streamed, and, if desired, encrypted.
Illus. 55
Illus. 55
Naming convention
You can treat the printer objects based on TP Output Gateway like any other printer
object. To use it instead of a native (conventional) printer driver, it must usually be
renamed according to the ThinPrint naming conventions. Output Gateway is either
used as a template for AutoConnect, or is renamed for targeting a specific printer.
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
48
Driver Free Printing: Output Gateway on terminal servers, printer drivers on
workstations and local print servers running Windows
Configuring ThinPrint
Example 3: Addressing the printer directly (TCP/IP printing)
Client
Client name
client1
ID
3
IP address
192.168.1.17
Printer name
HP LaserJet 5L
Printer name
HP LaserJet 5L#client1:3
Server
or
Printer name
HP LaserJet
5L#192.168.1.17:3
Output Gateway printer objects can be created manually with the ADD PRINTER function in printers folder using THINPRINT as manufacturer. The printers are to be
connected to a ThinPrint Port.
Paper formats and trays
After initial installation, a few default options are available for paper formats and
paper sources (= selection of paper trays or manual feed, Illus. 61). You can add
further options – provided they are supported by the printer drivers on the client
machine(s).
There are the following alternatives to do this:
• For printers created by AutoConnect:
Automatic upload of printer properties from the ThinPrint Client to the server
(Illus. 61)
• For manually created printers:
Setting Registry values for paper formats and sources on the server
Presettings on the server (administrators only)
© ThinPrint GmbH 2015
The following settings can be configured in the server’s printers folder for all templates using “TP Output Gateway” as their printer driver (e.g. “_#ThinPrint Output Gateway”); as such they affect all printers using these templates during a terminal session.
ThinPrint Engine on terminal servers.fm
Manual
49
Configuring ThinPrint
– Select for example FILE→ PROPERTIES→ DEVICE SETUP for _#ThinPrint Output
Gateway in the server's printers folder.
Compression range
There are five options available for print data compression (Illus. 56):
• Normal
• Optimal
• Maximum
• Extreme
• No images
Lossless
Text without loss, good image quality
Text without loss, medium image quality
Text without loss, lower image quality
Only text will be printed
At this point you can set the range of compression levels that the users will be able
to set, for example, OPTIMAL, and the level NORMAL is no longer available to users.
The default compression level itself is set in the tab ADVANCED→ PRINTING
DEFAULTS→ COMPRESSION (Illus. 60, on Page 53).
SpeedCache
Additionally the option SPEEDCACHE can be enabled or disabled for terminal server
users (Illus. 56).
SpeedCache makes printing even faster and more efficient. SpeedCache checks
every print job, for whether it replicates graphic elements (such as logos) and, if so,
sends them only once. Thereby, the volume of server-client communication is cut
down, without creating additional processor load.
Illus. 56
Illus. 56
User policies
The USER RESTRICTIONS group offers the options BLACK AND WHITE ONLY for presetting
gray-scale printing and ALWAYS USE DUPLEX for printing on both sides (Illus. 56 bottom). As a result, the respective options will be grayed out for users in their sessions
(see the arrows pointing to the options COLOR and NONE – for print on both sides –
in Illus. 57).
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
50
Setting compression range, SpeedCache and other
Configuring ThinPrint
Illus. 57
Illus. 57
Page Setup
COLOR and simplex printing (NONE) grayed out for users
Select the PAGE SETUP tab in ADVANCED→ PRINTING DEFAULTS to change paper and
color presettings; e.g., LETTER or A4 as paper size (Illus. 58). Additionally you can
select from the following settings for double-sided printing: LONG EDGE or SHORT EDGE
(= turn over edge).
© ThinPrint GmbH 2015
Illus. 58
Illus. 58
Advanced
Presetting paper size, print resolution, color, etc., on the server
In the ADVANCED tab (Illus. 59) you can preset if print jobs are to be sent without a
pop-up menu to the printer (PRINT DIRECTLY). Alternatively a PRINT PREVIEW (Illus. 63)
or the native printer driver's user interface (OPEN MY PRINTING PREFERENCES, Illus. 65)
ThinPrint Engine on terminal servers.fm
Manual
51
Configuring ThinPrint
can appear on a workstation. Both options allow the user to access all other printer
specific settings.
PAGE ADJUSTMENT offers options for the default procedure if the printable area of
the document and of the printer driver’s paper format don’t match. The option SCALE
TO FIT changes the size of the printout, ADJUST MARGINS moves the print area
(Illus. 59). It is recommended to leave both settings enabled for printer templates.
You can use the option PRINT AS IMAGE to solve layout problems. Because of print
performance please follow the steps described in the Solving problems with fonts
guide first.
Illus. 59
Illus. 59
Compression level
Presetting scaling and margin adjustment on the server
In the COMPRESSION tab, the default level of compression for users can be set
(Illus. 60). The number of shown levels depends on the configured compression
range (Illus. 56).
© ThinPrint GmbH 2015
52
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Illus. 60
Illus. 60
Presetting compression level on the server
The template settings from Illus. 58 to 60 will be shown as default options in a terminal session. Users can change them within their sessions.
Settings in a terminal session
The following properties of the printers installed on the client machine can be sent
from the client to the server via AutoConnect:
•
•
•
•
•
•
•
Color/grayscale
Paper sources
Print on both sides (duplex/simplex)
Finishing options such as staple, punch, binding
Print resolution
Paper size
Comments and location
© ThinPrint GmbH 2015
In a terminal session the users can change some printer settings in the printer properties dialogue before printing (except comments and location). The following settings can be edited in the PAGE SETUP tab (Illus. 61): PAPER SIZE, PRINT QUALITY, PAPER
SOURCE, COLOR, ORIENTATION and PRINT ON BOTH SIDES.
ThinPrint Engine on terminal servers.fm
Manual
53
Configuring ThinPrint
Illus. 61
Illus. 61
Display of paper sources in a native driver’s user interface (left) and in the
Output Gateway interface (right)
Printing with preview
Once the users have enabled the print preview (lower arrow in Illus. 62) the print job
will appear in the ThinPrint viewer (Illus. 63); this requires that the print jobs are sent
to a Windows workstation. Here the users can:
• Print to any printer that is connected to the client computer or can be reached
from it
• Navigate in documents with more than one page
• Zoom
• Cancel print job reception
• Save print job 8
54
File extension: .tpf (compressed EMF data); the preview program ThinPrint Viewture
(= TPView.exe) is needed for reloading a saved print job; see Page 97).
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
8
Configuring ThinPrint
Illus. 62
Illus. 62
Print mode, scaling and margin adjustment as well as PRINT AS IMAGE in a session
Illus. 63
ThinPrint preview on the client computer (water mark = demo version)
© ThinPrint GmbH 2015
Illus. 63
When printing with preview, the print options appear in the terminal session in the
Output Gateway design (Illus. 61 right). Once the client machine receives the print
job, the print job is displayed in a preview window (Illus. 63). The print options now
appear in the design of the native printer driver (Illus. 61 left).
ThinPrint Engine on terminal servers.fm
Manual
55
Configuring ThinPrint
Finishing options
If your printer supports finishing options9, you can find them in the similarly named
tab (Illus. 64). Here you can set, for example, where staples should be located on
the printout, where bindings should be set or hole punches made. Here you can also
set how many pages per sheet should be printed, and in which order.
Illus. 64
Illus. 64
Finishing options in a session
Open my printing preferences
If there is a printer function which is not supported by the Output Gateway’s user
interface the users can use the native driver’s user interface (Illus. 65). To do so, they
select OPEN MY PRINTING PREFERENCES (upper arrow in Illus. 62). This also requires
that the print jobs are sent to a Windows workstation on which the jobs are rendered
using the native driver.
56
Requirement: The printer must support Print Tickets from Microsoft. Download ThinPrint Finishing Detector (Page 97) to find out which finishing options are supported by your printer models.
Install this tool on the machine where the printer drivers are installed.
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
9
Configuring ThinPrint
Illus. 65
Illus. 65
Native driver properties will open automatically on a workstation
Changing Output Gateway print dialogue’s language
The Output Gateway print dialog (Illus. 60) is displayed for the users in the language
that was chosen during the installation of the ThinPrint Engine on the terminal server
(English, German, Spanish or French). This is set using the Windows registry value:
hkey_local_machine\software\ThinPrint\Lang
With Windows multi-language packs this print dialog can be displayed in the display
language of the respective user (Illus. 66). To do so, the registry value Lang is to be
changed from enu, deu, fra or esn to def. This single setting is sufficient if, for
instance, each terminal server user is to be shown the Output Gateway print dialogue
in the same language as her or his Windows desktop.
If, however, individual users are to be assigned a different language, the following
value must be set – within the sessions – to one of the Language abbreviations in the
table below:
© ThinPrint GmbH 2015
hkey_current_user\software\ThinPrint\Lang
Chinese, traditional (CHT)
Greek (ELL)
Portuguese (PTG)
Chinese, simplified (CHS)
Hungarian (HUN)
Russian (RUS)
Czech (CSY)
Italian (ITA)
Spanish (ESN)
English, United States (ENU)
Japanese (JPN)
Swedish (SVE)
French (FRA)
Korean (KOR)
Thai (THA)
German (DEU)
Polish (PLK)
ThinPrint Engine on terminal servers.fm
Manual
57
Configuring ThinPrint
Illus. 66
Illus. 66
Output Gateway’s localization (examples for JPN and ELL)
PostScript version of ThinPrint Output Gateway
With ThinPrint Client Mac the properties of native printer drivers can be transferred
from the Mac to the mapped printers in a XenApp session. When configuring ThinPrint Engine carry out the following:
– When configuring AutoConnect, enter the following line into Dynamic Printer
Matrix, in order to map printers without templates (Illus. 67):
TPPS!ThinPort:
Illus. 67
58
Dynamic Printer Matrix: one additional line for the creation of the Mac printers
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Illus. 67
Configuring ThinPrint
Legend:
Column x
Column I
TPPS
!
ThinPort:
connected
applies to Mac OS X clients (and other operating systems)
applies only for the ICA protocol
the PostScript driver TP Output Gateway PS
separator
name of the ThinPrint Port with which the session printers are to be
(one line is needed per ThinPrint Port)
The PostScript driver TP Output Gateway PS (see TPPS in the TARGET column of
Illus. 67) enables AutoConnect to transfer the driver properties from the Mac to the
session printers (Illus. 68).
Illus. 68
Illus. 68
Session printers with TP OUTPUT GATEWAY PS as a printer driver (example)
Encrypting print data
The ThinPrint Engine has been extended to include SSL/TLS encryption for printing,
which ensures a secure connection between the ThinPrint Engine and the ThinPrint
Client. Using SSL encryption requires the following types of certificates to be imported:
– one “personal” server certificate and one root certificate on each server with
ThinPrint Engine
– one “personal” client certificate on each client for sending encrypted print jobs
SSL certificates can be ordered at a certification authority or can be created by yourself (see the technical description Creating SSL certificates for printing with ThinPrint).
Using the root certificate the ThinPrint Engine checks the certificates received
from the clients. It checks whether the respective client is authorized to receive print
data. SSL encryption is also available for use with the Connection Service.
Importing SSL certificates on the servers
© ThinPrint GmbH 2015
Install your SSL certificates on the servers as follows:
1. Log on as a member of the ADMINISTRATORS group and open the Microsoft
Management Console from the Command Prompt with:
mmc
ThinPrint Engine on terminal servers.fm
Manual
59
Configuring ThinPrint
2. In the MMC, select:
FILE→ ADD/REMOVE SNAP-IN→ CERTIFICATES→ ADD→ SERVICE ACCOUNT→
NEXT—→ LOCAL COMPUTER→ NEXT→ PRINT SPOOLER→ FINISH
3. Select immediately thereafter:
ADD→ COMPUTER ACCOUNT→ NEXT→ LOCAL COMPUTER→ FINISH→ CLOSE
4. Lastly, click OK (Illus. 69).
Illus. 69
Illus. 69
Adding snap-ins for SSL certificates to the MMC
5. Import the certificate(s) to the two places shown in Illus. 70 (see arrows). To
do so, select each time ALL TASKS→ IMPORT in the context menu and then
NEXT→ BROWSE→ OPEN→ NEXT→ (PASSWORD→ NEXT)10→ PLACE ALL CERTIFICATES IN THE FOLLOWING STORE→ NEXT→ FINISH→ OK.
The branch CERTIFICATES will be created automatically, if necessary.
The “personal” server certificate will be imported under CERTIFICATES – SERVICE
(PRINT SPOOLER) ON LOCAL COMPUTER→ SPOOLER\PERSONAL and the root certificate under CERTIFICATES (LOCAL COMPUTER)→ TRUSTED ROOT CERTIFICATION
AUTHORITIES.
60
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
10 Please note that the server certificate is a password-protected .pfx file with a private key. For the
root certificate however, a .cer file (without a key and password) must be imported.
Configuring ThinPrint
Illus. 70
Illus. 70
Importing two SSL certificates to the server
Two examples for imported certificates can be found in Illus. 71 and 72.
Illus. 71
Illus. 71
First SSL certificate imported on the server (example for server certificate)
Illus. 72
Second SSL certificate imported on the server (example for root certificate)
© ThinPrint GmbH 2015
Illus. 72
ThinPrint Engine on terminal servers.fm
Manual
61
Configuring ThinPrint
Selecting
certificates
6. For using the imported SSL certificates with the ThinPrint Engine open the ThinPrint Port configuration.
7. Select ENCRYPTION SETTINGS in the PORT MANAGER context menu (Illus. 73).
Illus. 73
Illus. 73
Selecting ENCRYPTION SETTINGS
8. Enter the names of server and root certificates under ENCRYPTION CERTIFICATES
(Illus. 74). Use the names that are displayed in the column ISSUED TO of the
MMC’s certificate overview (in Illus. 71 and Illus. 72 Company ABC and Company ABC-CA as examples).
Illus. 74
Illus. 74
Entering imported SSL certificates (example)
9. Fill in both fields and check that each certificate is installed on the server
(Page 59) and that the certificates installed on the clients are trusted by the server certificates (see below). Otherwise, print jobs will not be executed.
Enabling
encryption
SSL encryption is enabled per ThinPrint Port in the Port Configuration (Illus. 75).
© ThinPrint GmbH 2015
62
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Illus. 75
Illus. 75
Enabling encryption in the port configuration
Importing SSL certificates on the clients
For client-side installation of SSL certificates, please consult the relevant ThinPrint
Client manuals. In the following, installation is described with the example of the
ThinPrint Client Windows.
© ThinPrint GmbH 2015
1. To install a client certificate, select the following in the MMC on the client workstation:
FILE→ ADD/REMOVE SNAP-IN→ CERTIFICATES→ ADD→ COMPUTER
ACCOUNT11→ LOCAL COMPUTER→ FINISH→ OK
2. Now import the certificate by selecting ALL TASKS→ IMPORT in the context menu
(Illus. 76) and then
NEXT→ BROWSE→ OPEN→ NEXT→ PASSWORD→ NEXT→ PLACE ALL
CERTIFICATES IN THE FOLLOWING STORE→ NEXT→ FINISH→ OK
11 If only one person uses the machine, at this point add instead MY USER ACCOUNT. Via CURRENT
USER→ PERSONAL, import the certificate to their user store. The client certificate is thereby linked to the current user.
ThinPrint Engine on terminal servers.fm
Manual
63
Configuring ThinPrint
Illus. 76
Illus. 76
Starting import of an SSL certificate on a client machine
The result is shown in Illus. 77.
Illus. 77
Illus. 77
Registry entry
CertName
SSL certificate imported to a client machine
Before sending encrypted print data, the server checks whether the name of the
imported certificate is included in the CertName entry in the client computer’s
Windows Registry and whether the stored certificate is present on the client machine.
The CertName entry in the Registry must be entered manually as follows:
1. After the certificate has been imported, create the following Registry value on
the client machines with REGEDIT (Illus. 78; data type: REG_SZ):
hkey_local_machine\software\thinprint\client\CertName
© ThinPrint GmbH 2015
64
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Illus. 78
Illus. 78
Registry entry for SSL encryption on Windows clients (example for certificate
Company ABC)
2. Enter as value the name of the imported certificate as displayed in the column
ISSUED TO of the MMC’s certificate overview (Company ABC as example in Illus.
77 and 78).
3. Restart ThinPrint Client Windows (application or Windows service).
The CertName Registry entry is only needed for encrypting print data; receipt of
unencrypted print data is still possible.
AutoConnect
With AutoConnect it's possible to create printer objects automatically using templates on a terminal server (Illus. 79). It is installed as a Windows service.
AutoConnect is supplied with the ThinPrint Engine.
AutoConnect can also be configured as a group policy (GPO). This is described in
detail in the ThinPrint Engine on print servers manual.
© ThinPrint GmbH 2015
AutoConnect features
• Dynamic creation of printer objects in a terminal session, based on various criteria, e.g.:
• Active Directory user or group name
• Printer name
• Client (or host) name
• Client IP address
• Two methods for AutoConnect configuration:
• Using an MMC snap-in (recommended for single terminal servers)
• Using a Group Policy Object (recommended for large environments)
• Support of Output Gateway
• Support of Connection Service
ThinPrint Engine on terminal servers.fm
Manual
65
Configuring ThinPrint
Basic constellation
• ThinPrint Engine on a terminal server as well as AutoConnect and Output Gateway
• ThinPrint Clients on workstations and/or local print servers and/or gateway
appliances
Illus. 79
Illus. 79
AutoConnect – configuration with terminal servers
Templates and ports
Printers generated with templates by AutoConnect on the server are always installed
on the same ThinPrint Port as the template. If printers are to print over several Ports,
multiple templates for the same driver can be set up on various Ports.
Template permissions
So that each user only sees his/her printers – and not all printers installed on the
server –, templates must be assigned the following permissions:
Administrators
Print, Manage documents and Printers
System
Print, Manage documents and Printers
if applicable:
All Application Packages
Print and Manage documents
– Delete all permissions of other accounts.
Note! Templates must not be shared.
66
Port pooling on ThinPrint Ports can also be used with AutoConnect; see Page 45.
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Port pooling
Configuring ThinPrint
AutoConnect configuration
You can configure AutoConnect locally as well as remotely; for remote configuration
AutoConnect must be installed on both machines.
1. Open the ThinPrint configuration. Select on the left AUTOCONNECT (Illus. 80).
Illus. 80
Open AutoConnect configuration
© ThinPrint GmbH 2015
Illus. 80
ThinPrint Engine on terminal servers.fm
Manual
67
Configuring ThinPrint
Configuration
– Click on EDIT SETTINGS (Illus. 80) will open the AutoConnect configuration
(Illus. 81).
Illus. 81
Illus. 81
AutoConnect configuration: GENERAL tab
Settings
General
In GENERAL tab (Illus. 81) the default value for the connection protocol between AutoConnect and ThinPrint Clients can be selected. If you select TCP/IP or VIRTUAL CHANNEL (ICA OR RDP), you restrict the communication to a protocol family. The AUTO setting allows both protocol families and is therefore recommended for ICA/RDP as well
as TCP/IP ThinPrint Ports. In the Dynamic Printer Matrix (see below) you can limit
this setting per rule; here, the columns T, R and I correspond to the protocols TCP/IP,
RDP and ICA.
Note! The protocols (TCP/IP, RDP or ICA) of AutoConnect, ThinPrint Client
and of the ThinPrint Port the template is connected with must match. See also
the ThinPrint Client manuals.
Furthermore you can decide here, which events AutoConnect are to be logged and
displayed in the AUTOCONNECT DIAGNOSTICS table (Illus. 80).
In PRINTER CREATION tab you can decide, when the printers are to be created or mapped:
• Either at each session logon / logoff
• Or when disconnecting and reconnecting a session (Illus. 82).
Restart the TP AUTOCONNECT SERVICE afterwards.
68
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Printer Creation
Configuring ThinPrint
In case you use only the Map Additional Printers table for connecting printer shares
you can speed up AutoConnect using the option DISABLE DYNAMIC PRINTER MATRIX.
Illus. 82
Illus. 82
Default Printer
AutoConnect configuration: PRINTER CREATION tab
Using the settings in the DEFAULT PRINTER tab (Illus. 83) you can set whether the session’s default printer should be changed and – if yes – which information is to be used
to change it:
© ThinPrint GmbH 2015
• either the CURRENT PRINTER of the relevant THINPRINT CLIENT (in case of using
Dynamic Printer Matrix)
• or the DEFAULT column of MAP ADDITIONAL PRINTER (Illus. 94)
• or the last CHOICE by the users in the session (connections to printer shares only)
ThinPrint Engine on terminal servers.fm
Manual
69
Configuring ThinPrint
Illus. 83
Illus. 83
Printers
AutoConnect configuration: DEFAULT PRINTER tab
In PRINTERS tab (Illus. 84) you can set the user rights for the printers to be created:
PRINT, MANAGE DOCUMENTS (default) or PRINT, MANAGE PRINTERS AND DOCUMENTS.
The permission MANAGE DOCUMENTS allows, among other things, “hanging” print jobs
to be deleted. MANAGE PRINTERS allows, among other things, printers to be deleted.
Under PRINTER NAME CONTAINS THE PREFERENCE, specify whether the printer names
to be created should include the CLIENT NAME (= computer name) or the CLIENT IP
ADDRESS. If the client name cannot be detected, the client IP address is automatically
entered (TCP/IP only).
Furthermore you can decide which properties of a local installed printer or driver
are to be transferred to the session printer’s properties:
• The COMMENTS and LOCATION columns of the local printers folder
• The native printer driver’s properties PAPER SIZE, COLOR, PAPER SOURCE, PRINT
ON BOTH SIDES, PRINT QUALITY and FINISHING options.
– Click APPLY or OK to confirm your settings.
© ThinPrint GmbH 2015
70
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Illus. 84
Illus. 84
AutoConnect configuration: PRINTERS tab
Dynamic Printer Matrix
With Dynamic Printer Matrix, you can specify which templates should be used for
creating a session printer.
– Select the DYNAMIC PRINTER MATRIX in the console tree (Illus. 85).
Illus. 85
Illus. 85
© ThinPrint GmbH 2015
Configuration
Dynamic Printer Matrix
– Double-clicking in the table (Illus. 85) will open the configuration console of
Dynamic Printer Matrix (Illus. 86). Use the Buttons (upper arrow) to edit the
table.
ThinPrint Engine on terminal servers.fm
Manual
71
Configuring ThinPrint
Illus. 86
Illus. 86
Assigning
templates
Editing Dynamic Printer Matrix
Dynamic Printer Matrix assigns any printer to a specific template. For example, the
_#ICA_32 template is assigned to the HP DeskJet printer in Illus. 87, and for a certain IP range is given the _#ThinPrint Output Gateway template.
All printer and class names listed in the ThinPrint Client can be translated, including printers which are connected to a shared printer (on a local print server); e.g.,
the printer Alps MD-1000 (last entry in Illus. 87).
Illus. 87
Illus. 87
Table functions
Dynamic Printer Matrix entries (example)
You have the option of hiding unneeded columns (Illus. 88). In all cases, hidden
columns (and their rules) are deactivated.
© ThinPrint GmbH 2015
72
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Illus. 88
Illus. 88
Hiding columns
In the Target column you can either specify a UNC path to a shared printer or select
one of the following options (Illus. 89):
• FIND PRINTER SHARES (allows the search of printers listed in the Active Directory)
• DO NOT CREATE CORRESPONDING PRINTERS (excludes printer shares from mapping
which will be found using the given criteria – e.g. all PDF writers, see the entry
*PDF* in the PRINTER NAME column in Illus. 89)
Illus. 89
Illus. 89
© ThinPrint GmbH 2015
Functional
principle
Target column options
When you start a terminal session or reconnect to an existing session, AutoConnect
is activated automatically. Then it processes the table from top to bottom, for each
printer activated in ThinPrint Client, (Illus. 15). If all criteria (columns) in one line are
met for the first printer AutoConnect searches for the template specified in the
column TARGET (without _#) and creates the session printer using the applicable template properties. AutoConnect now stops the search for this printer in the table and,
if applicable, continues the same procedure for the next activated printer in ThinPrint
Client etc. etc. You can change AutoConnect’s processing sequence by switching the
line order using the arrow keys (
). You can also add or delete lines. (For the two
gray lines refer to Page 75.)
The table has the following columns/translation rules: IP RANGE, CLIENT NAME,
DRIVER NAME, PRINTER NAME, CLASS NAME, CLIENT TYPE and USER /GROUP; here, * and
ThinPrint Engine on terminal servers.fm
Manual
73
Configuring ThinPrint
? can be used as wild cards. The TARGET column represents the template name
(without _#).
These features are explained in the scenarios below; the scenarios can also be
combined with each other.
Scenario: Remote offices and home users with various connections.
Illus. 90
Illus. 90
Connections with different bandwidths require different bandwidth limits
(ThinPrint components not shown here)
Each type of connection uses a different IP address range (Illus. 90). Different bandwidths, print protocols, and parameters can be assigned to each of them.
IP range
The IP RANGE column in the Dynamic Printer Matrix could contain, for example, the
following entries:
192.168.1.136
192.168.1.1–192.168.1.150
192.168.1.0/24
192.168.128.0/22
192.0.0.0/8
A separate template is given as each target; printers with different properties will thus
be mapped in the respective terminal session.
The default entry in IP RANGE is: 0.0.0.0–255.255.255.255
The “24” represents the following subnet mask: 255.255.255.0; i.e., 3x8=24
set bits (22 is equivalent to 255.255.252.0; 16 is equivalent to 255.255.0.0; and
8 is equivalent to 255.0.0.0).
© ThinPrint GmbH 2015
74
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Scenario: Native Printing or Driver Free Printing.
Illus. 91
Illus. 91
Windows clients can use Driver Free Printing, all other print with a native driver (ThinPrint components not shown here)
All Windows clients are to use Driver Free Printing; i.e., to print with the ThinPrint
Output Gateway virtual printer driver. The client type “W” is therefore selected for
them. All other clients are to use one or more native printer driver (Illus. 91).
Client type
User/Group
On the one hand you can select between the client platforms Windows (W), Unix or
Linux (U), Java (J) as well as Mac OS and other (X), and on the other hand between
the connection protocols TCP/IP (T), RDP (R) and ICA (I); see also Page 68. By
default, all client types are selected. If specific translation rules are only to apply to
selected client types, then, they are easily selected by simply adding or removing a
checkmark. In the following table, as an example, the “_#ThinPrint Output Gateway”
template is assigned to all Windows clients. All other client types use the “_#HPLaser” template, which uses a native printer driver.
W
U
J
X
T
R
I
Target
√
–
–
–
√
√
√
ThinPrint Output Gateway
–
√
√
√
√
√
√
HPLaser
The USER /GROUP column in the Dynamic Printer Matrix could contain names of local
or domain users or groups.
Try client printer name or client class name.
There are two special lines in Dynamic Printer Matrix:
© ThinPrint GmbH 2015
TRY CLIENT PRINTER NAME and
TRY CLIENT CLASS NAME
Unlike the other lines, these two lines do not include line subdivisions. These lines
mean that AutoConnect is trying to find a suitable template for the printer names or
the class names on the client machine.
As mentioned above in the paragraph “Dynamic Printer Matrix”: If a (gray) special
line (TRY CLIENT PRINTER NAME or TRY CLIENT CLASS NAME) is found for which a template
ThinPrint Engine on terminal servers.fm
Manual
75
Configuring ThinPrint
exists, the relevant printer is created and no further lines underneath in the table are
searched through. If, on the other hand, matches for all columns (except TARGET) are
found a white (editable) line, a printer is created according to the entry under TARGET.
In this case, too, the lower lines will not be checked. Priority is set by the order of the
lines in the table.
Illus. 92
Illus. 92
Special lines: try client printer name/try client class name
In the example in Illus. 92, the special line TRY CLIENT PRINTER NAME is used as the
first line. In this case, AutoConnect first checks whether a template
(_#HP LaserJet 4) exists for the printer name to be mapped (e.g., for
HP LaserJet 4). If so, a client printer is created using this template (see also
Page 66).
The special line TRY CLIENT CLASS NAME is used as the third line. In this case, AutoConnect checks whether a class (e.g., HPLaser) has been defined in the ThinPrint
Client Manager for the printer name to be mapped. If there is a template
(_#HPLaser) for this class, a printer is created in the session using this template.
Variables
Variables can also be used in the column TARGET, however, they are restricted to
connections to printer shares. Refer to the ThinPrint Engine on print servers manual.
Script control
If you want to run AutoConnect from the Command Prompt (see Page 25) or using a
script, amongst other the following parameters can be used:
Function
-v
(Verbose) Display messages; give detailed information at
startup
-d
Delete the printer(s) for a specific session
-dl
Delete only local printers (on terminal servers)
-dn
Delete only connections to printer shares
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
76
Parameter
Configuring ThinPrint
Parameter
Function
-d session_ID
Delete all printer(s) of a specific session (admins only). The
session ID can be found in the printers folder under LOCATION
(Illus. 25 and 26)
-d all
Delete all printers created with templates (admins only)
-q
(Quiet) Error messages are not sent to the client machine’s
desktop
-r
(Repair) Compares saved session information at actually
existing printer objects (admins only)
-F x
Keep AutoConnect running and restart every x seconds
-p port
(Port) TCP/IP port number (if other than port 4000)
Note: The TCP port numbers in ThinPrint Port, AutoConnect,
and ThinPrint Client must match.
-i protocol
(Interconnection) Select protocol for connection to the ThinPrint Clients; overwrites AutoConnect dialog settings (acceptable values: TCPIP, VC, AUTO); see Illus. 81)
-a address
Specification of IP address or client name of the computer on
which a ThinPrint Client is running – i.e., of local print servers or external print servers of network printers (e.g., from
SEH).
-L
Display ThinPrint Client’s printer list
-I printer ID
Specification of selected printer IDs from ThinPrint Client –
comma separated
-I d
Map only ThinPrint Client’s CURRENT PRINTER
-? or -h
(Help) Will open parameter help panel
Script control also works for network printer objects which are created with the Dynamic Printer Matrix.
© ThinPrint GmbH 2015
Using logon / logoff
script
Running AutoConnect script-controlled or from the Command Prompt (in script
mode):
– Enter the AutoConnect cue in a terminal server logon script.
Example for mapping of printers from a local print server or gateway appliance
(192.168.10.20, ThinPrint Client installed) in C:\Program Files\Common
Files\ThinPrint\:
tpautoconnect –d
tpautoconnect -a 192.168.10.20
ThinPrint Engine on terminal servers.fm
Manual
77
Configuring ThinPrint
Map additional printers
Illus. 93
Illus. 93
Open Map Additional Printers
Both scenarios in Illus. 90 and 91 require a ThinPrint client on the client side. However, if there is no ThinPrint Client on the target computer, any number of network printers can be added with the MAP ADDITIONAL PRINTERS function in the AutoConnect
configuration (Illus. 93):
Default
User /
Group
IP Range
Client
Name
Target
*
*
*
*
\\cps47\Lexmark
Please enter the domain in USER/GROUP (see Illus. 94). The following syntax
applies12:
\\domain\user(group)
Unlike it’s operation under the Dynamic Printer Matrix, when AutoConnect works in
MAP ADDITIONAL PRINTERS, it always works through all lines of the table from top to
bottom and installs the same number of printers in one terminal session as the number of lines existing in the table. If a share entered under TARGET belongs to a printer
that is connected to a ThinPrint Port, the resulting (= created by AutoConnect) printers print with ThinPrint; if not, then without.
For the function of DEFAULT column see Page 69.
78
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
12 You can also enter “\\\user(group)” if users belong to the same domain as the machine on
which AutoConnect is running (three backslashes because the domain name is not given).
Configuring ThinPrint
Illus. 94
Illus. 94
Edit Map Additional Printers and export configuration
Send, export and import the configuration
Similar to the port configuration, AutoConnect also has the additional options of SEND
CONFIGURATION, EXPORT, and IMPORT (Illus. 80 and 94). When sending, the entire
AutoConnect configuration is sent to other computers; with export/import, only the
Dynamic Printer Matrix or Map Additional Printers tables is sent.
© ThinPrint GmbH 2015
Caution! With Send and Import, an existing AutoConnect configuration will
be overwritten. Ensure you save the existing configuration beforehand with the
export function.
Send configuration
The SEND CONFIGURATION function lets data from the AutoConnect configuration be
sent to groups of servers; see also Procedure when sending (Page 39).
Export/Import
The EXPORT function (Illus. 94) lets the contents of the tables Dynamic Printer Matrix
and Map Additional Printers be written in a .csv file 13 (Illus. 95) and thus opened in
other programs, such as Microsoft Excel. Regardless of whether changes are made
thereby, the current status can be applied to the Dynamic Printer Matrix on any server
using the IMPORT function.
13 A .csv file is a text file for saving or exchanging simply structured data. The extension “csv”
stands for Character Separated Values or Comma Separated Values, because the individual
values are separated by a special character (here: semicolon).
ThinPrint Engine on terminal servers.fm
Manual
79
Configuring ThinPrint
Illus. 95
Illus. 95
Saving data in a .csv file
Once you are finished configuring AutoConnect, click APPLY or OK.
Cloud printing
Overview of Cloud Printing
With the Cloud Printing option you can both send print data to mobile devices (iOS,
Android or BlackBerry) and forward print jobs via these devices to network printers.
In this way, the print jobs can be rendered selectively in a Private Cloud (Illus. 96) or
in a Public Cloud (Illus. 97). In detail, there are the following print options:
• Print to Cloud Printer
Sending print jobs from a workstation or a remote desktop session to a smartphone or tablet. The mobile device can print the print job later on in a different
location (see below Printing to the mobile device or to network printers). Alternatively the print jobs can be sent directly to network printers.
• Print to ePaper
Sending files as PDF from a workstation or a remote desktop session to a smartphone or tablet (Page 82).
• Print to Instant Printer
scheduled for printing using laptops on which printer drivers cannot be installed
or – for security reasons – are not allowed to be installed
Printing to the
mobile device or to
network printers
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
80
Tablet or smartphone users can send print jobs from a remote desktop or workstation
session either to the Cortado app on their smartphone or tablet – to print them later,
on a printer accessible via Wi-Fi – or directly to a network printer. To do so, either the
Cortado Corporate Server enterprise solution (Illus. 96) or Cortado Workplace
/Teamplace in conjunction with the Cortado app on the smartphone or tablet is used
(Illus. 97).
Configuring ThinPrint
Illus. 96
Illus. 96
Cloud Printing with terminal servers and Cortado server
Illus. 97
Cloud Printing with terminal servers and Cortado Workplace/Teamplace
Illus. 97
Tablet or smartphone users can send print jobs from a desktop session directly to any
printer connected to a Mac or Windows workstation – also outside the corporate network. To do so, they need the Cloud Printer Connector on the Mac/PC to which the
printer is connected (Illus. 97).
If the users are to be able to print directly from the tablet or smartphone too they
must install the Cloud Printer app on their mobile device additionally. More information about ThinPrint Cloud Printer can be found here:
http://cloudprinter.thinprint.com/en-us/getstarted.aspx
© ThinPrint GmbH 2015
Printing to workstation printers
ThinPrint Engine on terminal servers.fm
Manual
81
Configuring ThinPrint
Setup
On Cloud Printing, the ThinPrint Engine installer creates the port monitor type
ThinPrint PrintToCloud (Illus. 98).
Illus. 98
Illus. 98
Creating a ThinPrint PrintToCloud port
ThinPrint PrintToCloud ports offer the following options (Illus. 99):
•
•
•
•
•
Cortado Workplace/Teamplace (= Public Cloud)
Cortado Corporate Server (= Private Cloud)
Print to Cloud Printer
Print to ePaper
Print to Instant Printer 14
If the option PRINT TO CLOUD PRINTER was chosen the users can access the sent print
data as .tpf files 15 using their Cortado app (Illus. 103). (These .tpf files cannot be
opened on the mobile device. They can only be forwarded to a printer.) With PRINT
TO EPAPER option a PDF is created instead and also sent to the Cortado app.
The optional Cloud Printer ID is provided for the use of network printers with an
integrated Cloud Printer Connector (Illus. 97). This field remains empty with the use
of Cortado app.
15
82
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
14 scheduled for printing using laptops on which printer drivers cannot be installed or – for security
reasons – are not allowed to be installed
Configuring ThinPrint
Illus. 99
Illus. 99
Default settings
on the server
© ThinPrint GmbH 2015
Self-signed
SSL certificates?
Cloud Printing options
– In case of using Cortado Teamplace (Illus. 97) you only must select between
PRINT TO CLOUD PRINTER and PRINT TO EPAPER (Illus. 99).
– In case of using Cortado Corporate Server (Illus. 96), select this instead. Enter
the URL of the Cortado server as follows:
https://<server_address>:<tcp_port>/cgi-bin/send/
Example: https://192.168.149.78/cgi-bin/send/ 16
– In each case, choose the ThinPrint Output Gateway as the printer driver.
In case of using Cortado Corporate Server (Illus. 96) with self-signed certificates
pleas note: The connection to the Cortado server using ThinPrint PrintToCloud ports
(see above) happens SSL-encrypted (via https). Therefore, you must import the root
certificate of the Cortado server – without key – to the server running the ThinPrint
Engine. This is only necessary when you use self-signed certificates.
You can find the Cortado root certificate on the Cortado server in the MMC in the
container CONSOLE ROOT→ CERTIFICATES (LOCAL COMPUTER)→ TRUSTED ROOT CERTIFICATION AUTHORITIES→ CERTIFICATES (Illus. 100). Import it to the same location on
the terminal server.
16 Note that the address notation must match the one given in Cortado server’s SSL certificate:
IP address, hostname or FQDN.
ThinPrint Engine on terminal servers.fm
Manual
83
Configuring ThinPrint
Illus. 100
Illus. 100 MMC Cortado server: Export Cortado root certificate
User settings
Within a desktop session, users have the option with the Print to Cloud Printer function to print jobs to a Cortado Teamplace client installed on a smartphone (or tablet).
With the Cortado app, you can print at a later time in another location.
To be able to send the print jobs to the – right – printers of your users the users
must register themselves before:
https://cloudcentral.cortado.com/?action=register&app=cloudprinterwebapp
Here, they can use any – e.g. private – e-mail account. This e-mail account represents their Cortado ID (= credential for the Cortado Teamplace account).
The users must then install the Cortado app on their smartphone or tablet. More
information on the installation and use of Cortado Teamplace can be found here:
https://www.teamplace.net/en-us/
and of Cortado Corporate Server here:
https://corporateserver.cortado.com/en-us/overview.aspx
Additionally, users should first open the printers folder on their desktop session and
then access the context menu by right-clicking on the cloud printer. In case of using
the public cloud the users’ Cortado Teamplace access credentials can then be saved
in the CORTADO ID tab (Illus. 101, right) under PRINTER PROPERTIES→ PREFERENCES
(Illus. 101, left). So it isn’t necessary to enter them at each time.
Otherwise – when Cortado Corporate Server (= private cloud) is used – no entry
is needed here. See also the Cortado Corporate Server manuals.
© ThinPrint GmbH 2015
84
Manual
ThinPrint Engine on terminal servers.fm
Configuring ThinPrint
Illus. 101
Illus. 101 Entering Cloud Printing credentials
Printing
For printing the Cortado app is only necessary if the Cloud Printer Connector isn’t
used because this transmits the print jobs immediately to the physical printer configured there.
To be able to open or print files using the Cortado app a print job must be sent from
a desktop session to a Cloud Printer (Illus. 102).
© ThinPrint GmbH 2015
Illus. 102
Illus. 102 Selecting the Cloud Printer
ThinPrint Engine on terminal servers.fm
Manual
85
Configuring ThinPrint
If the used printer object is set to the Print to Cloud Printer option the sent print data
will be stored in EMF data format (*.tpf file) in the Cortado app’s PRINT JOBS folder
which is accessible from the user's smartphone or tablet (Illus. 103). If required, it
can then be printed using the print function of the Cortado app.
If the used printer object is set to the Print to ePaper option the data will be converted to the PDF format and will appear in the Cortado app’s EPAPER folder. Here,
they can then be both read and printed.
Illus. 103
Illus. 103 Print Jobs and ePaper folders in the Cortado app (example for iOS)
© ThinPrint GmbH 2015
86
Manual
ThinPrint Engine on terminal servers.fm
Appendix
Appendix
Customer service and technical support
www.thinprint.com/→ RESOURCES & SUPPORT
www.thinprint.com/en-us/resourcessupport/supportrequest.aspx
Server roles and custom setup
Selecting a server role (Illus. 104) leads to the installation options listed below:
Illus. 104
© ThinPrint GmbH 2015
Illus. 104 Select a server role or the CUSTOM SETUP
Server role
Installation options
TERMINAL SERVER
Print Controller (= ThinPrint Engine) incl. Tracking
Service, Cloud Printing, Output Gateway, Output
Gateway PS, AutoConnect, Virtual Channel Gateway, Session in Session, Administration Tools
(= MMC components) and Client for License Server
PRINT SERVER
Print Controller incl. Tracking Service, Cloud Printing, Output Gateway, AutoConnect, Administration Tools and Client for License Server
TERMINAL SERVER
EXTENSION
Output Gateway, Session-in-Session, AutoConnect
and Virtual Channel Gateway
ADMINISTRATION
TOOLS
MMC components only
CUSTOM SETUP
Free choice of component
ThinPrint Engine on terminal servers.fm
Manual
87
Appendix
Custom Installation
Here you can specifically select and install individual ThinPrint components
(Illus. 105). The following components can be selected:
• Print Controller (= ThinPrint Engine)
• Tracking Service, see Page 29
• V-Layer Service, see ThinPrint Engine on print servers manual
• Cloud printing, see Page 80
• Cloud Printer
• Print-to-ePaper
• ThinPrint Output Gateway, see Page 48
• ThinPrint Output Gateway PS (native driver for printing to non-Windows clients)
• AutoConnect, see Page 65
• Virtual Channel Gateway, see ThinPrint Engine on print servers manual
• Session-in-Session, see Page 88
• Administration Tools (ThinPrint MMC component to remotely configure – from
this computer – another one with ThinPrint components installed on it, can be
installed both on workstations and servers)
• License Manager (License Server component for managing the license keys)
• Client for License Server (component for connecting the Print Controllers to the
License Server)
Illus. 105
Illus. 105 CUSTOM SETUP options
Session-in-Session
88
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
This feature makes it possible for client or network printers to be still available in a
session, even when a further session is opened from within an existing one, or if you
– from this (first) session – access a server or a virtual desktop that is already running
a Published Application (Illus. 106). Thereby, printers are mapped into the second
session and print jobs are “passed on” from the second to the first server or desktop.
Appendix
Illus. 106
Illus. 106 Session-in-Session: Open a further session from within an existing session
Installation,
licensing and
configuration
You need a ThinPrint Engine on the machine on which the (second) session is running
(right computer in Illus. 106) – that means a ThinPrint Engine on a terminal server.
A ThinPrint Client is installed on the client machine (here: a laptop), and an ICA or
RDP client must be running.
The Session-in-Session component is installed on the “middle” computer. On terminal servers, this can be selected during the installation procedure via CUSTOM
SETUP (Illus. 104). Select SESSION IN SESSION (arrow in Illus. 107). This feature functions without any further configuration. An ICA or RDP connection is a prerequisite.
Illus. 107
Illus. 107 Custom Installation: Select SESSION
IN
SESSION
© ThinPrint GmbH 2015
Install the Desktop Extension (optional component of ThinPrint Engine) on the
“middle” computer if it’s a virtual desktop.
If you also want to print from the “middle” computer, then you need two ThinPrint
Engines (on the middle and on the right computer in Illus. 106).
ThinPrint Engine on terminal servers.fm
Manual
89
Appendix
Citrix ICA Client
later installed
If you’ve installed a Citrix ICA Client after Session-in-Session, uninstall the Session-in-Session component via custom setup (see Illus. 106), and afterwards
reinstall it. Please also note the section If you still can't print • Checklist on Page 26.
Update and uninstallation
Update from ThinPrint version 9.0 to 10.0 or from 9.0 to 10.6
To update to ThinPrint 10, proceed as follows:
1. Apply for new license keys in the Cortado Enterprise Portal (free of charge for
customers with an update subscription): https://enterpriseportal.cortado.com
2. Install the Cortado License Server on a separate machine. This allows you to
continue working with the old version until the new one is fully functional. Enter
the new (ThinPrint 10) license keys there.
3. Perform an update of the ThinPrint Engine to version 10 and specify the license
server.
4. Delete your old license keys and complete the letter of destruction, which you
then send to ThinPrint or Cortado.
5. Activate your (new) licenses and activate your users/user groups for ThinPrint,
see Activating license keys in the License Server manual.
Note! Make sure that no user sessions run during the ThinPrint Engine
update.
Update from older ThinPrint versions
When you wish to retain your settings, perform the update step by step, e.g. from
8.0 to 8.6, then to 9.0, to 10.0 and last but not least to 10.6.
© ThinPrint GmbH 2015
90
Manual
ThinPrint Engine on terminal servers.fm
Appendix
Uninstallation
To uninstall a ThinPrint component open PROGRAMS AND FEATURES in CONTROL PANEL.
Mark a ThinPrint component and then select UNINSTALL (Illus. 108).
Illus. 108
Illus. 108 Uninstalling ThinPrint Engine
Disabling Windows printer mapping
To simplify the selection of a ThinPrint printer within a session, the Windows automatic printer mapping function could be disabled within and outside of the session.
To do so, configure the following on the terminal server:
By default, ThinPrint automatically creates client printers in every terminal session.
To simplify the selection of a ThinPrint printer within a session, the Windows automatic printer mapping function should be disabled using a policy. This is described
here:
1. On the terminal server, go to ADMINISTRATIVE TOOLS, and open the REMOTE DESKTOP SERVICES folder
© ThinPrint GmbH 2015
Windows Server
2012
ThinPrint Engine on terminal servers.fm
Manual
91
Appendix
2. Select REMOTE DESKTOP GATEWAY MANAGER (Illus. 110)
3. Select CONNECTION AUTHORIZATION POLICIES
4. Click on the policy RDG_CAP_ALLUSERS and go to the DEVICE REDIRECTION tab.
Place a checkmark at PRINTERS while selecting DISABLE DEVICE REDIRECTION FOR
THE FOLLOWING CLIENT DEVICE TYPES (right arrow in Illus. 110).
Illus. 109
Illus. 109 Disable Windows printer mapping using a policy (Windows Server 2012)
Windows Server
2003 and 2008
1. In Windows Control Panel, select ADMINISTRATIVE TOOLS→ SERVER MANAGER→
ROLES→ TERMINAL SERVICES CONFIGURATION (Windows Server 2008) or ADMINISTRATIVE TOOLS→ TERMINAL SERVICES CONFIGURATION (Windows Server 2003).
2. Click on the RDP-TCP connection and select PROPERTIES in the context menu
(Illus. 110).
3. Disable the mapping functions (arrows in Illus. 111). Click OK to confirm.
Illus. 110
4. If available, click on the ICA-TCP connection select PROPERTIES in the context
menu. Disable the mapping functions. Click OK to confirm.
92
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Illus. 110 Opening RDP configuration
Appendix
Illus. 111
Illus. 111 Session settings for printer mapping (Windows Server 2003 and 2008)
Windows Server
2003 only
1. In Windows Explorer, select TOOLS→ FOLDER OPTIONS→ VIEW.
2. Disable the AUTOMATICALLY SEARCH FOR NETWORK FOLDERS AND PRINTERS function
(Illus. 112). Click OK to confirm.
Illus. 112
© ThinPrint GmbH 2015
Illus. 112 Explorer settings for printer mapping (Windows Server 2003)
ThinPrint Engine on terminal servers.fm
Manual
93
Appendix
Windows registry
In the following you can find a selection of possibly relevant entries in the Windows
registry.
ThinPrint Engine: ThinPrint Ports and ThinPrint Connection Service Ports
hkey_local_machine\system\CurrentControlSet\Control\Print\Monitors\ThinPrint Port
\<port name>:
ThinPrint Engine
MMC
Description
Type
Default
value
Bandwidth
BANDWIDTH (KBIT/S
(KBPS))
Bandwidth used to send print
data (in bit/s, bits per second)
reg_dword
256000
BandwidthAccess
CLIENT CONTROL:
BANDWIDTH
Enables the ThinPrint Client
to reduce the bandwidth
0 = disabled; 1 = enabled
reg_dword
0
BandwidthCtrlEnabled
BANDWIDTH CONTROL: ENABLE
Enables bandwidth control
0 = disabled; 1 = enabled
reg_dword
0
CConnTries
CONNECTION RETRIES
Number of attempts to establish a
connection to the ThinPrint Client
or Connection Service
reg_dword
3
CLevel
BANDWIDTH CONTROL: ENABLE +
MINIMUM PRINT DATA
Compression level
0 = no compression
5 = default compression
8 = high compression
(BANDWIDTH CONTROL enabled)
9 = best compression (MINIMUM
PRINT DATA VOLUME enabled)
reg_dword
5
Name
VOLUME
—
Print job handling when ThinPrint
Client doesn’t take them
1 = failed jobs will be deleted
0 = failed jobs will be left in the
printer queue (Queue Manager)
reg_dword
1
Host
—;
CONNECTION SER-
With ThinPrint Ports: ThinPrint
Client address; with ThinPrint
Connection Service Ports:
Connection Service address
reg_sz
—
0 = ThinPrint Engine doesn’t
print to the Connection Service
1 = ThinPrint Engine prints to the
Connection Service
reg_dword
—
VICE ADDRESS
IsCSvcPort
94
NEW THINPRINT
PORT /NEW THINPRINT CONNECTION
SERVICE PORT
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
DeleteErrJobs
Appendix
Name
ThinPrint Engine
MMC
Description
Type
Default
value
NetSend
NET SEND SERVICE
Inform the users about errors?
0 = no
1 = yes
reg_dword
1
Port
TCP PORT
TCP port for communication to
ThinPrint Clients or Connection
Service
reg_dword
4000
SignCert
—
Name of certificate that signed
the client certificate. Overrides
global SignCert setting in
hkey_local_machine\system\currentcontrolset\control\print\monitors\ThinPrint Port\
reg_sz
—
UseEncryption
USE ENCRYPTION
0 = encryption disabled
1 = encryption enabled
reg_dword
0
WTSMsgBox
—
If set to 1 and an error occurred:
A message box will be sent to the
terminal server session which
started the print job.
reg_dword
1
AutoConnect
hkey_local_machine\software\ThinPrint\TPAutoConnect
Name
AutoConnect MMC
Description
Type
Default
value
ConnectToClient
PRINTER NAME CON-
Connection to client with client
name or client address (use: Auto,
ClientName, ClientAddress)
reg_sz
Auto
TAINS PREFERABLY
© ThinPrint GmbH 2015
(PRINTING VIA
TCP/IP)
DPMTries
—
Determines the number of rows
that is to be tried per printer
from Dynamic Printer Matrix
reg_dword
1
DisableSettingOfDefPrinter
AUTOCONNECT HAS
reg_dword
0
NO INFLUENCE
AutoConnect will not set any
default printer
InstallOrder
1, 2: DEFAULT
0
1
2
3
4
reg_dword
1
PRINTER TAKEN FROM
4: DISABLE DYNAMIC
PRINTER MATRIX
ThinPrint Engine on terminal servers.fm
=
=
=
=
=
create/connect no printer
Dynamic Printer Matrix first
Map Additional Printers first
Dynamic Printer Matrix only
Map Additional Printers only
Manual
95
Appendix
Name
AutoConnect MMC
Description
Type
Default
value
ListenToWTS
—
AutoConnect is started automatically on session logon
(Auto mode)
reg_dword
1
ListenToWTSCreatCmd
—
Command that will be launched
on session logon if ListenToWTS
is not 0
reg_sz
tpautoconnect.exe
ListenToWTSDeleteCmd
—
Command that will be launched
on session logoff
reg_sz
tpautoconnect.exe
-dl
ListenToWTSOnDisconnect
AT SESSION RECONNECT/DISCONNECT
Indicates whether printers will be
deleted when a session goes to
the disconnect state
reg_dword
1
NameTranslationEx
DYNAMIC PRINTER
MATRIX
Content of Dynamic Printer Matrix
reg_multi_sz
—
PrinterCreateListEx2
MAP ADDITIONAL
PRINTERS
Content of Map Additional Printers
reg_multi_sz
—
PrinterProperties
INHERIT CLIENT
Indicates whether the printer properties will be retrieved from
ThinPrint Clients
reg_dword
1
PrinterProperty
Flags
PAPER SIZE, PRINT ON
BOTH SIDES, PAPER
SOURCE, COLOR,
PRINT QUALITY, FINISHING, SHOW COM-
Bit 0: paper name and size
Bit 1: printable area
Bit 2: paper trays
Bit 3: print quality
Bit 4: print on both sides
Bit 5: color
Bit 8: punch holes
Bit 9: staple
Bit 10: bind
Bit 11: pages per sheet
reg_multi_sz
0x000ffff
PRINTER SETTINGS
MENTS AND LOCATION
TRANSFER PROTOCOL
Protocol for connections
to ThinPrint Clients (use: TCPIP,
VC, AUTO)
reg_sz
AUTO
UserDrivenDefaultPrinter
DEFAULT PRINTER –
Set to 1 if the selection of the
default printer will be user driven,
so AutoConnect will not interfere
it
reg_dword
0
GIVE PRIORITY TO THE
USER ’S CHOICE
96
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Protocol
Appendix
Additional resources
Further information about ThinPrint can be downloaded from our website.
Manuals and
descriptions
The following manuals and further technical information are – amongst other – available at www.thinprint.com/manuals:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
License Server
ThinPrint Engine on terminal servers • Quick installation
ThinPrint Engine on print servers
ThinPrint Tracking
Connection Service
Unattended installation and licensing of ThinPrint Engine components
Licensing
Solving problems with fonts
Tips for configuring ThinPrint
ThinPrint addressing
ThinPrint Ports
ThinPrint Port configuration for bandwidth controlled printing via LPR/LPD
Creating SSL certificates for printing with ThinPrint
Windows machine as a Client Gateway
SEH ISD as a Client Gateway
SEH TPG as a Client Gateway
Preconfiguration and unattended installation of ThinPrint Client Windows
ThinPrint Client manuals
Thin clients and
gateways
Thin Clients or terminals with embedded ICA/RDP type of ThinPrint Client as well as
ThinPrint gateway appliances can also be found at www.thinprint.com.
Software
downloads
The current version of ThinPrint Engine, can be downloaded at:
www.thinprint.com/demo.
ThinPrint Clients as well as tools like Finishing Detector and ThinPrint Preview
(TPView.exe) can also be found at www.thinprint.com.
© ThinPrint GmbH 2015
Glossary
Activation key
Entering the activation key in License Manager enables unlimited application of the
ThinPrint software. An activation key is obtained by submitting license and registration keys to ThinPrint GmbH.
Autocreated
printers
see ThinPrint AutoConnect
Bandwidth
The capacity of a network or data connection for digital transmission, usually measured in bit/second (bit/s, bits/sec, or bps) or in Kilo-bit/ second (kbit/s, kbits/sec, or
kbps).
Bandwidth control
A ThinPrint Port regulates bandwidth for print jobs. Because bandwidth is controlled
separately per printer port and can be set individually, optimal performance can be
achieved with the following ThinPrint settings:
ThinPrint Engine on terminal servers.fm
Manual
97
Appendix
• Number of ThinPrint Ports
• Different bandwidth settings for each ThinPrint Port
• Assignment of printers to ThinPrint Ports
see Printer Class
Client
The term client signifies a device which connects to, requests data from, and/or starts
an application on, a server. It receives, for example, print data from the server and
forwards it to a printer. Typical clients are: workstations, notebooks, thin clients, print
servers, gateway appliances and network printers.
Client Gateway
see Gateways
Compression
In addition to bandwidth control, ThinPrint compresses print data. Typical compression rates for PCL and Postscript printer drivers lie somewhere between 55% and
95% – depending on printer driver, application, and type of data (e.g.: pixel / vector
fonts, pixel / vector graphics). With Driver Free Printing there are four available compression options (normal, optimal, maximum and extreme; Page 50) Nonetheless,
when printing with either Driver Free Printing or with the native printer driver a higher
or lower compression may be chosen without compromising the print quality (see
Page 34).
Connection Service
ThinPrint Connection Service enables printing to ThinPrint Clients that are hidden
behind Network Address Translation (NAT). But in contrast to ThinPrint Virtual Channel Gateway the print data is sent over pure TCP/IP and not via an ICA or RDP channel.
ThinPrint Engine sends all print jobs to the ThinPrint Connection Service, which
passes them on to the ThinPrint Clients. No IP addresses are used for addressing the
ThinPrint Clients, but a ThinPrint specific Client ID. This Client ID is assigned automatically by the ThinPrint Connection Service (dynamic mode) or is created manually
in the ThinPrint Client (static mode).
Current printer
Setting in the ThinPrint Client Manager: A document is printed with the current printer if a client has only one printer, or if the printer can't be determined by ID. Current
printer can also be used to set the default printer at the server when using AutoConnect (with the option DEFAULT AT SERVER).
Data type
Several types are usually supported for printing under Windows. The two most commonly used – expanded metafile (EMF) and print-ready (RAW) – affect performance
on both client and print server machines differently. See also EMF
Dedicated
print server
A served “dedicated” to a single task: printing. If a terminal server does not send print
data directly to clients, but to central, dedicated print servers, there, it is first rendered and then sent to the clients or printers. The terminal server load is thus lightened. (see also Print server)
Driver Free Printing
Printing using the ThinPrint Output Gateway (see also Page 7)
98
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Class
Appendix
EMF
EMF (enhanced metafile) is default data type for most Windows programs. Unlike
RAW format, printed documents in EMF are converted to metafile format.
With Driver Free Printing, EMF files are smaller than RAW files containing the
same print job. In server-based computing, only the first half of a print job is generated on the terminal server (in consideration of system performance). The main work
is performed by the client machine, which improves the terminal server’s performance. See also Data type.
Gateways
ThinPrint differs between the following kinds of gateways:
© ThinPrint GmbH 2015
1. ThinPrint Output Gateway
ThinPrint’s “virtual“ printer driver for Driver Free Printing
2. ThinPrint Virtual Channel Gateway
With our Virtual Channel Gateway, we actually put print data coming from a
print server into the ICA or RDP virtual channel and send it directly to the client
(see ThinPrint Engine on print servers manual).
3. ThinPrint Client Gateway
Local print server with installed ThinPrint Client
ICA
Independent Computing Architecture (from Citrix); network protocol for communication between Windows terminal servers and ICA clients.
ICA is a 3-part technology for server-based computing which separates application
logic from user interface and allows the application to run entirely on the server. ICA
requires Citrix XenApp on the server; XenApp requires Microsoft Terminal Services.
License key
All ThinPrint software requires a license key. The key has the format:
THxx-xxxx-x-xxxxxx-xxxx (32 bit) or TAxx-xxxx-x-xxxxxx-xxxx (64 bit). License Manager uses the license key to generate a registration key according to system configuration. Both license key and registration key are required to request the activation key.
Local resources
Local in this sense means available to or installed upon the selected computer. Client
operating systems always search first for a local printer driver. When printing on the
client side, then, the printer driver is first sought on the client computer, and only if
necessary is a driver downloaded from the server.
LPD client
An LPD client is a network end device which supports the Line Printer Daemon
(LPD); e.g., a print server (print box), network printer, or Linux terminal. It is also
possible to print with ThinPrint to LPD devices, even if there is no ThinPrint Client
available there. Although compression cannot be used, bandwidth control is available to improve printing in this environment.
LPD filter
An LPD filter is run on LPD clients to decompress print jobs which have been processed over ThinPrint.
LPR
Line Printer Remote; Program for issuing a print job (Client component for LPD)
Network Address
Translation (NAT)
Multiple private addresses are transformed into a single public IP address. This lets
several PCs in a LAN use the IP address for Internet access, while the LAN hides
behind the router's IP address registered in the Internet.
ThinPrint Engine on terminal servers.fm
Manual
99
Appendix
Output Gateway
see Gateways
ThinPrint
AutoConnect
The ThinPrint component for auto-created printers is called AutoConnect. It can be
run on any Windows server. AutoConnect enables the printers needed for each client
to be created automatically on the server.
ThinPrint Client
On the client side, ThinPrint Client is generally responsible for receiving print data,
decompressing and decrypting it, and sending it to the print device. Many ThinPrint
Clients are available for different end devices and areas of deployment: for all
Windows versions, for Mac OS and Linux as well as for internal and external print
servers of network printers.
ThinPrint Client
Gateway
see Gateways
ThinPrint Client
Service Windows
The Windows service version of ThinPrint Client is automatically started when a client machine is activated. Thus, it is not necessary for a user to be logged on for the
Client Service Windows to function. This ThinPrint Client is therefore particularly well
suited for local print servers under Windows (ThinPrint Client Gateways). ThinPrint
Client Service Windows is not designed for print preview with Driver Free Printing.
ThinPrint
Connected Gateway
see Connection Service
ThinPrint
Connection Service
see Connection Service
ThinPrint Engine
The server component ThinPrint Engine is the actual core of the ThinPrint framework.
It provides complete printer driver management including Driver Free Printing. The
ThinPrint Engine performs the following main functions:
•
•
•
•
ThinPrint Preview
ThinPrint component for the client-side print preview with Output Gateway. It consists of the components TPView.dll and TPView.exe with the following features:
TPView.dll
TPView.exe
page preview
X
X
zoom
X
X
leaf
X
X
save in .tpf file format
X
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
100
Bandwidth controlled transmission of print jobs
Print data compression and streaming
Print data SSL/TLS encryption
Provisioning of the virtual printer driver ThinPrint Output Gateway (enables a
radical reduction of printer drivers on printing computers = Driver Free Printing).
Appendix
TPView.dll
open .tpf file format
X
print
X
installation with ThinPrint Client
X
can be downloaded at www.thinprint.com (Page 97)
© ThinPrint GmbH 2015
TPView.exe
X
X
Port pooling
s. Page 45
Print device
Contrary to popular nomenclature, hardware which produces printed material is called a print device and NOT a printer. Print resolution is measured in DPI (Dots Per
Inch). The higher the DPI value, the better the resolution. See also Printer
Printer
The point of interface between operating system and print device is called the printer.
In Windows architecture alone, many possible terms exist: logical printer, printer software, or printer object. Printer settings include, among other, the designation of a
connection (i.e., LPT1 or ThinPort), the printer driver (this is normally included by
the manufacturer), authorization of share names, etc. In Windows, every printer is
represented in the printers folder by an icon with an obvious name.
There is generally not a one-to-one relationship between printer and print devices.
Several printers for a single print device, for example, signify that either the print
device is connected to several computers, or that many printers with different parameters for the same print device have been set up on a computer.
For better understanding, this guide only distinguishes between printers, printer
objects, and print devices when the specific context makes it necessary.
Printer class
Printers whose drivers are compatible can be grouped in a class. For example, many
laser printers are compatible with HP LaserJet (class could be: HPLaser). Only one
AutoConnect template is necessary for all printers in a class.
Printer driver
Printer drivers are programs which enable communication between client applications and print devices. Each print device requires unambiguous commands which
are specific to that device, to employ such print functions as color, margin, format,
etc. An operating system comprehends these individual commands for specific print
devices through the printer driver.
Printer object
Under Windows: a printer created in the printers folder; it appears with its name in
the printers folder.
Printer pool
see Port pooling
Printer queue
The number of documents which are to be printed from a particular print device
and/or are already waiting for processing is referred to in Windows terminology as the
printer queue. Under NetWare and OS/2, the term printer queue is synonymous for
printer.
ThinPrint Engine on terminal servers.fm
Manual
101
Appendix
Print jobs are composed of a source code in the language of the relevant printer. This
source code contains both print data, such as a text or picture, and print device commands such as form feed or page format.
Print server
A print server is hardware which connects print devices with a network. The print
server is thus responsible for the printer queues of connected print devices. A print
server can also be a specific hardware device which exclusively embodies the network connection and a serial or parallel connection (print appliance/external print
server/print box). A print server can also be pre-integrated within a printer, so that
separate hardware is unnecessary and the print device can be directly connected
with the network (internal or onboard print server). (Illus. 1; see also Dedicated print
server)
Print server
services
Print server services is the term for the print server software which handles communication with non-Windows clients. Because a print job from a UNIX client is different
than one from a Macintosh client, there are different print server services. These can
change the parameter for data type as needed, for instance.
Print spooler
see Spooler
RDP
Remote Desktop Protocol; communication protocol between Remote Desktop Session Hosts or virtual desktops and clients under a Windows operating system. The
name of the service is Terminal Services, and the connection type under Windows is
named Remote Desktop Connection.
Remote Desktop
Connection
see RDP
Remote Desktop
Services
see Terminal Services
Remote Desktop
Session Host
see Terminal server
Rendering
A printer driver is used to translate a print job into printer-specific format.
Session-in-Session
When printers are assigned by AutoConnect in a terminal session, they are still available if a further session is configured from a terminal server, onto another machine.
Spooler
Print spooler describes the number of those programs or DLLs (Dynamic Link Libraries) which receive, process, temporarily save, chronologically sort, and distribute
queued print jobs.
With network printers, the spooler has a client component and a server component. The client component is normally found where the application is being run. The
server component is generally where the print device is installed, at the print server,
for example.
Spooling
Simultaneous Peripheral Operation On Line: Print jobs are temporarily stored as files
on a hard disk. This procedure is known as spooling and is only one of the several
102
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
Print job
Appendix
© ThinPrint GmbH 2015
functions of the spooler. Unspooling is the process of reading this file and sending it
to the print device.
SSL
To establish a secure connection with SSL/TLS, the communication partners must
first agree on the cryptographic methods and parameters to be used. Basically,
SSL/TLS offers the options of key exchange, systematic encryption, and the calculation of a cryptographic proof sum. There are various methods that can be used with
each of these options.
Template
Printer object used as a “model” to enable automatic client printer connection to
ThinPrint Engine over AutoConnect.
Terminal server
= Remote Desktop Session Host: a Windows server with Microsoft Terminal Services
or Remote Desktop Services
Terminal Services
= Remote Desktop Services: a Windows service for remote desktop sessions
Thin client
A minimum performance computer with only elementary hardware and/or software
components (no hard drive). In a server/client architecture, a client system on which
no application programs are run. Instead, all applications are processed at the server.
ThinPrint Output
Gateway
see Gateways
ThinPrint Port
To print with ThinPrint, printers are linked to ThinPrint Ports on the machine that creates the print jobs. These printer ports are created and configured with the MMC.17
It is, however, not necessary to create a port for every printer; many printers can be
configured to the same port. With port pooling, however, one or more printers are
connected to several ports.
ThinShare
See ThinPrint Engine on print servers manual
TLS
see SSL
VirtualCopy
See ThinPrint Engine on print servers manual
V-Layer
See ThinPrint Engine on print servers manual
x64
Identifies all 64-bit processors from Advanced Micro Devices (AMD) as well as Intel
processors with an AMD compatible 64-bit extension (e.g. Xeon and Pentium with
EM64T). In contrast ia64 identifies the 64-bit processor Itanium from HP and Intel.
XenApp
Server-based software (Citrix) for Microsoft Terminal Services
17 Recommended: 600 ThinPrint Ports with 800 active printer queues (Windows Server 2003 with
3 GHz Dual Xeon processor, 2 GB RAM, and SCASII ultra3 disk array) or 1500 queues with
Windows Server 2008 R2
ThinPrint Engine on terminal servers.fm
Manual
103
Appendix
Abbreviations and acronyms
Character/Comma Separated Value
DLL
Dynamic Link Library
DNS
Domain Name System
EMF
Enhanced Metafile (see glossary)
GPO
Group Policy Object
ICA
Independent Computing Architecture (see glossary)
ID
Identification (number)
IPv4
Internet Protocol address space with 232 addresses; example: 192.168.1.1
IPv6
Internet Protocol address space with 2128 addresses;
example: 2001:0db8:85a3:08d3:1319:8a2e:0370:7344
LAN
Local Area Network
LPD
Line Printer Daemon (see glossary)
LPR
Line Printer Remote (see glossary)
LPT
Windows Line Printer Port
MMC
Microsoft Management Console
NAT
Network Address Translation
OS
Operating System
OU
Organizational Unit
Output Gateway
ThinPrint Output Gateway
PCL
Printer Command Language
RAW
Standard print data type
RDP
Remote Desktop Protocol (see glossary)
SQL
Structured Query Language
SSL
Secure Socket Layer (see glossary)
TCP/IP
Transport Control Protocol/Internet Protocol
TLS
Transport Layer Security
TP
ThinPrint
TPOG
ThinPrint Output Gateway
UI
User Interface
VC
Virtual Channel (= ICA or RDP)
VCP
Virtual Channel Protocol (= ICA or RDP)
V-Layer
ThinPrint Printer Virtualization Layer
WinCE
Windows CE
WinNT
Windows NT 4, 2000, XP, Vista, 7, 8, 8.1, 2000, 2003, 2008, 2008 R2, 2012,
2012 R2
104
Manual
ThinPrint Engine on terminal servers.fm
© ThinPrint GmbH 2015
CSV