.print Server Engine and .print Printserver Basic Pack ... - ThinPrint

.print Server Engine 

and .print Printserver Basic Pack 

(version 7.6; 32 bit and x64) 

Manual 

ThinPrint AG 

Alt-Moabit 91 a/b 

10559 Berlin 

Germany/Alemania 

ThinPrint Pty. Ltd. 

L 10, 275 Alfred Street 

North Sydney / NSW / 2060 

Australia 

ThinPrint, Inc. 

20525 Center Ridge Rd, Suite 630 

Cleveland, Ohio 44116 

USA/EEUU 

ThinPrint, Inc. 

7600 Grandview Avenue, Suite 200 

Arvada, Colorado 80002 

USA/EEUU 

E-mail: info@thinprint.com 

Web: www.thinprint.com 

Issued: May 5, 2009 (v205)

Notes 

© Copyright 

This document is the intellectual property of ThinPrint 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 ThinPrint products are pure software solutions. Please note the safety warnings in the technical documentation 

from your hardware vendor and from the manufacturer of each device and component. 

Before beginning installation, we recommend closing all windows and applications and deactivating any 

virus scanner. 

How to use this manual 

The following conventions are used throughout this manual to represent recurring actions and text types. 

Conventions 

Note! Important tip, explanation, exception 

SMALL CAPS Menu, command, dialog panel, option 

Italic “Name” Proper name, emphasis, variable 

Courier Keyboard input 

→ Consecutive menu or command 

■ Enumeration, head note 

Example Example 

– 

1. 

2. 

Page 5 

www.cortado.com 

Procedural steps 

2 Manual .print Server Engine 

Links 

© ThinPrint AG 2009

© ThinPrint AG 2009 

Contents 

Introduction ................................................................................................................ 7 

What is ThinPrint .print? ................................................................................................. 7 

Server component ...................................................................................................... 7 

Driver Free Printing and Printer Virtualization Layer ....................................................... 7 

Advanced Adaptive Compression ................................................................................. 8 

Client component ...................................................................................................... 8 

Package contents ...................................................................................................... 8 

Downloads ................................................................................................................ 9 

Scenarios and licenses .................................................................................................. 10 

Host systems and virtual machines – Printing via TCP/IP .............................................. 10 

Terminal server(s) – Printing via TCP/IP ...................................................................... 11 

Terminal server(s) – Printing via ICA/RDP .................................................................. 13 

Which licensing is recommended? ............................................................................. 15 

Installation ................................................................................................................ 15 

Technical restrictions .................................................................................................... 15 

Network ................................................................................................................. 15 

.print Engine ........................................................................................................... 16 

.print Client ............................................................................................................. 16 

Administrator permissions ............................................................................................. 16 

Installing .print Engine (per central, dedicated print server) ............................................... 17 

Update ................................................................................................................... 17 

Upgrade from .print Engine for VMware View to .print Server Engine ............................. 17 

Unattended installation and licensing ......................................................................... 17 

Installation under VMware Workstation 6.0 ................................................................ 17 

Installation with the .print Engine installation wizard ................................................... 17 

License Manager ..................................................................................................... 18 

Output Gateway in mixed environments (Windows 2003/2008) ................................... 22 

Version numbers and update log ................................................................................ 23 

Installing AutoConnect, Virtual Channel Gateway, and Output Gateway (per terminal server or virtual 

desktop) ............................................................................................................... 23 

Overview ................................................................................................................ 23 

Update ................................................................................................................... 23 

.print AutoConnect and .print Virtual Channel Gateway ................................................ 24 

ThinPrint Output Gateway ........................................................................................ 25 

Sample configuration ............................................................................................ 26 

Sample scenario ........................................................................................................... 26 

Installing and configuring .print Clients ........................................................................... 28 

client1: .print Client WinCE (TCP/IP) on a thin client ................................................... 28 

printserver1: .print Client Service Windows on a local print server ................................. 29 

.print Server Engine Manual 3

Contents 

client2: RDP type of .print Client Windows on a PC ..................................................... 30 

Server configuration ...................................................................................................... 30 

printserver2: central print server ................................................................................ 30 

Terminal server farm ................................................................................................ 33 

Printing ....................................................................................................................... 37 

If you still can't print • Checklist .................................................................................... 38 

Setting up ports and printers ............................................................................. 40 

Overview ..................................................................................................................... 40 

ThinPrint Ports ............................................................................................................. 40 

Starting Port Manager .............................................................................................. 40 

Configure tab .......................................................................................................... 44 

Advanced tab .......................................................................................................... 45 

Job Statistics tab ..................................................................................................... 46 

Distributing port configuration ................................................................................... 47 

Installing printers on the ThinPrint Port at the server ........................................................ 52 

.print name conventions ........................................................................................... 52 

Port pooling ............................................................................................................ 54 

LPR/LPD printing with Windows CE or Linux clients ........................................................ 55 

Overview ................................................................................................................ 55 

Preparations on the central print server ...................................................................... 56 

Preparing .print Client (example for Windows CE) ........................................................ 57 

ThinPrint Output Gateway ............................................................................................. 59 

Additional Output Gateway printers ............................................................................ 60 

Compression ........................................................................................................... 61 

Paper formats and trays ........................................................................................... 61 

Presettings on the print server (administrators only) ..................................................... 61 

Settings in a session (on a terminal server or virtual desktop) ........................................ 63 

Printing with preview ............................................................................................... 65 

Printer Virtualization Layer (V-Layer) ............................................................................... 65 

SSL/TLS encryption ...................................................................................................... 67 

Importing SSL certificates on the servers .................................................................... 68 

Importing SSL certificates on the clients ..................................................................... 71 

Print job tracking .......................................................................................................... 73 

Overview ................................................................................................................ 73 

.print Tracking Service .............................................................................................. 74 

.print Tracking Report Engine .................................................................................... 74 

Preparing the .print Engine for tracking ...................................................................... 75 




Contents 

.print AutoConnect ................................................................................................. 76 

Introduction ................................................................................................................. 76 

.print AutoConnect features ....................................................................................... 76 

Basic constellations ................................................................................................. 77 

Where and how to install .print AutoConnect? .................................................................. 78 

.print AutoConnect configuration .................................................................................... 78 

Properties ............................................................................................................... 82 

Name translation (Dynamic Printer Matrix) ................................................................. 82 

Variables ................................................................................................................ 86 

Modes: Output Gateway printers ............................................................................... 90 

Modes: Auto-create and delete printers ...................................................................... 91 

Map additional printers ............................................................................................ 93 

Context menu .......................................................................................................... 93 

Applying changes .................................................................................................... 94 

AutoConnect on central print servers ............................................................................... 95 

.print Virtual Channel Gateway ........................................................................ 97 

Introduction ................................................................................................................. 97 

Installation .................................................................................................................. 98 

On terminal servers .................................................................................................. 98 

On desktop computers ............................................................................................. 98 

Configuration ............................................................................................................... 99 

Using Virtual Channel Gateway .................................................................................... 100 

Printing ..................................................................................................................... 102 

Appendix .................................................................................................................. 103 

Customer service and technical support ........................................................................ 103 

Entering and activating licenses ................................................................................... 104 

Reinstalling, uninstalling or disabling .print components ................................................. 105 

Central print server(s): .print Engine ......................................................................... 106 

Terminal server(s) or virtual desktops: .print AutoConnect, and Virtual Channel Gateway 107 

Terminal server(s) or virtual desktops: ThinPrint Output Gateway ................................ 108 

Central print server(s): Printer Virtualization Layer ..................................................... 108 

Updating .print components ........................................................................................ 108 

.print Server Engine update information .................................................................... 108 

Procedure ............................................................................................................. 109 

Central print server(s): .print Engine ......................................................................... 109 

Terminal server(s) or virtual desktops: .print AutoConnect, and Virtual Channel Gateway 109 


Contents 

Terminal server(s) or virtual desktops: ThinPrint Output Gateway ................................ 110 

Disabling Windows printer mapping ............................................................................. 111 

MMC functions .......................................................................................................... 112 

Examples of context menus in the MMC ................................................................... 112 

Context menu functions at a glance ......................................................................... 113 

Remote client configuration .................................................................................... 116 

Additional sources ...................................................................................................... 117 

Glossary .................................................................................................................... 118 

Abbreviations ............................................................................................................. 125 

.print Engine feature comparison .................................................................................. 127 




Introduction 

What is ThinPrint .print? 

Introduction 

ThinPrint .print is a software solution and consists of a server and a client component 

– the .print Engine and the .print Client (Illus. 1). 

Illus. 1 

Illus. 1 Using of ThinPrint .print with server and client components 

Server component 

The server component .print Engine is the actual core of the ThinPrint .print framework. 

It provides complete printer driver management including Driver Free Printing. 

The .print 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 TP Output Gateway 

(enables a radical reduction of printer drivers on printing computers 

= Driver Free Printing). 

■ Auto-created client printers are created by .print AutoConnect, a component of 

the product .print Server Engine. 

Driver Free Printing and Printer Virtualization Layer 

Thanks to this technology, time-consuming server-side installation and administration 

of printer drivers under Windows are no longer necessary. Printer driver conflicts 

are also a thing of the past. 

With Driver Free Printing, 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 


Introduction 

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. Just with Printer Virtualization 

Layer 1 , the printer drivers are not installed on the client side; they are only 

installed on the central print server. 

Advanced Adaptive Compression 

Furthermore, .print Engine combines the efficient Driver Free Printing system with a 

completely new kind of compression, the Advanced Adaptive Compression. This 

method analyzes the individual components of a print job and compresses each with 

the respective best algorithm before transmitting the data. 

Additionally, user errors that can occur when saving a document are corrected. In 

this way, data volume is reduced by 98%. 

Client component 

On the client side, .print Client is generally responsible for receiving print data, 

decompressing it, and sending it to the print device. Many .print Clients are available 

for different end devices and areas of deployment: for all Windows versions incl. 

Windows CE, for Linux, Solaris, DOS, Java, ActiveX, as well as for internal or external 

print servers of network printers 

All .print Clients can be downloaded from www.thinprint.com. The website also 

includes a current listing of devices which are already embedded with .print Clients. 

If you require a .print Client which is not listed on the website, please send an e-mail 

to info@thinprint.com. 

Package contents 

The .print Server Engine product CDs for .print version 7.6 contain: 

■ This manual 

■ The installation program Setup.exe for .print Engine 

(under ...\Software\.print Engine) 

In addition, you should have received license keys from your reseller or by e-mail from 

ThinPrint. Depending on the purchased Product version (32 bit or x64) and on the 

1 V-Layer, formerly Driver Free Native Printing (DFNP) 




Introduction 

selected license type, (server or user based), select the license key from the following 

types: 

Product version 

Licensing type 

Server-based User-based 

32-bit THPS-0388-1 

(basic license key: 

Server Engine) 

THSA-0388-1 

(Server Access license keys 

– supplied with Application 

Server Engines) 

64-bit TAPS-0388-1 


Server Engine) 

THSA-0388-1 

(Server Access license keys 

– supplied with Application 

Server Engines) 

TPPS-0388-1 


Printserver Basic Pack) 

TPUS-0388-10 

(license key for 10 Named 

Users) 

TPPS-0388-1 


Printserver Basic Pack) 

TPUS-0388-10 

(license key for 10 Named 

Users) 

When purchasing user based licensing, it is usual to buy as many licenses as there 

are users in terminal-server, virtual-desktop, or host environments. Therefore you 

may have received further TPUS licenses, for example TPUS-0388-20 for 20 named 

users, TPUS-0388-100 for 100 named users etc. 

You will have only received the Server Access license key(s) if you are using the 

.print Server Engine together with Microsoft or Citrix terminal servers. 2 A specific 

Server Access license is available for non-Windows systems such as Unix servers, 

AS/400 machines, or IBM mainframes (= .print Host Access License). 

Downloads 

■ .print Clients for different platforms can be downloaded from: 

www.thinprint.com/→ SUPPORT & SERVICES→ SOFTWARE DOWNLOAD→ .PRINT 

CLIENT COMPONENTS 

■ All .print Engine program versions can be downloaded from: 

www.thinprint.com/→ FIND PRODUCT→ .PRINT SERVER ENGINE→ DEMO 

For updates of .print Engines older than one year, valid license keys are 

required. These license keys can be purchased via ThinPrint’s Update Subscription 

Program. Please contact your reseller or send an e-mail to info@thinprint.com. 

2 Alternatively, for larger terminal-server environments, a single Server Access license key can be 

supplied for all application servers, e.g. THSA-0388-25 for a farm with 25 terminal servers. 


Introduction 

Scenarios and licenses 

The following sample scenarios illustrate typical environments in which ThinPrint 

.print can be deployed. The depicted scenarios can also be combined – flexibility in 

mixed environments is one of the many strengths of ThinPrint .print. 

An accompanying table displays, for each case, what type of license key can be 

used in each environment. More information about .print licensing is found starting 

on Page 104. 

Host systems and virtual machines – Printing via TCP/IP 

The main purposes of centralized, dedicated print servers are to centralize print 

administration and to remove workload from other servers and/or host systems. 

.print Engine makes it possible to compress print data received by hosts or virtual 

machines (= virtual desktops), to encode it and, within bandwidth limits, send it to 

client computers or to network printers, (Illus. 2). If Windows hosts or virtual 

Windows desktops are being employed, it is also possible to use Driver Free Printing 

and Printer Virtualization Layer (= Driver Free Native Printing). 

Each user can use all printers in the network which are reachable 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 in this manual starting on Page 26. 

Illus. 2 

Illus. 2 .print printing via a central print server (example) 




Licensing License name 

License 

type 

Introduction 

Installed on ... 

Server-based .print Server Engine 32 bit THPS Central print server 

.print Server Engine 64 bit TAPS Central print server 

Server Access (if Windows 

terminal servers existent) 

User-based .print Printserver Basic Pack 

(32 bit/x64) 

THSA Central print server 

TPPS Central print server 

(Named) User licenses TPUS Central print server 

(per named user) 

Terminal server(s) – Printing via TCP/IP 

Connected to Microsoft or Citrix terminal servers 3 , central printer servers can make 

Driver Free Printing available not only for Windows clients, but also for non-Windows 

clients and network printers (= Printer Virtualization Layer). 

In the case of a terminal server environment, the print server’s protocol (TCP/IP) 

is different than the terminal server’s protocol (ICA or RDP; Illus. 3). Further information 

can be found in this manual starting on Page 26. 

3 with Microsoft Terminal Services or Citrix XenApp 


Introduction 

Illus. 3 

Illus. 3 Central print server printing via TCP/IP 


Server-based .print Server Engine 

32 bit 


64 bit 

Server Access licenses 

(32 bit/x64) 

User-based .print Printserver Basic 

Pack (32 bit/x64) 

License 

type 


THPS Each central print 

server 

TAPS Each central print 

server 

THSA Each central print 

server (per Windows 

terminal server) 

TPPS Each central print 

server 

(Named) User licenses TPUS Each central print 

server (per named 

user) 

If necessary, addressing .print Clients in masked networks via TCP/IP is made possible 

with the .print Connection Service (Illus. 4). Further information can be found in 

the “.print Connected Gateway” manual; see also Page 117. 




Illus. 4 

Illus. 4 Central print server printing via TCP/IP despite NAT 



32 bit 


64 bit 


(32 bit/x64) 

License 

type 

Introduction 



server 

TAPS Each central print 

server 




.print Connection Service THCG Any central server 

(per local print server) 




server 



user) 

.print Connection Service THCG Any central server 

(per local print server) 

Terminal server(s) – Printing via ICA/RDP 

Central, dedicated print servers generally print to a client or network printer via 

TCP/IP (Illus. 3). If, however, TCP/IP is not possible or not wanted as print protocol, 

the .print Virtual Channel Gateway allows print data to be sent through the ICA or 

RDP virtual channel to the client (Illus. 5). 

The .print Virtual Channel Gateway receives TCP/IP print jobs from the central 

print server, converts addressing from TCP/IP to ICA or RDP, and forwards the print 

data on to the session user. Further information can be found in this manual starting 


Introduction 

on Page 26 and in the “.print AutoConnect and .print Virtual Channel Gateway” 

white paper; see also Page 117. 

Illus. 5 

Illus. 5 Central print server printing via ICA or RDP 



(32 bit) 

License 

type 



server 

.print Server Engine x64 TAPS Each central print 

server 


(32 bit/x64) 







server 



user) 

For further scenarios see the “.print Management Center” manual (Page 117). 




Installation 

Which licensing is recommended? 

Server-based licensing User-based licensing 

SBC and client/server environments 

without a central print server 

• .print Application Server Engine 

Midsize and large SBC environments 

• .print Application Server Engine or 

• .print Server Engine + Server 

Access licenses (Illus. 3 to 5) 

Virtual desktop environments (VDIs) 

without a central print server 

•.print Desktop Engine 

Environments with a central print 

server (Illus. 3 to 5) 

• .print Server Engine + Server 

Access licenses 

Installation 

