Appl Server Engine en

ThinPrint Application Server Engine
(version 9.0)
Manual
Cortado AG Alt-Moabit 91 a/b 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@team.cortado.com Web: www.thinprint.com Issued: December 4, 2012 (v307)
Notes
Copyright
This document is the intellectual property of Cortado AG. 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 Cortado 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.
Cortado AG 2012
Manual
Contents
Introduction
................................................................................................................ 6
What is ThinPrint? .......................................................................................................... 6 The technology .......................................................................................................... Server components .................................................................................................... Driver Free Printing .................................................................................................... Advanced Adaptive Compression ................................................................................. Client component ...................................................................................................... 6 6 7 7 7
Package contents ........................................................................................................... 7 Licenses ........................................................................................................................ 7 Scenarios ...................................................................................................................... 8 Terminal server(s) Printing via TCP/IP ....................................................................... 8 Terminal server(s) Printing via ICA/RDP .................................................................... 9
Installation
................................................................................................................ 10
Technical requirements ................................................................................................. 10 ThinPrint Engine ...................................................................................................... 10 ThinPrint Client ....................................................................................................... 10 Installing ThinPrint Engine (per terminal server) ............................................................... 11 Installation with installation wizard ............................................................................ 11 New Printers ........................................................................................................... 14 Disabling Windows printer mapping ........................................................................... 15
Sample configuration ............................................................................................ 16

Installing ThinPrint Clients ............................................................................................. 17 Configuring thin client .............................................................................................. 17 Configuring local print server ..................................................................................... 19 client2: RDP type of ThinPrint Client Windows on a PC ............................................... 20 Server configuration ...................................................................................................... 21 ThinPrint Ports ........................................................................................................ 21 Configuring AutoConnect .......................................................................................... 25 Printing ....................................................................................................................... 26 If you still can't print Checklist .................................................................................... 27
Cortado AG 2012
Manual
Contents
Configuring ThinPrint
........................................................................................... 29
Ports ........................................................................................................................... 29 Starting Port Manager .............................................................................................. Configure tab .......................................................................................................... Advanced tab .......................................................................................................... Job Statistics tab ..................................................................................................... Distributing port configuration ................................................................................... 29 32 33 34 35
Creating printers and templates ...................................................................................... 41 Templates ............................................................................................................... 41 Manually created printers ......................................................................................... 42 Port pooling ............................................................................................................ 44 Printing with thin clients ............................................................................................... 45 Preparations on the server ........................................................................................ 46 Preparing ThinPrint Client (example for Windows CE) .................................................. 48 Printing .................................................................................................................. 50 ThinPrint Output Gateway ............................................................................................. 50 Paper formats and trays ........................................................................................... Presettings on the server (administrators only) ............................................................ Settings in a terminal session .................................................................................... Printing with preview ............................................................................................... Finishing options ..................................................................................................... Language versions ................................................................................................... 51 52 55 55 56 57
Cloud Printing .............................................................................................................. 59 Encrypting print jobs ..................................................................................................... 60 Importing SSL certificates on the servers .................................................................... 60 Importing SSL certificates on the clients ..................................................................... 64 Print job tracking .......................................................................................................... 66 Tracking Service ...................................................................................................... 67 Tracking Report Engine ............................................................................................ 67 Preparing ThinPrint Engine and Tracking Service ......................................................... 68 AutoConnect ................................................................................................................ 70 AutoConnect features ............................................................................................... Basic constellation ................................................................................................... Templates and ports ................................................................................................ Template permissions .............................................................................................. AutoConnect configuration ........................................................................................ Settings .................................................................................................................. Dynamic Printer Matrix ............................................................................................. Variables ................................................................................................................ Script control .......................................................................................................... Map additional printers ............................................................................................ Send, export and import the configuration .................................................................. 4 Manual 71 71 71 72 72 74 76 82 82 84 85
Cortado AG 2012
Contents
Appendix .................................................................................................................... 86
Customer service and technical support .......................................................................... 86 Licenses ...................................................................................................................... 86 Entering and activating license keys ........................................................................... 86 License usage ......................................................................................................... 88 Server roles and custom setup ....................................................................................... 89 Session-in-Session ........................................................................................................ 90 Update ........................................................................................................................ 91 Uninstallation .............................................................................................................. 92 Remote client configuration ........................................................................................... 92 Additional sources ........................................................................................................ 92 Glossary ...................................................................................................................... 93 Abbreviations ............................................................................................................. 100 ThinPrint Engine feature comparison ............................................................................ 101
Cortado AG 2012
Manual
Introduction
Introduction
What is ThinPrint?
Cortado's ThinPrint 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 a server as well as a client component, i.e. ThinPrint Engine 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: 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 Application Server Engine.

ThinPrint AG 2012
Manual
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 Server Engine manual, Page 92).
Advanced Adaptive Compression

Furthermore, ThinPrint Engine combines the efficient Driver Free Printing system with a new kind of compression, Advanced Adaptive Compression. 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% (see Illus. 39, Page 35).
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 including Windows CE, for Linux, Solaris, DOS, Java as well as for both internal and external print servers of network printers. ThinPrint Clients can be downloaded from ThinPrints website (see Page 93). 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@team.cortado.com.
Package contents
The ThinPrint Application Server Engine product CD for ThinPrint version 9.0 contains: The installation program Setup.exe for ThinPrint Engine A quick installation guide
Licenses
ThinPrint AG 2012
In addition, you should have received license keys from your reseller or by e-mail from ThinPrint. These are installed on the terminal server. Depending on the licensing type you got license keys from the following type:
Annual licenses TLUS-0688Annual licenses can be server or user based. Manual 7
Introduction
serverbased licenses x86: THPR-0688-1 or x64: TAPR-0688-1 1 userbased licenses TPPR-0688-1(basic license key: Application Server Basic Pack) and TPUS-0688-10 (license key for 10 Named Users, for example)
When purchasing user based licensing, it is common to buy as many licenses as there are users in the terminal server environment. Therefore you may have received further TPUS licenses, for example TPUS-0688-5 for 5 named users, TPUS-068820 for 20 named users. More information about ThinPrint licensing can be found starting on Page 86 and in the ThinPrint licensing documentation.
Scenarios
The following sample 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 many strengths of ThinPrint.
Terminal server(s) Printing via TCP/IP

PCs and terminals (thin clients) communicate with the terminal server2 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. Moreover, each user can use all printers in the network which are accessible via TCP/IP regardless of whether he is using a PC (rich client), a thin client, or any other type of client. Further information can be found starting on Page 16.
ThinPrint AG 2012
1 2
For more than one terminal server the user-based licensing is possible only if a central print servers is used. with Microsoft Terminal Services or Citrix XenApp
Manual
Introduction
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 3 (Illus. 3). Further information can be found on Page 16. Illus. 3
Illus. 3
ThinPrint printing with terminal servers over ICA or RDP
ThinPrint AG 2012
Networks behind routers with Network Address Translation (NAT)
Manual
Installation
Installation
Technical requirements
Be sure that the TCP port numbers for printing via TCP/IP are not being blocked by another program or by a server-side or client-side firewall. IPv4 has to be enabled for each involved machine.
ThinPrint Engine
Supported server operating systems Windows Server 2012 Windows Server 2008 Windows Server 2008 R2 Windows Server 2003 with Service Pack 2 or later Windows Server 2003 R2 with Service Pack 2 or later Windows Server 2012 Also required: .net Framework with Version 2.0 or later 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 90) to a XenApp server or XenDesktop: Citrix ICA Client v10.0 or later In DNS a Reverse Lookup Zone has to be set up, in which all computers, devices and appliances are registered. For Citrix XenApp: XenApp Web Plugin 11.0.150 or later The Windows service PRINT SPOOLER should not be disabled.
ThinPrint Client
Workstations or local print servers: Windows 7, 7 x64, Vista, Vista x64, XP , XP x64, 2008, 2008 x64, 2008 R2, 2003, 2003 x64, 2003 R2, 2003 R2 x64 supported, but with limited functionality, are: Windows 2000, NT 4, ME, 98, 95 with Windows-Installer version 2.0 and later, Apple MacIntosh, Linux, Java Thin Clients with embedded ThinPrint Client (see Page 93).
Administrator permissions
Administrator permissions are required for all installation and configuration procedures. It is therefore best to log on to Windows as the local ADMINISTRATOR.
ThinPrint AG 2012
10
Manual
Installation Installing ThinPrint Engine (per terminal server)