The user-based licensing is possible for terminal server farms only if central print 

servers are used. 

Technical restrictions 

Your architecture must meet certain requirements to run .print Engine. Please ensure 

that the following network, server and client requirements are met. 

Network 

ThinPrint .print works in a network architecture. One of the following must be 

installed: 

■ TCP/IP network with at least one printer 

Environments with a central print server 

(Illus. 3 to 5) 

• .print Printserver Basic Pack 

+ (Named) User licenses 

Small SBC environments 

with overall maximum 20 users 

• .print Application Server Basic Pack 


Virtual server and desktop environments 

with a central print server 

(Illus. 2) 



Non-SBC environments like WAN connections, 

client server architectures, 

mobile or web applications (Illus. 2) 



Be sure that the TCP port number/s for printing via TCP/IP is/are not being blocked 

by another program or by a server-side or client-side firewall. IPv4 has to be enabled 

for all involved machines. 


Installation 

.print Engine 

ThinPrint .print requires the following: 

Supported server operating systems 

■ Windows Server 2003 with Service Pack 1 or later 

■ Windows Server 2003 x64 with Service Pack 1 or later 

■ Windows Server 2008 4 

■ Windows Server 2008 x64 4 

Windows Server Cores are not supported. 

Minimum hardware requirements 

32 bit: Intel Pentium/Celeron, AMD K6/Athlon/Duron 

or compatible processor with 733 MHz, 256 MB RAM, 

3.5 MB of available hard disk space 

x64: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T, 

Intel Pentium with Intel EM64T, 

system clock 1,4 GHz, 512 MB RAM, 

10 MB of available hard disk space 

.print Client 

Supported .print Clients 5 : 

■ Windows Vista/Vista x64/XP/XP x64/2003/2003 x64/2000/NT 4 

(TCP/IP, ICA, RDP); XP: Service Pack 1 and later 

■ As a Windows service: Vista/Vista x64/XP/XP x64/2003/2003 

x64/2000/NT 4 (TCP/IP); XP: Service Pack 1 and later 

■ Windows 9x/ME (TCP/IP, ICA, RDP) 

■ Windows CE (TCP/IP, ICA, RDP) 

■ MS-DOS (TCP/IP) 

■ Windows 3.11, Win OS/2 (TCP/IP) 

■ Linux (TCP/IP), Solaris (TCP/IP) 

■ Java (TCP/IP, ICA) 

■ ActiveX – Windows NT 4/2000/XP/2003 (TCP/IP) 

■ ActiveX – Windows 9x / ME (TCP/IP) 

Administrator permissions 

Administrator permissions are required for all installation and configuration procedures. 

It is therefore best to log on under Windows as ADMINISTRATOR. 

To open the PRINTERS folder on Windows Server 2008 machines as an administrator 

use START→ PROGRAMS→ .PRINT ENGINE→ PRINTERS. 

4 incl. Microsoft Hotfixes KB958741 (Printjob Owner) and KB958656 (Client Side Rendering). 

5 ICA and RDP via .print Virtual Channel Gateway only 




Installing .print Engine (per central, dedicated print server) 

Update 

For update installation, see “Updating .print components” (Page 108). 

Installation 

Upgrade from .print Engine for VMware View to .print Server Engine 

To upgrade from the .print Engine for VMware View to the .print Server Engine reinstalling 

the .print Engine is not necessary. Simply complete the following steps: 

1. Add the .print Server Engine license keys using the License Manager 

(Page 104). 

2. Install the upgrade component SEAdmin. Depending on your operating system 

use one of the following .msi files: 

English German 

32 bit SEAdmin_x86EN.msi SEAdmin_x86DE.msi 

x64 SEAdmin_x64EN.msi SEAdmin_x64DE.msi 

Note! For further information see the “.print Engine for VMware View” manual 

for .print AutoConnect configuration on(Page 117. 

Unattended installation and licensing 

Unattended installation and licensing are also possible; refer to the White Paper 

“Unattended installation and licensing of .print server components” Page 117. 

Installation under VMware Workstation 6.0 

If VMware Tools of VMware Workstation 6.0 are already installed please uninstall 

them before installation of a .print component. Alternatively, VMware Tools of 

VMware Server 1.0.x can be used. 

Installation with the .print Engine installation wizard 

Install .print Engine according to the scenario in illustration Illus. 2. 

Note! Before beginning installation, we recommend closing all windows and 

applications and deactivating any virus scanner. Also be aware that after 

installation .print Engine will only become functional after a Windows restart 

(Windows Server 2003 only). 

1. Copy the ThinPrint server software to the print server’s hard disk and start 

Setup.exe (Illus. 6). 


Installation 

Entering 

a license key 

Illus. 6 

Illus. 6 Starting installation program Setup.exe 

2. Choose a language and confirm with OK. 

3. Read the license agreement and ACCEPT it. The menu in Illus. 7 will open. 

4. Select INSTALL .PRINT ENGINE. 

Illus. 7 

Illus. 7 .print Engine installation menu: 

Click INSTALL .PRINT ENGINE 

(Windows Server 2008 and 2003) 

Note! Note that the print spooler is restarted during installation of .print 

Engine. 

License Manager 

5. The prompt shown in Illus. 8 reminds you to have your .print Server Engine 

(demo) license key(s) ready. Click OK, and the License Manager will open 

(Illus. 9). 




Illus. 8 

Illus. 9 

Illus. 8 Tip: Have (demo) license key(s) ready 

(example for Windows Server 2003) 

Illus. 9 License Manager: select ADD LICENSE KEY 

Installation 


Installation 

6. Select ADD LICENSE KEY in the context menu of the LOCALHOST server node 

(Illus. 9) and enter your license keys for the .print Server Engine. (If you do not 

have license keys, contact your reseller.) 

Note! For both licensing types you need minimum two license keys per 

central print server: either with server-based licensing one for the print 

server (THPS/TAPS) and minimum one for each computer using the 

print server (THSA), or with user-based licensing one for the print server 

(TPPS) and minimum one for the number of users (TPUS); see the table 

below. 

For the LICENSE/ACTIVATION SET option see Page 114 and the “Unattended 

installation and licensing of .print server components” white paper, Page 117. 

Licensing License name Type of license key 


32-bit; per print server or 

cluster node 


64-bit; per print server or 

cluster node 

Server Access or Host 

Access license(s) 

(at least 1); per computer 

printing to central print 

server(s) 


Pack (32-bit/x64); per 

print server or cluster 

node 

THPS-0388-1-xxxxxx-xxxx 

TAPS-0388-1-xxxxxx-xxxx 

THSA-0388-1-xxxxxx-xxxx 

TPPS-0388-1-xxxxxx-xxxx 

(Named) User licenses TPUS-0388-yy-xxxxxx-xxxx 

Note! All license keys are installed on the central print server, none on 

application servers, hosts or virtual desktops. With more than one print 

server the license keys of Server Access, Host Access, or (Named) User 

licenses are distributed among all print servers; a multiple installation of 

these license keys and hence activation (on each node) is allowed within 

a cluster only – with the exception of licenses contained in .print Printserver 

Basic Pack. 

Splitting up licenses of an individual key is not possible. 




Illus. 10 

Installation 

7. Click OK to confirm (Illus. 10). The license key(s) now appear(s) under LICENSE 

KEY (Illus. 11 or 12). 

Illus. 11 

Illus. 12 

Illus. 10 Enter license key (example) 

Illus. 11 License key entered 

(example for server-based licensing with one terminal server, 32-bit) 

Illus. 12 License keys entered (example for user-based licensing with 10 users) 

8. Close the License Manager to continue with the installation. 

Note! Once a license key has been entered, it is valid without activation for 

30 days. See Page 104 for information about activating licenses. 

9. To complete installation the server needs to be restarted (Windows Server 2003 

only). You can do this immediately (YES in Illus. 13). Or if you choose NO the 

ThinPrint software will become operational next time the server is restarted. 

Caution! Before you restart the server make sure that no data will be lost. 

Ensure that all applications are closed and no print jobs active. Selecting YES 

will Restart immediately. If in doubt, select NO (see arrow in Illus. 13). 


Installation 

Illus. 13 

Illus. 13 Restart the server: Now or later? (Windows Server 2003 only) 

If you selected NO, .print Engine installation has been completed successfully when 

the statement “Installation complete” in the installation menu appears (Illus. 14). 

(Note: Enter the installation window via START→ PROGRAMS→ .PRINT ENGINE→ 

SETUP.) 

10. CLOSE the .print Engine installation menu (Illus. 14). 

Illus. 14 

Illus. 14 Closing the .print Engine installation menu 


Output Gateway in mixed environments (Windows 2003/2008) 

The following installation is only required if you access a Windows print server 2003 

from a Windows Server 2008. In this case, install both Output Gateway drivers (x86 

and x64) on the print server 2003, as shown in Illus. 15. 




Illus. 15 

Illus. 15 Two Output Gateway drivers on a print server 

Installation 

Version numbers and update log 

The .print Engine installation program offers two further useful options (Illus. 14): 

■ VIEW LOG FILE is used to monitor the installation as well as to save this information 

to a file (see above note). 

■ VIEW VERSION INFORMATION displays which files are installed where on your system 

and allows you to save this information to a file. 

Installing AutoConnect, Virtual Channel Gateway, and Output Gateway 

(per terminal server or virtual desktop) 

Overview 

Terminal server or virtual desktop installation is only necessary if one of the following 

.print components is to be used with a print server on which .print Engine is installed: 

■ .print AutoConnect 

■ .print Virtual Channel Gateway 

■ ThinPrint Output Gateway 

Update 



Installation 

Installation on 

terminal servers 

Installation on 

virtual desktops 

.print AutoConnect and .print Virtual Channel Gateway 

Note that there is a slight difference between the Virtual Channel Gateway for virtual 

desktops and for terminal servers. 

To install .print AutoConnect and .print Virtual Channel Gateway, use the .print 

Engine CD. 

1. Copy the ThinPrint server software to the terminal server’s or virtual desktop’s 

hard disk and start Setup.exe (Illus. 16). 

Illus. 16 

Illus. 16 Starting installation program Setup.exe 

2. Choose a language and confirm with OK. 


4. Select INSTALL AUTOCONNECT and/or INSTALL VC GATEWAY. 

Illus. 17 

Illus. 17 .print Engine installation menu: Click INSTALL AUTOCONNECT and/or (then) 

INSTALL VC GATEWAY 

For the following steps see .print Engine installation on central print server (Page 18). 

For .print AutoConnect installation see “Installation on terminal servers” (above). 


desktops and for terminal servers 6 . Please use the version dedicated to virtual 

environments, and not the one delivered with .print Server Engine (free download at 

www.thinprint.com). 




Installation 

1. Copy the files TPVCGateway.exe, tpicaw32.dll, and tprdpw32.dll onto the virtual 

machine (best you create a program directory such as C:\Programs\ThinPrint). 

2. Install the file TPVCGateway.exe from the program directory with the Command 

Prompt: 

TPVCGateway.exe -install 

3. In the SERVICES folder, start TPVCGateway.exe manually (Illus. 18). 

Illus. 18 

Illus. 18 Starting the Virtual Channel Gateways service manually 

The service runs on port 4000. Make sure that no other application is using this port. 

Once installed, the Virtual Channel Gateway requires no further administration. 

ThinPrint Output Gateway 

1. Install the ThinPrint Output Gateway virtual printer driver in the server’s PRINT- 

ERS (AND FAXES) folder with FILE→ SERVER PROPERTIES→ DRIVER→ ADD→ 

NEXT→ HAVE DISK→ BROWSE. Select OEMPRINT.inf from the TPOG3 folder of 

the .print Engine CD. 

2. Confirm the following window with OK→ NEXT→ NEXT→ FINISH. 

3. Once installation is complete, close the server properties window (Illus. 19). 

6 When using the Virtual Channel Gateway on terminal servers, you need to enter the IP address of 

the print server, but this is not required in virtual environments. Please note also, that because 

the virtual desktop version cannot handle multiple user sessions, it cannot be used on terminal 

servers. 


Sample configuration 

Illus. 19 


Sample scenario 

Illus. 19 Virtual driver installed; CLOSE print server properties 

The installation wizards for the .print Engine server component and the .print Client 

Windows client component are preprogrammed so that when .print Engine is 

installed onto a Windows terminal server, it is possible to print immediately after 

installation is complete with no further configuration (see “.print Application Server 

Engine” user manual; Page 117). 

In contrast, this section describes how .print Engine can be run on a central, dedicated 

print server (Page 17). Here too, it may be necessary to install .print components 

on the Windows terminal servers: 

■ ThinPrint Output Gateway 

■ .print AutoConnect 

■ .print Virtual Channel Gateway 

The main configuration options are illustrated here using a sample scenario as example 

(Illus. 20). The following descriptions refer to the sample scenario below. 




Machine 

name 

Illus. 20 


Our scenario attempts to combine a couple of typical client and connection types in 

a terminal server environment. Client types are a PC and a thin client as well as a 

local print server. 

The following table describes the print environment necessary in the sample configuration 

(Illus. 20). 

User 

name 

Illus. 20 Sample scenario with client and user names 

Printer 

client1 user1 Epson Stylus 

Color 400 

printserver1 

(local print 

server) 

— Lexmark 

T620 

Connection 

to Server 

DSL 

(768 kbit/s) 

DSL 

(768 kbit/s) 

client2 user2 HP DeskJet ISDN 

(64 kbit/s) 

printserver2 

(central print 

server) 

.print Client type Print mode 

TCP/IP type of 


WinCE 


Service Windows 

(TCP/IP) 

RDP type of 


Windows 

With native 

printer driver 

Driver Free Printing 


— — LAN (1 Gbit/s) — With native 

printer driver and 


The ICA protocol can also be used instead of RDP. In this case, all RDP specific 

installations and configurations must be made for ICA. 



Installing and configuring .print Clients 

client1: .print Client WinCE (TCP/IP) on a thin client 

1. For this sample scenario, choose a thin client with embedded .print Client. 

A list of these devices can be found at www.thinprint.com/. 

2. Open the control panel on the thin client and select THINPRINT (click OPEN, 

Illus. 21). 

Illus. 21 

Illus. 21 .print Client WinCE in the control panel (example for Neoware terminals) 

3. Enable the .print Client (ENABLE THINPRINT; Illus. 22 left). 

4. Select the protocol you will select for the share Epson on the central print server 

(THINPRINT OVER TCP or TCP/IP, Page 32), and click OK (Illus. 22 left). 

5. Open the .print Client configuration menu (CONFIGURE THINPRINT; Illus. 22 

right). 

Illus. 22 

Illus. 22 Selecting and enabling .print Client WinCE 

and opening configuration menu (example for Neoware terminals) 

6. Click ASSIGNMENT (Illus. 23). 




Illus. 23 


7. Select a printer, e.g., LPT1:, and enter a printer name under EDIT PRINTER (in 

the sample scenario, Epson Stylus Color 400; Illus. 24). 

8. Enable .print AutoConnect for this printer by marking the checkbox to the left 

of the printer name (Illus. 25). 

9. Finish configuration by clicking OK. 

10. Close the thin client’s control panel. 

Illus. 24 

Illus. 25 

Illus. 23 Configuring .print Client WinCE 

Illus. 24 Assignment menu: select printer and click EDIT PRINTER 

Illus. 25 client1: enabling .print AutoConnect for a printer 

printserver1: .print Client Service Windows on a local print server 

1. For the sample scenario, install a Lexmark T620 printer (Illus. 26). 

2. Install .print Client Service Windows; please refer to the “.print Client Service 

Windows” user manual (Page 117). 

Illus. 26 

Illus. 26 Local printer installed on printserver1 



Illus. 27 .print Client in 

the task bar 

Creating 

ThinPrint Ports 

Illus. 27 

3. Once installation is complete, .print Client Service Windows will be started and 

its icon appears in the task bar of the local Windows installation (Illus. 27). It 

does not need to be configured for the sample installation. 

client2: RDP type of .print Client Windows on a PC 

Requirement: An RDP client is installed (= Remote Desktop Connection) – default 

with Windows XP and later. The scenario in Illus. 20 (Page 28) applies. 

1. For the sample scenario, install a HP DeskJet printer (Illus. 28). 

2. Install .print Client Windows and select .PRINT CLIENT WINDOWS RDP during the 

installation; please refer to the “.print Client Windows” user manual 

(Page 117). 

.print Client is started automatically with a Remote Desktop Connection. It does 

not need to be configured for the sample installation. 

Illus. 28 

Server configuration 

Illus. 28 Printer installed locally on client2 

printserver2: central print server 

Requirement: .print Engine has already been installed (Page 17). The scenario in 

Illus. 20 (Page 28) applies. 

1. Open the ThinPrint Port configuration (in the MMC) with START→ PROGRAMS 

→ .PRINT ENGINE→ PORT MANAGER (Illus. 29). 

Advice: The ThinPort: printer port shown in Illus. 30 (right arrow) including the 

printer ThinPrint Output Gateway will not be used in the sample scenario. 

Illus. 29 

Illus. 29 Starting Port Manager (example for Windows Server 2008) 




Illus. 30 


2. Create the following ThinPrint Ports by clicking the NEW THINPRINT PORT icon 

(left arrow in Illus. 30) and set bandwidth and protocol (Illus. 31 and 32): 

Port name Port type (protocol) Bandwidth 

TCP1: TCP/IP (sockets) 256 kbit/s 

RDP1: USE VIRTUAL CHANNEL GATE- 

WAY 

Illus. 31 

Illus. 30 ThinPrint Port in Port Manager 

32 kbit/s 

Illus. 31 Selecting port type and bandwidth for port “RDP1:”; click APPLY 



Illus. 32 

Note! It is possible to create multiple ports each for the ThinPrint Ports TCP1: 

and RDP1: and group these in printer pools. For more information, see “Port 

pooling” (Page 54) and the “ThinPrint Ports” white paper (Page 118). 

Creating printers 3. In the server’s PRINTERS (AND FAXES) folder, create the following printer(s) and 

share them (Illus. 33): 

Printer name 

Illus. 33 

Illus. 32 Two new ThinPrint Ports 

ThinPrint 

Port 

Printer 

driver 

Epson Stylus Color 400#client1:2 TCP1: Epson Stylus 

Color 400 

Esc/P2 

Lexmark T620#printserver1 TCP1: TP Output 

Gateway 

HP DeskJet RDP1: TP Output 

Gateway 

Note! In larger environments you can also automate printer setup using 

.print AutoConnect (or using .print Management Center). 

Refer to the section “AutoConnect on central print servers” (Page 95). 

Illus. 33 Three new printers 

Share 

name 

Epson 

Lexmark 

DeskJet 





4. Change to the port configuration (in the MMC) and check that the new printers 

have been assigned correctly to the ThinPrint Ports (Illus. 34; if necessary, 

press F5 to refresh). 

Illus. 34 

Illus. 34 The new printers assigned to the ThinPrint Ports 

Terminal server farm 

All settings will be performed on each terminal server in a server farm (for 

import/export and sending configuration see Page 113). Requirement: .print Auto- 

Connect, .print Virtual Channel Gateway, and ThinPrint Output Gateway have 

already been installed (Page 23). 

.print AutoConnect 1. Open the AutoConnect configuration in the MMC with START→ PROGRAMS→ 

.PRINT ENGINE→ AUTOCONNECT (Illus. 35). 

Illus. 35 

Illus. 35 Starting AutoConnect configuration (example for Windows Server 2003) 

2. To ensure that AutoConnect can create printers both for RDP and for TCP/IP 

printing, select AUTO under TRANSFER PROTOCOL (Illus. 35). Click APPLY. 



Illus. 36 

3. Click the NAME TRANSLATION tab. 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: 

4. Click APPLY. 

Illus. 37 

Illus. 36 .print AutoConnect in the MMC: select AUTO 

IP Range Client Name Printer Name Target 

* *2 * \\printserver2\DeskJet 

* * Eps* \\printserver2\Epson 

Illus. 37 .print AutoConnect: name translation table 

5. Enable the AUTO-CREATE AND DELETE PRINTERS function on the AUTO-CREATE 

PRINTERS tab (Illus. 38). Click APPLY. 




.print Virtual 

Channel Gateway 

Illus. 38 


6. Select the MAP ADDITIONAL PRINTERS (Illus. 39). To enable AutoConnect to create 

the printers from printserver1 for the session from user1, add the following 

lines: 

Illus. 39 

Illus. 38 Enabling .print AutoConnect auto mode 

IP Range Client Name Target 

* *1 \\printserver2\Lexmark 

Illus. 39 .print AutoConnect: enter additional printers 

1. Open Virtual Channel Gateway configuration in the MMC with 

START→ PROGRAMS→ .PRINT ENGINE→ VIRTUAL CHANNEL GATEWAY (Illus. 40). 



Illus. 40 

Illus. 40 Starting Virtual Channel Gateway configuration 

2. Click ADD to enter the central print server’s IP address (Illus. 41). 

Illus. 41 

Illus. 41 .print Virtual Channel Gateway: Entering .print Engine IP address(es) and 

checking TCP port number (example; see also Illus. 42) 

3. Check the TCP port number; it must match with the ThinPrint Port number on 

the central print server (Illus. 42). Click APPLY. 

Illus. 42 

Illus. 42 TCP port number for ThinPrint Port “RDP1:” (see also Illus. 41) 




Printing 


– Establish a Remote Desktop Connection (or an RDP connection) from each client 

machine to the terminal server farm; as in our example, log on as “user1” 

and “user2”, respectively. The printers in Illus. 43 and 44 appear in the PRINT- 

ERS (AND FAXES) folder in the two sessions. 

– Open an application and print with each of these printers. 

Illus. 43 

Illus. 44 

Illus. 43 Printers from “user1” in an RDP session as in the example 

Illus. 44 Printer from “user2” in an RDP session as in the example 

Print jobs will be received from the .print Clients and forwarded to the printers as follows: 

Client name Protocol Addressed printer ID Target printer 

client1 TCP/IP 2 Printer with ID 2 

printserver1 TCP/IP no .print Client’s 

“Current Printer” 

client2 RDP no .print Client’s 




If you still can't print • Checklist 

If .print AutoConnect does not create the desired printers or printing itself does not 

work properly, please check the following before contacting ThinPrint support 

(Page 103). 

■ If you run Windows Server 2008 or Windows Server 2008 x64: 

Did you install the Microsoft Hotfixes KB958741 (Print Job Owner) and 

KB958656 (Client Side Rendering)? (footnote on Page 16) 

■ Is the same protocol selected for the .print Client, the ThinPrint Port, and .print 

AutoConnect? Example for RDP: 

• Is the RDP type of the .print Client installed on the client machine? (Page 30) 

• To which ThinPrint Port is the printer for this .print Client connected? USE VIR- 

TUAL CHANNEL GATEWAY (Illus. 31) must be enabled in the port configuration 

(MMC) on the central print server. 

• For .print AutoConnect, either VIRTUAL CHANNEL (ICA OR RDP) or AUTO must 

be set as connection protocol on the terminal server (Illus. 36). 

•Is TPAUTOCONNECT SERVICE (Windows service) running on each terminal 

server? 

Note! For printing using ThinPrint Ports the Windows service 

TP AutoConnect Service has to be run together with the .print Engine 


■ If USE VIRTUAL CHANNEL GATEWAY (above) is selected in the central print server 

port configuration, please also check the following: 

• Is/are the IP address(es) of the central print server(s) entered in the .print Virtual 

Channel Gateway configuration on the terminal servers (Illus. 41)? 

• Are the TCP port numbers the same for the ThinPrint Port and the .print Virtual 

Channel Gateway? (Illus. 41 and 42) 

•Is TPVCGATEWAY SERVICE running on each terminal server? 

■ If TCP/IP is the selected protocol: 

• Are the port numbers the same on server and client (see port configuration in 

MMC on the central print sever (Illus. 52) and .print Client Manager)? 

• Are you sure that the TCP port number is not being blocked by the firewall or 

by another program (e.g., .print Virtual Channel Gateway)? 

• Is the client machine in a masked network (NAT)? If so, you must either select 

ICA or RDP, or additionally install the .print Connection Service (see also the 

.print Connected Gateway user manual; Page 117). 

■ If a printer was created manually (see “Lexmark T620#printserver1” in 

Illus. 33), check the name convention of the ThinPrint Port (see port configuration 

in MMC on the central print sever and Illus. 54). 

■ If you selected USE ENCRYPTION on the server (Illus. 42), continue reading the 

section “SSL/TLS encryption” (Page 67), or disable encryption for now. 

■ If AutoConnect doesn’t install printers establish a printer connection (as an 

Administrator) from the terminal server or virtual desktop to a shared Output 

Gateway printer on the central print server manually once. The resulting printer 

connection (Illus. 45) can be deleted afterwards. 




Illus. 45 


Illus. 45 Connection to a Output Gateway share on the central print server (example) 

■ When .print AutoConnect starts (on the terminal server), are the correct shares 

on the central print server connected (see Illus. 33)? The entries in the name 

translation table must refer to the printer shares (Illus. 37). Check .print Auto- 

Connect working by starting it manually: Open the Command Prompt in a terminal 

session, change to the .print Engine’s program directory 7 and enter the 

following to create the session printers: 

TPAutoConnect -v [-i VMware -a COM1] 

And to delete them: 

TPAutoConnect -d 

If the session printers can be created manually by entering TPAutoConnect 

in the command line but are not automatically created when the session is 

started, check all .print AutoConnect settings (Illus. 36 to 38). 

■ Testing the TCP/IP connection: For printing via TCP/IP, a TCP/IP connection 

must exist between server and client which allows direct communication to the 

.print Client and its TCP port. Masked client networks (NAT) in this case can 

often cause difficulties. Test to see if the connection exists by trying a telnet 

from the server to the client’s TCP port. To do this, enter the following at the 

server’s Command Prompt: 

telnet IP port (blank space between IP address and TCP port number) 

IP is the client machine’s IP address; port is the TCP port the .print Client is 

using. (See also the .print Client user manuals; Page 117.) 

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. 

Perform the same test from the print server to the terminal server or virtual 

desktop, if the print jobs are to be delivered to the .print Client via RDP (actual 

Virtual Channel Gateway) instead of TCP/IP. 

7 e.g. c:\Program Files\ThinPrint .print Engine or c:\Program Files\VMware\VMware Tools 


Setting up ports and printers 


Overview 

General information about ThinPrint printer ports can be found in the “ThinPrint 

Ports” white paper (Page 117). 

This chapter describes configuration of the .print Engine with special attention to 

adding ThinPrint Ports and adapting them to specific requirements for print job transmission. 

The Port Manager offers the following functions 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 ports and their properties to other Windows machines 

on which a .print Engine is installed 

■ Export and import port properties 

■ Make general settings for the local .print Engine: 

• Encryption settings 

• Tracking settings 


Starting Port Manager 

Local – Open the port configuration on the central print server (logged on locally) with 

START→ PROGRAMS→ .PRINT ENGINE→ PORT MANAGER (Illus. 29). 

Remote 1. For port configuration of remote servers, start the Microsoft Management Console 

from the Command Prompt with: mmc. This will open the window shown 

in Illus. 46. 

Illus. 46 

Illus. 46 Started Microsoft Management Console 

2. Select CONSOLE→ ADD/REMOVE SNAP-IN (Illus. 47). 




Illus. 47 

Illus. 47 MMC: Add Snap-in 

3. Select ADD (Illus. 48). 

Illus. 48 

Illus. 48 MMC: Select ADD 


4. Select .PRINT PORT MANAGER for ThinPrint Port configuration (Illus. 49) and 

click ADD. 



Illus. 49 

Illus. 49 MMC: Select a .print component 

5. Select ANOTHER COMPUTER, and enter the computer you want to manage. 

Click OK or FINISH (Illus. 50). 

Illus. 50 

Illus. 50 MMC: Select another computer to be managed 

6. Repeat steps 4 and 5. Click CLOSE and OK once you have added all computers 

you need to manage (Illus. 51). 




Illus. 51 


Illus. 51 MMC: All .print components to be managed selected 

Configuration – Double clicking a port name (arrow in Illus. 52) will open the port configuration 

(Illus. 53). 

Illus. 52 

Illus. 52 ThinPrint Ports in Port Manager 

Note! Here, ThinPrint Port configuration using the MMC node .PRINT ENGINE 

simply is described. For the other nodes see the respective chapters in this 

manual: LICENSES (Page 104), .PRINT CLIENT (Page 116), AUTOCONNECT 

(Page 78), and VIRTUAL CHANNEL GATEWAY (Page 99) if necessary. See also 

the chapter “MMC functions” (Page 112). 



Configure tab 

Illus. 53 

The ThinPrint Ports can be configured as follows: 

USE ENCRYP- 

TION 

BANDWIDTH 

CONTROL 

Enables SSL/TLS encryption; a valid and corresponding certificate 

must be available on both .print Engine and .print Client 

(not for LPD; see also Page 67). 

•ENABLE: Bandwidth control on 

• Max. bandwidth available for printing with ThinPrint .print; 

minimum: 1600 bit/s, default: unlimited 

Print protocol • TCP/IP (sockets) 

•USE VIRTUAL CHANNEL GATEWAY (Print data will be sent via 

TCP/IP to the terminal server or virtual desktop and then sent 

via ICA/RDP with the .print Virtual Channel Gateway installed 

there) 

• LPD (LPR/LPD) 

MINIMUM 

PRINT DATA 

VOLUME 

Illus. 53 Port configuration 

•(VIRTUAL CHANNEL PROTOCOL (ICA/RDP) 

Note: This function is intended for printing from terminal servers. 

See also the “.print Application Server Engine” user manual, 

Page 117.) 

• Enabled: always high compression (classic case) 

• Disabled: transfer rate optimized compression – depends on 

bandwidth settings 

You can also select the TCP port (default: 4000) for the TCP/IP, LPD8 , and USE VIR- 

TUAL CHANNEL GATEWAY 9 print protocols. With TCP/IP, the TCP ports of the .print Cli- 




Creating new 



ents must be the same as those of the ThinPrint Ports, and with USE VIRTUAL CHAN- 

NEL GATEWAY the TCP ports of the .print Virtual Channel Gateway must be the same 

as those of the ThinPrint Ports. 

How to create new ThinPrint Ports? 

To create new ports use the buttons in MMC’s menu bar (Illus. left) NEW THINPRINT 

PORT or NEW THINPRINT CONNECTION SERVICE PORT 10 (Illus. 52). Choose the port settings: 

port type (protocol), bandwidth and/or encryption. 

We recommend assigning port names from which port properties can be easily 

deducted. Examples: TCP_256k, ICA_32k, CS_1M, TCP_128k_SSL. Up to 600 

ports are possible. 11 

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.). 

Save – Confirm changes with APPLY or OK. 

Advanced tab 

Illus. 54 

Illus. 54 Port configuration: ADVANCED 

8 See the “ThinPrint port configuration for bandwidth controlled printing via LPR/LPD” white 

paper (Page 118) 

9 See also “Using Virtual Channel Gateway” starting on Page 100 

10 For Connection Service Ports see “.print Connected Gateway” user manual (Page 117) 

11 maximum of 600 ThinPrint Ports with a maximum of 800 active printer queues (Windows 

Server 2003 with 3 GHz Dual Xeon processor, 2 GB RAM, and SCASII ultra3 disk array) 



Under ADVANCED are the options: 

CLIENT CONTROL: BANDWIDTH 

If this option is enabled, each client user can set his own bandwidth value 

(in the .print Client Manager). 

Client bandwidth settings must be lower than server-side settings; otherwise, 

.print Engine settings are applied. 

CONNECTION RETRIES (TCP/IP and LPD only) 

Enter the number of times .print Engine should attempt to establish a connection 

with the client. 

NET SEND SERVICE 

Net Send Service can be used to notify users if ThinPrint .print 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), .print Engine will 

send error messages to the relevant account. 

Note: This function can become irksome if several users are logged on to the 

same account. 

NAME CONVENTION 

You can select for each ThinPrint Port whether the address information is at the 

beginning or the end of the printer name. Examples: 

Default addressing Reversed addressing 

TCP/IP 

Lexmark 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 

Use Virtual Channel Gateway (ICA / RDP) 

LPD 

HP LaserJet 1200 PCL# 

Lexmark T620 PS3#:1 

HP PhotoSmart P1000#192.168.1.101 

HP PhotoSmart P1000#client3 

Job Statistics tab 

Print statistics must be activated per port. 

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 

192.168.1.101#HP PhotoSmart P1000 

client3#HP PhotoSmart P1000 

– 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. 55. 

Note! Use this function only part-time, as it may affect print performance. 

See also “Print job tracking” (Page 73). 




Additional 

functions 

Illus. 55 

Illus. 55 Port configuration: JOB STATISTICS 

For other functions, please refer to the table on Page 113. 

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 40) 

■ 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 MMC for remote configuration of ThinPrint Ports (Page 40). 

– Mark a port in the .print Engine of a ThinPrint node (e.g., server-01 in Illus. 56) 

and select COPY from the context menu. 

– Mark a .print Engine in another ThinPrint node (e.g., server-02 in Illus. 56) and 

select PASTE from the context menu. 



Illus. 56 

Export/Import The following export and import functions are available: 

Illus. 57 

Illus. 56 Copy and paste a ThinPrint Port 

EXPORT CONFIGURATION Exports the selected ThinPrint Port to an .xml 

file (top arrow in Illus. 57) 

IMPORT/EXPORT→ EXPORT 

PORT CONFIGURATION 

IMPORT/EXPORT→ IMPORT 


Illus. 57 Exporting or sending a ThinPrint Port 

Exports all ThinPrint Ports to an .xml file (top 

arrow in Illus. 58) if no port is selected 

Imports ThinPrint Ports from an .xml file (top 

arrow in Illus. 58) 