Unattended installation Unattended installation and licensing are also possible; refer to the White Paper Unattended installation and licensing of ThinPrint Engine components Page 92.
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. 1. Copy the software for ThinPrint Engine installation to the servers hard disk and start Setup.exe (Illus. 4). Illus. 4
Illus. 4
Start the installation program Setup.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).
2. Select one of the following languages: English, German, French, or Spanish. 3. Click NEXT to confirm the Welcome window. 4. Read the license agreement, accept it and click NEXT to confirm. The menu shown in Illus. 5 will open. Select TERMINAL SERVER.
ThinPrint AG 2012
Manual
11
Installation
Illus. 5
Illus. 5
Select the APPLICATION SERVER role
For assistance selecting the role, read Page 89. Print Server This option only applies if you install ThinPrint Engine on a central print server. In that case, consult ThinPrint Server Engine manual. Select TERMINAL SERVER EXTENSION, if you use a central print server in your terminal server environment. In this case only AutoConnect, Virtual Channel Gateway and Output Gateway are installed, but ThinPrint Engine is not4. 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 PC 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 on Page 10. Here you can specifically select individual ThinPrint components, e.g. Session-inSession. See Page 89.
Terminal Server Extension
Administration Tools
Custom Setup
ThinPrint AG 2012
ThinPrint Engine will be installed on the print server; so you will need Server Engine licences. Read the ThinPrint Server Engine manual for print server installation.
12
Manual
Installation
5. In the next dialogue box you can select the installation path by clicking on CHANGE (Illus. 6). Click NEXT to continue. Illus. 6
Illus. 6
Choose an installation path
6. Select ENTER LICENSE(S) if you already received license keys from your reseller or from Cortado. Otherwise select DEMO MODE (Illus. 7). Click NEXT to confirm. Illus. 7
Illus. 7
Select a licensing type
Entering a license key
7. If you selected ENTER LICENSE(S) the window in Illus. 8 will appear. If so, copy your license keys for ThinPrint Application Server Engine or ThinPrint Application Server Basic Pack (see licenses on Page 7) into the white field, as shown on the left in Illus. 8 and click INSTALL LICENSE(S).
ThinPrint AG 2012
Manual
13
Installation
Illus. 8
Illus. 8
Copy license keys into the white field and click INSTALL LICENSE(S) to confirm (example for Windows x64 with server-based licensing)
That causes one of the exclamation marks in a red circle to change to a checkmark in a green circle (above right in Illus. 8). Click OK to continue. Note! Once a license key has been entered, it is valid without activation for 30 days. See Page 86 for information about activating licenses. With more than one terminal server using user-based licensing the license keys of (Named) User licenses have to be distributed among all terminal servers. 8. 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 Printers
After installation, three new printers can be found in the servers Printers folder (Illus. 9):
_#ThinPrint Output Gateway (template)
ThinPrint AG 2012
14
Manual
Installation
Illus. 9
Illus. 9
_#ThinPrint Output Gateway printer template in servers Printers folder
Template ThinPrint Output Gateway
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 him 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. 10). Illus. 10
Illus. 10
Printer in a terminal session: TP Output Gateway printer driver inherited from a template (example)
For more information about creating and configuring printers and templates, see Pages 41 and 50. ThinPrint Clients must be installed on the client machines to receive ThinPrint print data (Page 17). 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.
Disabling Windows printer mapping

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 should be disabled within and outside of the session. To do so (on the terminal server):
ThinPrint AG 2012
Disabling client printer mapping
1. In Windows Control Panel, select SYSTEM AND SECURITY ADMINISTRATIVE TOOLS SERVER MANAGER ROLES REMOTE DESKTOP SERVICES RD SESSION HOST CONFIGURATION. 2. Click on the RDP-TCP connection and select PROPERTIES in the context menu (Illus. 11) Manual 15
Sample configuration
Illus. 11
Illus. 11
Configuring RDP configuration
3. Disable the mapping functions in CLIENT SETTING tab (arrows in Illus. 12). 4. If available, click on the ICA-TCP connection select PROPERTIES in the context menu. 5. Disable the mapping functions. Click OK to confirm. Illus. 12
Illus. 12
Settings for printer mapping
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 the RDP type of ThinPrint Client Windows or on Citrix XenApp servers the ICA type of ThinPrint Client Windows.
ThinPrint AG 2012
16
Manual
This plug-and-play installation cannot be used in every scenario. One reason is that it requires a Windows PC as client. So only the main configuration options are illustrated here, using a sample scenario as example. The following descriptions refer to the sample scenario below. Illus. 13
Illus. 13
Sample 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 PC and a thin client as well as a local print server. The following table describes the print environment used in the sample configuration (Illus. 13). Machine name client1 User name user1 Connection to Server DSL (768 kbit/s) ThinPrint Client type TCP/IP type of ThinPrint Client WinCE ThinPrint Client Service Windows (TCP/IP) RDP type of ThinPrint Client Windows
Printer Epson Stylus Color 400
Print mode with native printer driver
ps05
Lexmark T620
DSL (768 kbit/s)
client2
user2
HP DeskJet
ISDN (64 kbit/s)
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.
ThinPrint AG 2012
Installing ThinPrint Clients

Configuring thin client
client1: ThinPrint Client WinCE (TCP/IP) on a thin client ThinPrint Application Server Engine Manual 17
1. For this sample scenario, choose a thin client with an embedded ThinPrint Client (see Page 93). 2. Open the control panel on the thin client and select THINPRINT, then click OPEN, (Illus. 14). Illus. 14
Illus. 14
ThinPrint Client WinCE in the control panel (example for Neoware terminals)
3. Enable the ThinPrint Client (ENABLE THINPRINT; Illus. 15 left). 4. Select the protocol you will select for the template _#Epson Stylus COLOR 400 on the server (THINPRINT OVER TCP or TCP/IP Illus. 29), and click OK (Illus. 15 , left). 5. Open the ThinPrint Client configuration menu (CONFIGURE THINPRINT; Illus. 15 right). Illus. 15
Illus. 15
Selecting and enabling ThinPrint Client WinCE and opening configuration menu (example for Neoware terminals)
6. Click ASSIGNMENT (Illus. 16).

ThinPrint AG 2012
18
Manual
Illus. 16
Illus. 16
Configuring ThinPrint Client WinCE
7. Select a printer, e.g., LPT1:, click EDIT PRINTER and enter a printer name (in the sample scenario, Epson Stylus Color 400; Illus. 17). 8. Enable AutoConnect for this printer by marking the checkbox to the left of the printer name (Illus. 18). 9. Finish configuration by clicking OK. 10. Close the thin client's control panel. Illus. 17
Illus. 17
Assignment menu: select printer and click EDIT
PRINTER
Illus. 18
Illus. 18
client1: enabling AutoConnect for a printer
Configuring local print server

ps05: ThinPrint Client Service Windows on a local print server
ThinPrint AG 2012
Manual
19
1. For the sample scenario, install a Lexmark T620 printer (Illus. 19). 2. Install ThinPrint Client Service Windows; please refer to the ThinPrint Client Service Windows manual (Page 92). Illus. 19
Illus. 19
Printer installed on local print server ps05
3. Open the ThinPrint Client Manager. Determine the Lexmark T620 printer ID from the ASSIGNMENT tab (Illus. 20). Illus. 20
Illus. 20
Printer ID of the Lexmark T620 (here: 1)
client2: RDP type of ThinPrint Client Windows on a PC