Sending 

port configuration 

Procedure 

when sending 

Illus. 58 


Illus. 58 Exporting, importing, or sending all ThinPrint Ports 

The SEND PORT CONFIGURATION function sends ThinPrint Ports to other servers or 

server groups. There are various modes: 

SEND PORT CONFIGURATION 

(OVERWRITE) 

SEND PORT CONFIGURATION 

(ADD ONLY) 

IMPORT/EXPORT→ SEND PORT 

CONFIGURATION (OVERWRITE) 

IMPORT/EXPORT→ SEND PORT 

CONFIGURATION (ADD ONLY) 

Sends the selected ThinPrint Port (bottom 

arrow in Illus. 57); ports with the same name 

on the target system will be overwritten 

Sends the selected ThinPrint Port (bottom 

arrow in Illus. 57); ports with the same name 

on the target system will not be overwritten 

Send all ThinPrint Ports (bottom arrow in 

Illus. 58); ports with the same name on the 

target system will be overwritten 

If ThinPrint Ports already exist on the target computers that are not available on the 

sending computer, they are not changed. 

Selecting the send option will open the dialog in Illus. 59. 

Illus. 59 

Illus. 59 Dialog for sending properties 

Send all ThinPrint Ports (bottom arrow in 

Illus. 58); ports with the same name on the 

target system will not be overwritten 



– To improve clarity, first select OBJECT TYPES, and disable GROUPS (Illus. 60). 

Confirm with OK. 

– Select ADVANCED (Illus. 59) and then FIND NOW (Illus. 61). 

Illus. 60 

Illus. 61 

Illus. 60 Limiting the selection to computers 

Illus. 61 Finding target servers 

– Mark all target servers and confirm with OK (Illus. 62). 

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 

(Illus. 63). 




Illus. 62 

Illus. 63 

Illus. 64 

Illus. 62 Selecting target server(s) 


Illus. 63 Confirmation prompt 

Note! If you receive an error message when sending, create a connection with 

the MMC to the target computer via the relevant ThinPrint node for remote 

configuration (Page 40) and repeat the send process from the source computer 

while keeping the Console open (Illus. 64). 

Illus. 64 Create a connection to the target computer with the MMC (here: arrow to 

server-02) and repeat send process from source computer (here: server-03) 



Installing printers on the ThinPrint Port at the server 

General information about creating printers can be found in the “.print addressing” 

and “ThinPrint Ports” white papers (Page 117). 

There’s one last step after installing and configuring the .print Engine: 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 before printer installation to see which ThinPrint Port supports 

what protocol (Page 43). 

Printer names 

.print name conventions 

Please also refer to the following information when adding printers on the server manually 

(without AutoConnect). 

For simplicity’s sake, only standard addressing is treated here; reversed addressing 

can be found in the chart on Page 46, and addressing THINPRINT CONNECTION SERVICE 

PORTS is explained in detail in the “.print Connected Gateway” manual (Page 117). 

It is irrelevant to a .print printer name whether the object represents a traditional 

(native) printer driver or the Output Gateway “printer driver”. The .print printer name 

is composed according to the network protocol in use: 

Network protocol Names of printer objects 

TCP/IP Either: printer_name#client_name:printer_ID 

Example: Kyocera FS-850#client1:3 

Or: printer_name#IP_address:printer_ID 

Example: Kyocera FS-850#191.168.1.17:3 

Use Virtual Channel 

Gateway (ICA/RDP) 

Either: printer_name#user_name:printer_ID 

Example: Kyocera FS-850#administrator:3 

Or: printer_name#_:printer_ID 

Example: Kyocera FS-850#_:3 

LPD Either: printer_name#client_name 

Example: Kyocera FS-850#printer1 

Or: printer_name#IP_address 

Example: Kyocera FS-850#191.168.1.18 

client_name Client name with TCP/IP and LPD 12 means the real name of the client in the network 

(= host name). Alternatively, the client’s IP address can be used; this is especially 

necessary when there are difficulties with name resolutions 

Note! With TCP/IP it is possible to send print data to any client installed with 

.print Client – independent of a session (on a terminal server or virtual desktop). 

12 See the “ThinPrint port configuration for bandwidth controlled printing via LPR/LPD” white 

paper (Page 118) 





printer_ID At the client, the .print Client automatically assigns every installed printer an ID (see 

Illus. 24, Page 29). The printer_ID can be omitted if there is only one printer 

installed on the client, or if printing should take place on the current printer. 

printer_name The printer name can be anything you like. It is nonetheless recommended that it be 

the same as the printer name at the client. 

Example 2: 

Client 

Client name client1 

IP Address 192.168.1.17 

Printer HP LaserJet 1200 PCL 

.print Client assigns this printer ID 2 (Illus. 24). 

Server HP LaserJet 1200 PCL#client1:2 

Or 

HP LaserJet 1200 PCL#192.168.1.17:2 

With the Use Virtual Channel Gateway protocol type, it is possible to print from print 

serves via ICA/RDP. Print jobs are then sent via TCP/IP from the .print Engine 

installed on the print server to the .print Virtual Channel Gateway on the terminal 

server (or virtual desktop) and from there via ICA or RDP to the client. The name convention 

for the printers on the print server is the same as for ICA/RDP. 

The ICA and the RDP protocols assume all communication with the client, including 

the client’s unambiguous identification. The printer name is composed of: 

Description of the Printer and the Printer ID 

Note! With the ICA/RDP protocol print data is automatically sent to the client 

from whose session the print data was created. 



Example 3: 

A Kyocera FS-850 shall print via ThinPrint .print with the ICA protocol. If 

several printers are installed and .print Client assigned the printer the ID 3, 

the printer name could be something like: 

laser_printer #:3 (# before the :) 

Or Kyocera# :3 (blank space 

before the :) 

Or Kyocera FS-850#_:3 (underscore 

before the :) 

If Kyocera FS-850 is the current printer (in the .print Client), the printer name 

could be: 

laser_printer 

Port pooling 

Pooling printers with .print means you can connect a printer with several ThinPrint 

Ports (Illus. 65 and 66). This has the following advantages: 

■ Improved performance 

■ Little chance of blockage from very large or “hanging” print jobs 

■ Less printers on the server 

Illus. 65 

Port pooling is supported by: 

■ ThinPrint Ports 

■ Output Gateway 

■ AutoConnect 

Illus. 65 Principle of port pooling 

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 .print AutoConnect, 

however, brings more than maximum performance; it also makes administration par- 





ticularly easy and convenient. Port pooling (with three or four ThinPrint Ports) is recommended 

for templates on print servers, e.g., _#ThinPrint Output Gateway. 

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 117). 

Illus. 66 

Illus. 66 Activating port pooling 

LPR/LPD printing with Windows CE or Linux clients 

Overview 

Windows CE and Linux clients are capable of forwarding print jobs to LPD devices. 

The .print Client WinCE or .print Client Linux is installed on a thin client or PC and 

can then receive .print 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. 67). 

All .print Clients Linux support LPR/LPD printing as well as all .print Clients 

WinCE in version 5.5 and later. 

Note! For Information on sending print orders directly via LPR/LPD with .print 

Engine, see the “ThinPrint port configuration for bandwidth controlled printing 

via LPR/LPD” white paper (Page 118). 



Illus. 67 

Illus. 67 LPR/LPD printing via Windows CE or Linux clients 

Preparations on the central print server 

– Create a new printer. For TCP/IP this must contain the Windows CE or Linux 

client’s address in its name. Assign a ThinPrint Port that uses TCP/IP, ICA, or 

RDP as print protocol (e.g., ThinPort:) and share the printer (Illus. 68). 

Illus. 68 

Illus. 68 Printer set up, printing to Windows-CE or Linux device 

– Make sure that the printer completely spool the print data on the hard drive 

before sending. To do so, select GENERAL under PRINTER PROPERTIES (Illus. 69). 

– Select START PRINTING AFTER LAST PAGE IS SPOOLED. 

– Disable the Advanced Printing Features. 




Illus. 69 


Illus. 69 Preferences on the server for client-side LPD printing 

Preparing .print Client (example for Windows CE) 

– Open the control panel on the Windows CE device and select THINPRINT (click 

OPEN, Illus. 70). 

Illus. 70 

Illus. 70 .print Client WinCE in the control panel (example for Neoware terminals) 

– Enable the .print Client (ENABLE THINPRINT, Illus. 71 left). 

– Select the protocol you selected for the corresponding ThinPrint Port (here: 

TCP/IP, Page 56) and click OK (Illus. 71 left). 

– Open the .print Client configuration menu by clicking CONFIGURE THINPRINT 

(Illus. 71 right). 



Illus. 71 

– Use ASSIGNMENT to list available printers (Illus. 72). Select ADD NETWORK 

PRINTER and then LPD PRINTER (Illus. 73). 

Illus. 72 

Illus. 73 

Illus. 71 Selecting the protocol (here: TCP/IP), enabling .print Client and opening configuration 

menu 

Illus. 72 Select ADD NETWORK PRINTER 

Illus. 73 Select LPD PRINTER 

– Enter any PRINTER NAME and the printer’s IP address or client name (PRINTER 

ACCESS) and, for external print servers with more than one printer port, the name 

of the printer QUEUE (Illus. 74); leave LPD FILTER l unchanged. 

– Confirm with OK. 

Illus. 74 

Illus. 74 Enter a network printer 

(example) 





– In SETUP select the new printer as CURRENT PRINTER (Illus. 75) because there is 

no printer ID created in the printer name on the server (Illus. 68). 

– Finish configuration with OK. 

Illus. 75 

Printing – Set up a connection from a virtual desktop or terminal server sesstion to the 

printer share “laser printer#192.168.20.15“ in Illus. 68 – either manually, or 

utilizing AutoConnect (Pages 33 and 78). 

– Make a test print to the printer. 

Multiple printers If you want to use multiple printers, get their printer IDs from the .print Client configuration 

(Illus. 72) and create a suitable printer object with the printer ID in its 

name on the server for each printer (Illus. 68); an example using the printer ID “6” is: 

Laser printer#192.168.20.15:6 

ThinPrint Output Gateway 

The “TP Output Gateway” is a virtual printer driver (see the MODEL column in 

Illus. 76) 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 

or the virtual desktop (Illus. 77). 

Illus. 76 

Illus. 75 Choosing the new printer as “current printer” and finishing with OK 

Note! ThinPrint Output Gateway will only function with .print Clients installed 

on machines with Windows 9x/ME/NT 4.0/2000/XP/2003/Vista operating 

system; exception: Printer Virtualization Layer (Page 65). Relevant printer 

drivers must be installed on these machines. 

Illus. 76 “TP Output Gateway” in the server’s PRINTERS (AND FAXES) folder 



Illus. 77 

Illus. 77 Driver Free Printing: Output Gateway on terminal servers and central print 

server, printer drivers on PCs and local print servers running Windows 

With Driver Free Printing, print data is sent from the terminal server or virtual desktop 

to the central print server and sent from there to the client machine in Windows’ own 

EMF data format – from the print server to the client machine, it is also bandwidth 

controlled, compressed, streamed, and, if desired, encrypted. 

Name convention You can treat the printer objects based on TP Output Gateway like any other printer 

object. To use them instead of a native (conventional) printer driver, they must usually 

be renamed according to the .print name conventions. Example: 

Example 4: 

Client 

Addressing the printer directly (TCP/IP printing) 

Client name client1 

ID 3 

IP address 192.168.1.17 

Printer name HP LaserJet 5L 

Server 

Printer name HP LaserJet 5L#client1:3 

or 

Printer name HP LaserJet 5L#192.168.1.17:3 

Note! If you prefer to work with conventional printer drivers and not Output 

Gateways, simply delete the ThinPrint Output Gateway printer which is automatically 

created during installation. 

Additional Output Gateway printers 

Additional Output Gateway printers can be created with the ADD PRINTER function in 

the server’s PRINTERS (AND FAXES) folder using THINPRINT as manufacturer. The print- 





ers are to be connected with a ThinPrint Port; exception: Printer Virtualization Layer 

(V-Layer) (Page 65). 

Compression 

ThinPrint .print combines the efficiency of Driver Free Printing with adaptive .print 

compression (OPTIMAL option in Illus. 78). If high quality printout is not an important 

issue, data volume (and toner usage) can be even further reduced by selecting maximum 

compression 13 or by completely omitting images from the document (MAXI- 

MUM, EXTREME and NO IMAGES options). With Driver Free Printing, of course the standard, 

no-loss compression known from native printer drivers is also still available 

(NORMAL option). 

Paper formats and trays 

After adding an Output Gateway printer, a few default options are available for paper 

formats (Illus. 82) and paper sources 14 (Illus. 83). You can add further options – 

provided they are supported by the printer drivers on the client machine(s). 

There are two ways to do this: 

■ For printers created by .print AutoConnect: 

Automatic upload of printer properties from the .print Client to the server (see 

the “.print Application Server Engine” manual; Page 117) 

■ For manually created printers: 

Setting Windows Registry values for paper formats and sources on the server 

(see the “Adaption of Output Gateway options” white paper; Page 117) 

Presettings on the print server (administrators only) 

The following settings for Output Gateway printer shares can be made in the central 

print server’s PRINTERS (AND FAXES) folder; they will then apply to all printers, created 

with this printer share as a network printer in a session (on a terminal server or virtual 

desktop). (In one particular case, this applies not only for printer shares but also to 

printer templates. Refer to the section “AutoConnect on central print servers”, 

Page 95.) 

– Select for example FILE→ PROPERTIES→ THINPRINT DEVICE SETUP 

for the Output Gateway share n the server's PRINTERS (AND FAXES) folder: 

There are five options available for print data compression (Illus. 78): 

• 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 

The additional options DUPLEX and TRAY SELECTION can also be enabled or disabled 

for users. 

13 Don’t confuse with the MINIMUM PRINT DATA VOLUME option (Page 44). 

14 Selection of paper trays or manual feed 



Illus. 78 

Illus. 78 Setting compression and 

enabling duplex and paper 

source selection 

The settings shown in Illus. 78 can only be made on the print server for Output Gateway 

printer shares and cannot be changed in a session – unlike the settings below 

(Illus. 79–81). 

Select ADVANCED→ PRINTING DEFAULTS to edit page and color settings (Illus. 79); 

e.g., A4 or LETTER as paper size. 

Illus. 79 

Illus. 79 Presetting paper size, print resolution, 

color, etc., on the server 

You can edit the following settings for double-sided printing under ADVANCED 

(Illus. 80): LONG EDGE or SHORT EDGE (= turn over edge). 

If duplex and paper source are enabled on the print server (as in Illus. 78), have 

the choice between simplex/duplex and of paper source, as in Illus. 80 – provided 

the original printer driver supports this function. If they are not enabled on the server, 

the corresponding user interface will not be available and it is only possible to select 

the preview (PREVIEW ON CLIENT BEFORE PRINTING: Illus. 85). 




Illus. 80 


Illus. 80 Presetting preview, duplex, and 

paper source on the server 

ADJUSTMENT offers options for the default procedure if the printable area of the document 

and of the printer driver’s paper format don’t match. The option SCALE TO FIT 

changes the size of the printout, ADJUST MARGINS moves the zero point (Illus. 81). 

It is recommended to leave the settings enabled for printer shares on the print server. 

Illus. 81 

Illus. 81 Presetting scaling and margin adjustment 

on the server 

The printer share settings from Illus. 79–81 are the shown as default options in a 

session. Users can change them within their sessions. 

Settings in a session (on a terminal server or virtual desktop) 

Without admin permissions it is possible to change some printer settings in the 

printer properties dialogue by the users before printing. 

The following settings can be edited under GENERAL→ PRINTING DEFAULTS 

(Illus. 82): PAPER SIZE, COPY COUNT, PRINT RESOLUTION, PORTRAIT or LANDSCAPE, and 

COLOR or GRAY SCALE. 



Illus. 82 

Illus. 82 Specifying paper size, print resolution, 

color, etc., in a session 

If the printer supports it, there are settings for double-sided printing under ADVANCED 

(Illus. 83; LONG EDGE or SHORT EDGE) as well as paper tray or PAPER SOURCE. Users 

can choose to see a preview before printing (Illus. 85), by selecting PREVIEW ON CLI- 

ENT BEFORE PRINTING. 

Illus. 83 

Illus. 83 Paper sources as well as selection of 

duplex and preview in a session 

ADJUSTMENT offers options if the printable area of the document and of the printer 

driver’s paper format don’t match. The option SCALE TO FIT changes the size of the 

printout, ADJUST MARGINS moves the zero point (Illus. 84). 

Illus. 84 

Illus. 84 Modifying scaling and margin adjustment 

in a session 





Printing with preview 

Once the print preview is enabled (Illus. 83: checkmark on PREVIEW ON CLIENT BEFORE 

PRINTING) the print job appears in the .print viewer (= ThinPrint Viewture; Illus. 85). 

Here the users can: 

■ Print to any printer that is connected to the client computer or can be reached 

from it 

■ All client printer settings are available, even if they cannot be uploaded to the 

session on the server. 

■ Navigate in documents with more than one page 

■ Zoom 

■ Cancel print job reception 

■ Save print job 15 

Illus. 85 

Printer Virtualization Layer (V-Layer) 

Illus. 85 Preview with .print 

Viewture on the client 

computer 

(water mark 

=demo version) 

Scenario If Driver Free Printing (Page 59) is only to be used for terminal servers or virtual desktops 

together with central print servers, without requiring a Windows computer 

installed with a .print Client on the client side, then Printer Virtualization Layer 

(= Driver Free Native Printing) can be used – whereas “Driver Free” refers to the terminal 

server or virtual desktop and “Native” refers to printing from a central print 

server to the client machines (Illus. 86). 

With Printer Virtualization Layer, print data is sent from the terminal server or virtual 

desktop to the central print server in Windows’ own EMF data format. On the 

15 File extension: .tpf (compressed EMF data); the Viewture program is needed for reloading a 

saved print job; see TPView.exe on your product CD or: www.thinprint.com/→ SUPPORT & SER- 

VICES→ SOFTWARE DOWNLOAD→ SOFTWARE TOOLS 



central print server, it is sent from the ThinPrint Output Gateway to the native printer 

driver. One advantage of Printer Virtualization Layer is that Output Gateway printers 

on the central print server are not connected to ThinPrint Ports and do not have to 

conform to any particular name convention. 

Illus. 86 

Illus. 86 Printer Virtualization Layer: Output Gateway on terminal servers and central 

print server, printer drivers on the central print server 

Setup – Install .print Engine on the central, dedicated print server (Page 17). 

– Install ThinPrint Output Gateway on each terminal server or virtual desktop 

(Page 25). 

– On the central print server, add all necessary printers with their native printer 

drivers and share them. 

– If you want to send the print jobs using the .print Engine rename the printers 

according to .print name convention (Page 52) and connect them with 

ThinPrint Ports (e.g. Oki and Ricoh printer in Illus. 87). 16 Otherwise connect 

them with Standard TCP/IP ports or with LPR ports (HP printer in Illus. 87). 

Illus. 87 

Illus. 87 Printers on a central print server which use native printer drivers (example) 

16 It is recommended to use port pooling (Page 54) or to connect each printer to a separate 

ThinPrint Port. 




V-Layer 

configuration 


– To convert the printers use the Printer Virtualization Layer configuration tool; 

it’s a component of .print Server Engine 7.6 Feature Release 1. See the respective 

manual (Page 117). 

For each (selected) printer the Printer Virtualization Layer configuration (Illus. 88) 

creates a second printer which uses the TP Output Gateway as the driver. Afterwards 

it moves the share from the old to the new printer. Later on the new shared printer 

receives the print jobs and transmits them to the second printer of the pair (Illus. 89). 

Illus. 88 

Illus. 89 

SSL/TLS encryption 

Illus. 88 V-Layer configuration of Feature Release 1 (example) 

Illus. 89 V-Layer printer pairs: The first printer of a pair uses the TP Output Gateway 

and the second one uses the native driver (example) 

The .print Engine has been extended to include SSL/TLS encryption for printing, 

which ensures a secure connection between the .print Engine and the .print Client 

(available with .print Client version 6.2 and later). To do so, the following SSL certificates 

have to be imported: 

– one “personal” server certificate and one root certificate on each server with 

.print Engine 

– one “personal” client certificate on each client for sending encrypted print jobs 



The .print Engine checks whether the client is authorized to receive print data. 

SSL/TLS encryption is also available for use with the .print Connection Service. 

Importing SSL certificates on the servers 

Install your own 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→ ADD→ 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. 90). 

Illus. 90 

Illus. 90 Adding snap-ins for SSL certificates to the MMC 

5. Import the certificate(s) to the two places shown in Illus. 91 (see arrows). To 

do so, select each time ALL TASKS→ IMPORT in the context menu and then 

NEXT→ BROWSE→ OPEN→ NEXT→ PASSWORD→ NEXT→ PLACE ALL CERTIFI- 

CATES IN THE FOLLOWING STORE→ NEXT→ FINISH→ OK. The subdirectory 

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. 91 

Illus. 91 Importing two SSL certificates to the server 


Two examples for imported certificates can be found in Illus. 92 and 93. 

Illus. 92 

Illus. 92 First SSL certificate imported on the server (example for server certificate) 



Selecting 

certificates 

Illus. 93 

Illus. 93 Second SSL certificate imported on the server (example for root certificate) 

6. For using the imported SSL certificates with the .print Engine open port configuration 

in the MMC (START→ PROGRAMS→ .PRINT ENGINE→ PORT MANAGER). 

7. Select ENCRYPTION SETTINGS in the .PRINT ENGINE context menu (Illus. 94). 

Illus. 94 

Illus. 94 Selecting ENCRYPTION SETTINGS 

8. Enter the names of server and root certificates under ENCRYPTION CERTIFICATES 

(Illus. 95). Use the names that are displayed in the column ISSUED TO of the 

MMC’s certificate overview (in Illus. 92 and Illus. 93 tpthinmon and tproot 

as examples). 




Enabling 

encryption 

Illus. 95 


Illus. 95 Selecting imported SSL certificates 

(example) 

9. Fill in both fields and check that each certificate is installed on the server 

(Page 68) and that the certificates installed on the clients are trusted by the 

server certificates (see below). Otherwise, print jobs will not be executed. 

SSL encryption is enabled per ThinPrint Port in the MMC (Illus. 96). 

Illus. 96 

Illus. 96 Enabling encryption in the port configuration (MMC) 

Note! In case of using Microsoft Cluster Services, perform all port settings on 

the cluster instance (Illus. 95 and 96). However the server-side certificates 

must be installed individually on each cluster node; for this see the “Microsoft 

Cluster Services and ThinPrint .print” white paper (Page 117). 

Importing SSL certificates on the clients 

For client-side installation of SSL certificates, please consult the relevant .print Client 

user manual (Page 117). In the following, installation is described with the example 

of the .print Client Windows. 



Registry entry 

CertName 

1. To install a client certificate, select the following in the MMC on the client PC: 

FILE→ ADD/REMOVE SNAP-IN→ ADD→ CERTIFICATES→ ADD→ MY USER 

ACCOUNT→ FINISH→ CLOSE→ OK 

2. Now import the certificate by selecting ALL TASKS→ IMPORT in the context menu 

(Illus. 97) and then 

NEXT→ BROWSE→ OPEN→ NEXT→ PASSWORD→ NEXT→ PLACE ALL 

CERTIFICATES IN THE FOLLOWING STORE→ NEXT→ FINISH→ OK 

Illus. 97 

The result is shown in Illus. 98. 

Illus. 98 

Illus. 98 SSL certificate imported to a client 

Note! If different users on a client are to receive encrypted print data, the certificate 

must be imported to CURRENT USER→ PERSONAL for each user. 

Before sending encrypted print data, the server checks whether the name of the 

imported certificate is included in the CertName entry in the client computer’s 

Windows Registry and whether the stored certificate is present on the client. 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. 99; data type: reg_sz): 





hkey_local_machine\software\thinprint\client\CertName 

Illus. 99 

2. Enter as value the name of the imported certificate as displayed in the column 

ISSUED TO of the MMC’s certificate overview (tpclient as example in Illus. 98 

and 99). 

3. Restart .print Client Windows. 

The CertName Registry entry is only needed for encrypting print data; receipt of 

unencrypted print data is still possible. 

Print job tracking 

Illus. 99 Registry entry for SSL encryption on Windows clients 

(example for tpclient certificate) 

Overview 

The .print Tracking Service must be installed to enable use of the tracking function 

in .print Engine. The .print Tracking Service is included in the .print Engine software. 

Its setup is described in the “.print Tracking Service” user manual (Page 117). 

Print job tracking gathers information about print activities using .print Engine. 

With it, print related data is gathered on the server and forwarded to an SQL server 

(Illus. 100). Print job tracking has the following components: 

■ .print Engine (sends data to the tracking service) 

■ .print Tracking Service (receives data and writes it to the SQL database) 

■ .print Tracking Report Engine (web component for clear analysis, summary, and 

graphic report of tracking results) 

Note! The .print Tracking Service, SQL server, and .print Tracking Report 

Engine can be set up on the same machine (Windows 2000, XP, or 2003). 



Illus. 100 

Illus. 100 Example for using .print tracking 

See also “Job Statistics tab” (Page 46). 

.print Tracking Service 

You can gather information about the print jobs sent with the .print Engine for your 

statistics (tracking). To do so, you must set up a Microsoft SQL server (2000 or 2005 

family). The .print Engine sends tracking data to this server via the .print Tracking 

Service. Print data available for tracking is: 

– Author of a print job 

– Printer used 

– Settings used 

– Number of pages printed 

– Information on any errors 

– Duration of a print job 

The SQL server can collect print data both from different sources – from .print 

Engines on application or print servers as well as on workstations – and from different 

operating systems (Windows and Unix). 

.print Tracking Report Engine 

.print 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. 101). 




Illus. 101 

Illus. 101 Analyzing SQL data in a web browser (example) 


Preparing the .print Engine for tracking 

To prepare the .print Engine for sending tracking data to the tracking server, you must 

make the following settings in the MMC configuration for the ThinPrint Ports: 

1. Open port configuration in the MMC (START→ PROGRAMS→ .PRINT 

ENGINE→ PORT MANAGER). 

2. Select TRACKING SETTINGS in the .PRINT ENGINE context menu (Illus. 102). 

Illus. 102 

Illus. 102 Selecting TRACKING SETTINGS 


.print AutoConnect 

3. In the next window, enter the IP address of the tracking server and the TCP port 

number 4100 for communication with the tracking server (Illus. 103). 

4. Select AFTER PRINT JOB and confirm with OK. 

Illus. 103 

Print job tracking is enabled with the AFTER PRINT JOB option. If you also want to compile 

the duration of print jobs in the SQL database, select BEFORE PRINT JOB, too. If 

both options are disabled, no data will be sent to the tracking server. 


Introduction 

Illus. 103 Entering tracking server IP 

address and TCP port 4100 and 