Requirement: An RDP client must be installed. The scenario in Illus. 13 (Page 17) applies. 1. For the sample scenario, install an HP DeskJet printer (Illus. 21). 2. Install RDP type of ThinPrint Client Windows; please refer to the ThinPrint Client Windows manual (Page 92). ThinPrint Client is started automatically with the RDP session. It does not need to be configured for the sample installation.
ThinPrint AG 2012
20
Manual
Illus. 21
Illus. 21
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 35). Requirement: ThinPrint Engine must already be installed (Page 11). The scenario in Illus. 13 (Page 17) applies.
ThinPrint Ports
1. Open the ThinPrint configuration with START THINPRINT ENGINE CONFIGURATION (Illus. 22). Illus. 22
Illus. 22
Opening ThinPrint Configuration
ThinPrint AG 2012
Manual
21
2. Click ADD and then specify the computer address (Illus. 23) for each local or remote ThinPrint Engine to be configured (Illus. 24). Illus. 23
Illus. 23
Open the configuration console for server components
Illus. 24
Illus. 24
Specify - local or remote configuration
3. The ThinPrint Engine console appears (Illus. 25). Select on the left, i.e., in the Console Tree: THINPRINT THINPRINT ENGINE PORT MANAGER. Illus. 25
Illus. 25
ThinPrint Port(s) in the configuration console (= Port Manager)
ThinPrint AG 2012
22
Manual
4. Create the following ThinPrint Port by clicking the NEW THINPRINT PORT icon (upper arrow in Illus. 25) and set the protocol (Illus. 26 and 27): Port name RDP1: Illus. 26 Port type (protocol) VCP = VIRTUAL CHANNEL PROTOCOL (ICA OR RDP)
Illus. 26
Selecting port type for port RDP1:; click APPLY
Illus. 27
Illus. 27
A new ThinPrint Port
ThinPrint AG 2012
Manual
23
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. 28) in the servers Printers folder 5 (Windows Server 2008: START PROGRAMS THINPRINT ENGINE PRINTERS, Illus. 22): Printer name _#Epson Stylus Color 400 ThinPrint Port ThinPort: Printer driver Epson Stylus Color 400 Esc/P2 TP Output Gateway
_#RDP Illus. 28
RDP1:
Illus. 28
Two new printer objects as templates
6. Under PROPERTIES SECURITY, assign permissions to the two printer templates, _#Epson Stylus Color 400 and _#RDP: Delete all users and groups except for administrators. Add SYSTEM and allow full control. 7. Change to the port configuration in the MMC and check that the new printers have been assigned correctly to the ThinPrint Ports (Illus. 29; if necessary, press F5 to refresh).
ThinPrint AG 2012
With Windows Server 2008 R2 in Print Management
24
Manual
Illus. 29
Illus. 29
The new templates (right) assigned to the ThinPrint Ports (left)
Configuring AutoConnect
8. Select DYNAMIC PRINTER MATRIX in the Console Tree (Illus. 30, 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 \\mydomain\user1 Target Epson Stylus Color 400 RDP
\\mydomain\user2
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 users session. So, lower lines will only be executed if the conditions of the upper lines dont match for this client printer. Illus. 30
ThinPrint AG 2012
Illus. 30
Dynamic Printer Matrix in the configuration console
Manual
25
Creating a printer manually Create the following printer object in the terminal servers Printers folder 6 for the printer in Illus. 19 and 20: Lexmark T620#ps05:1 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. 31 and 32 appear in the Printers folder 6 in the two sessions. Open an application and print with each of these printers. Illus. 31
Illus. 31
Printers from user1 in an terminal session as in the example
Illus. 32
Illus. 32
Printers from user2 in an terminal session as in the example
Print jobs will be received from the ThinPrint Clients and forwarded to the printers as follows: Client name (User name) client1 (user1) ps05 (user1 + user2) client2 (user2)
6
Print protocol TCP/IP TCP/IP RDP
Addressed printer ID 2 1 2
Target printer Epson Stylus Color 400

ThinPrint AG 2012
Lexmark T620 HP DeskJet
With Windows Server 2008 R2 in Print Management
26
Manual
Please note which printers in terminal sessions use a native driver and which use the TP Output Gateway (see the MODEL column in Illus. 31 and 32).
If you still can't print Checklist

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 86). 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 20) 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. 26). For AutoConnect, either VIRTUAL CHANNEL (ICA OR RDP) or AUTO must be set as connection protocol (Illus. 91), 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?
Note! For printing using ThinPrint Ports the TP AutoConnect Service has to be run together with the ThinPrint Engine. If TCP/IP is the selected protocol: Are the TCP port numbers the same on server and client (see port configuration in MMC Illus. 37 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 Connected Gateway manual; Page 92). If a printer was created manually (see Page 26), check the naming convention of the ThinPrint Port (see port configuration in MMC, Illus. 38). If you selected USE ENCRYPTION on the server (Illus. 78), continue reading the section Encrypting print jobs for further information (Page 60), or disable encryption for now. Are the correct templates used when AutoConnect starts (see Illus. 28)? For each template, there must be an appropriate printer name, printer class, or entry in the Dynamic Printer Matrix (see ThinPrint Client Manager, Illus. 20, and AutoConnect, Illus. 96). Check that AutoConnect is working by starting it
ThinPrint AG 2012
Manual
27
manually: Open the Command Prompt in a terminal session, change to the ThinPrint Engines program directory 7 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. 91 to 102). 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 cause difficulties in this situation. Test to see if the connection exists by trying a telnet from the server to the clients TCP port.8 To do this, enter the following at the servers Command Prompt: telnet IP port (blank space between IP address and TCP port number) IP is the client machines IP address; port is the TCP port the ThinPrint Client is using. (See also the ThinPrint Client manuals; Page 92.)
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. 20) INHERIT CLIENT PRINTER SETTINGS in the AutoConnect configuration (Illus. 93) 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 90). 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 Clients 9 directory (e.g.: C:\Program Files (x86)\Citrix\ICA Client). If not, copy it from the ThinPrint program directory 10 to this directory. Please also note the chapter Citrix ICA Client later installed (Page 91).
7 8 9 10 e.g. c:\Program Files\ThinPrint Engine A ThinPrint Client (TCP/IP type) is necessary on the respective client machine. also: Citrix XenApp Plugin for Hosted Apps e.g.: C:\Program Files\ThinPrint Engine
ThinPrint AG 2012
28
Manual
Ports
ThinPrint prints with own printer ports which will be automatically created during installation. Furthermore, you can continue printing with conventional ports at the same time; ThinPrint does not affect this. Two kinds of ports are included with ThinPrint: ThinPort/Connection Service Port for printing in terminal server sessions Print-to-Cloud Port Printing to a directory. The print job can be displayed and printed not only on a PC, but also on a mobile device (see the ThinPrint Server Engine manual, Page 92) General information about ThinPrints printer ports can be found in the ThinPrint Ports white paper (Page 92). This chapter describes configuration of the ThinPrint Engine with special attention to adding ThinPrint Ports and adapting them to specific requirements for print job transmission. The Port Manager 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
Starting Port Manager

1. Open the ThinPrint configuration with START (ALL) PROGRAMS THINPRINT ENGINE CONFIGURATION. 2. Click ADD for each local or remote ThinPrint Engine to be configured (Illus. 33) and specify the computer address (Illus. 34). Illus. 33
ThinPrint AG 2012
Illus. 33
Manual
29
Illus. 34
Illus. 34
Local or remote configuration?
3. The ThinPrint Engine console appears (Illus. 35). Illus. 35
Illus. 35
Selecting TRACKING SETTINGS
ThinPrint AG 2012
30
Manual
Here, you will find all events generated by ThinPrint components. Additionally you can display print spooler events here (arrow in Illus. 35). Note! Note that saved server settings will only be effective after a spooler restart. With Windows Server 2008 R2, spooler events cannot be shown here at present. How to create new ThinPrint Ports? To create new ports use the buttons in MMCs menu bar (Illus. left) NEW THINPRINT PORT or NEW THINPRINT CONNECTION SERVICE PORT 11 (Illus. 36). Choose the port settings: port type (protocol), bandwidth and/or encryption. Up to 600 ports are possible.12
Creating new ThinPrint Ports
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 4. To configure ports, select on the left, in the Console Tree: THINPRINT THINPRINT ENGINE PORT MANAGER (Illus. 36). Illus. 36
Illus. 36
ThinPrint Ports in Port Manager
ThinPrint AG 2012
5. Double clicking a port name (right arrow in Illus. 36) will open the port configuration (Illus. 37).
11 For Connection Service Ports see ThinPrint Connected Gateway manual (Page 92) 12 maximum 600 ThinPrint Ports with maximum 800 active printer queues (Windows Server 2003 with 3 GHz Dual Xeon processor, 2 GB RAM, and SCASII ultra3 disk array) or maximum 1500 Queues with Windows Server 2008 R2
Manual
31
Configure tab
Illus. 37
Illus. 37
Port settings: CONFIGURE tab
The ThinPrint Ports can be configured as follows: USE ENCRYPTION
Enables SSL/TLS encryption; a valid and corresponding certificate must be available on both ThinPrint Engine and ThinPrint Client (not for LPD; see also Page 60). ENABLE: Bandwidth control on Max. bandwidth available for printing with ThinPrint; minimum: 1600 bit/s, default: unlimited TCP/IP (sockets) ICA / RDP (Virtual Channel Protocol) LPD (Unix print protocol LPR/LPD) (USE VIRTUAL CHANNEL GATEWAY) Note: This function is for printing from print servers via ICA or RDP See also the ThinPrint Server Engine manual, . Page 92.)
BANDWIDTH
CONTROL
Print protocol
MINIMUM
PRINT DATA VOLUME
Enabled: always high compression (classic case) Disabled: transfer rate optimized compression depends on bandwidth settings
ThinPrint AG 2012
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 ThinPrint port configuration for bandwidth controlled printing via LPR/LPD white paper (Page 93). 32 Manual ThinPrint Application Server Engine
Save Confirm changes with APPLY or OK.
Advanced tab
Illus. 38
Illus. 38
Port settings: ADVANCED tab
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 Engine settings are applied. This function is only available if bandwidth control (see Illus. 37 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 can be used to notify users if ThinPrint experiences print errors. If a problem occurs during data transmission, an error message is generally not sent to the user. 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.
ThinPrint AG 2012
Manual
33
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 TCP/IP Lexmark T620 PS3#192.168.1.100 Lexmark T620 PS3#192.168.1.100:1 HP LaserJet 1200 PCL#client1 HP LaserJet 1200 PCL#client1:2 ICA / RDP HP LaserJet 1200 PCL# Lexmark T620 PS3#:1 Reversed addressing
192.168.1.100#Lexmark T620 PS3 192.168.1.100:1#Lexmark T620 PS3 client1#HP LaserJet 1200 PCL client1:2#HP LaserJet 1200 PCL
HP LaserJet 1200 PCL :1#Lexmark T620 PS3
Example for auto-created printers (AutoConnect): HP LaserJet 1200 PCL#user1:2 LPD Lexmark T630#192.168.1.101 Lexmark T630#networkprinter3 user1:2#HP LaserJet 1200 PCL
192.168.1.101#Lexmark T630 networkprinter3#Lexmark T630
Job Statistics tab

Print statistics must be activated per port. 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. 39. Note! Use this function only part-time, as it may affect print performance. See also Print job tracking (Page 66).
ThinPrint AG 2012
34
Manual
Illus. 39
Illus. 39
Port settings: JOB
STATISTICS
tab
OK
Save your settings by clicking OK.
Distributing port configuration

The following strategies are available for creating the same configuration for ThinPrint Ports on multiple servers: Remote configuration of ThinPrint Ports (Page 29) 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)