selecting AFTER PRINT JOB (exam- 

Note! If the configured tracking server cannot be reached, disable the tracking 

service by deselecting the two options (BEFORE and AFTER PRINT JOB). Otherwise, 

print performance will suffer because .print Engine will establish a connection 

to the tracking server for each print job. 

Automatically connecting printers with a ThinPrint Port saves a lot of time and work 

in server-based and client-server environments. 

So that a user can print with ThinPrint .print from a client over a server, a printer 

must be set up on a ThinPrint Port at the server. Of course, it is possible to set up all 

printers for all clients manually. Then again, this is a hefty task, especially in large 

server farms with an appropriately large number of users. 

.print AutoConnect enables automatic connection from local client printers during 

a session (on a terminal server or virtual desktop). It is installed as a Windows service. 

.print AutoConnect is supplied as an enhanced component of .print Engine, with 

the .print Server Engine package. 

.print AutoConnect features 

■ Central administration of remote client printers 

■ Dynamic connection to shares on central, dedicated print servers 

■ Support of .print Connection Service 





If several clients, each with its own printer, are working on a server, it is usual that 

every printer must be installed onto the server. .print AutoConnect makes it possible 

to create these printer objects automatically if a shared printer can be used on a central, 

dedicated print server (Constellation 2). 

Note! For printing using ThinPrint Ports the TP AutoConnect Service 

(Windows service) has to be run together with the .print Engine 


Basic constellations 

Constellation 1 ■ .print Engine with .print AutoConnect on a terminal server 

Illus. 104 

Illus. 104 .print AutoConnect – configuration without central print server 

More information about this constellation can be found in the “.print Application 

Server Engine” user manual (Page 117). 

Constellation 2 ■ .print Engine on a central, dedicated print server 

■ .print AutoConnect and .print Virtual Channel Gateway (if necessary) 

on a terminal server or virtual desktop 



Illus. 105 

Illus. 105 .print AutoConnect – configuration with central print server 

Where and how to install .print AutoConnect? 

With central, dedicated print servers, .print Engine is installed on the print server(s) 

– and .print AutoConnect on the terminal server(s) or virtual desktops (Page 23). The 

same installation program is used for both components. 


.print AutoConnect configuration 

The description below is for the configuration of AutoConnect for terminal servers or 

virtual desktops. In addition, AutoConnect can also be installed on central printer 

servers. Refer to the section “AutoConnect on central print servers”, Page 95. 

You can configure .print AutoConnect locally as well as remotely; for remote configuration 

.print AutoConnect must be installed on both machines. 

Local – Start the local AutoConnect dialog on the terminal server or virtual desktop with 

START→ PROGRAMS→ .PRINT ENGINE→ AUTOCONNECT (Illus. 106). 

Illus. 106 

Illus. 106 Starting configuration of AutoConnect (example for Windows Server 2003) 





Remote 1. For remote AutoConnect configuration, open the Microsoft Management Console 

from the Command Prompt with: mmc. This will open the window shown 

in Illus. 107. 

Illus. 107 

Illus. 107 Started Microsoft Management Console 

2. Select CONSOLE→ ADD/REMOVE SNAP-IN (Illus. 108). 

Illus. 108 

Illus. 108 MMC: Add Snap-in 

3. Select ADD (Illus. 109). 



Illus. 109 

Illus. 109 MMC: Select ADD 

4. Select .PRINT AC/VCG CONFIGURATION for AutoConnect or Virtual Channel Gateway 

configuration (Illus. 110) and click ADD. 

Illus. 110 

Illus. 110 MMC: Select a .print component 

5. Select ANOTHER COMPUTER, and enter all computers you want to manage. 

Click OK or FINISH (Illus. 111). 

Illus. 111 

Illus. 111 MMC: Select another computer to be managed 





6. Repeat steps 4 and 5. Click CLOSE and OK once you have added all computers 

you need to manage (Illus. 112). 

Illus. 112 

Illus. 112 MMC: All .print components and computers to be managed selected 

Configuration – Click an AutoConnect node (arrow in Illus. 113) to open the AutoConnect configuration. 

Illus. 113 

Illus. 113 AutoConnect configuration 



Properties 

The PRINTER NAME CONTAINS THE PREFERENCE and PRINTER ACCESS RIGHTS options on 

the PROPERTIES tab (Illus. 113) are configured on the central, dedicated print server. 

Because AutoConnect is run on terminal servers or virtual desktops, though, these 

options are unimportant here. 

At the bottom of the screen, you can specify the connection protocol. 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. 

– Confirm your entries with APPLY. 

Note! The protocols (TCP/IP or RDP) of .print AutoConnect, .print Client and 

of the ThinPrint Port the template is connected with must match. See also the 

.print Client user manual. 

Name translation (Dynamic Printer Matrix) 

The name translation table (Dynamic Printer Matrix) lets .print AutoConnect map the 

printer shares created on the central, dedicated print servers to the user sessions (on 

a terminal server or virtual desktop). You can precisely control which user is to get 

what printer. This table requires a .print Client on the user’s workstation or terminal 

as well as a .print Engine on the print server(s). For all other shares, use the “Map 

additional printers” (Page 93). 

– Select the NAME TRANSLATION tab. Use the ADD, DELETE or ARROW buttons to edit 

the table. 

Illus. 114 

Illus. 114 Name translation table 

Table functions If your name translation table consists of only two columns you can convert the table 

into the form shown in Illus. 114 using the option ADVANCED NAME TRANSLATION (in 

the left column of the context menu of the AUTOCONNECT node). You then have the 

option of hiding unneeded columns (Illus. 115). In all cases, hidden columns (and 

their rules) are deactivated. 




Illus. 115 

Illus. 115 Hiding columns 


When AutoConnect is executed, it processes the table from top to bottom, for each 

printer activated in .print Client (Illus. 116). If all criteria (columns) in one line are 

met for the first printer AutoConnect searches for the share specified in the column 

TARGET and establishes a connection to this printer share during the session. Autoconnect 

now stops the search for this printer in the table and, if applicable, continues 

the same procedure for the next activated printer in .print Client etc. etc. 

Illus. 116 

Illus. 116 Three printers enabled in the .print Client Manager 

You can change AutoConnect’s processing sequence by switching the line order using 

the arrow keys ( and ) . You can also add or delete lines. For the two grey lines 

refer to Page 85. The table has the following columns/translation rules: IP RANGE, 

CLIENT NAME, DRIVER NAME, PRINTER NAME, CLASS NAME and CLIENT TYPE; here, * and 

? can be used as wild cards. The TARGET column represents the shares on the central, 

dedicated print server(s). 

These features are explained in the scenarios below; the scenarios can also be 

combined with each other. 



IP range The IP RANGE column in the name translation table could contain, for example, the 

following entries: 

192.168.1.136 

192.168.1.1–192.168.1.150 

192.168.1.0/24 

192.168.128.0/22 

192.0.0.0/8 

A separate template is given as each target; printers with different properties will thus 

be mapped in the respective terminal session. 

The default entry in IP RANGE is: 0.0.0.0–255.255.255.255 

The “24” represents the following subnet mask: 255.255.255.0; i.e., 3x8=24 

set bits (22 is equivalent to 255.255.252.0; 16 is equivalent to 255.255.0.0; and 

8 is equivalent to 255.0.0.0). 

Scenario: Network printer in remote offices or office floors 

Illus. 117 

Illus. 117 Users are to have their closest printers mapped when they open a 

session (.print components not shown here) 

Each remote office (or floor) uses different client names (both for PCs and for local 

print servers or external and internal print servers). In this way, different printers on 

different workstations can be mapped using the client name (Illus. 117). 

The CLIENT NAME and TARGET columns on the NAME TRANSLATION tab could contain 

the following entries: 

Client name Target 

floor_1* \\printserver\floor_10 





Client name Target 



As an alternative to the CLIENT NAME column, you can also use the IP RANGE column. 

Only printer shares are entered in the TARGET column. (The default entry in CLIENT 

NAME and IP RANGE is: *) 

Client type You can select between Windows clients (W), Unix clients (U), Java clients (J), and 

other (X). 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” share is assigned to all Windows clients 17 . All other client types use the 

“HPLaser” share, which uses a native printer driver. 

Try client printer name or client class name 

There are two special lines in the name translation table (Illus. 118): 

TRY CLIENT PRINTER NAME and 

TRY CLIENT CLASS NAME 

Special lines require that .print AutoConnect and .print Engine are installed on the 

same computer. See also Constellation 2 (Page 77) and the “.print Application 

Server Engine” user manual (Page 117). 

17 Windows 95 or later 

W U J X Target 

* * * * * � – – – \\printserver2\ 

ThinPrint 

Output Gateway 

* * * * * – � � � \\printserver2\ 

HPLaser 



Illus. 118 

Variables 

.print AutoConnect enables automatic mapping of client printers in the session. To 

simplify printer administration, it is now possible to use variables. 

In addition to the wildcards, variables (example: %LPSRV%) can also be used in 

the name translation table. Several printers can thus be created with one single entry 

where the variables are replaced by the printer name or the print server name of the 

printer in the .print Client respectively. 

%LPSRV% 

(Local Print Server) 

Illus. 118 Special lines 

This variable is replaced by the 

print server name 

in the .print Client of the user machine. 

%LCPRN% 

(Local Client Printer) 

This variable is replaced by the 

printer name 

in the .print Client of the user machine. 

The entries are made in the TARGET field in the name translation table of Auto- 

Connect. Either variable can be used as desired and also used in combination. 

Below is two examples of how entries in the table can be simplified with variables. 





Example without local print servers 

The main office has a terminal server (or a VDI) and a central print server with the 

.print Engine (Illus. 119). The goal is to create the printers of the respective workstation 

(or terminal) in the session of each user with only one entry in the AutoConnect 

table of the terminal server or virtual desktop. 

Illus. 119 

The individual printers of the Windows PC are created according to ThinPrint name 

conventions (here: TCP/IP) and shared on the central print server (printserver2) at 

the main office, for example: 

Illus. 120 

Illus. 119 Example scenario 1 for variables in the name translation table 

Printer name Share name 

HP DeskJet#192.168.131.124:1 

Lexmark T620#192.168.131.124:2 

Only one entry is then necessary in the name translation table of AutoConnect on the 

terminal server (or virtual desktop), namely 

\\printserver2\%LCPRN% 

HP DeskJet 

Lexmark T620 

Illus. 120 Shared printers on the central print server 

where printserver2 is the central print server (Illus. 121): 



Illus. 121 

Illus. 121 Name translation table: 

A single entry is enough to create all printers of all the workstation/terminal 

The printer folder is then displayed in the user’s session as shown in Illus. 122. 

Illus. 122 

Illus. 122 Printers created with variables in the session 





Example with local print servers 

The main office has a terminal server (or a VDI) and a central print server with the 

.print Engine, the numerous branch offices each have a local print server installed 

with the .print Client as a service (Illus. 123). The goal is to create the printers of the 

respective branch offices in the session of each user with only one entry in the Auto- 

Connect table of the terminal server or virtual desktop. 

Illus. 123 

Illus. 123 Example scenario 2 for variables in the name translation table 

The printers of each branch office are created and shared on the local print servers 

(here: Berlin and Paris). 

The individual printers of the various branch offices are created according to 

ThinPrint name conventions (here: TCP/IP) and shared on the central print server 

(CPS) at the main office, for example: 

Printer name Share 

Lexmark Optra#berlin:1 

HP Color#berlin:2 

Lexmark Optra#paris:1 

Epson Stylus#paris:2 

The printer ID (:1, :2) is the ID in the .print Client on the local print server. Berlin 

and Paris are the names of the local print servers. In this example, we are printing 

via TCP/IP. Only one entry is then necessary in the name translation table of 

AutoConnect on the terminal server or virtual desktop, namely 

\\CPS\%LPSRV%_%LCPRN% 

where CPS is the central print server (Illus. 124): 

berlin_Lexmark Optra 

berlin_HP Color 

paris_Lexmark Optra 

paris_Epson Stylus 



Illus. 124 

Illus. 124 Name translation table: 

A single entry is enough to create the printers of all the branch offices 

The variable %LPSRV%_%LCPRN% is then translated based on the printer name in 

the .print Client of the user machine as follows: BERLIN_HP COLOR or PARIS_EPSON 

STYLUS. It thus exactly matches the share name on the central print server. Using this 

share, you can then print directly to the corresponding printer on the local print 

server: for example HP COLOR on the BERLIN print server. 

The printer folder is then displayed in the user’s session as shown (Illus. 125, 

example for Berlin): 

Illus. 125 

Illus. 125 Printers created with variables in the session 

For more examples of using variables see the “.print Management Center” manual 

(Page 117). 

Modes: Output Gateway printers 

Enable APPLY CLIENT PRINTER PROPERTIES (Illus. 126, lower arrow) to display the properties 

of client-side printer drivers with Driver Free Printing (thus in the Output Gateway’s 

user interface). The option ENABLE SENDING PROPERTIES in the .print Client Manager 

– on (Windows) client machines or local (Windows) print servers – also has to 

be enabled (default setting; Illus. 116). 




Modes: Auto-create and delete printers 

There are two ways to activate .print AutoConnect: 


1. You can configure AutoConnect to create the printers for all users automatically 

(Illus. 126, upper arrow): 

• At each terminal session logon / logoff or virtual desktop logon / logoff or 

• When disconnecting and reconnecting such a session 

Restart the TP AUTOCONNECT SERVICE (Windows service) afterwards. 

Illus. 126 

Illus. 126 Enabling AutoConnect and sending printer driver options 

from client to server 

Each time AutoConnect creates the printers installed on the workstations or thin 

clients (and enabled in the .print Client Manager) in the session (on the terminal 

server or virtual desktop). 

Here, the parameters -i, -q and -p can be used. To do so for logon, the 

following value must be changed in the registry (Illus. 127): 

hkey_local_machine\software\thinprint\TPAutoConnect 

\ListenToWTSCreatCmd 

An example is depicted in Illus. 128. The three permitted parameters have 

been added; they specify that: 

• The Windows error messages are suppressed (quiet) globally for all users (-q) 

• The connection to a .print Client is always established over TCP/IP (-i TCPIP) 

And 

• An alternative TCP port is used (-p 4001). 18 

18 Tip: The TCP port numbers in ThinPrint Port, .print AutoConnect, and .print Client must match. 



Illus. 127 

Illus. 128 

Illus. 127 Using AutoConnect parameters: ListenToWTSCreatCmd in the Registry 

(example) 

Illus. 128 AutoConnect parameters added: -q, -i and -p (example) 

The adequate registry value for logoff is: 

hkey_local_machine\software\thinprint\TPAutoConnect 

\ListenToWTSDeleteCmd 

2. If you want to create printers for certain user(s) only or printers of other 

machines – e.g., local print servers – (additionally), you can run .print Auto- 

Connect by script or from the Command Prompt to do so. 

Furthermore all AutoConnect parameters can be used; see also Page 95. 

Update Please, note the .print AutoConnect update information on Page 110. 




Map additional printers 

Illus. 129 

Illus. 129 Connecting printer shares on central print servers 

independent of selection in the .print Client Manager 


The NAME TRANSLATION tab requires a .print Client on the user’s workstation or terminal. 

If either no .print Client is available on the workstation (or terminal) or non- 

.print printers are to be mapped, further printer shares on any print server can be connected 

with the MAP ADDITIONAL PRINTERS option (Illus. 129). Here is an example for 

the scenario in Illus. 117: 

IP Range Client Name Target 

* * \\printserver\floor_10 

Unlike it’s operation under the tab NAME TRANSLATION, 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 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 .print; if not, then without. 

Context menu 

Similar to the port configuration, the .print AutoConnect program also has the additional 

context menu options of SEND CONFIGURATION, EXPORT, and IMPORT 

(Illus. 130). When sending, the entire AutoConnect configuration is sent to other 

computers; with export/import, only the “Name Translation” and “Map Additional 

Printers” tables are sent. 



Illus. 130 

Illus. 130 Context menu 

Send configuration The SEND CONFIGURATION function lets data from the AutoConnect configuration be 

sent to groups of servers; see also “Procedure when sending” (Page 49). 

Export/Import The EXPORT function (Illus. 130) lets the contents of the tables “Name Translation” 

and “Map Additional Printers” be written in a .csv file 19 (Illus. 131) 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 name translation table on any server 

using the IMPORT function. 

Illus. 131 

Illus. 131 Saving data in a .csv file 

Applying changes 

Once you are finished configuring .print AutoConnect, click APPLY (Illus. 130). 

19 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). 




AutoConnect 

installation 

(Windows Server 

2003 only) 

AutoConnect on central print servers 


In the preceding sections we described the application of AutoConnect on terminal 

servers or virtual desktops. However it may be useful in larger environments to automate 

printer setup on central print servers as well. For this purpose you can either 

use the .print Management Center (Page 117) or do this by installing AutoConnect 

on a central print server (Windows Server 2003 only) and then control it from the 

command line or with a script (Windows Server 2003 and 2008). 

Proceed as follows: 

1. Start the installation procedure for .print Engine on the central print server 

(START→ PROGRAMS→ .PRINT ENGINE→ SETUP). 

2. Accept the license agreement. 

3. The window in Illus. 132 appears. Select INSTALL AUTOCONNECT. 

Illus. 132 

4. To complete installation restart the server (Windows Server 2003 only). You 

can do this immediately if you want (YES in Illus. 13). If you select NO, the 

ThinPrint-Software will become functional after the next server restart. 

Illus. 133 

Illus. 132 Installing .print AutoConnect (Windows Server 2003 only) 

Caution! Before you restart the server make sure that no data will be lost. 

Ensure that all applications are closed and no print jobs active. Selecting YES 

will Restart immediately. If in doubt, select NO (see arrow in Illus. 133). 

Illus. 133 Restart the server: immediately or later? (Windows Server 2003 only) 



AutoConnect 

configuration 

5. Open the AutoConnect configuration (Illus. 106) and select the MODES tab 

(Illus. 126). Disable the options AT SESSION LOGON/LOGOFF and AT SESSION 

RECONNECT/DISCONNECT to prevent deleting the printers (created automatically) 

with logging off from the server. Select APPLY to confirm and restart the 

TP AUTOCONNECT SERVICE (Windows service) afterwards. 

Creating a template Refer back to the printer set up in the scenario shown on Page 32. The printers set 

up manually in that example, using TCP/IP as their protocol, can be set up with Auto- 

Connect. The following example shows how to import printers from a local print 

server to a central print server: 

Execute 

AutoConnect 

6. Set up the following printer template in the PRINTERS (AND FAXES) folder: 

_#Lexmark T620 20 

Note! Open the PRINTERS folder of Windows Server 2008 as an Administrator 

to be able to see all printer objects including templates. To do so open it using 

START→ PROGRAMS→ .PRINT ENGINE→ PRINTERS (Illus. 29). 

7. Connect the template to the ThinPrint port TCP1: 

8. Allocate the following permissions to the template so only administrators may 

view it: 

Administrators Printing, Manage documents and printers 

System Printing, Manage documents and printers 

Delete all permissions of other users. 

9. Open the Command Prompt, change to the .print Engine’s program directory 21 

and import the printer(s) with the following command: 

TPAutoConnect -a printserver1 -f 

The result is shown in Illus. 134. 

Illus. 134 

Illus. 134 Lexmark T620#printserver1:1 created by AutoConnect 

Afterwards, if you want to delete the printer, then enter in the command line: 

TPAutoConnect -d 

20 With Windows Server 2008, select START→ PROGRAMS→ .PRINT ENGINE→ PRINTERS. So you 

will get administrative permissions on the Printers folder. 

21 e.g. c:\Program Files\ThinPrint .print Engine 




Parameters The most important Parameters for a script call are: 

Parameter Function 

-v (Verbose) Display messages; 

give detailed information at startup 

.print Virtual Channel Gateway 

Introduction 


-d Delete the printer(s) for a specific session 

-d all Delete all printers created with templates (admins only) 

-d session_ID Delete all printer(s) of a specific session (admins only). The 

session ID can be found in the PRINTERS (AND FAXES) folder 

under LOCATION (Illus. 43 and 44) 

-q (Quiet) Error messages are not sent to the client machine’s 

desktop 

-r (Repair) Compares saved session information at actually 

existing printer objects (admins only) 

-p port (Port) TCP/IP port number (if other than port 4000) 

Note: The TCP port numbers in ThinPrint Port, .print Auto- 

Connect, and .print Client must match. 

-i protocol (Interconnection) Select protocol for connection to the .print 

Clients; overwrites .print AutoConnect dialog settings 

(acceptable values: TCPIP, VC, AUTO); see Illus. 113) 

-a address Specification of IP address or client name of the computer on 

which a .print Client is running – i.e., of local print servers or 

external print servers of network printers (e.g. SEH TPG120, 

Page 118). 

-? or -h (Help) Will open parameter help panel 

The .print Virtual Channel Gateway is only necessary if .print Engine is installed on 

a central, dedicated print server AND printers must be targeted over ICA or RDP. It 

enables print jobs from central print servers to be sent to the client through the virtual 

channel of an ICA or RDP connection. This lets printers which can’t be reached over 

TCP/IP – for example, behind firewalls or with Network Address Translation (NAT) – 

also be targeted. 

Virtual Channel Gateway is installed onto terminal servers or virtual desktops – 

while .print Engine is running on the central print server(s). Virtual Channel Gateway 

requires at least Microsoft Windows 2000 Server on the server, including Terminal 



Services (ICA and RDP). Either ICA respectively RDP sessions must be opened on the 

terminal server(s) or virtual desktops. 

Note! If .print Server Engine is used as print server software with terminal 

servers, every print server requires the license .print Server Engine and every 

terminal server requires at the license .print Application Server Engine. 

If .print Server Engine is used as print server software with virtual desktops, 

every print server requires the license .print Printserver Basic Pack and every 

desktop requires at a Named User License. See also the “License agreement”. 

Installation 

Only use unambiguous accounts for printing over the Virtual Channel Gateway (i.e., 

not a Guest account), and make sure that the terminal server, the virtual desktop, 

and the central print server are not in different workgroups. 


On terminal servers 

.print Virtual Channel Gateway can be installed on terminal servers with the .print 

Engine installation program (Page 23). 

On desktop computers 


desktops and for terminal servers 22 . Please use the version dedicated to virtual environments 

(and not the one delivered with .print Server Engine). 

1. Copy the file TPVCGateway.exe onto the virtual machine (best you create a program 

directory like C:\Programs\ThinPrint). 

2. Install the file in the program directory from the command line with: 

TPVCGateway.exe -install 

3. In the SERVICES folder, start TP VC GATEWAY Windows service manually 

(Illus. 135). 

22 With the version for terminal servers the IP addresses of print servers have to be set up. 

This is not necessary with the virtual desktop version of Virtual Channel Gateway. 




Illus. 135 


The service runs on port 4000 (default); the port numbers of this service and 

of the ThinPrint Port properties on the central print server(s) must match 

(Page 31). Make sure that no other application is using this port. 

The Virtual Channel Gateway version for desktop computers needs no administration 

at all. 

Configuration 

Illus. 135 Starting the Virtual Channel Gateways service manually 

Local – Start Virtual Channel Gateway configuration on the terminal server or virtual 

desktop with START→ PROGRAMS→ .PRINT ENGINE→ VIRTUAL CHANNEL GATEWAY 

(Illus. 136). The menu in Illus. 137 appears. 

Remote – For remote configuration, see Page 79. 

Illus. 136 

Illus. 136 Starting configuration of Virtual Channel Gateway 




Illus. 137 

ADD Select ADD to enter IP addresses for print servers, on which .print Engine is installed 

and .print Virtual Channel Gateway is to be used for printing. 

CHANGE Modify IP addresses for print servers 

DELETE Delete a print server’s IP address 