Copy-and-Paste
Open the ThinPrint Engine configuration (Page 29). Mark a port in a servers Port Manager (e.g. TS01 in Illus. 40) and select COPY from the context menu. Mark the Port Manager of a target server (e.g. TS02 in Illus. 41) and select PASTE from the context menu.
ThinPrint AG 2012
Manual
35
Illus. 40
Illus. 40
Copy a port on a server
Illus. 41
Illus. 41
Paste the port on another server
Export/Import
The following export and import functions are available: EXPORT CONFIGURATION Exports the selected ThinPrint Port to an .xml file (Illus. 40) Exports all ThinPrint Ports to an .xml file if no port is selected (Illus. 42)
ThinPrint AG 2012
IMPORT /EXPORT EXPORT PORT CONFIGURATION IMPORT /EXPORT IMPORT PORT CONFIGURATION
Imports ThinPrint Ports from an .xml file (Illus. 42)
36
Manual
Illus. 42
Illus. 42
Exporting, importing, or sending all ThinPrint Ports
Sending port configuration
The SEND PORT CONFIGURATION function sends ThinPrint Ports to other servers or server groups (Illus. 42). 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 Sends the selected ThinPrint Port; ports with the same name on the target system will not be overwritten Send all ThinPrint Ports (bottom arrow in; ports with the same name on the target system will be overwritten Send all ThinPrint Ports (bottom arrow in; ports with the same name on the target system will not be overwritten
SEND PORT CONFIGURATION (ADD ONLY)
IMPORT /EXPORT SEND PORT CONFIGURATION (OVERWRITE)
IMPORT /EXPORT SEND PORT CONFIGURATION (ADD ONLY)
ThinPrint Ports on the target computer which do not exist on the on the sending computer remain unchanged. Procedure when sending
ThinPrint AG 2012
Selecting the send option will open the dialog in Illus. 43.
Manual
37
Illus. 43
Illus. 43
Dialog for sending properties
To improve clarity, first select OBJECT TYPES (upper arrow in Illus. 43), and disable GROUPS (Illus. 44). Click OK to confirm. Select ADVANCED (lower arrow in Illus. 43) and then FIND NOW (Illus. 45). Illus. 44
Illus. 44
Limiting the selection to computers
ThinPrint AG 2012
38
Manual
Illus. 45
Illus. 45
Find target servers
Mark all target servers and click OK to confirm (Illus. 46). 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 AG 2012
Manual
39
Illus. 46
Illus. 46
Selecting target server(s)
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 (Page 29) and repeat the send process from the source computer while keeping the console open (Illus. 47). Illus. 47
ThinPrint AG 2012
Illus. 47
Create a connection to the target computer with the MMC (here: arrow to TS02) and repeat send process from source computer (here: TS01)
40
Manual
Configuring ThinPrint Creating printers and templates

General information about creating printers can be found in the ThinPrint addressing and ThinPrint Ports white papers (Page 92). Theres one last step after installing and configuring the ThinPrint Engine on the terminal servers: setting up printers on the ThinPrint Ports. Which protocol? If you are working with several ThinPrint Ports, each with a different protocol, then check port configuration (Page 31) before printer installation to see which ThinPrint Port supports what protocol.

Simplification(s)
ThinPrint Output Gateway (Page 50) .print AutoConnect (Page 70)
Templates
What are templates? With ThinPrint, a template is a printer in the servers Printers folder 13 from which the client or session printers created with AutoConnect inherit their properties (see chapter AutoConnect, Page 70). The _#ThinPrint Output Gateway template appears in the servers Printers folder after installation of ThinPrint Engine (Illus. 60, Page 50). Among other things, client printers that are created by AutoConnect in the terminal sessions Printers folder 13 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
Which properties are inherited?
ThinPrint AG 2012
13 With Windows Server 2008 R2 in Print Management
Manual
41
Template denominations
Network protocol TCP/IP ICA, RDP ,
Names of printer objects (for templates) 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 (Page 33) once. If you also want to create printers on the server manually, though, please also refer to the following information. For simplicitys sake, only standard addressing is treated here; reversed addressing can be found in the chart on Page 34, and addressing THINPRINT CONNECTION SERVICE PORTS is explained in detail in the ThinPrint Connected Gateway manual (Page 92). 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: Printer names Network protocol TCP/IP Names of printer objects Either: Example: Or: Example: Either: Example: Or: Example: 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 printer_name#user_name:printer_ID Kyocera FS-850#administrator:3 printer_name#:printer_ID Kyocera FS-850#:3 printer_name#client_name Kyocera FS-850#printer1 printer_name#IP_address Kyocera FS-850#191.168.1.18
ICA/RDP
LPD
ThinPrint AG 2012
42
Manual
client_name Client name with TCP/IP and LPD 14 means the real name of the client in the network (= host name). Alternatively, the clients 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 15, the ThinPrint Client automatically assigns every installed printer an ID (see Illus. 17, Page 19). 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 Clients current printer (Illus. 16). The printer name can be anything you like. It is nonetheless recommended that it is the same as the printer name at the client.
printer_name
Example 2:
Client Client name IP Address Printer client1 192.168.1.17 HP LaserJet 1200 PCL
ThinPrint Client assigned this printer ID 2 (Illus. 17). 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 clients 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.
ThinPrint AG 2012
14 See the ThinPrint port configuration for bandwidth controlled printing via LPR/LPD white paper (Page 93) 15 i.e., a Workstation, a thin client (terminal), a gateway appliance or a local print server
Manual
43
Example 3:
A Kyocera FS-850 shall print via ThinPrint with the ICA protocol. If several printers are installed and ThinPrint Client assigned the printer the ID 3, the printer name could be something like: Or Or laser_printer #:3 Kyocera# :3 Kyocera FS-850#_:3 (# before the :) (blank space before the :) (underscore before the :)
If Kyocera FS-850 is the current printer (in the ThinPrint Client), the printer name could be: laser_printer
Port pooling
Pooling printers with ThinPrint means you can attach a printer to several ThinPrint Ports (Illus. 48 and 49) also known as printer pooling. This has the following advantages: Improved performance Little chance of blockage from very large or hanging print jobs Less printers on the server Illus. 48

Illus. 48
Principle of port pooling
Port pooling is supported by: ThinPrint Ports ThinPrint Output Gateway AutoConnect ThinPrint Virtual Channel Gateway ThinPrint Connection Service 16

ThinPrint AG 2012
16 not in included in the ThinPrint Engine; see the ThinPrint Connected Gateway manual (Page 92)
44
Manual
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 ThinPrint Ports white paper (Page 92). Illus. 49
Illus. 49
Activating port pooling (example)
Note! Port-Pooling is not recommended for printing to gateway appliances without an own spool system (e.g., SEH TPG60/120 and Intermate IAPS ThinPrint). With these devices attach each printer object to an own ThinPrint Port.
Printing with thin clients

Windows CE and Linux clients are capable of forwarding print jobs to LPD devices. The ThinPrint Client WinCE or ThinPrint Client Linux is installed on a thin client or PC 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. 50). All ThinPrint Clients for Linux and Windows CE (5.5 or later) operating systems support LPR/LPD printing.
ThinPrint AG 2012
Manual
45
Note! For more information on sending print jobs directly via LPR/LPD with ThinPrint Engine, see the ThinPrint port configuration for bandwidth controlled printing via LPR/LPD white paper (Page 93). Illus. 50
Illus. 50
LPR/LPD printing via Windows CE or Linux clients
Preparations on the server

Set up a new template on the server (e.g. #HPLaser, left arrow in Illus. 51) and attach it to a ThinPrint Port (e.g. ThinPort:, Illus. 25 on Page 22). Use a native printer driver to do this. (e.g. HP Color LaserJet 4700, right arrow in Illus. 51, or TP Output Gateway PS). Illus. 51
Illus. 51
Preparing a template for LPD printing with thin clients (example)
ThinPrint AG 2012
46
Manual
Make sure that the printers completely spool the print data on the hard drive before sending. To do so, open the templates printer properties and select GENERAL. Select START PRINTING AFTER LAST PAGE IS SPOOLED (Illus. 52). Additionally disable the ADVANCED PRINTING FEATURES. Click OK to confirm. Select the appropriate settings in AutoConnect to ensure that the relevant Windows-CE or Linux clients printers operate with the new template (_#HPLaser) in the terminal sessions. Refer to the configuration example on Page 25 or in the paragraph AutoConnect on Page 70. Illus. 52
Illus. 52
Recommended settings for client-side LPD printing on the server
ThinPrint AG 2012
Manual
47
Preparing ThinPrint Client (example for Windows CE)
Open the control panel on the Windows CE device and select THINPRINT (click OPEN, Illus. 14). Illus. 53
Illus. 53
ThinPrint Client WinCE in the control panel (example for Neoware terminals)
Enable the ThinPrint Client (ENABLE THINPRINT, Illus. 54 left). Select the protocol you selected for the corresponding template (TCP/IP ICA, or , RDP; see Illus. 29 on Page 25) and click OK (Illus. 54 left). Open the ThinPrint Client configuration menu by clicking CONFIGURE THINPRINT (Illus. 54 right). Illus. 54
Illus. 54
Selecting a protocol, enabling ThinPrint Client and opening configuration
Use ASSIGNMENT to list available printers (Illus. 55). Select ADD NETWORK PRINTER and then LPD PRINTER (Illus. 56).
ThinPrint AG 2012
48
Manual
Illus. 55
Illus. 55
Select ADD
NETWORK PRINTER
Illus. 56
Illus. 56
Select LPD
PRINTER
Enter hplaser as PRINTER NAME and the printers IP address or client name (PRINTER ADDRESS) and, for external print servers with more than one printer port, the name of the printer QUEUE (e.g., LPQ1) according to the print servers manual (Illus. 57); leave LPD FILTER l unchanged. Click OK to confirm. Illus. 57
Illus. 57
Enter a network printer (example)
Enable this printer in the ASSIGNMENT tab and finish configuration with OK (Illus. 58). Illus. 58
ThinPrint AG 2012
Illus. 58
Enable the new printer and click OK to confirm
Manual
49
Printing
Establish an ICA or RDP connection from the terminal to the terminal server. The new printer appears in the sessions Printers folder 17 (Illus. 59). Open an application and print with this printer. Illus. 59
Illus. 59
Auto-created printer hplaser#user1:6 in the session
ThinPrint Output Gateway

The TP Output Gateway is a virtual printer driver (see the MODEL column in Illus. 60) that makes it possible to render print data using original (native) printer drivers installed on the client side. Because no other, native printer driver is required on the server in addition to the Output Gateway, this print method is called Driver Free Printing. In this sense, of course, Driver Free only refers to the terminal server (Illus. 61). The user interface of Output Gateway is available in 16 languages, see Page 57. Illus. 60
Illus. 60
TP Output Gateway driver in the servers 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.
ThinPrint AG 2012
17 With Windows Server 2008 R2 in Print Management
50
Manual
Illus. 61
Illus. 61
Driver Free Printing: Output Gateway on terminal servers, printer drivers on PCs and local print servers running Windows
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. Example:
Example 4:
Client
Addressing the printer directly (TCP/IP printing) client1 3 192.168.1.17 HP LaserJet 5L
Client name ID IP address Printer name Server Printer name or Printer name
HP LaserJet 5L#client1:3 HP LaserJet 5L#192.168.1.17:3
Output Gateway printer objects can be created manually with the ADD PRINTER function in Printers folder 18 using THINPRINT as manufacturer. The printers are to be connected to a ThinPrint Port.
Paper formats and trays

ThinPrint AG 2012
After initial installation, a few default options are available for paper formats and paper sources 19 (Illus. 66). You can add further options provided they are supported by the printer drivers on the client machine(s).
18 With Windows Server 2008 R2 in Print Management 19 Selection of paper trays or manual feed
Manual
51
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. 66) For manually created printers: Setting registry values for paper formats and sources on the server (see the Adaption of Output Gateway options white paper; Page 92)
Presettings on the server (administrators only)

The following settings need to be set in the servers Printers folder 18 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. Select for example FILE PROPERTIES DEVICE SETUP for _#ThinPrint Output Gateway in the server's Printers folder 18. Compression range There are five options available for print data compression (Illus. 62): Normal Lossless Optimal Text without loss, good image quality Maximum Text without loss, medium image quality Extreme Text without loss, low image quality No images Only text will be printed At this point you can set the range of compression levels that the users will be able to set Select, for example, OPTIMAL, and the level NORMAL is no longer available to users. The default compression level itself, is set however in the tab ADVANCED PRINTING DEFAULTS COMPRESSION (Illus. 65, on Page 54). Additionally the option SPEEDCACHE can be enabled or disabled for terminal server users. A ThinPrint Client Windows v8.6 (or later) is required. SpeedCache makes printing even faster and more efficient. SpeedCache checks every print job, for whether it replicates graphic elements (such as logos or fonts) and, if so, sends them only once. Thereby, the volume of server-client communication is cut down, without creating additional load on the network. You can set up and adjust SpeedCache on the printer driver ThinPrint Output Gateway (see Illus. 62).20
SpeedCache
ThinPrint AG 2012
20 SpeedCache is not available for V-Layer printers. If SpeedCache is chosen as a setting, it will not have any effect.
52
Manual
Illus. 62
Illus. 62
Setting compression and SpeedCache
Page Setup
Select the PAGE SETUP tab in ADVANCED PRINTING DEFAULTS to edit page and color presettings; e.g., LETTER or A4 as paper size (Illus. 63). Additionally you can edit the following settings for double-sided printing: LONG EDGE or SHORT EDGE (= turn over edge). Illus. 63
Illus. 63
Presetting paper size, print resolution, color, etc., on the server
ThinPrint AG 2012
Advanced
In the ADVANCED tab (Illus. 64) 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. 68) or the native printer driver's user interface (OPEN MY PRINTING PREFERENCES, Illus. 69) can appear on a workstation. Both options allow the user to access all other printer specific settings. Manual 53
PAGE ADJUSTMENT offers options for the default procedure if the printable area of the document and of the printer drivers paper format dont match. The option SCALE TO FIT changes the size of the printout, ADJUST MARGINS moves the print area (Illus. 64). It is recommended to leave both settings enabled for printer templates. Illus. 64
Illus. 64
Presetting scaling and margin adjustment on the server
Compression level
In the COMPRESSION tab, the default level of compression for users can be set (Illus. 65). Illus. 65
ThinPrint AG 2012
Illus. 65
Setting compression on the server
The template settings from Illus. 63 and 65 will be shown as default options in a terminal session. Users can change them within their sessions. 54 Manual ThinPrint Application Server Engine
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 Duplex/simplex Finishing options such as staple, punch, binding Print resolution Paper size Comments and location
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. 66): PAPER SIZE, PRINT QUALITY, PAPER SOURCE, COLOR, ORIENTATION and PRINT ON BOTH SIDES. Illus. 66
Illus. 66
Display of paper sources on a workstation (left) and in a terminal session (right)
Printing with preview