TCP PORT TCP Port number for TCP/IP communication with the .print Engine (default: 4000). 

Tip: The TCP port numbers in .print Engine (on print servers) and .print Virtual Channel 

Gateway (on terminal servers or virtual desktops) must match. 

APPLY Apply changes. 

Illus. 137 .print Virtual Channel Gateway panel in MMC 

Using Virtual Channel Gateway 

– Terminal servers only: In the Virtual Channel Gateway dialog on the terminal 

servers, enter the IP addresses of central print servers (Illus. 137). 

– Configure the printers on the client(s) (Illus. 138); see the respective .print 

Client user manual (Page 117), e.g., 

• for Windows clients: “.print Client Windows” 

• for thin clients (Page 118): “.print Client WinCE” or “.print Client Linux” 




Illus. 138 


– Configure the printers on the central, dedicated print servers, and share them 

(Illus. 139). Connect the printers with a ThinPrint Port selected to USE VIRTUAL 

CHANNEL GATEWAY (Illus. 140). 

Illus. 139 

Illus. 140 

Illus. 138 Two printers in the .print Client Windows (ICA) on the computer from which 

the session was started (example) 

Note! ThinPrint Output Gateway will only function with clients with an operating 

system starting with Windows 95. The printer's driver must be installed 

on these clients. 

Illus. 139 Two printer shares on a central print server – 

with and without a given printer ID (example) 

Illus. 140 Both printers connected to the ThinPrint Port “ICA1:” (example) 

– Specify at least one entry in the AutoConnect MAP ADDITIONAL PRINTERS table 

on the terminal server(s) or virtual desktops for each printer share on the print 

server (Illus. 141). 



Printing 

Illus. 141 

Illus. 141 Two entries for AutoConnect (example) 

– Alternatively, you can also use the NAME TRANSLATION table (Illus. 142). 

Illus. 142 

Illus. 142 Alternative entries for AutoConnect (example) 

– Establish an RDP connection to the terminal server farm from the Client 

(Illus. 138) as “user2” as shown in our sample scenario (Page 26). .print Client 

Windows (RDP) starts automatically with the session, and .print AutoConnect 

creates the session printers immediately thereafter (Illus. 143). 




Appendix 

Illus. 143 

– Open an application and print to each of these printers. 

The print data is forwarded from .print Client to the printers as follows: 

Customer service and technical support 

Customer Service www.thinprint.com/→ SUPPORT & SERVICES 

support@thinprint.com 

Downloads See Page 9 

Client Protocol addressed printer ID Target printer 

Epson Stylus 

Color 400 

Illus. 143 Resulting printers in the session (example) 

Appendix 

ICA 2 Printer with ID 2 

HP DeskJet ICA no .print Client’s 


Note! Please also see the checklist on Page 38. 


Appendix 

Entering and activating licenses 

Note! Activating a .print 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 key's expiration date can be found in License Manager 

under VALID UNTIL (Illus. 11, Page 21). 

Once you have successfully installed and tested the .print 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. 

1. Open the License Manager from START→ PROGRAMS→ .PRINT ENGINE→ LICENSE 

MANAGER to enter license keys, check registration keys (for activation), and activate 

licenses (Illus. 144). 

2. The window depicted in Illus. 145 or 146 will open; select the desired function: 

Add, Activate, Copy, Export, or Delete 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! 

Note! Use the Delete option only if you have to transfer User or Server Access 

license keys from one machine to another to split them between several servers. 

Alternative: You can delete licenses in the Windows Registry under 

hkey_local_machine→ software→ thinprint→ licenses if you 

want to keep the option of later reentering licenses open. 

Illus. 144 

Illus. 144 Starting License Manager (example for Windows Server 2003) 




Illus. 145 

Illus. 146 

Appendix 

Illus. 145 Context menu for one license key (example for server-based licensing) 

Illus. 146 Context menu for all license keys (example for user-based licensing) 

Note! To avoid issues with ThinPrint licenses disable the Windows explorer 

option “Automatically search for network folders and printers“ per Policy for all 

PCs and/or users. 

Reinstalling, uninstalling or disabling .print components 

For later installation of .print components, for their uninstallation or for viewing version 

information, start the .print Engine installation program with START→ PRO- 

GRAMS→ .PRINT ENGINE→ SETUP (Illus. 147). The menu in Illus. 150 will open. 

Illus. 147 

Illus. 147 Starting .print installation routine (example for Windows Server 2003) 

Note! Have any .print files been moved or deleted after first installation, the 

message in Illus. 148 will open. Click OK and select the new path (Illus. 148). 


Appendix 

Illus. 148 

Illus. 149 

Illus. 148 .print installation path not found 

Illus. 149 Assigning new installation path 

Note! If individual files cannot be deleted during uninstallation of a .print 

component, they will be deleted automatically the next time the computer is 

rebooted. For this reason, the computer might have to rebooted before the next 

installation of a .print component. 

Central print server(s): .print Engine 

1. To release locked files restart Windows. 

2. Before removing the .print Engine delete all printer objects in the PRINTERS (AND 

FAXES) folder which use TP Output Gateway as the printer driver. Connect all 

printer objects connected to ThinPrint Ports to other printer ports. 

3. Run Setup (Illus. 147). 


Select ...: 

... to add ... to delete 

INSTALL .PRINT ENGINE UNINSTALL .PRINT ENGINE 

INSTALL AUTOCONNECT (see Page 95) UNINSTALL AUTOCONNECT 

Recommended:Restart the print spooler before uninstalling .print Engine. 




Illus. 150 

Illus. 150 .print Engine installation menu on a print server 


Appendix 

Terminal server(s) or virtual desktops: .print AutoConnect, and Virtual Channel Gateway 


2. Run Setup (Illus. 147). 


Select ...: 

... to add ... to delete 

INSTALL AUTOCONNECT (see Page 76) UNINSTALL AUTOCONNECT 

INSTALL VC GATEWAY (see Page 97) UNINSTALL VC GATEWAY 

Note! The SERVICES configuration must be closed to uninstall a Windows service 

(here: TP AUTOCONNECT SERVICE and TP VC GATEWAY SERVICE). 


Appendix 

Illus. 151 

Illus. 151 .print Engine installation menu on a terminal server 


Terminal server(s) or virtual desktops: ThinPrint Output Gateway 

Uninstallation – In the server’s PRINTERS (AND FAXES) folder, select: 

FILE→ SERVER PROPERTIES→ DRIVER→ TP OUTPUT GATEWAY→ REMOVE 

Central print server(s): Printer Virtualization Layer 

Disabling See the “.print Server Engine 7.6 Feature Release 1” manual (Page 117). 

Updating .print components 

.print Server Engine update information 

With .print version 7.6 a new license model has been introduced. It allows a central 

license management of all servers involved in the print process – irrespective of the 

licensing type (server-based or user-based). This requires for each computer that utilizes 

the central print server(s) an installed Server Access license (also called .print 

Access License) or .print Host Access license on the central print server(s). 

Existing customers whose .print Application Server Engine have a valid update service 

should when updating to version 7.6 request a – free of charge – Server Access 

license per updatable .print Application Server Engine on: 

www.thinprint.com/accesslicense 

On central print servers, you need a valid Update Subscription (of .print Server 

Engine) + an additional Server Access license (at least 1) for the software update. 

The Server Access licenses are mandatory for normal operations of the .print 

Server Engine. More information can be found in the “What’s new in ThinPrint .print 

v7.6?” white paper (Page 117). 




Appendix 

Procedure 

For updates of older .print versions use the Setup.exe from the new .print version. 

The menu in Illus. 152 will open. 

Note! Updating the software might require a server reboot. 

Central print server(s): .print Engine 


2. Run the Setup.exe from the new .print version. 


4. Select UPDATE .PRINT COMPONENTS. 

Note! To update a .print version older than 6.0 at first remove the old program 

at the CONTROL PANEL and then install the new version. 

Illus. 152 

Illus. 152 Updating .print components on a print server 


Terminal server(s) or virtual desktops: .print AutoConnect, and Virtual Channel Gateway 


2. Run the Setup.exe from the new .print version. 


4. Select UPDATE .PRINT COMPONENTS. 


Appendix 

AutoConnect 

update 

Illus. 153 

Until version 6.5, shares on print servers were only connected in script mode. Updating 

to version 7.6 does not change this setting. If you nevertheless also want printer 

shares to be connected without a script, delete the parameter -N in the following 

value in the Windows Registry (Illus. 154): 

hkey_local_machine\software\thinprint\ 

TPAutoConnect\ListenToWTSCreatCmd 

Illus. 154 

See also Page 115. 

Illus. 153 Updating .print components on a terminal server 


Illus. 154 AutoConnect parameters in the Windows Registry 

Terminal server(s) or virtual desktops: ThinPrint Output Gateway 

Update – In the server’s PRINTERS (AND FAXES) folder, select: 

FILE→ SERVER PROPERTIES→ DRIVER→ TP OUTPUT GATEWAY→ REINSTALL 




Disabling 

printer share 

mapping 

Disabling 

client printer 

mapping 

Disabling Windows printer mapping 

Appendix 

To simplify the selection of a .print printer within a session on a terminal server or 

virtual desktop, the Windows automatic printer mapping function should be disabled 

within and outside of the session. To do so (on the terminal server or virtual desktop): 

1. In Windows Explorer, select TOOLS→ FOLDER OPTIONS→ VIEW. 

2. Disable the AUTOMATICALLY SEARCH FOR NETWORK FOLDERS AND PRINTERS function 

(Illus. 155). Confirm with OK. 

Illus. 155 

Illus. 155 Explorer settings for printer 

mapping 

1. In Windows Control Panel, select ADMINISTRATIVE TOOLS→ TERMINAL SERVICES 

CONFIGURATION. 

2. Click on the RDP-TCP connection and select ACTION→ PROPERTIES (Illus. 156) 

3. Disable CONNECT CLIENT PRINTERS AT LOGON, DEFAULT TO MAIN CLIENT PRINTER, 

and WINDOWS PRINTER MAPPING (Illus. 157). Confirm with OK. 

Illus. 156 

Illus. 156 Opening RDP configuration 


Appendix 

Illus. 157 

Illus. 157 Session settings for printer 

mapping 

4. If available, click on the ICA-TCP connection and select ACTION→ PROPERTIES 

(Illus. 156) 

5. Disable CONNECT CLIENT PRINTERS AT LOGON, DEFAULT TO MAIN CLIENT PRINTER, 

and WINDOWS PRINTER MAPPING. Confirm with OK. 

MMC functions 

Examples of context menus in the MMC 

Illus. 158 

Illus. 158 Example 1: Computer node context menu 




Illus. 159 

Illus. 160 

Illus. 159 Example 2: .print Engine context menu 

Illus. 160 Example 3: AutoConnect context menu 

Appendix 

Context menu functions at a glance 

Use the following options to configure each .print component with the Microsoft Management 

Console: 

.print component Function Context menu 

System 

(computer node) 

• Remote configuration of ThinPrint 

Ports, licenses, AutoConnect, .print 

Clients, and/or Virtual Channel Gateways 

.print Engine Create new ThinPrint Port (TCP/IP, 

ICA, RDP, or LPD) 

Create new ThinPrint Port for .print 

Connection Service 

CONNECT TO ANOTHER COMPUTER 

NEW PORT→ THINPRINT PORT 

NEW PORT→ THINPRINT CONNECTION 

SERVICE PORT 


Appendix 


Selected 

ThinPrint Port 

Insert ThinPrint Port from another 

.print Engine from Windows clipboard 

Import ThinPrint Port data from an 

.xml file 

Export all ThinPrint Port data to an 

.xml file 

Send ThinPrint Port data to (an)other 

server(s) 

PASTE FROM CLIPBOARD 

ALL TASKS→ IMPORT/EXPORT→ IMPORT 


ALL TASKS→ IMPORT/EXPORT→ EXPORT 


ALL TASKS→ IMPORT/EXPORT→ SEND 

PORT CONFIGURATION (OVERWRITE) or 

ALL TASKS→ IMPORT/EXPORT→ SEND 

PORT CONFIGURATION (ADD ONLY) 

Register name of SSL/TLS certificates ALL TASKS→ ENCRYPTION SETTINGS 

Register tracking server, enable print 

job tracking, and select tracking mode 

Reload port data into MMC REFRESH 

ALL TASKS→ TRACKING SETTINGS 

Restart print spooler ALL TASKS→ RESTART SPOOLER 

Write port data to a text file EXPORT LIST 

Copy port data into clipboard 

(can be inserted in another .print 

Engine only) 

Insert ThinPrint Port of another .print 

Engine from Windows clipboard 


COPY 

PASTE 

Export port data into an .xml file EXPORT CONFIGURATION 

Send ThinPrint Port to (an)other 

server(s) 

Delete ThinPrint Port DELETE 

Reload port data into MMC REFRESH 

Run ThinPrint Port configuration; 

see Page 40 

SEND PORT CONFIGURATION (OVERWRITE) 

or SEND PORT CONFIGURATION (ADD 

ONLY) 

PROPERTIES 

Licenses • Enter a new license key ADD LICENSE KEY 

• Enter or activate multiple license 

keys (including Subscription keys); 

see the “Unattended installation and 

licensing of .print server components” 

white paper 

LICENSE/ACTIVATION SET 




• Reload license data in the MMC REFRESH 

• Copy the complete table to a text file EXPORT LIST 

Selected license • Activate a license key ACTIVATE 

• Enter a Subscription key for an activated 

license key 

ADD SUBSCRIPTION KEY 

Appendix 

• Copy one or all keys to the clipboard COPY→ LICENSE KEY, COPY→ REGISTRA- 

TION KEY, COPY→ ACTIVATION KEY, or 

COPY ALL 

Caution! 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! (Page 104) 

DELETE 

• Reload license data in the MMC REFRESH 

.print Client Reload .print Client settings in the 

MMC (see also the “.print Client 

Windows” user manual, Page 117) 

.print AutoConnect Send all AutoConnect properties to 

(an)other server(s) 



Convert old name translation table to 

new format (only necessary after an 

update) 

Restart TP AUTOCONNECT SERVICE 

(Windows service) 

ALL TASKS→ REFRESH 

SEND CONFIGURATION 

ADVANCED NAME TRANSLATION 

ALL TASKS→ RESTART SERVICE 

Reload AutoConnect data into MMC ALL TASKS→ REFRESH 

Write NAME TRANSLATION and MAP 

ADDITIONAL PRINTERS tables to a .csv 

file 

Read NAME TRANSLATION and MAP 

ADDITIONAL PRINTERS tables from a .csv 

file 

Send all Virtual Channel Gateway 

properties to (an)other server(s) 

ALL TASKS→ EXPORT 

ALL TASKS→ IMPORT 

SEND CONFIGURATION 

Restart “TP VC Gateway Service“ ALL TASKS→ RESTART SERVICE 

Reload Virtual Channel Gateway data 

into MMC 

ALL TASKS→ REFRESH 


Appendix 

Remote client configuration 

Remote configuration is possible for .print Client Windows printing with TCP/IP protocol. 

The entry RmtConf is needed in the Windows registry of all client machines 

you want to configure. This can be done manually (Illus. 161) or by using the Custom 

Installation Wizard 7.0 or 7.0 V (see the Preconfiguration and unattended installation 

of .print Client Windows white paper). 

– Open the Windows registry of the client machine you want to configure. Add 

the entry RmtConf (reg_mulit_sz) under hkey_local_machine\software\thinprint\client. 

Enter the IP addresses of all those machines from which the client 

should be configured (Illus. 161). 

– Restart .print Client. 

– Go to the machine on which .print Engine is installed. Open the MMC, select 

.print Client snap-in and enter the address of the client machine to configure 

(Illus. 162). 

– Now, the selected machine is ready for remote configuration (Illus. 163). 

Illus. 161 

Illus. 161.print Client machine: 

Registry entry RMTCONF added for remote configuration of .print Client 




Illus. 162 

Illus. 163 

Additional sources 

Appendix 

Illus. 162.print Engine machine: Open the MMC, select .print Client snap-in and enter 

the address of the client machine to configure 

Illus. 163.print Engine machine: Remote configuration of a .print Client 

Further information about ThinPrint .print can be downloaded from our website. 

Manuals The following manuals are available at www.thinprint.com/→ FIND PRODUCT 

→ → MANUAL(S) or ...→ DOCUMENTATION: 

■ .print Server Engine 7.6 Feature Release 1 (Printer Virtualization Layer) 

■ .print Tracking Service 

■ .print Management Center 

■ .print Application Server Engine 

■ .print Engine for VMware View 

■ .print Connected Gateway 

■ .print Queue Manager 


Appendix 

■ .print Host Integration Service 

■ .print Client user manuals 

White papers The following white papers can be downloaded at www.thinprint.com/→ FIND PRO- 

DUCT→ .PRINT SERVER ENGINE→ WHITE PAPERs or ...→ DOCUMENTATION or 

www.thinprint.com/→ SUPPORT & SERVICES→ WHITE PAPER DOWNLOAD: 