Once the users have enabled the print preview (lower arrow in Illus. 67) the print job will appear in the ThinPrint viewer (= ThinPrint Viewture; Illus. 68); this requires that the print jobs are sent to a Windows workstation. Here the users can:
ThinPrint AG 2012
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 21
21 File extension: .tpf (compressed EMF data); the Viewture program (= TPView.exe) is needed for reloading a saved print job; see Page 93).
Manual
55
Illus. 67
Illus. 67
Print mode, scaling and margin adjustment in a terminal session
Illus. 68
Illus. 68
Preview with ThinPrint Viewture on the client computer (water mark = demo version)
When printing with preview, the print options appear in the terminal session in an Output Gateway design (Illus. 66 right). Once the client machine receives the print job, the print job is displayed in a preview window (Illus. 68). The print options now appear in the design of the native printer driver (Illus. 66 left).
ThinPrint AG 2012
Finishing options
If your printer supports finishing options22, you can find them in the similarly named tab (Illus. 69). Here you can set, for example, where staples should be located on
56
Manual
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. 69
Illus. 69
Finishing options in a terminal session
Language versions
Output Gateway is available in the languages listed below (Language abbreviations in parentheses):
ThinPrint AG 2012
Chinese, traditional (CHT) Chinese, simplified (CHS) Czech (CSY) English, United States (ENU) French (FRA) German (DEU) Greek (ELL) Hungarian (HUN) Italian (ITA) Japanese (JPN) Korean (KOR) Polish (PLK) Portuguese (PTG) Russian (RUS) Spanish (ESN) Swedish (SVE) Thai (THA)
22 Requirement: The printer must support PrintTickets from Microsoft. Download ThinPrint Finishing Detector (Page 93) 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
57
Illus. 70
Illus. 70
Output Gateways localization (examples)
You can appoint languages per user. Or you can select an approach that automatically appoints a language, according to each user's Windows language pack. Create a registry key for each required language, export it and then distribute it to the users. Appointing a language Set the language in the registry of the application server. Change the registry value Lang (REG_SZ) under hkey_current_user\software\thinprint\ and enter the abbreviation of your preferred language (list of abbreviations on Page 57), e.g. french = fra (Illus. 71). The change becomes effective with session logoff/logon.
ThinPrint AG 2012
58
Manual
Illus. 71
Illus. 71
Appointing a language for the user
Match language automatically
If you enter Def rather than the language abbreviation described above, the user is automatically appointed the language that corresponds to her or his language pack. For this, Microsoft language packs must have been installed. Give Def instead of fra as an example to registry value Lang (REG_SZ) under: hkey_current_user\software\thinprint\
Distributing language keys
If you have created a registry key for a language (as described above), you can make it available to all users. Click on the key and, in the menu, select FILE EXPORT. That way, the key will be exported in the file format .reg (example: Output_Gateway_French.reg). In the session, the users click on the .reg file of the desired language, so that the key is inserted into the registry. The user specified language setting is retained when they logoff/logon.
Cloud Printing
For using Print-to-Cloud and Print-to-ePaper see the description in the ThinPrint Server Engine manual (Page 92).
ThinPrint AG 2012
Manual
59
Configuring ThinPrint Encrypting print jobs

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/TLS certificates can be ordered at a certification authority or can be created by yourself (see the Creating SSL/TLS certificates for printing with ThinPrint white paper, Page 92). Depending on your security restrictions you can:
Create an own client certificate for each server and for each client Create only one client certificate to install it on all servers and on all client machines.
Or
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/TLS encryption is also available for use with the ThinPrint Connection Service.
Importing SSL certificates on the servers

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 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. 72).
ThinPrint AG 2012
60
Manual
Illus. 72
Illus. 72
Adding snap-ins for SSL certificates to the MMC
5. Import the certificate(s) to the two places shown in Illus. 73 (see arrows). To do so, select each time ALL TASKS IMPORT in the context menu and then NEXT BROWSE OPEN NEXT (PASSWORD NEXT)23 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. Illus. 73
ThinPrint AG 2012
Illus. 73
Importing two SSL certificates to the server
23 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.
Manual
61
Two examples for imported certificates can be found in Illus. 74 and 75. Illus. 74
Illus. 74
First SSL certificate imported on the server (example for server certificate)
Illus. 75
Illus. 75
Second SSL certificate imported on the server (example for root certificate)
Selecting certificates
6. For using the imported SSL certificates with the ThinPrint Engine open the ThinPrint Port configuration with START (ALL) PROGRAMS THINPRINT ENGINE CONFIGURATION.
ThinPrint AG 2012
62
Manual
7. Select ENCRYPTION SETTINGS in the PORT MANAGER context menu (Illus. 76). Illus. 76
Illus. 76
Selecting ENCRYPTION SETTINGS
8. Enter the names of server and root certificates under ENCRYPTION CERTIFICATES (Illus. 77). Use the names that are displayed in the column ISSUED TO of the MMCs certificate overview (in Illus. 74 and Illus. 75 Company ABC and Company ABC-CA as examples). Illus. 77
Illus. 77
Entering imported SSL certificates (example)
9. Fill in both fields and check that each certificate is installed on the server (Page 60) 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. 78).
ThinPrint AG 2012
Manual
63
Illus. 78
Illus. 78
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 manual (Page 92). In the following, installation is described with the example of the ThinPrint Client Windows. 1. To install a client certificate, select the following in the MMC on the client PC: FILE ADD/REMOVE SNAP-IN CERTIFICATES ADD COMPUTER ACCOUNT24 LOCAL COMPUTER FINISH OK 2. Now import the certificate by selecting ALL TASKS IMPORT in the context menu (Illus. 79) and then NEXT BROWSE OPEN NEXT PASSWORD NEXT PLACE ALL CERTIFICATES IN THE FOLLOWING STORE NEXT FINISH OK
ThinPrint AG 2012
24 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.
64
Manual
Illus. 79
Illus. 79
Starting import of an SSL certificate on a client machine
The result is shown in Illus. 80. Illus. 80
Illus. 80
SSL certificate imported to a client machine
Registry entry CertName
Before sending encrypted print data, the server checks whether the name of the imported certificate is included in the CertName entry in the client computers 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 key on the client machines with REGEDIT (Illus. 81; data type: reg_sz): hkey_local_machine\software\thinprint\client\CertName
ThinPrint AG 2012
Manual
65
Illus. 81
Illus. 81
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 MMCs certificate overview (Company ABC as example in Illus. 80 and 81). 3. Restart ThinPrint Client Windows. The CertName registry entry is only needed for encrypting print data; receipt of unencrypted print data is still possible.
Print job tracking

The ThinPrint Tracking Service is included in the ThinPrint Engine installer software. Its setup is described in the ThinPrint Tracking manual (Page 92). Print job tracking gathers information about print activities using ThinPrint Engine, if you print via ThinPrint Ports. With it, print related data is gathered on the server and forwarded to an SQL server (Illus. 82). Print job tracking has the following components: ThinPrint Engine (sends data to the Tracking Service) ThinPrint Tracking Service (receives data and writes it to an SQL database) ThinPrint Tracking Report Engine (web component for clear analysis, summary, and graphic report of tracking results)
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 ThinPrint Tracking manual).
ThinPrint AG 2012
66
Manual
Illus. 82
Illus. 82
Example for using Tracking
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: Author of a print job Printer used Settings used Print job compression Number of pages printed Information on any errors Print volume per user/group
Tracking Report Engine

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. 83).
ThinPrint AG 2012
Manual
67
Illus. 83
Illus. 83
Analyzing SQL data in a web browser (example)
Preparing ThinPrint Engine and Tracking Service

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: 1. Open configuration with START (ALL) PROGRAMS THINPRINT ENGINE THINPRINT CONFIGURATION. 2. Mark the respective ThinPrint Engine node and select EDIT SETTINGS (Illus. 84).
ThinPrint AG 2012
68
Manual
Illus. 84
Illus. 84
Selecting TRACKING settings
3. Enter the following settings in the TRACKING tab (Illus. 85): ENABLE TRACKING SQL servers address and name25 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 sent encrypted to the SQL server Name of the Tracking database (created using its installer) Click OK to confirm. The Result is shown in Illus. 86.
ThinPrint AG 2012
25 In case you access the SQL server remotely, open SQL Server Configuration Manager and enable the protocols NAMED PIPES and TCP/IP Then start SQL SERVER BROWSER in the services folder. .
Manual
69
Illus. 85
Illus. 85
Enable Tracking and enter settings
Illus. 86
Illus. 86
Print job tracking enabled
For details, see ThinPrint Tracking manual (Page 92).
AutoConnect
With AutoConnect it's possible to create printer objects automatically using templates on a terminal server (Illus. 87). 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 ThinPrint Server Engine manual.
ThinPrint AG 2012
70
Manual
AutoConnect features
Dynamic creation of printer objects in a terminal session, based on various criteria, e.g.: User name Printer name Client (or host) name Client IP address Organizational Units of which the terminal servers or virtual desktops are members Support of ThinPrint Output Gateway Support of ThinPrint Virtual Channel Gateway Support of ThinPrint Connection Service
Note! AutoConnect is installed together with ThinPrint Engine (because its Windows service has to be run together with the ThinPrint Engine) to enable printing. This is independent of the AutoConnect functions of mapping or creating printers on terminal servers.
Basic constellation
ThinPrint Engine on a terminal server, as well as AutoConnect and ThinPrint Output Gateway Illus. 87
Illus. 87
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.
ThinPrint AG 2012
Manual
71
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 System Print, Manage documents and Printer Print, Manage documents and Printer
Delete all permissions of other users. Note! Templates must not be shared. Port pooling Port pooling on ThinPrint Ports can also be used with AutoConnect; see Page 44.
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 with START (ALL) PROGRAMS THINPRINT ENGINE CONFIGURATION. 2. Click ADD and then specify the computer address (Illus. 88) for each local or remote ThinPrint Engine to be configured (Illus. 89). Illus. 88
Illus. 88
Illus. 89
ThinPrint AG 2012
Illus. 89
Specify - local or remote configuration
72
Manual
3. The ThinPrint Engine console appears (Illus. 90). Select on the left, i.e., in the Console Tree: THINPRINT THINPRINT ENGINE AUTOCONNECT. Illus. 90
Illus. 90
Open AutoConnect configuration
Configuration
Click on EDIT SETTINGS (Illus. 90) will open the AutoConnect configuration (Illus. 91).
ThinPrint AG 2012
Manual
73
Illus. 91
Illus. 91
AutoConnect configuration: GENERAL tab
Settings
In GENERAL tab (Illus. 91) 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 manual. Furthermore you can decide here, which events AutoConnect art to be logged and displayed in the AUTOCONNECT DIAGNOSTICS table (Illus. 90). 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. 92). Restart the TP AUTOCONNECT SERVICE afterwards. Here it is also possible to choose the way to set the sessions default printer either the CURRENT PRINTER of the respective THINPRINT CLIENT or the DEFAULT column in MAP ADDITIONAL PRINTERS (Illus. 103)
ThinPrint AG 2012
74
Manual
Illus. 92
Illus. 92
AutoConnect configuration: PRINTER CREATION tab
In PRINTERS tab (Illus. 93) 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 printers properties: The COMMENTS and LOCATION columns of the local Printers folder The native printer drivers properties PAPER SIZE, COLOR, PAPER SOURCE, PRINT ON BOTH SIDES, PRINT QUALITY and FINISHING options. Click APPLY or OK to confirm your settings.
ThinPrint AG 2012
Manual
75
Illus. 93
Illus. 93
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. 94). Illus. 94
Illus. 94
Dynamic Printer Matrix in the MMC ThinPrint AG 2012
Configuration
Double-clicking in the table (Illus. 94) will open the configuration console of Dynamic Printer Matrix (Illus. 95). Use the Buttons (upper arrow) to edit the table.
76
Manual
Illus. 95
Illus. 95
Edit Dynamic Printer Matrix
Assigning templates
Dynamic Printer Matrix assigns any printer to a specific template. For example, the _#ICA_32 template is assigned to the HP DeskJet 460 printer in Illus. 96; the Brother HL-10DV printer 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. 96). Illus. 96
Illus. 96 ThinPrint AG 2012
Dynamic Printer Matrix entries
Table functions
You have the option of hiding unneeded columns (Illus. 97). In all cases, hidden columns (and their rules) are deactivated.
Manual
77
Illus. 97
Illus. 97
Hiding columns
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 18 and 20). 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 AutoConnects 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 81.) 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 ? 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.
ThinPrint AG 2012
78
Manual
Scenario: Remote offices and home users with various connections. Illus. 98
Illus. 98
Connections with different bandwidths require different bandwidth limits (ThinPrint components not shown here)
Each type of connection uses a different IP address range (Illus. 98). 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.1192.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.0255.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 AG 2012
Manual
79
Scenario: Native Printing or Driver Free Printing. Illus. 99
Illus. 99
Windows clients can use Driver Free Printing, all others 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. 99). Client type On the one hand you can select between the client platforms Windows (W), Unix or Linux (U), Java (J) and other (X), and on the other hand between the connection protocols TCP/IP (T), RDP (R) and ICA (I); see also Page 74. 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 26. 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
ThinPrint AG 2012
26 Windows 95 and later
80
Manual
Illus. 100
Illus. 100 Templates for native printing (_#HPLaser) and for Driver Free Printing (_#ThinPrint Output Gateway)
User/Group
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: 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 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.
ThinPrint AG 2012
Manual
81
Illus. 101
Illus. 101 Special lines: try client printer name/try client class name
In the example in Illus. 101, 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 71). 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 ThinPrint Server Engine manual (Page 92).
Script control
If you want to run AutoConnect from the Command Prompt (Page 27) or using a script, amongst others the following parameters can be used: Parameter -v -d -d all -d session_ID Function (Verbose) Display messages; give detailed information at startup Delete the printer(s) for a specific session Delete all printers created with templates (admins only) Delete all printer(s) of a specific session (admins only). The session ID can be found in the Printers folder under LOCATION (Illus. 31 and 32) (Quiet) Error messages are not sent to the client machines desktop
ThinPrint AG 2012
-q
82
Manual
Parameter -r -p port
Function (Repair) Compares saved session information at actually existing printer objects (admins only) (Port) TCP/IP port number (if other than port 4000) Note: The TCP port numbers in ThinPrint Port, AutoConnect, and ThinPrint Client must match. (Interconnection) Select protocol for connection to the ThinPrint Clients; overwrites AutoConnect dialog settings (acceptable values: TCPIP VC, AUTO); see Illus. 91) , 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. SEH TPG120, Page 93). (Help) Will open parameter help panel
-i protocol
-a address
-? or -h
Script control also works for network printer objects which are created with the Dynamic Printer Matrix. 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 (192.168.10.20, ThinPrint Client installed): tpautoconnect d tpautoconnect -a 192.168.10.20 Enter the option disconnect printers in a terminal server logoff script: tpautoconnect d
ThinPrint AG 2012
Manual
83
Map additional printers
Illus. 102
Illus. 102 Open Map Additional Printers
Both scenarios in Illus. 98 and 99 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. 102): User/ Group * Client Name *
Default *
IP Range *
Target \\cps03\lexmark
Please enter the domain in USER/GROUP (see Illus. 103). The following syntax applies27: \\domain\user(group) Unlike its 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 74.
ThinPrint AG 2012
27 You can also enter \\\user(group) if users belong to the same domain as the machine on which AutoConnect is running.
84
Manual
Illus. 103
Illus. 103 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. 90 and 103). 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. 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 37). The EXPORT function (Illus. 103) lets the contents of the tables Dynamic Printer Matrix and Map Additional Printers be written in a .csv file 28 (Illus. 104) 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.
Export/Import
ThinPrint AG 2012
28 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).
Manual
85
Appendix
Illus. 104
Illus. 104 Saving data in a .csv file
Once you are finished configuring AutoConnect, click APPLY or OK.
Appendix
Customer service and technical support
Customer Service www.thinprint.com/ SUPPORT www.thinprint.com/Support/SupportRequest.aspx
Licenses
Entering and activating license keys
Note! Activating a ThinPrint license All license keys are valid for 30 days after they have been entered. They must be activated within this time to continue printing. Demo license keys cannot be activated. A license keys expiration date can be found in License Manager under VALID UNTIL (Illus. 107). Once you have successfully tested the ThinPrint Engine, you can purchase a full license. You will receive a new license key, which is then entered in the License Manager and activated. To activate the license, select SUPPORT & SERVICES SOFTWARE ACTIVATION at the ThinPrint website and follow the instructions. Once your information has been verified, you will receive an activation key by e-mail.
ThinPrint AG 2012
1. Open the License Manager from START (ALL) PROGRAMS THINPRINT ENGINE CONFIGURATION THINPRINT LICENSE MANAGER to enter license keys, check registration keys (for activation), and activate licenses (Illus. 105). 86 Manual ThinPrint Application Server Engine
Appendix
2. The window depicted in Illus. 106 or 107 will open; select the desired function: Add, Activate, Copy, Delete (can be reentered later) or Destroy (cant be reentered) a license key. Caution! License Manager offers the possibility of deleting license keys. Be aware however, that once license keys have been deleted they can not be reentered on the same machine not even if they had been previously activated. Illus. 105
Illus. 105 Starting License Manager: Open configuration console for server components
Illus. 106
Illus. 106 Context menu for one license key
Illus. 107
ThinPrint AG 2012
Illus. 107 Context menu for all license keys
Manual
87
Appendix
License usage
With user-based licensing you can check how many licenses are already used. Select LICENSE USAGE in the respective ThinPrint Engine node (Illus. 108). Afterwards the number of licenses installed on this machine and the number of used licenses are shown (Illus. 109). Illus. 108
Illus. 108 Context menu of ThinPrint Engine node
Illus. 109
Illus. 109 License usage
ThinPrint AG 2012
88
Manual
Appendix Server roles and custom setup