■ Creating SSL/TLS certificates for printing with ThinPrint .print 

■ Microsoft Cluster Services and ThinPrint .print 

■ ThinPrint Ports 

■ Tips for configuring ThinPrint .print 

■ .print addressing 

■ .print AutoConnect and .print Virtual Channel Gateway 

■ SAP and ThinPrint .print 

■ .print Clients (overview) 

■ Licensing 

■ Unattended installation and licensing of .print server components 

■ Preconfiguration and unattended installation of .print Client Windows 

■ Windows machine as a .print Client Gateway 

■ IAPS ThinPrint as a .print Client Gateway 

■ SEH ISD200/300 as a .print Client Gateway 

■ SEH TPG60/120 as a .print Client Gateway 

■ Intermate 10x as a .print Client Gateway 

■ ThinPrint port configuration for bandwidth controlled printing via LPR / LPD 

■ Adaption of Output Gateway options 

Thin clients At www.thinprint.com/→ FIND PRODUCT→ .PRINT RDP ENGINE→ SUPPORTED THIN 

CLIENTS you will find terminals with embedded ICA/RDP version of .print Client. 

These can be used for .print Virtual Channel Gateway. 

Downloads ■ Download the .print Engine: www.thinprint.com/→ FIND PRODUCT→ .PRINT 

SERVER ENGINE→ DEMO 

■ Download the .print Client Windows: www.thinprint.com/→ SUPPORT & SER- 

VICES→ SOFTWARE DOWNLOAD→ CONTINUE→ .PRINT CLIENT COMPONENTS→ 

.PRINT CLIENT WINDOWS 7.6 

Glossary 

ActiveX Microsoft technology that enables software components to interact with one another 

in a networked environment regardless of the language in which they were created. 

ActiveX is built on the Component Object Model. 

Activation key Entering the activation key in License Manager enables unlimited application of the 

.print software. An activation key is obtained by submitting license and registration 

keys to ThinPrint GmbH. 

Autocreated 

printers 

see .print AutoConnect 




Appendix 

Bandwidth The capacity of a network or data connection for digital transmission, usually measured 

in bit/second (bit/s, bits/sec, or bps) or in Kilo-bit/ second (kbit/s, kbits/sec, or 

kbps). 

Bandwidth control A ThinPrint Port regulates bandwidth for print jobs. Because bandwidth is controlled 

separately per printer port and can be set individually, optimal performance can be 

achieved with the following .print settings: 

■ Number of ThinPrint Ports 

■ Different bandwidth settings for each ThinPrint Port 

■ Assignment of printers to ThinPrint Ports 

Class see Printer Class 

Client The term client signifies a device which connects to, requests data from, and/or starts 

an application on, a server. It receives, for example, print data from the server and 

forwards it to a printer. Typical clients are: desktop PCs, notebooks, thin clients, print 

servers, PDAs, and mobile telephones. 

Client Gateway see Gateways 

COM Component Object Model; fundamental communication model for icon communication 

under Windows NT. 

Compression In addition to bandwidth control, ThinPrint .print 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; Illus. 78) 

Nonetheless, when printing with either Driver Free Printing or with the original printer 

driver (native printing) a higher or lower compression may be chosen without compromising 

the print quality (Page 44). 

Connection Service .print Connection Service enables printing to .print Clients that are hidden behind 

Network Address Translation (NAT). But in contrast to .print Virtual Channel Gateway 

the print data is sent over pure TCP/IP and not over the ICA or RDP channel. 

.print Engine sends all print jobs to the .print Connection Service, which passes 

them on to the .print Clients. No IP addresses are used for addressing the .print Clients, 

but a .print specific Client ID. This Client ID is assigned automatically by the 

.print Connection Service (dynamic mode) or is created manually in the .print Client 

(static mode). 

Current printer Setting in the .print 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 .print Auto- 

Connect (with the option DEFAULT AT SERVER). 

Data type Several types are usually supported for printing under Windows. The two most commonly 

used – expanded metafile (EMF) and print-ready (RAW) – affect performance 

on both client and print server machines differently. See also EMF 


Appendix 

Dedicated 

print server 

Driver Free (Native) 

Printing 

A served “dedicated” to a single task: printing. A terminal server or virtual desktop 

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 

or virtual desktop load is thus lightened. (see also Print server) 

Device Here: thin client, print server, printer (print device), print appliance or print server 

(print box) 

Printing with ThinPrint Output Gateway; s. Page 7 (Driver Free Printing and Printer 

Virtualization Layer) 

EMF EMF (enhanced metafile) is default data type for most Windows NT 4.0/2000/ 

XP/2003/Vista 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 or virtual desktop (in consideration of system performance). 

The main work is performed by the client machine, which improves the terminal 

server’s or virtual desktop’s performance. See also Data type 

Encryption see SSL 

Fat client see Rich Client 

Gateways .print differs between four kinds of gateways: 

1. ThinPrint Output Gateway: 

ThinPrint .print’s virtual printer driver 

2. .print 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. .print Client Gateway: 

Local print server with installed .print Client 

4. .print Connected Gateway: 

.print Client Gateway connected with .print Connection Service; for using in networks 

with Network Address Translation. For local print servers located in 

masked networks additional .print licenses are required; see .print Connected 

Gateway user manual (Page 117). 

ICA Independent Computing Architecture (from Citrix); network protocol for communication 

between Windows terminal servers (or virtual desktops) 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. 

IP masking see Network Address Translation 

License key All .print software requires a license key. The key has the format: THxx-xxxx-x-xxxxxxxxxx 

(32 bit) or TAxx-xxxx-x-xxxxxx-xxxx (x64). License Manager uses the license key 




Appendix 

to generate a registration key according to system configuration. Both license key and 

registration key are required to request the activation key. 

Local resources Local in this sense means available to or installed upon the selected computer. Client 

operating systems always search first for a local printer driver. When printing on the 

client side, then, the printer driver is first sought on the client computer, and only if 

necessary is a driver downloaded from the server. 

LPD client An LPD client is a network end device which supports the Line Printer Daemon 

(LPD); e.g., an internal or external print server of a network printer, or a Linux terminal. 

It is also possible to print with ThinPrint .print to LPD devices, even if there is 

no .print Client available there. Although compression cannot be used, bandwidth 

control is available to improve printing in this environment. 

LPD filter An LPD filter is run on LPD clients to decompress print jobs which have been processed 

over ThinPrint .print. 

LPR Line Printer Remote; Program for issuing a print job (Client component for LPD) 

Masking see Network Address Translation 

MetaFrame see XenApp 

Network Address 

Translation (NAT) 

Output Gateway see Gateways 

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. 

.print AutoConnect The .print component for auto-created printers is called .print AutoConnect. It can 

be run on any Windows server. .print AutoConnect enables the printers needed for 

each client to be created automatically on the server. 

.print Client On the client side, .print Client is generally responsible for receiving print data, 

decompressing and decrypting it, and sending it to the print device. Many .print 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, Symbian (e.g. UIQ 

and Nokia series 60 and 80), Java, ActiveX, as well as for internal or external print 

servers of network printers. 


Gateway 


Service Windows 

see Gateways 

The Windows service version of .print 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 .print Client is therefore 

particularly well suited for local print servers under Windows (.print Client Gateways). 

.print Client Service Windows is not designed for print preview with Driver Free Printing. 


Appendix 

.print Connection 

Service 

see Connection Service 

.print Engine The server component .print Engine is the actual core of the ThinPrint .print framework. 

It provides complete printer driver management including Driver Free Printing. 

The .print 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). 

.print Viewture .print component for the client-side print preview with Output Gateway. Viewture 

consists of the components TPView.dll and TPView.exe with the following functions 

and features: 



TPView.dll is also installed together with .print Engine on non-terminal servers. In 

this case, it helps with Printer Virtualization Layer. 

see Gateways 

Presentation Server see XenApp 

Port pooling s. Page 54 

page preview ✕ 

TPView.dll TPView.exe 

zoom ✕ ✕ 

leaf ✕ ✕ 

save in .tpf file format ✕ 

open .tpf file format ✕ 

print ✕ ✕ 

installation with .print Client ✕ 

can be downloaded from 

www.thinprint.com 

Print device Contrary to popular nomenclature, hardware which produces printed material is 

called a print device and NOT a printer. Print resolution is measured in DPI (Dots Per 

Inch). The higher the DPI value, the better the resolution. See also Printer 


✕ 



Appendix 

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 (AND FAXES) folder by an icon with an obvious name. 

There is generally not a one-to-one relationship between printer and print devices. 

Several printers for a single print device, for example, signify that either the print 

device is connected to several computers, or that many printers with different parameters 

for the same print device have been set up on a computer. 

For better understanding, this manual only distinguishes between printers, printer 

objects, and print devices when the specific context makes it necessary. 

Printer class Printers whose drivers are compatible can be grouped in a class. For example, many 

laser printers are compatible with HP LaserJet (class could be: HPLaser). Only one 

entry in the name translation tab of .print AutoConnect is necessary for all printers in 

a class. 

Printer driver Printer drivers are programs which enable communication between client applications 

and print devices. Each print device requires unambiguous commands which 

are specific to that device, to employ such print functions as color, margin, format, 

etc. An operating system comprehends these individual commands for specific print 

devices through the printer driver. 

Printer object Under Windows: a printer created over START→ SETTINGS→ PRINTERS (AND FAXES); it 

appears with its name in the PRINTERS (AND FAXES) folder. 

Printer pool see Port pooling 

Printer queue The number of documents which are to be printed from a particular print device 

and/or are already waiting for processing is referred to in NT terminology as the 

printer queue. Under NetWare and OS/2, the term printer queue is synonymous for 

printer. 

Printer software Printer software is the commonly used name for logical printer or printer. 

Printer 

Virtualization Layer 

Printing with ThinPrint Output Gateway; s. Page 7 (Driver Free Printing and Printer 

Virtualization Layer) 

see also the “.print Server Engine 7.6 Feature Release 1” manual 

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. 

Print server 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 


Appendix 

Print server 

services 

Print spooler see Spooler 

Remote Desktop 

Connection 

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. 

Queue see Printer queue 

RDP Remote Desktop Protocol; communication protocol between multiuser NT (NT 4.0, 

2000, XP, 2003, or Windows Vista) servers and clients under a Windows operating 

system. The name of the NT service is Terminal Services, and the connection type 

under Windows XP is named Remote Desktop Connection. 

see RDP 

Rendering A printer driver is used to translate a print job into printer-specific format. 

Rich client Computer with high performance hardware (= PC). Applications can be locally 

installed and run. 

Server based 

Computing 

A server-centric basis for enabling user access to applications, with application logic 

being run on a server or virtual desktop and only user interface transmitted through 

the network. See also Terminal server 

Spooler Print spooler describes the number of those programs or DLLs (Dynamic Link Libraries) 

which receive, process, temporarily save, chronologically sort, and distribute 

queued print jobs. 

With network printers, the spooler has a client component and a server component. 

The client component is normally found where the application is being run. The 

server component is generally where the print device is installed, at the print server, 

for example (Windows service denomination: “Print Spooler”). 

Spooling Simultaneous Peripheral Operation On Line: Print jobs are temporarily stored as files 

on a hard disk. This procedure is known as spooling and is only one of the several 

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. 

Terminal server a server with Terminal Services 




Appendix 

Terminal Services a Windows service under Windows 2000 Server, Windows XP Professional, 

Windows Server 2003, or Windows Vista (Business, Enterprise, or Ultimate) 

Thin client a minimum performance computer with only elementary hardware and/or software 

components (no hard drive) 

In a server/client architecture, a client system on which no application programs 

are run. Instead, all applications are processed at the server. 

ThinPrint Output 

Gateway 

see Gateways 

ThinPrint Port To print with ThinPrint .print, printers are linked to ThinPrint Ports on the machine 

that creates the print jobs. These printer ports are created and configured with the 

MMC. 23 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. 

Virtual Channel 

Gateway 

TLS see SSL 

see Gateways 

x64 Identifies all 64-bit processors from Advanced Micro Devices (AMD) as well as Intel 

processors with an AMD compatible 64-bit extension (e.g. Xeon and Pentium with 

EM64T). In contrast ia64 identifies the 64-bit processor Itanium from HP and Intel. 

XenApp Server-based software (Citrix) for Microsoft Terminal Services; 

formerly MetaFrame alias Presentation Server 

Abbreviations 

ASP Application Service Providing 

COM Component Object Model 

DFNP Driver Free Native Printing (= Printer Virtualization Layer) 

DLL Dynamic Link Library 

EMF Enhanced Metafile (see glossary) 

FR Feature Release 

ICA Independent Computing Architecture (see glossary) 

ID Identification (number) 

IPv4 Internet Protocol address space with 2 32 addresses; example: 192.168.1.1 

IPv6 Internet Protocol address space with 2 128 addresses; 

example: 2001:0db8:85a3:08d3:1319:8a2e:0370:7344 

23 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) 


Appendix 

IPX/SPX Internetwork Packet Exchange / Sequenced Packed Exchange (from Novell) 

LAN Local Area Network 

LPD Line Printer Daemon (see glossary) 

LPR Line Printer Remote (see glossary) 

LPT Windows Line Printer Port 

MMC Microsoft Management Console 

NAT Network Address Translation 

OS Operating System 

Output Gateway ThinPrint Output Gateway 

PCL Printer Command Language 

PDA Personal Digital Assistant 

RAW Standard Print Data Type 

RDP Remote Desktop Protocol (see glossary) 

RFC Request for Comments; Series of documents, begun in 1969, which describe the 

Internet Protocol Suite and relevant experiments 

SBC Server Based Computing 

SQL Structured Query Language 

SSL Secure Socket Layer (see glossary) 

TCP/IP Transport Control Protocol / Internet Protocol 

TLS Transport Layer Security 

TP ThinPrint 

TPOG ThinPrint Output Gateway 

TPVC .print Virtual Channel Gateway 

ULA User License Agreement 

URL Uniform Resource Locator (web address) 

VC Virtual Channel (= ICA or RDP) 

VC G(ateway) .print Virtual Channel Gateway 

VCP Virtual Channel Protocol (= ICA or RDP) 

VDI Virtual Desktop Infrastructure (e.g., VMWare VDI, Citrix XenDesktop) 

V-Layer Printer Virtualization Layer 

WAN Wide Area Network 

Win32 Windows 9x, ME, NT 4, 2000, XP, 2003, and Windows Vista 

WinCE Windows CE 

WinNT Windows NT 4, 2000, XP, 2003, and Windows Vista 

WLAN wireless LAN = Wi-Fi 

WMI Windows Management Instrumentation 




.print Engine feature comparison 

a Central print servers in VMware View environments only 

b Linux and Windows CE only 

c Per encryption of RDP connection only 

d Via .print Virtual Channel Gateway 

e .print Engine Unix only 

.print 

Application 


Engine 


RDP 







for 

VMware 

View 


Desktop 




Unix, 

AS/400 

+ Host 

Recommended server environments 

• Terminal servers 

with Windows Server 2003/2008 (x64) 

with/without Citrix XenApp 

● ● – – – – 

• Other Windows 2003/2008 (x64) servers as 

well as environments with central dedicated 

print servers 

– – ● ● a 

– 

• PCs with Windows XP Prof. (x64) – – – – ● – 

• Virtual Windows XP (x64) desktops 

(e.g. VMware or Citrix XenServer) 

– – – – ● – 

• Linux, Solaris, AIX, or HP-UX, OS/400, 

MVS, OS/390, or z/OS 

Supported client environments 

– – – – – ● 

• Windows Vista, Vista x64, XP, XP x64, 

2003, 2003 x64, 2000, NT 4, 9x, ME 

● ● ● ● ● ● 

• Linux, Java, Windows CE, 3.x, MS-DOS ● ●b ● ● ●b ● 

Plug-and-play installation ● ● – – ● – 

User-based licensing ● – ● – – – 

MMC configuration ● – ● ● – – 

SSL/TLS encryption ● ●c ● – ●c ● 

Driver Free Printing ● ● ● ● ● – 

Native printing ● ● ● ● ● ● 

Multiple printers per user ● ● ● ● – ● 

Bandwidth control 

Network protocols 

● – ● ● – ● 

•TCP/IP (sockets) 

● – ● 

•ICA 

•RDP 

• LPR/LPD 

● 

● 

● 

– 

● 

– 

●d ●d ● 

● 

– 

● d 

– ● 

● 

– 

● 

– 

– 

– 

● e 

Supported .print components 

• AutoConnect 

● ● ● ● ● – 

• Virtual Channel Gateway 

– – ● ● – – 

• Printer Virtualization Layer (V-Layer) 

– – ● ● – – 

•Tracking Service 

● – ● – – ● 

• Connected Gateway 

● – ● – – 

• Queue Manager 

● – ● – – 

• Host Integration Service 

● – – – – 

e 

● e 

– 

– 

.print Engine feature comparison 127

.print Server Engine and .print Printserver Basic Pack ... - ThinPrint

Create successful ePaper yourself

Delete template?

Save as template?