Selecting a server role (Illus. 110) leads to the installation options listed below: Illus. 110
Illus. 110 Select a server role or the CUSTOM SETUP
Server role TERMINAL SERVER
Installation options Print Controller (= ThinPrint Engine) incl. Tracking Service, Output Gateway, AutoConnect, Virtual Channel Gateway, Session in Session and Administration Tools (= MMC components) Print Controller incl. Tracking Service, Output Gateway, AutoConnect, Print-to-Cloud, Print-to-ePaper and Administration Tools Output Gateway, Session-in-Session, AutoConnect and Virtual Channel Gateway MMC components only free choice of components Here you can specifically select and install individual ThinPrint components (Illus. 111). The following components can be selected:

PRINT SERVER
TERMINAL SERVER EXTENSION ADMINISTRATION TOOLS CUSTOM SETUP Custom Installation
ThinPrint AG 2012
Print Controller (=ThinPrint Engine) Tracking Service, see Page 66 Output Gateway (for Windows clients), see Page 50 Output Gateway PS (for non-Windows clients) AutoConnect, see Page 70 Session-in-Session, see Page 90. Administration Tools Installation of ThinPrint MMC components, to remotely configure from this computer another one with ThinPrint components installed on it. System requirements: Windows 8 Classic, 7 SP1, Vista SP2 or XP Professional x64 SP2 or the server operating systems referred to on Page 10. Manual 89
Appendix
Print-to-Cloud (see the ThinPrint Server Engine manual, Page 92) Virtual Channel Gateway (for print server environments only) V-Layer Service (for print server environments only) Illus. 111
Illus. 111 All CUSTOM SETUP options
Session-in-Session
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. 112). Thereby, printers are mapped into the second session and print jobs are passed on from the second to the first server or desktop. Illus. 112
Illus. 112 Session-in-Session: Open a further session from within an existing session ThinPrint AG 2012
Installation, licensing and configuration
You need a ThinPrint Engine on the machine on which the (second) session is running (orange computer in Illus. 112) that means a ThinPrint Application Server Engine on a terminal server or a ThinPrint Desktop Engine on a virtual desktop. Session-inSession is a part of ThinPrint Application Server Engine and does not require its own
90
Manual
Appendix
license. 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 (shown blue). On terminal servers, this can be selected during the installation procedure via CUSTOM SETUP (Illus. 110). Select SESSION IN SESSION (arrow in Illus. 113). This feature functions without any further configuration. An ICA or RDP connection is a prerequisite. Illus. 113
Illus. 113 Custom Installation: Select SESSION
IN
SESSION
Install the Desktop Extension of ThinPrint (Application) Server Engine 9.0 on the middle computer (shown blue) if its a virtual (or real) desktop irrespective of an installed ThinPrint Desktop Engine. If you also want to print from the middle computer, then you need two ThinPrint Engines 29 (on the orange and on the blue computer in Illus. 112). If you are using central print servers, then Session-in-Session is not required, as all computers can print via the print server anyway. Citrix ICA Client later installed If youve installed a Citrix ICA Client after Session-in-Session, uninstall the Sessionin-Session component via custom setup (see Illus. 112), and afterwards reinstall it. Please also note the checklist on Page 28.
Update
If you want to update from ThinPrint 8.6 to 9.0, simply install version 9.0, using the standard setup procedure. The old version will be updated automatically. Your settings will be retained. When updating from ThinPrint 8.0 to 9.0 and you wish to retain your settings, first update from 8.0 to 8.6 and then install 9.0, fully updating 8.0 to 9.0. For updates of ThinPrint Engines older than one year 30, valid license keys are required. These license keys can be purchased via the Update Subscription Program. Please contact your reseller or send an e-mail to info@team.cortado.com.
ThinPrint AG 2012
29 ThinPrint Application Server Engine 9.0 on terminal servers or ThinPrint Desktop Engine on virtual desktops 30 or youre a customer from North America
Manual
91
Appendix Uninstallation
To uninstall a ThinPrint component open PROGRAMS AND FEATURES in CONTROL PANEL. Mark a ThinPrint component and then select UNINSTALL (Illus. 114). Illus. 114
Illus. 114 Uninstalling ThinPrint components
Remote client configuration

Remote configuration is possible for ThinPrint Client Windows printing with TCP/IP protocol. The entry RmtConf is needed in the Windows registry of all client machines you want to configure remotely. More information can be found in the ThinPrint Client Windows or ThinPrint Client Service Windows manuals (see below).
Additional sources
Further information about ThinPrint can be downloaded from our website. Manuals The following manuals and further technical information are available at www.thinprint.com/ PRODUCTS OVERVIEW <product name> MANUALS:

Application Server Engine Quick installation Server Engine ThinPrint Tracking Connected Gateway Unattended installation and licensing of ThinPrint Engine components ThinPrint licensing Tips for configuring ThinPrint ThinPrint addressing ThinPrint Ports ThinPrint Port configuration for bandwidth controlled printing via LPR/LPD Creating SSL/TLS certificates for printing with ThinPrint Windows machine as a Client Gateway Manual ThinPrint Application Server Engine
ThinPrint AG 2012
92
Appendix
SEH ISD400 as a Client Gateway SEH TPG120 as a Client Gateway Preconfiguration and unattended installation of ThinPrint Client Windows ThinPrint Client manuals
White papers
The following white papers (amongst others) are available at www.thinprint.com/ SUPPORT WHITE PAPERS: Centralize your printer drivers Solving problems with fonts
Thin clients and gateways
Thin Clients with embedded ThinPrint Client as well as ThinPrint gateway appliances can be found at www.thinprint.com/ SUPPORT SUPPORTED DEVICES. At www.thinprint.com/Products/Overview/Supportedthinclients.aspx you will find terminals with embedded ICA/RDP type of ThinPrint Client.
Downloads
ThinPrint Engine: www.thinprint.com/ PRODUCTS OVERVIEW THINPRINT APPLICATION SERVER ENGINE DEMO VERSION ThinPrint Clients: www.thinprint.com/ SUPPORT CLIENTS & TOOLS THINPRINT CLIENTS Finishing Detector and ThinPrint Viewture (TPView.exe): www.thinprint.com/ SUPPORT CLIENTS & TOOLS THINPRINT SOFTWARE TOOLS
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 Cortado AG. see AutoConnect
Autocreated printers 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). 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: Number of ThinPrint Ports Different bandwidth settings for each ThinPrint Port Assignment of printers to ThinPrint Ports
Bandwidth control
ThinPrint AG 2012
Class Client
see Printer Class 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 Manual 93
Appendix
forwards it to a printer. Typical clients are: desktop PCs, notebooks, thin clients, print servers, gateway appliances and network printers. Client Gateway Compression see Gateways 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 53) 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 (Page 31). 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). 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). 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 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) Printing using the ThinPrint Output Gateway (see also Page 7) 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 servers performance. See also Data type ThinPrint differs between four kinds of gateways:
Connection Service
Current printer
Data type
Dedicated print server
Driver Free Printing EMF
ThinPrint AG 2012
Gateways
94
Manual
Appendix
1. ThinPrint Output Gateway ThinPrints 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. 3. ThinPrint Client Gateway Local print server with installed ThinPrint Client 4. ThinPrint Connected Gateway ThinPrint Client Gateway connected with ThinPrint Connection Service; for using in networks with Network Address Translation. For local print servers located in masked networks additional ThinPrint licenses are required; see ThinPrint Connected Gateway manual (Page 92). 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. All ThinPrint software requires a license key. The key has the format: THxx-xxxx-xxxxxxx-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 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. 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. An LPD filter is run on LPD clients to decompress print jobs which have been processed over ThinPrint. Line Printer Remote; Program for issuing a print job (Client component for LPD) 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. see Gateways 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. Manual 95
License key
Local resources
LPD client
LPD filter
LPR Network Address Translation (NAT)
ThinPrint AG 2012
Output Gateway AutoConnect
Appendix
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 incl. Windows CE, for Linux, Solaris, DOS, Win OS/2, Java as well as for internal and external print servers of network printers. see Gateways
ThinPrint Client Gateway ThinPrint Client Service Windows
The Windows service version of ThinPrint Client is automatically started when a client machine is activated (only WinNT machines). 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. see Gateways
ThinPrint Connected Gateway ThinPrint Connection Service ThinPrint Engine
see Connection Service
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: 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).
ThinPrint Viewture
ThinPrint component for the client-side print preview with Output Gateway. Viewture consists of the components TPView.dll and TPView.exe with the following features: TPView.dll page preview zoom leaf save in .tpf file format open .tpf file format print
ThinPrint AG 2012
TPView.exe
96
Manual
Appendix
TPView.dll installation with ThinPrint Client can be downloaded (Page 93)
TPView.exe
TPView.dll is also installed together with ThinPrint Engine on non-terminal servers. In this case, it helps with V-Layer. Port pooling Print device s. Page 44 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 The point of interface between operating system and print device is called the printer. In NT architecture alone, many possible terms exist: logical printer, printer software, or printer object. Printer settings include, among others, 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 31 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 manual only distinguishes between printers, printer objects, and print devices when the specific context makes it necessary. 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 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. Under Windows: a printer created over START SETTINGS /CONTROL PANEL PRINT32 ERS (AND FAXES); it appears with its name in the Printers folder . see Port pooling 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 NT terminology as the printer queue. Under NetWare and OS/2, the term printer queue is synonymous for printer.
31 With Windows Server 2008 R2 in Print Management 32 With Windows Server 2008 R2 in Print Management
Printer
Printer class
Printer driver
Printer object
Printer pool Printer queue

ThinPrint AG 2012
Manual
97
Appendix
Print job 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. A print server is that 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 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. see Spooler Remote Desktop Protocol; communication protocol between multiuser NT servers and clients under a Windows operating system. The name of the NT service is Terminal Services, and the connection type under Windows is named Remote Desktop Connection. see RDP
Print server
Print server services
Print spooler RDP
Remote Desktop Connection Remote Desktop Services Remote Desktop Session Host Rendering Session-in-Session
see Terminal Services
see Terminal server
A printer driver is used to translate a print job into printer-specific format. 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. 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 (Windows service denomination: Print Spooler). 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
Spooler
ThinPrint AG 2012
Spooling
98
Manual
Appendix
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. Printer object used as a model to enable automatic client printer connection to ThinPrint Engine over AutoConnect. = Remote Desktop Session Host: a Windows server with Microsoft Terminal Services or Remote Desktop Services = Remote Desktop Services: a Windows service for remote desktop sessions 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. see Gateways
Template
Terminal server
Terminal Services Thin client
ThinPrint Output Gateway 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.33 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. see SSL See ThinPrint Server Engine manual 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. Server-based software (Citrix) for Microsoft Terminal Services; formerly MetaFrame alias Presentation Server
TLS V-Layer x64
XenApp
ThinPrint AG 2012
33 maximum 600 ThinPrint Ports with maximum 800 active printer queues (Windows Server 2003 with 3 GHz Dual Xeon processor, 2 GB RAM, and SCASII ultra3 disk array) or maximum 1500 Queues with Windows Server 2008 R2
Manual
99
Appendix Abbreviations
CSV DLL DNS EMF GPO ICA ID IPv4 IPv6 LAN LPD LPR LPT MMC NAT NTLM OS OU Output Gateway PCL RAW RDP SQL SSL TCP/IP TLS TP TPOG UPN VC VCP V-Layer WinCE WinNT Character/Comma Separated Value Dynamic Link Library Domain Name System Enhanced Metafile (see glossary) Group Policy Object Independent Computing Architecture (see glossary) Identification (number) Internet Protocol address space with 232 addresses; example: 192.168.1.1 Internet Protocol address space with 2128 addresses; example: 2001:0db8:85a3:08d3:1319:8a2e:0370:7344 Local Area Network Line Printer Daemon (see glossary) Line Printer Remote (see glossary) Windows Line Printer Port Microsoft Management Console Network Address Translation NT LAN Manager Operating System Organizational Unit ThinPrint Output Gateway Printer Command Language Standard print data type Remote Desktop Protocol (see glossary) Structured Query Language Secure Socket Layer (see glossary) Transport Control Protocol/Internet Protocol Transport Layer Security ThinPrint ThinPrint Output Gateway User Principle Name Virtual Channel (= ICA or RDP) Virtual Channel Protocol (= ICA or RDP)
ThinPrint AG 2012
ThinPrint Printer Virtualization Layer Windows CE Windows NT 4.0, 2000, XP Vista, 7, 2003, 2008 ,
100
Manual
ThinPrint Engine feature comparison

Application RDP Server Engine Engine Recommended server environments Terminal servers with Windows Server 2012/2008 R2/ 2008/2003 with/without Citrix XenApp Other Windows servers (2012/2008 R2/ 2008/2003 including Cluster Services) as well as environments with central dedicated print servers Windows Server 2012/2008 R2 Core Virtual or real desktops with Windows 7, Vista or XP Supported client environments Windows 8, 7, Vista, XP 2012, 2008 R2, , 2008, 2003 and earlier versions Linux, Mac OS X, Windows CE Plug-and-play installation Unattended installation possible AutoConnect configuration using Group Policies possible SSL encryption Driver Free Printing with V-Layer Driver Free Printing without V-Layer Bandwidth control Network protocols TCP/IP (sockets) ICA RDP LPR/LPD Supported ThinPrint components AutoConnect Virtual Channel Gateway Print-to-Cloud and Print-to-ePaper Tracking Service Desktop Extension Connected Gateway Host Integration Service Management Center
a b c d Cortado AG 2012 Windows Server 2012 in preparation Windows CE only Per encryption of RDP connection only Via Virtual Channel Gateway
Server Engine
V-Layer Basic
Desktop Engine
b c
d d
ThinPrint Engine feature comparison
101

Appl Server Engine en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Appl Server Engine en

Uploaded by

Copyright:

Available Formats

ThinPrint Application Server Engine

E-Mail: info@team.cortado.com Web: www.thinprint.com Issued: December 4, 2012 (v307)

Registered trade marks

ThinPrint Application Server Engine

Sample configuration ............................................................................................ 16

ThinPrint Application Server Engine

ThinPrint Application Server Engine

ThinPrint Application Server Engine

Using ThinPrint with server and client components

ThinPrint Application Server Engine

Advanced Adaptive Compression

Annual licenses TLUS-0688Annual licenses can be server or user based. Manual 7

ThinPrint Application Server Engine

Terminal server(s) Printing via TCP/IP

ThinPrint Application Server Engine

ThinPrint printing with terminal servers over TCP/IP

Terminal server(s) Printing via ICA/RDP

ThinPrint printing with terminal servers over ICA or RDP

Networks behind routers with Network Address Translation (NAT)

ThinPrint Application Server Engine

ThinPrint Application Server Engine

Installation Installing ThinPrint Engine (per terminal server)

Installation with installation wizard

Start the installation program Setup.exe

ThinPrint Application Server Engine

Select the APPLICATION SERVER role

Terminal Server Extension

ThinPrint Application Server Engine

Choose an installation path

Select a licensing type

Entering a license key

ThinPrint Application Server Engine

_#ThinPrint Output Gateway (template)

ThinPrint Application Server Engine

_#ThinPrint Output Gateway printer template in servers Printers folder

Template ThinPrint Output Gateway

Disabling Windows printer mapping

Disabling client printer mapping

ThinPrint Application Server Engine

Configuring RDP configuration

Settings for printer mapping

ThinPrint Application Server Engine

Sample scenario with client and user names

Printer Epson Stylus Color 400

Print mode with native printer driver

DSL (768 kbit/s)

Driver Free Printing

ISDN (64 kbit/s)

Driver Free Printing

Installing ThinPrint Clients

6. Click ASSIGNMENT (Illus. 16).

ThinPrint Application Server Engine

Configuring ThinPrint Client WinCE

Assignment menu: select printer and click EDIT

client1: enabling AutoConnect for a printer

Configuring local print server

ThinPrint Application Server Engine

Printer installed on local print server ps05

Printer ID of the Lexmark T620 (here: 1)

client2: RDP type of ThinPrint Client Windows on a PC

ThinPrint Application Server Engine

Printer installed locally on client2

Opening ThinPrint Configuration