ThinPrint Application Server Engine

Transcription

1 ThinPrint Application Server Engine (version 8.6) Manual Cortado AG Alt-Moabit 91 a/b Berlin Germany/ Alemania Cortado, Inc Grandview Avenue Suite 200 Denver, Colorado USA/EEUU Cortado Pty. Ltd. Level 20, The Zenith Centre, Tower A 821 Pacific Highway Chatswood, NSW 2067 Australia info@team.cortado.com Web: Issued: March 22, 2012 (v292)

2 Notes Copyright This document is the intellectual property of Cortado AG. This document may be copied in whole or in part, provided this Copyright notice is included in every copy. Registered trade marks All hardware and software names mentioned in this document are the registered trademarks of their respective companies or should be regarded as such. Safety warning All Cortado products are pure software solutions. Please note the safety warnings in the technical documentation from your hardware vendor and from the manufacturer of each device and component. Before beginning installation, we recommend closing all windows and applications and deactivating any virus scanner. Cortado AG Manual ThinPrint Application Server Engine

3 Contents Introduction... 6 What is ThinPrint?... 6 Server components... 6 Driver Free Printing... 6 Advanced Adaptive Compression... 7 Client component... 7 Package contents... 7 Licenses... 7 Scenarios... 8 Terminal server(s) Printing via TCP/IP... 8 Terminal server(s) Printing via ICA/RDP... 8 Installation... 9 Technical requirements... 9 ThinPrint Engine... 9 ThinPrint Client Installing ThinPrint Engine (per terminal server) Installation with installation wizard New Printers Disabling Windows printer mapping Sample configuration Installing ThinPrint Clients Configuring thin client Configuring local print server client2: RDP type of ThinPrint Client Windows on a PC Server configuration ThinPrint Ports Configuring AutoConnect Printing If you still can't print Checklist Cortado AG 2012 ThinPrint Application Server Engine Manual 3

4 Contents Configuring ThinPrint Ports Starting Port Manager Configure tab Advanced tab Job Statistics tab Distributing port configuration Creating printers and templates Templates Manually created printers Port pooling Printing with thin clients Overview Preparations on the server Preparing ThinPrint Client (example for Windows CE) Printing ThinPrint Output Gateway Paper formats and trays Presettings on the server (administrators only) Settings in a terminal session Printing with preview Finishing options Language versions Cloud Printing Print-to-Cloud Print-to-ePaper Encrypting print jobs Importing SSL certificates on the servers Importing SSL certificates on the clients Print job tracking Tracking Service Tracking Report Engine Preparing ThinPrint Engine and Tracking Service Cortado AG Manual ThinPrint Application Server Engine

5 Contents AutoConnect AutoConnect features Basic constellation Templates and ports Template permissions AutoConnect configuration Settings Dynamic Printer Matrix Variables Script control Map additional printers Send, export and import the configuration Appendix Customer service and technical support Licenses Entering and activating license keys License usage Server roles and custom setup Session-in-Session Update Uninstallation Remote client configuration Additional sources Glossary Abbreviations ThinPrint Engine feature comparison Cortado AG 2012 ThinPrint Application Server Engine Manual 5

6 Introduction Introduction What is ThinPrint? ThinPrint is a software solution for effective print management. It consists of a server as well as a client component, i.e. ThinPrint Engine and ThinPrint Client (Illus. 1). Illus. 1 Illus. 1 Using ThinPrint with server and client components Server components The server component ThinPrint Engine is the core of the ThinPrint framework. It provides complete printer driver management including Driver Free Printing. ThinPrint Engine performs the following main functions: Bandwidth controlled transmission of print jobs Print data compression and streaming Print data SSL/TLS encryption Provision of the virtual printer driver TP Output Gateway (enables a radical reduction of printer drivers on printing computers = Driver Free Printing). Auto-created client printers are created by AutoConnect, a component of the product ThinPrint Application Server Engine. Driver Free Printing Thanks to TP Output Gateway, time-consuming server-side installation and administration of printer drivers under Windows is no longer necessary. Printer driver conflicts on terminal servers are also a thing of the past. The printer drivers are only installed on the client PCs or on local print servers. That means that any type of printer can be used on any printer port; e.g., multifunctional devices (printer, fax, copier, and scanner in one device) on a USB interface or a laser printer on a bidirectional interface. 6 Manual ThinPrint Application Server Engine

7 Introduction For ThinPrint Clients on non-windows computers, the generic PostScript driver TP Output Gateway PS is applied. Or you install a central print server additionally where you can use the V-Layer (refer to ThinPrint Server Engine manual, Page 94). Advanced Adaptive Compression Furthermore, ThinPrint Engine combines the efficient Driver Free Printing system with a new kind of compression, Advanced Adaptive Compression. This method analyzes the individual components of a print job and compresses each with the corresponding best algorithm before transmitting the data. Additionally, user errors that can occur when inserting pictures in a document are corrected. Thereby reducing data volume by up to 98% (see Illus. 39, Page 34). Client component On the client side, ThinPrint Client is generally responsible for receiving print data, decompressing it, and sending it to the print device. There are many ThinPrint Clients available for different end devices and types of use: for all Windows versions including Windows CE, for Linux, Solaris, DOS, Java as well as for both internal and external print servers of network printers. ThinPrint Clients can be downloaded from ThinPrint s website (see Page 95). The website also includes a list of information on devices which are already embedded with ThinPrint Clients. If you require a ThinPrint Client which is not listed on the website, please send an to info@thinprint.com. Package contents The ThinPrint Application Server Engine product CD for ThinPrint version 8.6 contains: The installation program Setup.exe for ThinPrint Engine A quick installation guide The ThinPrint Client Windows manuals Licenses In addition, you should have received license keys from your reseller or by from ThinPrint. These are installed on the terminal server. Depending on the licensing type you got license keys from the following type: Annual licenses TLUS Annual licenses can be server or user based. serverbased licenses x86: THPR or x64: TAPR userbased licenses 1 TPPR (basic license key: Application Server Basic Pack) and TPUS (license key for 10 Named Users, for example) ThinPrint Application Server Engine Manual 7

8 Introduction When purchasing user based licensing, it is common to buy as many licenses as there are users in the terminal server environment. Therefore you may have received further TPUS licenses, for example TPUS for 5 named users, TPUS for 20 named users. More information about ThinPrint licensing can be found starting on Page 88 and in the ThinPrint licensing white paper. Scenarios The following sample scenarios illustrate typical environments in which ThinPrint can be deployed. The depicted scenarios can also be combined flexibility in mixed environments is one of the many strengths of ThinPrint. Terminal server(s) Printing via TCP/IP PCs and terminals (thin clients) communicate with the terminal server 2 via the Citrix protocol ICA or the Microsoft protocol RDP (Illus. 2). With ThinPrint, though, they are able to print via TCP/IP in either case. The print jobs are then sent directly to the client computer or network printer, circumventing the terminal session (separation of the data streams). This improves performance during printing, since available bandwidth can be utilized better. Moreover, each user can use all printers in the network which are accessible via TCP/IP regardless of whether he is using a PC (rich client), a thin client, or any other type of client. Further information can be found starting on Page 16. Illus. 2 Illus. 2 ThinPrint printing with terminal servers over TCP/IP Terminal server(s) Printing via ICA/RDP Both the Citrix protocol ICA and the Microsoft protocol RDP enable print jobs to be sent to a user of a terminal session through the virtual channels of terminal server 1 For more than one terminal server the user-based licensing is possible only if a central print servers is used. 2 with Microsoft Terminal Services or Citrix XenApp 8 Manual ThinPrint Application Server Engine

9 Installation communication (ICA or RDP). This ThinPrint print mode is also possible to clients in masked networks 3 (Illus. 3). Further information can be found on Page 16. Illus. 3 Illus. 3 ThinPrint printing with terminal servers over ICA or RDP Installation Technical requirements Be sure that the TCP port numbers for printing via TCP/IP are not being blocked by another program or by a server-side or client-side firewall. IPv4 has to be enabled for each involved machine. ThinPrint Engine Supported server operating systems Windows Server 2003 with Service Pack 2 or later Windows Server 2003 x64 with Service Pack 2 or later Windows Server 2003 R2 with Service Pack 2 or later Windows Server 2003 R2 x64 with Service Pack 2 or later Windows Server 2008 Windows Server 2008 x64 Windows Server 2008 R2 Also required:.net Framework with Version 2.0 or later With Windows Server 2008 SP1: Microsoft Hotfixes KB (Print Job Owner) and KB (Client Side Rendering) For Session-in-Session (Page 92) to a XenApp server or XenDesktop: Citrix ICA Client v10.0 or later For Citrix XenApp: XenApp Web Plugin or later The Windows service PRINT SPOOLER should not be disabled. 3 Networks behind routers with Network Address Translation (NAT) ThinPrint Application Server Engine Manual 9

10 Installation ThinPrint Client Workstations or local print servers: Windows 7, 7 x64, Vista, Vista x64, XP, XP x64, 2008, 2008 x64, 2008 R2, 2003, 2003 x64, 2003 R2, 2003 R2 x64 supported, but with limited functionality, are: Windows 2000, NT 4, ME, 98, 95 with Windows-Installer version 2.0 and later, Apple MacIntosh, Linux, Java Thin Clients with embedded ThinPrint Client (see Page 95). Administrator permissions Administrator permissions are required for all installation and configuration procedures. It is therefore best to log on to Windows as the local ADMINISTRATOR. Installing ThinPrint Engine (per terminal server) Unattended installation Unattended installation and licensing are also possible; refer to the White Paper Unattended installation and licensing of ThinPrint Engine components Page 94. Installation with installation wizard Install ThinPrint Engine according to the scenarios depicted in illustrations 2 and 3. Note! Before beginning installation, we recommend closing all windows and applications and deactivating any virus scanner. Also be aware that after installation ThinPrint Engine will only become functional after a Windows restart. 1. Copy the software for ThinPrint Engine installation to the server s hard disk and start Setup.exe (Illus. 4). Illus. 4 Illus. 4 Start the installation program Setup.exe Note! With Windows Server 2003, a reboot is required if Windows Installer 4.5 was not installed before installation (in this case, Windows Installer 4.5 will be installed automatically). 2. Select one of the following languages: English, German, French, or Spanish. 3. Click NEXT to confirm the Welcome window. 10 Manual ThinPrint Application Server Engine

11 Installation 4. Read the license agreement, accept it and click NEXT to confirm. The menu shown in Illus. 5 will open. Select TERMINAL SERVER. Illus. 5 Illus. 5 Select the APPLICATION SERVER role For assistance selecting the role, read Page 91. Print Server Terminal Server Extension Print Server for VMware View Administration Tools Custom Setup This option only applies if you install ThinPrint Engine on a central print server. In that case, consult ThinPrint Server Engine manual. Select TERMINAL SERVER EXTENSION, if you use a central print server in your terminal server environment. In this case only AutoConnect, Virtual Channel Gateway and Output Gateway are installed, but ThinPrint Engine is not 4. Select this option if you wish to install ThinPrint Engine for VMware View and read the ThinPrint Engine for VMware View manual. Select this option if you want to configure ThinPrint Engine remotely from this computer. In this case only the necessary MMC components will be installed. Here you can specifically select individual ThinPrint components, e.g. Session-in- Session. See Page ThinPrint Engine will be installed on the print server; so you will need Server Engine licences. Read the ThinPrint Server Engine manual for print server installation. ThinPrint Application Server Engine Manual 11

12 Installation 5. In the next dialogue box you can select the installation path by clicking on CHANGE (Illus. 6). Click NEXT to continue. Illus. 6 Illus. 6 Choose an installation path 6. Select ENTER LICENSE(S) if you already received license keys from your reseller or from Cortado. Otherwise select DEMO MODE (Illus. 7). Click NEXT to confirm. Illus. 7 Illus. 7 Select a licensing type Entering a license key 7. If you selected ENTER LICENSE(S) the window in Illus. 8 will appear. If so, copy your license keys for ThinPrint Application Server Engine or ThinPrint Application Server Basic Pack (see licenses on Page 7) into the white field, as shown on the left in Illus. 8 and click INSTALL LICENSE(S). 12 Manual ThinPrint Application Server Engine

13 Installation Illus. 8 Illus. 8 Copy license keys into the white field and click INSTALL LICENSE(S) to confirm (example for Windows x64 with server-based licensing) That causes one of the exclamation marks in a red circle to change to a checkmark in a green circle (above right in Illus. 8). Click OK to continue. Note! Once a license key has been entered, it is valid without activation for 30 days. See Page 88 for information about activating licenses. With more than one terminal server using user-based licensing the license keys of (Named) User licenses have to be distributed among all terminal servers. 8. Click on INSTALL in the next dialogue box to start the actual installation process. Click FINISH to close the last window. Note! Be aware that after installation ThinPrint Engine will only become functional after a Windows restart. New Printers After installation, three new printers can be found in the server s Printers folder (Illus. 9): _#ThinPrint Output Gateway (template) Print-to-Cloud Print-to-ePaper The printers Print-to-Cloud and Print-to-ePaper are for print jobs that are to be made available to mobile devices (smartphones), either to be read there, or to be faxed, mailed, or printed from them. See Page 58. ThinPrint Application Server Engine Manual 13

14 Installation Illus. 9 Illus. 9 _#ThinPrint Output Gateway printer template and two printers: Print-to- Cloud and Print-to-ePaper in server s Printers folder Template ThinPrint Output Gateway This printer is a template for auto-created client printers. In other words, when a user establishes a connection to the terminal server, a printer is created (mapped) for him in the ICA or RDP session; this printer inherits all settings (e.g., compression level, the transmission protocol, and the TP Output Gateway printer driver) from the template (Illus. 10). Illus. 10 Illus. 10 Printer in a terminal session: TP Output Gateway printer driver inherited from a template (example) For more information about creating and configuring printers and templates, see Pages 40 and 49. ThinPrint Clients must be installed on the client machines to receive ThinPrint print data (Page 17). The TP Output Gateway is used as a universal printer driver for Windows devices. Alternatively you can use the generic PostScript driver TP Output Gateway PS for Non-Windows devices. Disabling Windows printer mapping By default, ThinPrint Engine automatically creates client printers in every terminal session. To simplify the selection of a ThinPrint printer within a session, the Windows automatic printer mapping function should be disabled within and outside of the session. To do so (on the terminal server): 14 Manual ThinPrint Application Server Engine

15 Installation Disabling client printer mapping 1. In Windows Control Panel, select SYSTEM AND SECURITY ADMINISTRATIVE TOOLS SERVER MANAGER ROLES REMOTE DESKTOP SERVICES RD SESSION HOST CONFIGURATION. 2. Click on the RDP-TCP connection and select PROPERTIES in the context menu (Illus. 11) Illus. 11 Illus. 11 Configuring RDP configuration 3. Disable the mapping functions in CLIENT SETTING tab (arrows in Illus. 12). 4. If available, click on the ICA-TCP connection select PROPERTIES in the context menu. 5. Disable the mapping functions. Click OK to confirm. Illus. 12 Illus. 12 Settings for printer mapping ThinPrint Application Server Engine Manual 15

16 Sample configuration Sample configuration The installation wizards for both the ThinPrint Engine server and the ThinPrint Client Windows client components are preconfigured so that it is possible to print immediately after installation is completed, with no further configuration provided you install the RDP type of ThinPrint Client Windows or on Citrix XenApp servers the ICA type of ThinPrint Client Windows. This plug-and-play installation cannot be used in every scenario. One reason is that it requires a Windows PC as client. So only the main configuration options are illustrated here, using a sample scenario as example. The following descriptions refer to the sample scenario below. Illus. 13 Illus. 13 Sample scenario with client and user names Our scenario attempts to combine a couple of typical client and connection types in a terminal server environment. Clients are a PC and a thin client as well as a local print server. The following table describes the print environment used in the sample configuration (Illus. 13). Machine name User name Printer Connection to Server ThinPrint Client type Print mode client1 user1 Epson Stylus Color 400 DSL (768 kbit/s) TCP/IP type of ThinPrint Client WinCE with native printer driver ps05 Lexmark T620 DSL (768 kbit/s) ThinPrint Client Service Windows (TCP/IP) Driver Free Printing client2 user2 HP DeskJet ISDN (64 kbit/s) RDP type of ThinPrint Client Windows Driver Free Printing 16 Manual ThinPrint Application Server Engine

17 Sample configuration The ICA protocol can also be used as an alternative to RDP. In that case, all RDP specific installations and configurations must be replaced with those for ICA. Installing ThinPrint Clients Configuring thin client client1: ThinPrint Client WinCE (TCP/IP) on a thin client 1. For this sample scenario, choose a thin client with an embedded ThinPrint Client (see Page 95). 2. Open the control panel on the thin client and select THINPRINT, then click OPEN, (Illus. 14). Illus. 14 Illus. 14 ThinPrint Client WinCE in the control panel (example for Neoware terminals) 3. Enable the ThinPrint Client (ENABLE THINPRINT; Illus. 15 left). 4. Select the protocol you will select for the template _#Epson Stylus COLOR 400 on the server (THINPRINT OVER TCP or TCP/IP, Illus. 29), and click OK (Illus. 15 left). 5. Open the ThinPrint Client configuration menu (CONFIGURE THINPRINT; Illus. 15 right). Illus. 15 Illus. 15 Selecting and enabling ThinPrint Client WinCE and opening configuration menu (example for Neoware terminals) ThinPrint Application Server Engine Manual 17

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

19 Sample configuration 1. For the sample scenario, install a Lexmark T620 printer (Illus. 19). 2. Install ThinPrint Client Service Windows; please refer to the ThinPrint Client Service Windows manual (Page 94). Illus. 19 Illus. 19 Printer installed on local print server ps05 3. Open the ThinPrint Client Manager. Determine the Lexmark T620 printer ID from the ASSIGNMENT tab (Illus. 20). Illus. 20 Illus. 20 Printer ID of the Lexmark T620 (here: 1) client2: RDP type of ThinPrint Client Windows on a PC Requirement: An RDP client must be installed. The scenario in Illus. 13 (Page 16) applies. 1. For the sample scenario, install an HP DeskJet printer (Illus. 21). 2. Install RDP type of ThinPrint Client Windows; please refer to the ThinPrint Client Windows manual (Page 94). ThinPrint Client is started automatically with the RDP session. It does not need to be configured for the sample installation. ThinPrint Application Server Engine Manual 19

20 Sample configuration Illus. 21 Illus. 21 Printer installed locally on client2 Server configuration All settings made for server configuration must be performed on each terminal server in a server farm (for import/export and sending configuration see Page 34). Requirement: ThinPrint Engine must already be installed (Page 10). The scenario in Illus. 13 (Page 16) applies. ThinPrint Ports 1. Open the ThinPrint configuration with START THINPRINT ENGINE CONFIGURA- TION (Illus. 22). Illus. 22 Illus. 22 Opening ThinPrint Configuration 20 Manual ThinPrint Application Server Engine

21 Sample configuration 2. Click ADD and then specify the computer address (Illus. 23) for each local or remote ThinPrint Engine to be configured (Illus. 24). Illus. 23 Illus. 24 Illus. 23 Open the configuration console for server components Illus. 24 Specify - local or remote configuration 3. The ThinPrint Engine console appears (Illus. 25). Select on the left, i.e., in the Console Tree: THINPRINT THINPRINT ENGINE PORT MANAGER. Illus. 25 Illus. 25 ThinPrint Port(s) in the configuration console (= Port Manager) ThinPrint Application Server Engine Manual 21

22 Sample configuration 4. Create the following ThinPrint Port by clicking the NEW THINPRINT PORT icon (upper arrow in Illus. 25) and set the protocol (Illus. 26 and 27): Port name RDP1: Port type (protocol) VCP = VIRTUAL CHANNEL PROTOCOL (ICA OR RDP) Illus. 26 Illus. 27 Illus. 26 Selecting port type for port RDP1: ; click APPLY Illus. 27 A new ThinPrint Port 22 Manual ThinPrint Application Server Engine

23 Sample configuration 5. To enable AutoConnect to create a corresponding printer for each client printer in a terminal session and also so that the printer can print across different connections, create the following printer templates (Illus. 28) in the server s Printers folder 5 (Windows Server 2008: START PROGRAMS THINPRINT ENGINE PRINTERS, Illus. 22): Printer name ThinPrint Port Printer driver _#Epson Stylus Color 400 ThinPort: Epson Stylus Color 400 Esc/P2 _#RDP RDP1: TP Output Gateway Illus. 28 Illus. 28 Two new printer objects as templates 6. Under PROPERTIES SECURITY, assign permissions to the two printer templates, _#Epson Stylus Color 400 and _#RDP: Delete all users and groups except for administrators. Add SYSTEM and allow full control. 7. Change to the port configuration in the MMC and check that the new printers have been assigned correctly to the ThinPrint Ports (Illus. 29; if necessary, press F5 to refresh). 5 With Windows Server 2008 R2 in Print Management ThinPrint Application Server Engine Manual 23

24 Sample configuration Illus. 29 Illus. 29 The new templates (right) assigned to the ThinPrint Ports (left) Configuring AutoConnect 8. Select DYNAMIC PRINTER MATRIX in the Console Tree (Illus. 30, left). To enable AutoConnect to create the printers from client1 and client2 for the sessions of user1 and user2, add the following entries to the first two lines: IP Range Client Name Printer Name User/Group Target * * * \\mydomain\user1 Epson Stylus Color 400 * * * \\mydomain\user2 RDP Notes: Double-click in the gray area to change to the edit mode. AutoConnect processes the Dynamic Printer Matrix from top to bottom, for each printer activated in ThinPrint Client (on a workstation). When a matching entry is found, AutoConnect stops searching the table and the target printer of the matching line is being created in the user s session. So, lower lines will only be executed if the conditions of the upper lines don t match for this client printer. Illus. 30 Illus. 30 Dynamic Printer Matrix in the configuration console 24 Manual ThinPrint Application Server Engine

25 Sample configuration Creating a printer manually Create the following printer object in the terminal server s Printers folder 6 for the printer in Illus. 19 and 20: Lexmark T620#ps05:1 Attach it to the ThinPort: printer port. Printing Establish a Remote Desktop Connection from each client machine to the terminal server farm; as shown in our example, logging on as user1 and user2, respectively. The printers in Illus. 31 and 32 appear in the Printers folder 6 in the two sessions. Open an application and print with each of these printers. Illus. 31 Illus. 32 Illus. 31 Printers from user1 in an terminal session as in the example Illus. 32 Printers from user2 in an terminal session as in the example Print jobs will be received from the ThinPrint Clients and forwarded to the printers as follows: Client name (User name) Print protocol Addressed printer ID Target printer client1 (user1) TCP/IP 2 Epson Stylus Color 400 ps05 (user1 + user2) TCP/IP 1 Lexmark T620 client2 (user2) RDP 2 HP DeskJet 6 With Windows Server 2008 R2 in Print Management ThinPrint Application Server Engine Manual 25

26 Sample configuration Please note which printers in terminal sessions use a native driver and which use the TP Output Gateway (see the MODEL column in Illus. 31 and 32). If you still can't print Checklist If AutoConnect does not create the desired printers or if printing itself fails to work properly, please check the following before contacting ThinPrint support (Page 88). If you run Windows Server 2008 (x64) SP1: Did you install the Microsoft Hotfixes KB (Print Job Owner) and KB (Client Side Rendering)? (Page 9) Is the same protocol selected for the ThinPrint Client, the ThinPrint Port, and AutoConnect? Example for RDP: Is the RDP type of the ThinPrint Client installed on the client machine? (Page 19) To which type of ThinPrint Port is the specified printer template connected? VIRTUAL CHANNEL PROTOCOL (ICA OR RDP); must be enabled in the port configuration (Illus. 26). For AutoConnect, either VIRTUAL CHANNEL (ICA OR RDP) or AUTO must be set as connection protocol (Illus. 96), and the respective column in the Dynamic Printer Matrix has to be set to enabled (here R for RDP). Is TPAUTOCONNECT SERVICE running on each terminal server? Note! For printing using ThinPrint Ports the TP AutoConnect Service has to be run together with the ThinPrint Engine. If TCP/IP is the selected protocol: Are the TCP port numbers the same on server and client (see port configuration in MMC Illus. 37 and ThinPrint Client Manager)? Are you sure that the TCP port number is not being blocked by the firewall or by another program? Is the client in a masked network (NAT)? If so, you must select either RDP or ICA (and client-side use the respective ThinPrint Client), or additionally install the ThinPrint Connection Service (see also the ThinPrint Connected Gateway manual; Page 94). If a printer was created manually (see Page 25), check the naming convention of the ThinPrint Port (see port configuration in MMC, Illus. 38). If you selected USE ENCRYPTION on the server (Illus. 83), continue reading the section Encrypting print jobs for further information (Page 62), or disable encryption for now. Are the correct templates used when AutoConnect starts (see Illus. 28)? For each template, there must be an appropriate printer name, printer class, or entry in the Dynamic Printer Matrix (see ThinPrint Client Manager, Illus. 20, and AutoConnect, Illus. 101). Check that AutoConnect is working by starting it 26 Manual ThinPrint Application Server Engine

27 Sample configuration manually: Open the Command Prompt in a terminal session, change to the ThinPrint Engine s program directory 7 and enter the following to create the session printers: tpautoconnect d tpautoconnect -v (tpautoconnect -d removes existing autocreated printers and ends the AutoConnect application in the session) If the session printers can be created manually by entering TPAutoConnect in the command line but are not automatically created when the terminal session is started, check all AutoConnect settings in MMC (Illus. 96 to 107). Testing the TCP/IP connection: For printing via TCP/IP, there must exist between server and client a TCP/IP connection which allows direct communication with the ThinPrint Client and its TCP port. Masked client networks (NAT) can often cause difficulties in this situation. Test to see if the connection exists by trying a telnet from the server to the client s TCP port. 8 To do this, enter the following at the server s Command Prompt: telnet IP port (blank space between IP address and TCP port number) IP is the client machine s IP address; port is the TCP port the ThinPrint Client is using. (See also the ThinPrint Client manuals; Page 94.) Example 1: telnet After executing this command, a telnet window should open without error message. If so, the connection is OK. If you are using Driver Free Printing but, even though the printers are created in the terminal session with AutoConnect, printer options such as paper formats and sources are unavailable, check whether the following functions have been enabled: ENABLE SENDING PROPERTIES in the ThinPrint Client Manager (Illus. 20) INHERIT CLIENT PRINTER SETTINGS in the AutoConnect configuration (Illus. 98) Session-in-Session: Check whether ThinPrint Engine is installed on the machine that you want to run the second session on. The Session-in-Session component must be installed on the middle computer (see Page 92). Check here: Whether the required registry value SISACTIVE (REG_DWORD) is present and set to 1 (0=inactive, 1=active). Path: hkey_local_machine\software\thinprint\tpclnrdp (or \TPClnIca) Whether the ThinPrint component TPClnICA.dll is present in the ICA Client s 9 directory (e.g.: C:\Program Files (x86)\citrix\ica Client). If not, copy it from the ThinPrint program directory 10 to this directory. Please also note the chapter Citrix ICA Client later installed (Page 93). 7 e.g. c:\program Files\ThinPrint Engine 8 A ThinPrint Client (TCP/IP type) is necessary on the respective client machine. 9 also: Citrix XenApp Plugin for Hosted Apps 10 e.g.: C:\Program Files\ThinPrint Engine ThinPrint Application Server Engine Manual 27

28 Configuring ThinPrint Ports ThinPrint prints with own printer ports which will be automatically created during installation. Furthermore, you can continue printing with conventional ports at the same time; ThinPrint does not affect this. Two kinds of ports are included with ThinPrint: ThinPort/Connection Service Port for printing in terminal server sessions Print-to-Cloud Port (for Print-to-Cloud and Print-to-ePaper) Printing to a directory. The print job can be displayed and printed not only on a PC, but also on a mobile device (see Page 58). General information about ThinPrint s printer ports can be found in the ThinPrint Ports white paper (Page 94). This chapter describes configuration of the ThinPrint Engine with special attention to adding ThinPrint Ports and adapting them to specific requirements for print job transmission. The Port Manager offers the following options for ThinPrint Ports: Add a ThinPrint Port local and remote Configure a ThinPrint Port local and remote Delete a ThinPrint Port local and remote Send port configuration to other Windows machines on which a ThinPrint Engine is installed Export and import port properties Encryption settings Starting Port Manager 1. Open the ThinPrint configuration with START (ALL) PROGRAMS THINPRINT ENGINE CONFIGURATION. 2. Click ADD for each local or remote ThinPrint Engine to be configured (Illus. 33) and specify the computer address (Illus. 34). Illus. 33 Illus. 33 Open the configuration console for server components 28 Manual ThinPrint Application Server Engine

29 Illus. 34 Illus. 34 Local or remote configuration? 3. The ThinPrint Engine console appears (Illus. 35). Illus. 35 Illus. 35 Selecting TRACKING SETTINGS ThinPrint Application Server Engine Manual 29

30 Here, you will find all events generated by ThinPrint components. Additionally you can display print spooler events here (arrow in Illus. 35). Note! Note that saved server settings will only be effective after a spooler restart. With Windows Server 2008 R2, spooler events cannot be shown here at present. Creating new 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 11 (Illus. 36). Choose the port settings: port type (protocol), bandwidth and/or encryption. Up to 600 ports are possible. 12 Note! In principle, there is no limit to the length of printer port names. Some applications, however, only support port names with a length of four or six characters; if longer port names are used, this could cause problems (printer is not visible in the application, etc.). Configuration 4. To configure ports, select on the left, in the Console Tree: THINPRINT THIN- PRINT ENGINE PORT MANAGER (Illus. 36). Illus. 36 Illus. 36 ThinPrint Ports in Port Manager 5. Double clicking a port name (right arrow in Illus. 36) will open the port configuration (Illus. 37). 11 For Connection Service Ports see ThinPrint Connected Gateway manual (Page 94) 12 maximum 600 ThinPrint Ports with maximum 800 active printer queues (Windows Server 2003 with 3 GHz Dual Xeon processor, 2 GB RAM, and SCASII ultra3 disk array) or maximum 1500 Queues with Windows Server 2008 R2 30 Manual ThinPrint Application Server Engine

31 Configure tab Illus. 37 Illus. 37 Port settings: CONFIGURE tab The ThinPrint Ports can be configured as follows: USE ENCRYP- TION BANDWIDTH CONTROL Print protocol Enables SSL/TLS encryption; a valid and corresponding certificate must be available on both ThinPrint Engine and ThinPrint Client (not for LPD; see also Page 62). ENABLE: Bandwidth control on Max. bandwidth available for printing with ThinPrint; minimum: 1600 bit/s, default: unlimited TCP/IP (sockets) ICA / RDP (Virtual Channel Protocol) LPD (Unix print protocol LPR/LPD) (USE VIRTUAL CHANNEL GATEWAY) Note: This function is for printing from print servers via ICA or RDP. See also the ThinPrint Server Engine manual, Page 94.) MINIMUM PRINT DATA VOLUME 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 print protocols. The TCP ports of the ThinPrint Clients must be the same as those of the ThinPrint Ports. For LPD printing, see the ThinPrint port configuration for bandwidth controlled printing via LPR/LPD white paper (Page 95). ThinPrint Application Server Engine Manual 31

32 Save Confirm changes with APPLY or OK. Advanced tab Illus. 38 Illus. 38 Port settings: ADVANCED tab Under ADVANCED are the options: CLIENT CONTROL: BANDWIDTH If this option is enabled, each client user can set his own bandwidth value (in the ThinPrint Client Manager). Client bandwidth settings must be lower than server-side settings; otherwise, ThinPrint Engine settings are applied. This function is only available if bandwidth control (see Illus. 37 above right) has been enabled. CONNECTION RETRIES (TCP/IP and LPD only) Enter the number of times ThinPrint Engine should attempt to establish a connection to the client. NET SEND SERVICE Net Send Service can be used to notify users if ThinPrint experiences print errors. If a problem occurs during data transmission, an error message is generally not sent to the user. If this box is checked (= default), ThinPrint Engine will send error messages to the relevant account. Note: This function can become irksome if several users are logged on using the same account. 32 Manual ThinPrint Application Server Engine

33 NAMING CONVENTION You can select for each ThinPrint Port whether the address information is at the beginning or the end of the printer name. Examples: Default addressing TCP/IP Lexmark T620 PS3# Lexmark T620 PS3# :1 HP LaserJet 1200 PCL#client1 HP LaserJet 1200 PCL#client1:2 ICA / RDP HP LaserJet 1200 PCL# Lexmark T620 PS3#:1 Reversed addressing #Lexmark T620 PS :1#Lexmark T620 PS3 client1#hp LaserJet 1200 PCL client1:2#hp LaserJet 1200 PCL HP LaserJet 1200 PCL :1#Lexmark T620 PS3 Example for auto-created printers (AutoConnect): HP LaserJet 1200 PCL#user1:2 LPD Lexmark T630# Lexmark T630#networkprinter3 user1:2#hp LaserJet 1200 PCL #Lexmark T630 networkprinter3#lexmark T630 Job Statistics tab Print statistics must be activated per port. Select the relevant ThinPrint Port; click PROPERTIES JOB STATISTICS and then High (every second), Normal (every 10 seconds), Low (every 30 seconds), No update, or Statistics off (default) under UPDATE SPEED as in Illus. 39. Note! Use this function only part-time, as it may affect print performance. See also Print job tracking (Page 68). ThinPrint Application Server Engine Manual 33

34 Illus. 39 Illus. 39 Port settings: JOB STATISTICS tab OK Save your settings by clicking OK. Distributing port configuration The following strategies are available for creating the same configuration for ThinPrint Ports on multiple servers: Remote configuration of ThinPrint Ports (Page 28) Copying port properties with copy-and-paste (see below) Export to an.xml file and import to target servers (see below) Sending port configuration to target servers (see below) Copy-and-Paste Open the ThinPrint Engine configuration (Page 28). Mark a port in a server s Port Manager (e.g. TS01 in Illus. 40) and select COPY from the context menu. Mark the Port Manager of a target server (e.g. TS02 in Illus. 41) and select PASTE from the context menu. 34 Manual ThinPrint Application Server Engine

35 Illus. 40 Illus. 41 Illus. 40 Copy a port on a server Illus. 41 Paste the port on another server Export/Import The following export and import functions are available: EXPORT CONFIGURATION Exports the selected ThinPrint Port to an.xml file (Illus. 40) IMPORT/EXPORT EXPORT PORT CONFIGURATION IMPORT/EXPORT IMPORT PORT CONFIGURATION Exports all ThinPrint Ports to an.xml file if no port is selected (Illus. 42) Imports ThinPrint Ports from an.xml file (Illus. 42) ThinPrint Application Server Engine Manual 35

36 Illus. 42 Illus. 42 Exporting, importing, or sending all ThinPrint Ports Sending port configuration The SEND PORT CONFIGURATION function sends ThinPrint Ports to other servers or server groups (Illus. 42). There are various modes: SEND PORT CONFIGURATION (OVERWRITE) SEND PORT CONFIGURATION (ADD ONLY) IMPORT/EXPORT SEND PORT CONFIGURATION (OVERWRITE) IMPORT/EXPORT SEND PORT CONFIGURATION (ADD ONLY) Sends the selected ThinPrint Port; ports with the same name on the target system will be overwritten Sends the selected ThinPrint Port; ports with the same name on the target system will not be overwritten Send all ThinPrint Ports (bottom arrow in; ports with the same name on the target system will be overwritten Send all ThinPrint Ports (bottom arrow in; ports with the same name on the target system will not be overwritten ThinPrint Ports on the target computer which do not exist on the on the sending computer remain unchanged. Procedure when sending Selecting the send option will open the dialog in Illus Manual ThinPrint Application Server Engine

37 Illus. 43 Illus. 43 Dialog for sending properties To improve clarity, first select OBJECT TYPES (upper arrow in Illus. 43), and disable GROUPS (Illus. 44). Click OK to confirm. Select ADVANCED (lower arrow in Illus. 43) and then FIND NOW (Illus. 45). Illus. 44 Illus. 44 Limiting the selection to computers ThinPrint Application Server Engine Manual 37

38 Illus. 45 Illus. 45 Find target servers Mark all target servers and click OK to confirm (Illus. 46). Caution! You are influencing the configuration of remote computers. Check once more that you really want to send the configured ThinPrint Ports to the selected servers. A confirmation prompt allows you to cancel the process. 38 Manual ThinPrint Application Server Engine

39 Illus. 46 Illus. 46 Selecting target server(s) Note! If you receive an error message when sending, create a connection with the MMC to the target computer via the relevant ThinPrint Engine node for remote configuration (Page 28) and repeat the send process from the source computer while keeping the console open (Illus. 47). Illus. 47 Illus. 47 Create a connection to the target computer with the MMC (here: arrow to TS02) and repeat send process from source computer (here: TS01) ThinPrint Application Server Engine Manual 39

40 Creating printers and templates General information about creating printers can be found in the ThinPrint addressing and ThinPrint Ports white papers (Page 94). There s one last step after installing and configuring the ThinPrint Engine on the terminal servers: setting up printers on the ThinPrint Ports. Which protocol? If you are working with several ThinPrint Ports, each with a different protocol, then check port configuration (Page 30) before printer installation to see which ThinPrint Port supports what protocol. Simplification(s) ThinPrint Output Gateway (Page 49).print AutoConnect (Page 72) What are templates? Templates With ThinPrint, a template is a printer in the server s Printers folder 13 from which the client or session printers created with AutoConnect inherit their properties (see chapter AutoConnect, Page 72). The _#ThinPrint Output Gateway template appears in the server s Printers folder after installation of ThinPrint Engine (Illus. 60, Page 49). Which properties are inherited? Among other things, client printers that are created by AutoConnect in the terminal session s Printers folder 13 inherit the following properties from templates: Number of copies, orientation, preview options, compression settings and page adjustment (scale to fit or adjust margins); these are inherited always from the templates. The other properties (e.g., paper trays, paper format, color, print resolution, and print on both sides (duplex) are retrieved from the ThinPrint Client. These will be also inherited from the templates if sending properties from the ThinPrint Client to the ThinPrint Engine is disabled. (Native) printer driver or Driver Free Printing (TP Output Gateway) Printer port and thus: Bandwidth Print protocol (TCP/IP, ICA, RDP) Printing with or without the ThinPrint Connection Service Printing with or without print data encryption Port pooling Naming convention for ThinPrint printers 13 With Windows Server 2008 R2 in Print Management 40 Manual ThinPrint Application Server Engine

41 Template denominations Network protocol Names of printer objects (for templates) TCP/IP, ICA, RDP Either: _#printer Example: _#Kyocera FS-850 Or: _#class Example: _#HPLaser Printers can be connected via a template with a specific name (e.g., _#printer) if their printer name or class name corresponds with the template name (after the #). Using class names is sensible if printers with different names shall use the same template (this is possible if the driver in the template is appropriate for the different client printers). The underscore ( _ ) marks the template as such and is replaced with client-specific information for the automatically created printers. Manually created printers If you let AutoConnect automatically create all client printers in the sessions, then you only need to create templates and select the naming convention in the port configuration (Page 32) once. If you also want to create printers on the server manually, though, please also refer to the following information. For simplicity s sake, only standard addressing is treated here; reversed addressing can be found in the chart on Page 33, and addressing THINPRINT CONNECTION SERVICE PORTS is explained in detail in the ThinPrint Connected Gateway manual (Page 94). It is irrelevant to a ThinPrint printer name whether the object represents a traditional (native) printer driver. or the Output Gateway printer driver. The ThinPrint printer name is composed according to the network protocol in use: Printer names Network protocol 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# :3 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# ThinPrint Application Server Engine Manual 41

42 client_name Client name with TCP/IP and LPD 14 means the real name of the client in the network (= host name). Alternatively, the client s IP address can be used; this is especially necessary when there are difficulties with name resolutions Note! With TCP/IP it is possible to send print data to any client computer running a ThinPrint Client independent of the terminal session. printer_id printer_name At the client 15, the ThinPrint Client automatically assigns every installed printer an ID (see Illus. 17, Page 18). The printer_id can be omitted if there is only one printer installed on the client, or if printing should take place on the ThinPrint Client s current printer (Illus. 16). The printer name can be anything you like. It is nonetheless recommended that it is the same as the printer name at the client. Example 2: Client Client name client1 IP Address Printer HP LaserJet 1200 PCL ThinPrint Client assigned this printer ID 2 (Illus. 17). Server HP LaserJet 1200 PCL#client1:2 Or HP LaserJet 1200 PCL# :2 The ICA and the RDP protocols assume all communication with the client, including the client s unambiguous identification. The printer name is composed of: Description of the Printer and the Printer ID Note! With the ICA/RDP protocol print data is sent automatically to the client from whose terminal session the print data was created. 14 See the ThinPrint port configuration for bandwidth controlled printing via LPR/LPD white paper (Page 95) 15 i.e., a Workstation, a thin client (terminal), a gateway appliance or a local print server 42 Manual ThinPrint Application Server Engine

43 Example 3: A Kyocera FS-850 shall print via ThinPrint with the ICA protocol. If several printers are installed and ThinPrint Client assigned the printer the ID 3, the printer name could be something like: 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 ThinPrint Client), the printer name could be: laser_printer Port pooling Pooling printers with ThinPrint means you can attach a printer to several ThinPrint Ports (Illus. 48 and 49) also known as printer pooling. This has the following advantages: Improved performance Little chance of blockage from very large or hanging print jobs Less printers on the server Illus. 48 Illus. 48 Principle of port pooling Port pooling is supported by: ThinPrint Ports ThinPrint Output Gateway AutoConnect ThinPrint Virtual Channel Gateway ThinPrint Connection Service not in included in the ThinPrint Engine; see the ThinPrint Connected Gateway manual (Page 94) ThinPrint Application Server Engine Manual 43

44 Port pooling is mainly used to improve print performance. It should be considered, though, that all ThinPrint Ports in a pool should have the same settings. Port pooling with ThinPrint Ports in combination with Output Gateways and AutoConnect, however, brings more than maximum performance; it also makes administration particularly easy and convenient. When setting bandwidth, note that the bandwidths of a pool are added to each other when all ThinPrint Ports print simultaneously. Detailed information can be found in the ThinPrint Ports white paper (Page 94). Illus. 49 Illus. 49 Activating port pooling (example) Note! Port-Pooling is not recommended for printing to gateway appliances without an own spool system (e.g., SEH TPG60/120 and Intermate IAPS ThinPrint). With these devices attach each printer object to an own ThinPrint Port. Printing with thin clients Overview Windows CE and Linux clients are capable of forwarding print jobs to LPD devices. The ThinPrint Client WinCE or ThinPrint Client Linux is installed on a thin client or PC and can then receive ThinPrint print jobs (via TCP/IP, ICA, or RDP) and send them directly to internal or external print servers of network printers (via LPR/LPD, Illus. 50). 44 Manual ThinPrint Application Server Engine

45 All ThinPrint Clients for Linux and Windows CE (5.5 or later) operating systems support LPR/LPD printing. Note! For more information on sending print jobs directly via LPR/LPD with ThinPrint Engine, see the ThinPrint port configuration for bandwidth controlled printing via LPR/LPD white paper (Page 95). Illus. 50 Illus. 50 LPR/LPD printing via Windows CE or Linux clients Preparations on the server Set up a new template on the server (e.g. #HPLaser, left arrow in Illus. 51) and attach it to a ThinPrint Port (e.g. ThinPort:, Illus. 25 on Page 21). Use a native printer driver to do this. (e.g. HP Color LaserJet 4700, right arrow in Illus. 51, or TP Output Gateway PS). Illus. 51 Illus. 51 Preparing a template for LPD printing with thin clients (example) ThinPrint Application Server Engine Manual 45

46 Make sure that the printers completely spool the print data on the hard drive before sending. To do so, open the template s printer properties and select GENERAL. Select START PRINTING AFTER LAST PAGE IS SPOOLED (Illus. 52). Additionally disable the ADVANCED PRINTING FEATURES. Click OK to confirm. Select the appropriate settings in AutoConnect to ensure that the relevant Windows-CE or Linux clients printers operate with the new template (_#HPLaser) in the terminal sessions. Refer to the configuration example on Page 24 or in the paragraph AutoConnect on Page 72. Illus. 52 Illus. 52 Recommended settings for client-side LPD printing on the server 46 Manual ThinPrint Application Server Engine

47 Preparing ThinPrint Client (example for Windows CE) Open the control panel on the Windows CE device and select THINPRINT (click OPEN, Illus. 14). Illus. 53 Illus. 53 ThinPrint Client WinCE in the control panel (example for Neoware terminals) Enable the ThinPrint Client (ENABLE THINPRINT, Illus. 54 left). Select the protocol you selected for the corresponding template (TCP/IP, ICA, or RDP; see Illus. 29 on Page 24) and click OK (Illus. 54 left). Open the ThinPrint Client configuration menu by clicking CONFIGURE THINPRINT (Illus. 54 right). Illus. 54 Illus. 54 Selecting a protocol, enabling ThinPrint Client and opening configuration Use ASSIGNMENT to list available printers (Illus. 55). Select ADD NETWORK PRINTER and then LPD PRINTER (Illus. 56). ThinPrint Application Server Engine Manual 47

48 Illus. 55 Illus. 56 Illus. 55 Select ADD NETWORK PRINTER Illus. 56 Select LPD PRINTER Enter hplaser as PRINTER NAME and the printer s IP address or client name (PRINTER ADDRESS) and, for external print servers with more than one printer port, the name of the printer QUEUE (e.g., LPQ1 ) according to the print server s manual (Illus. 57); leave LPD FILTER l unchanged. Click OK to confirm. Illus. 57 Illus. 57 Enter a network printer (example) Enable this printer in the ASSIGNMENT tab and finish configuration with OK (Illus. 58). Illus. 58 Illus. 58 Enable the new printer and click OK to confirm 48 Manual ThinPrint Application Server Engine

49 Printing Establish an ICA or RDP connection from the terminal to the terminal server. The new printer appears in the session s Printers folder 17 (Illus. 59). Open an application and print with this printer. Illus. 59 Illus. 59 Auto-created printer hplaser#user1:6 in the session ThinPrint Output Gateway The TP Output Gateway is a virtual printer driver (see the MODEL column in Illus. 60) that makes it possible to render print data using original (native) printer drivers installed on the client side. Because no other, native printer driver is required on the server in addition to the Output Gateway, this print method is called Driver Free Printing. In this sense, of course, Driver Free only refers to the terminal server (Illus. 61). The user interface of Output Gateway is available in 16 languages, see Page 56. Illus. 60 Illus. 60 TP Output Gateway driver in the server s Printers folder With Driver Free Printing, print data is sent from the terminal server to the client machine in Windows own EMF data format bandwidth controlled, compressed, streamed, and, if desired, encrypted. 17 With Windows Server 2008 R2 in Print Management ThinPrint Application Server Engine Manual 49

50 Illus. 61 Illus. 61 Driver Free Printing: Output Gateway on terminal servers, printer drivers on PCs and local print servers running Windows Naming convention You can treat the printer objects based on TP Output Gateway like any other printer object. To use it instead of a native (conventional) printer driver, it must usually be renamed according to the ThinPrint naming conventions. Output Gateway is either used as a template for AutoConnect, or is renamed for targeting a specific printer. Example: Example 4: Addressing the printer directly (TCP/IP printing) Client Client name client1 ID 3 IP address Printer name HP LaserJet 5L Server Printer name or Printer name HP LaserJet 5L#client1:3 HP LaserJet 5L# :3 Output Gateway printer objects can be created manually with the ADD PRINTER function in Printers folder 18 using THINPRINT as manufacturer. The printers are to be connected to a ThinPrint Port. Paper formats and trays After initial installation, a few default options are available for paper formats and paper sources 19 (Illus. 66). You can add further options provided they are supported by the printer drivers on the client machine(s). 18 With Windows Server 2008 R2 in Print Management 19 Selection of paper trays or manual feed 50 Manual ThinPrint Application Server Engine

51 There are the following alternatives to do this: For printers created by AutoConnect: Automatic upload of printer properties from the ThinPrint Client to the server (Illus. 66) For manually created printers: Setting registry values for paper formats and sources on the server (see the Adaption of Output Gateway options white paper; Page 94) Presettings on the server (administrators only) The following settings need to be set in the server s Printers folder 18 for all templates using TP Output Gateway as their printer driver (e.g. _#ThinPrint Output Gateway ); as such they affect all printers using these templates during a terminal session. Select for example FILE PROPERTIES DEVICE SETUP for _#ThinPrint Output Gateway in the server's Printers folder 18. Compression range There are five options available for print data compression (Illus. 62): Normal Lossless Optimal Text without loss, good image quality Maximum Text without loss, medium image quality Extreme Text without loss, low image quality No images Only text will be printed At this point you can set the range of compression levels that the users will be able to set Select, for example, OPTIMAL, and the level NORMAL is no longer available to users. The default compression level itself, is set however in the tab ADVANCED PRINTING DEFAULTS COMPRESSION (Illus. 65, on Page 53). SpeedCache Additionally the option SPEEDCACHE can be enabled or disabled for terminal server users. A ThinPrint Client 8.6 is required. SpeedCache makes printing even faster and more efficient. SpeedCache checks every print job, for whether it replicates graphic elements (such as logos or fonts) and, if so, sends them only once. Thereby, the volume of server-client communication is cut down, without creating additional load on the network. You can set up and adjust SpeedCache on the printer driver ThinPrint Output Gateway (see Illus. 62) SpeedCache is not available for V-Layer printers. If SpeedCache is chosen as a setting, it will not have any effect. ThinPrint Application Server Engine Manual 51

52 Illus. 62 Illus. 62 Setting compression and SpeedCache Page Setup Select the PAGE SETUP tab in ADVANCED PRINTING DEFAULTS to edit page and color presettings; e.g., LETTER or A4 as paper size (Illus. 63). Additionally you can edit the following settings for double-sided printing: LONG EDGE or SHORT EDGE (= turn over edge). Illus. 63 Illus. 63 Presetting paper size, print resolution, color, etc., on the server Advanced In the ADVANCED tab (Illus. 64) you can preset if print jobs are to be sent without a pop-up menu to the printer (PRINT DIRECTLY). Alternatively a PRINT PREVIEW (Illus. 68) or the native printer driver's user interface (OPEN MY PRINTING PREFERENCES, Illus. 69) can appear on a workstation. Both options allow the user to access all other printer specific settings. 52 Manual ThinPrint Application Server Engine

53 PAGE ADJUSTMENT offers options for the default procedure if the printable area of the document and of the printer driver s paper format don t match. The option SCALE TO FIT changes the size of the printout, ADJUST MARGINS moves the print area (Illus. 64). It is recommended to leave both settings enabled for printer templates. Illus. 64 Illus. 64 Presetting scaling and margin adjustment on the server Compression level In the COMPRESSION tab, the default level of compression for users can be set (Illus. 65). Illus. 65 Illus. 65 Setting compression on the server The template settings from Illus. 63 and 65 will be shown as default options in a terminal session. Users can change them within their sessions. ThinPrint Application Server Engine Manual 53

54 Settings in a terminal session The following properties of the printers installed on the client machine can be sent from the client to the server via AutoConnect: Color/grayscale Paper sources Duplex/simplex Finishing options such as staple, punch, binding Print resolution Paper size Comments and location In a terminal session the users can change some printer settings in the printer properties dialogue before printing (except comments and location). The following settings can be edited in the PAGE SETUP tab (Illus. 66): PAPER SIZE, PRINT QUALITY, PAPER SOURCE, COLOR, ORIENTATION and PRINT ON BOTH SIDES. Illus. 66 Illus. 66 Display of paper sources on a workstation (left) and in a terminal session (right) Printing with preview Once the users have enabled the print preview (lower arrow in Illus. 67) the print job will appear in the ThinPrint viewer (= ThinPrint Viewture; Illus. 68); this requires that the print jobs are sent to a Windows workstation. Here the users can: Print to any printer that is connected to the client computer or can be reached from it Navigate in documents with more than one page Zoom Cancel print job reception Save print job File extension:.tpf (compressed EMF data); the Viewture program (= TPView.exe) is needed for reloading a saved print job; see Page 95). 54 Manual ThinPrint Application Server Engine

55 Illus. 67 Illus. 68 Illus. 67 Print mode, scaling and margin adjustment in a terminal session Illus. 68 Preview with ThinPrint Viewture on the client computer (water mark =demo version) When printing with preview, the print options appear in the terminal session in an Output Gateway design (Illus. 66 right). Once the client machine receives the print job, the print job is displayed in a preview window (Illus. 68). The print options now appear in the design of the native printer driver (Illus. 66 left). Finishing options If your printer supports finishing options 22, you can find them in the similarly named tab (Illus. 69). Here you can set, for example, where staples should be located on ThinPrint Application Server Engine Manual 55

56 the printout, where bindings should be set or hole punches made. Here you can also set how many pages per sheet should be printed, and in which order. Illus. 69 Illus. 69 Finishing options in a terminal session Language versions Output Gateway is available in the languages listed below (Language abbreviations in parentheses): Chinese, traditional (CHT) Chinese, simplified (CHS) Czech (CSY) English, United States (ENU) French (FRA) German (DEU) Greek (ELL) Hungarian (HUN) Italian (ITA) Japanese (JPN) Korean (KOR) Polish (PLK) Portuguese (PTG) Russian (RUS) Spanish (ESN) Swedish (SVE) Thai (THA) 22 Requirement: The printer must support PrintTickets from Microsoft. Download ThinPrint Finishing Detector (Page 95) to find out which finishing options are supported by your printer models. Install this tool on the machine where the printer drivers are installed. 56 Manual ThinPrint Application Server Engine

57 Illus. 70 Illus. 70 Output Gateway s localization (examples) You can appoint languages per user. Or you can select an approach that automatically appoints a language, according to each user's Windows language pack. Create a registry key for each required language, export it and then distribute it to the users. Appointing a language Set the language in the registry of the application server. Change the registry value Lang (REG_SZ) under hkey_current_user\software\thinprint\ and enter the abbreviation of your preferred language (list of abbreviations on Page 56), e.g. french = fra (Illus. 71). The change becomes effective with session logoff/logon. ThinPrint Application Server Engine Manual 57

58 Illus. 71 Illus. 71 Appointing a language for the user Match language automatically If you enter Def rather than the language abbreviation described above, the user is automatically appointed the language that corresponds to her or his language pack. For this, Microsoft language packs must have been installed. Give Def instead of fra as an example to registry value Lang (REG_SZ) under: hkey_current_user\software\thinprint\ Distributing language keys If you have created a registry key for a language (as described above), you can make it available to all users. Click on the key and, in the menu, select FILE EXPORT. That way, the key will be exported in the file format.reg (example: Output_Gateway_French.reg). In the session, the users click on the.reg file of the desired language, so that the key is inserted into the registry. The user specified language setting is retained when they logoff/logon. Cloud Printing ThinPrint allows print jobs to be sent directly to a smartphone or tablet in order to print them at a later time (in a different location) with any printer reachable via Wi- Fi. To do so, either the Cortado Corporate Server enterprise solution or the hosted cloud printing app Cortado Workplace on the smartphone or tablet is used. More information on the products are available here: 58 Manual ThinPrint Application Server Engine

59 Default Settings on the Server Print-to-Cloud After installing ThinPrint, the printers Print-to-Cloud and Print-to-ePaper are available in the Printers folder of the server (Illus. 72). Illus. 72 Illus. 72 Print-to-Cloud printer in the Printers folder (server) To specify whether users should send their print jobs to an existing Cortado Corporate Server or to Cortado Workplace (Hosting Center), select the appropriate printer, and view its properties. Then, select the tab PORTS and then CONFIGURE PORT, for example Print-to-Cloud (Illus. 72 and Illus. 73 left). If you want to use Cortado Workplace, select Cortado Workplace at CLOUD (upper arrow in Illus. 73 right) in the Print-to- Cloud Port Properties. If you have Cortado Corporate Server, choose this instead (lower arrow in Illus. 74 right). Enter the URL of the Cortado Corporate Server as follows: Should you want to use both versions, simply set up a further port via ADD PORT. Illus. 73 Illus. 73 Configure Print-to-Cloud ThinPrint Application Server Engine Manual 59

60 User Settings Within a terminal session, users have the option with the Print-to-Cloud function to print jobs to a Cortado Workplace client installed on a smartphone 23 (or tablet). With the Cortado app, you can print at a later time in another location. The users must first install the Cortado app on their smartphone or tablet. More information on the installation and use of Cortado Workplace can be found here: and of Cortado Corporate Server here: To do so, the print job must be sent from the user session to the Print-to-Cloud printer. Illus. 74 Illus. 74 Select printer: Print-to-Cloud In addition, the credentials for the Cortado Workplace account must be stored via the PREFERENCES (lower arrow in Illus. 74) option in the tab PRINT-TO-CLOUD (Illus. 75). If Cortado Corporate Server is used, the users need to enter instead their address that is stored on this server and the domain password. 23 Print-to-Cloud for Cortado Workplace is available for Android, BlackBerry and ios devices. 60 Manual ThinPrint Application Server Engine

61 Illus. 75 Bild 75 Print-to-Cloud: Put in Workplace credentials The sent print data will be stored in EMF data form (*.tpf file) in the PRINT JOBS folder which is accessible from the user's smartphone or tablet. If required, it can then be printed using the print function of Cortado Workplace. Illus. 76 Illus. 76 Print Jobs folder in Cortado Workplace for BlackBerry, ios and Android You will find a detailed guide for printing with Cortado Workplace here: BlackBerry: Berry/QuickGuide.aspx ios: Pad/QuickGuideiPhone.aspx ThinPrint Application Server Engine Manual 61

62 Android OS: A preview or opening the.tpf files on the smartphone or tablet is not possible. Print-to-ePaper The Print-to-ePaper printer will be available in the near future. Files that are sent to this printer, are available in Cortado Workplace in.pdf format. Encrypting print jobs The ThinPrint Engine has been extended to include SSL/TLS encryption for printing, which ensures a secure connection between the ThinPrint Engine and the ThinPrint Client. Using SSL encryption requires the following types of certificates to be imported: one personal server certificate and one root certificate on each server with ThinPrint Engine one personal client certificate on each client for sending encrypted print jobs SSL/TLS certificates can be ordered at a certification authority or can be created by yourself (see the Creating SSL/TLS certificates for printing with ThinPrint white paper, Page 94). Depending on your security restrictions you can: Create an own client certificate for each server and for each client Or Create only one client certificate to install it on all servers and on all client machines. Using the root certificate the ThinPrint Engine checks the certificates received from the clients. It checks whether the respective client is authorized to receive print data. SSL/TLS encryption is also available for use with the ThinPrint Connection Service. Importing SSL certificates on the servers Install your SSL certificates on the servers as follows: 1. Log on as a member of the ADMINISTRATORS group and open the Microsoft Management Console from the Command Prompt with: mmc 2. In the MMC, select: FILE ADD/REMOVE SNAP-IN CERTIFICATES ADD SERVICE ACCOUNT NEXT LOCAL COMPUTER NEXT PRINT SPOOLER FINISH 3. Select immediately thereafter: ADD COMPUTER ACCOUNT NEXT LOCAL COMPUTER FINISH CLOSE 4. Lastly, click OK (Illus. 77). 62 Manual ThinPrint Application Server Engine

63 Illus. 77 Illus. 77 Adding snap-ins for SSL certificates to the MMC 5. Import the certificate(s) to the two places shown in Illus. 78 (see arrows). To do so, select each time ALL TASKS IMPORT in the context menu and then NEXT BROWSE OPEN NEXT (PASSWORD NEXT) 24 PLACE ALL CERTIFI- CATES IN THE FOLLOWING STORE NEXT FINISH OK. The branch CERTIFICATES will be created automatically, if necessary. The personal server certificate will be imported under CERTIFICATES SERVICE (PRINT SPOOLER) ON LOCAL COMPUTER SPOOLER\PERSONAL and the root certificate under CERTIFICATES (LOCAL COMPUTER) TRUSTED ROOT CERTIFICATION AUTHORITIES. Illus. 78 Illus. 78 Importing two SSL certificates to the server 24 Please note that the server certificate is a password-protected.pfx file with a private key. For the root certificate however, a.cer file (without a key and password) must be imported. ThinPrint Application Server Engine Manual 63

64 Two examples for imported certificates can be found in Illus. 79 and 80. Illus. 79 Illus. 79 First SSL certificate imported on the server (example for server certificate) Illus. 80 Illus. 80 Second SSL certificate imported on the server (example for root certificate) Selecting certificates 6. For using the imported SSL certificates with the ThinPrint Engine open the Thin- Print Port configuration with START (ALL) PROGRAMS THINPRINT ENGINE CONFIGURATION. 64 Manual ThinPrint Application Server Engine

65 7. Select ENCRYPTION SETTINGS in the PORT MANAGER context menu (Illus. 81). Illus. 81 Illus. 81 Selecting ENCRYPTION SETTINGS 8. Enter the names of server and root certificates under ENCRYPTION CERTIFICATES (Illus. 82). Use the names that are displayed in the column ISSUED TO of the MMC s certificate overview (in Illus. 79 and Illus. 80 Company ABC and Company ABC-CA as examples). Illus. 82 Illus. 82 Entering imported SSL certificates (example) 9. Fill in both fields and check that each certificate is installed on the server (Page 62) and that the certificates installed on the clients are trusted by the server certificates (see below). Otherwise, print jobs will not be executed. Enabling encryption SSL encryption is enabled per ThinPrint Port in the Port Configuration (Illus. 83). ThinPrint Application Server Engine Manual 65

66 Illus. 83 Illus. 83 Enabling encryption in the port configuration Importing SSL certificates on the clients For client-side installation of SSL certificates, please consult the relevant ThinPrint Client manual (Page 94). In the following, installation is described with the example of the ThinPrint Client Windows. 1. To install a client certificate, select the following in the MMC on the client PC: FILE ADD/REMOVE S NAP-IN CERTIFICATES ADD COMPUTER ACCOUNT 25 LOCAL COMPUTER FINISH OK 2. Now import the certificate by selecting ALL TASKS IMPORT in the context menu (Illus. 84) and then NEXT BROWSE OPEN NEXT PASSWORD NEXT PLACE ALL CERTIFICATES IN THE FOLLOWING STORE NEXT FINISH OK 25 If only one person uses the machine, at this point add instead MY USER ACCOUNT. Via CURRENT USER PERSONAL, import the certificate to their user store. The client certificate is thereby linked to the current user. 66 Manual ThinPrint Application Server Engine

67 Illus. 84 Illus. 84 Starting import of an SSL certificate on a client machine The result is shown in Illus. 85. Illus. 85 Illus. 85 SSL certificate imported to a client machine Registry entry CertName Before sending encrypted print data, the server checks whether the name of the imported certificate is included in the CertName entry in the client computer s Windows registry and whether the stored certificate is present on the client machine. The CertName entry in the registry must be entered manually as follows: 1. After the certificate has been imported, create the following registry key on the client machines with REGEDIT (Illus. 86; data type: reg_sz): hkey_local_machine\software\thinprint\client\certname ThinPrint Application Server Engine Manual 67

68 Illus. 86 Illus. 86 Registry entry for SSL encryption on Windows clients (example for certificate Company ABC) 2. Enter as value the name of the imported certificate as displayed in the column ISSUED TO of the MMC s certificate overview (Company ABC as example in Illus. 85 and 86). 3. Restart ThinPrint Client Windows. The CertName registry entry is only needed for encrypting print data; receipt of unencrypted print data is still possible. Print job tracking The ThinPrint Tracking Service is included in the ThinPrint Engine installer software. Its setup is described in the ThinPrint Tracking manual (Page 94). Print job tracking gathers information about print activities using ThinPrint Engine, if you print via ThinPrint Ports. With it, print related data is gathered on the server and forwarded to an SQL server (Illus. 87). Print job tracking has the following components: ThinPrint Engine (sends data to the Tracking Service) ThinPrint Tracking Service (receives data and writes it to an SQL database) ThinPrint Tracking Report Engine (web component for clear analysis, summary, and graphic report of tracking results) Note! The SQL server is not included in the ThinPrint Engine. Tracking Report Engine and SQL server have to be set up separately (see the ThinPrint Tracking manual). 68 Manual ThinPrint Application Server Engine

69 Illus. 87 Illus. 87 Example for using Tracking Tracking Service You can gather information about the print jobs sent with the ThinPrint Engine for your statistics (tracking). To do so, you must set up a Microsoft SQL server. The Thin- Print Engine sends tracking data to this server via the Tracking Service. Print data available for tracking is: Author of a print job Printer used Settings used Print job compression Number of pages printed Information on any errors Print volume per user/group Tracking Report Engine The Tracking Report Engine makes it possible to display data from the SQL database as an overview in a web browser. All significant information on print jobs can be summarized by various criteria, sorted, and graphically displayed (Illus. 88). ThinPrint Application Server Engine Manual 69

70 Illus. 88 Illus. 88 Analyzing SQL data in a web browser (example) Preparing ThinPrint Engine and Tracking Service To prepare the ThinPrint Engine for sending data of sent print jobs to the Tracking Service, you must make the following changes to the configuration of the ThinPrint Engine: 1. Open configuration with START (ALL) PROGRAMS THINPRINT ENGINE THIN- PRINT CONFIGURATION. 2. Mark the respective ThinPrint Engine node and select EDIT SETTINGS (Illus. 89). 70 Manual ThinPrint Application Server Engine

71 Illus. 89 Illus. 89 Selecting TRACKING settings 3. Enter the following settings in the TRACKING tab (Illus. 90): ENABLE TRACKING SQL server s address and name 26 SQL server or Windows authentication: an account (specified with Tracking Database installer) which has write permissions for your database Encryption settings if the data are to sent encrypted to the SQL server Name of the Tracking database (created using its installer) Click OK to confirm. The Result is shown in Illus In case you access the SQL server remotely, open SQL Server Configuration Manager and enable the protocols NAMED PIPES and TCP/IP. Then start SQL SERVER BROWSER in the services folder. ThinPrint Application Server Engine Manual 71

72 Illus. 90 Illus. 91 Illus. 90 Enable Tracking and enter settings Illus. 91 Print job tracking enabled For details, see ThinPrint Tracking manual (Page 94). AutoConnect With AutoConnect it's possible to create printer objects automatically using templates on a terminal server (Illus. 92). It is installed as a Windows service. AutoConnect is supplied with the ThinPrint Engine. AutoConnect can also be configured as a group policy (GPO). This is described in detail in ThinPrint Server Engine manual. 72 Manual ThinPrint Application Server Engine

73 AutoConnect features Dynamic creation of printer objects in a terminal session, based on various criteria, e.g.: User name Printer name Client (or host) name Client IP address Organizational Units of which the terminal servers or virtual desktops are members Support of ThinPrint Output Gateway Support of ThinPrint Virtual Channel Gateway Support of ThinPrint Connection Service Note! AutoConnect is installed together with ThinPrint Engine (because its Windows service has to be run together with the ThinPrint Engine) to enable printing. This is independent of the AutoConnect functions of mapping or creating printers on terminal servers. Basic constellation ThinPrint Engine on a terminal server, as well as AutoConnect and ThinPrint Output Gateway Illus. 92 Illus. 92 AutoConnect configuration with terminal servers Templates and ports Printers generated with templates by AutoConnect on the server are always installed on the same ThinPrint Port as the template. If printers are to print over several Ports, multiple templates for the same driver can be set up on various Ports. ThinPrint Application Server Engine Manual 73

74 Template permissions So that each user only sees his/her printers and not all printers installed on the server, templates must be assigned the following permissions: Administrators System Print, Manage documents and Printer Print, Manage documents and Printer Delete all permissions of other users. Note! Templates must not be shared. Port pooling Port pooling on ThinPrint Ports can also be used with AutoConnect; see Page 43. AutoConnect configuration You can configure AutoConnect locally as well as remotely; for remote configuration AutoConnect must be installed on both machines. 1. Open the ThinPrint configuration with START (ALL) PROGRAMS THINPRINT ENGINE CONFIGURATION. 2. Click ADD and then specify the computer address (Illus. 93) for each local or remote ThinPrint Engine to be configured (Illus. 94). Illus. 93 Illus. 94 Illus. 93 Open the configuration console for server components Illus. 94 Specify - local or remote configuration 74 Manual ThinPrint Application Server Engine

75 3. The ThinPrint Engine console appears (Illus. 95). Select on the left, i.e., in the Console Tree: THINPRINT THINPRINT ENGINE AUTOCONNECT. Illus. 95 Illus. 95 Open AutoConnect configuration Configuration Click on EDIT SETTINGS (Illus. 95) will open the AutoConnect configuration (Illus. 96). ThinPrint Application Server Engine Manual 75

76 Illus. 96 Illus. 96 AutoConnect configuration: GENERAL tab Settings In GENERAL tab (Illus. 96) the default value for the connection protocol between Auto- Connect and ThinPrint Clients can be selected. If you select TCP/IP or VIRTUAL CHAN- NEL (ICA OR RDP), you restrict the communication to a protocol family. The AUTO setting allows both protocol families and is therefore recommended for ICA/RDP as well as TCP/IP ThinPrint Ports. In the Dynamic Printer Matrix (see below) you can limit this setting per rule; here, the columns T, R and I correspond to the protocols TCP/IP, RDP and ICA. Note! The protocols (TCP/IP, RDP or ICA) of AutoConnect, ThinPrint Client and of the ThinPrint Port the template is connected with must match. See also the ThinPrint Client manual. Furthermore you can decide here, which events AutoConnect art to be logged and displayed in the AUTOCONNECT DIAGNOSTICS table (Illus. 95). In PRINTER CREATION tab you can decide, when the printers are to be created or mapped: Either at each session logon / logoff Or when disconnecting and reconnecting a session (Illus. 97). Restart the TP AUTOCONNECT SERVICE afterwards. Here it is also possible to choose the way to set the session s default printer either the CURRENT PRINTER of the respective THINPRINT CLIENT or the DEFAULT column in MAP ADDITIONAL PRINTERS (Illus. 108) 76 Manual ThinPrint Application Server Engine

77 Illus. 97 Illus. 97 AutoConnect configuration: PRINTER CREATION tab In PRINTERS tab (Illus. 98) you can set the user rights for the printers to be created: PRINT, MANAGE DOCUMENTS (default) or PRINT, MANAGE PRINTERS AND DOCUMENTS. The permission MANAGE DOCUMENTS allows, among other things, hanging print jobs to be deleted. MANAGE PRINTERS allows, among other things, printers to be deleted. Under PRINTER NAME CONTAINS THE PREFERENCE, specify whether the printer names to be created should include the CLIENT NAME (= computer name) or the CLIENT IP ADDRESS. If the client name cannot be detected, the client IP address is automatically entered (TCP/IP only). Furthermore you can decide which properties of a local installed printer or driver are to be transferred to the session printer s properties: The COMMENTS and LOCATION columns of the local Printers folder The native printer driver s properties PAPER SIZE, COLOR, PAPER SOURCE, PRINT ON BOTH SIDES, PRINT QUALITY and FINISHING options. Click APPLY or OK to confirm your settings. ThinPrint Application Server Engine Manual 77

78 Illus. 98 Illus. 98 AutoConnect configuration: PRINTERS tab Dynamic Printer Matrix With Dynamic Printer Matrix, you can specify which templates should be used for creating a session printer. Select the DYNAMIC PRINTER MATRIX in the console tree (Illus. 99). Illus. 99 Configuration Illus. 99 Dynamic Printer Matrix in the MMC Double-clicking in the table (Illus. 99) will open the configuration console of Dynamic Printer Matrix (Illus. 100). Use the Buttons (upper arrow) to edit the table. 78 Manual ThinPrint Application Server Engine

79 Illus. 100 Illus. 100 Edit Dynamic Printer Matrix Assigning templates Dynamic Printer Matrix assigns any printer to a specific template. For example, the _#ICA_32 template is assigned to the HP DeskJet 460 printer in Illus. 101; the Brother HL-10DV printer is given the _#ThinPrint Output Gateway template. All printer and class names listed in the ThinPrint Client can be translated, including printers which are connected to a shared printer (on a local print server); e.g., the printer Alps MD-1000 (last entry in Illus. 101). Illus. 101 Illus. 101 Dynamic Printer Matrix entries Table functions You have the option of hiding unneeded columns (Illus. 102). In all cases, hidden columns (and their rules) are deactivated. ThinPrint Application Server Engine Manual 79

80 Illus. 102 Illus. 102 Hiding columns When you start a terminal session or reconnect to an existing session, AutoConnect is activated automatically. Then it processes the table from top to bottom, for each printer activated in ThinPrint Client, (Illus 18 and 20). If all criteria (columns) in one line are met for the first printer AutoConnect searches for the template specified in the column TARGET (without _#) and creates the session printer using the applicable template properties. AutoConnect now stops the search for this printer in the table and, if applicable, continues the same procedure for the next activated printer in ThinPrint Client etc. etc. You can change AutoConnect s processing sequence by switching the line order using the arrow keys ( ). You can also add or delete lines. (For the two gray lines refer to Page 83.) The table has the following columns/translation rules: IP RANGE, CLIENT NAME, DRIVER NAME, PRINTER NAME, CLASS NAME, CLIENT TYPE and USER/GROUP; here, * and? can be used as wild cards. The TARGET column represents the template name (without _#). These features are explained in the scenarios below; the scenarios can also be combined with each other. 80 Manual ThinPrint Application Server Engine

81 Scenario: Remote offices and home users with various connections. Illus. 103 Illus. 103 Connections with different bandwidths require different bandwidth limits (ThinPrint components not shown here) Each type of connection uses a different IP address range (Illus. 103). Different bandwidths, print protocols, and parameters can be assigned to each of them. IP range The IP RANGE column in the Dynamic Printer Matrix could contain, for example, the following entries: / / /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: The 24 represents the following subnet mask: ; i.e., 3x8=24 set bits (22 is equivalent to ; 16 is equivalent to ; and 8 is equivalent to ). ThinPrint Application Server Engine Manual 81

82 Scenario: Native Printing or Driver Free Printing. Illus. 104 Illus. 104 Windows clients can use Driver Free Printing, all others print with a native driver (ThinPrint components not shown here) All Windows clients are to use Driver Free Printing; i.e., to print with the ThinPrint Output Gateway virtual printer driver. The client type W is therefore selected for them. All other clients are to use one or more native printer driver (Illus. 104). Client type On the one hand you can select between the client platforms Windows (W), Unix or Linux (U), Java (J) and other (X), and on the other hand between the connection protocols TCP/IP (T), RDP (R) and ICA (I); see also Page 76. By default, all client types are selected. If specific translation rules are only to apply to selected client types, then, they are easily selected by simply adding or removing a checkmark. In the following table, as an example, the _#ThinPrint Output Gateway template is assigned to all Windows clients 27. All other client types use the _#HPLaser template, which uses a native printer driver. W U J X T R I Target ThinPrint Output Gateway HPLaser 27 Windows 95 and later 82 Manual ThinPrint Application Server Engine

83 Illus. 105 Illus. 105 Templates for native printing (_#HPLaser) and for Driver Free Printing (_#ThinPrint Output Gateway) User/Group The USER/GROUP column in the Dynamic Printer Matrix could contain names of local or domain users or groups. Try client printer name or client class name. There are two special lines in Dynamic Printer Matrix: TRY CLIENT PRINTER NAME and TRY CLIENT CLASS NAME Unlike the other lines, these two lines do not include line subdivisions. These lines mean that AutoConnect is trying to find a suitable template for the printer names or the class names on the client machine. As mentioned above in the paragraph Dynamic Printer Matrix : If a (gray) special line (TRY CLIENT PRINTER NAME or TRY CLIENT CLASS NAME) is found for which a template exists, the relevant printer is created and no further lines underneath in the table are searched through. If, on the other hand, matches for all columns (except TARGET) are found a white (editable) line, a printer is created according to the entry under TARGET. In this case, too, the lower lines will not be checked. Priority is set by the order of the lines in the table. ThinPrint Application Server Engine Manual 83

84 Illus. 106 Illus. 106 Special lines: try client printer name/try client class name In the example in Illus. 106, the special line TRY CLIENT PRINTER NAME is used as the first line. In this case, AutoConnect first checks whether a template (_#HP LaserJet 4) exists for the printer name to be mapped (e.g., for HP LaserJet 4). If so, a client printer is created using this template (see also Page 73). The special line TRY CLIENT CLASS NAME is used as the third line. In this case, Auto- Connect checks whether a class (e.g., HPLaser) has been defined in the ThinPrint Client Manager for the printer name to be mapped. If there is a template (_#HPLaser) for this class, a printer is created in the session using this template. Variables Variables can also be used in the column TARGET, however, they are restricted to connections to printer shares. Refer to ThinPrint Server Engine manual (Page 94). Script control If you want to run AutoConnect from the Command Prompt (Page 26) or using a script, amongst others the following parameters can be used: Parameter Function -v (Verbose) Display messages; give detailed information at startup -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 folder under LOCATION (Illus. 31 and 32) -q (Quiet) Error messages are not sent to the client machine s desktop 84 Manual ThinPrint Application Server Engine

85 Parameter Function -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, AutoConnect, and ThinPrint Client must match. -i protocol (Interconnection) Select protocol for connection to the Thin- Print Clients; overwrites AutoConnect dialog settings (acceptable values: TCPIP, VC, AUTO); see Illus. 96) -a address Specification of IP address or client name of the computer on which a ThinPrint Client is running i.e., of local print servers or external print servers of network printers (e.g. SEH TPG120, Page 95). -? or -h (Help) Will open parameter help panel Script control also works for network printer objects which are created with the Dynamic Printer Matrix. Using logon / logoff script Running AutoConnect script-controlled or from the Command Prompt (in script mode): Enter the AutoConnect cue in a terminal server logon script. Example for mapping of printers from a local print server ( , ThinPrint Client installed): tpautoconnect d tpautoconnect -a Enter the option disconnect printers in a terminal server logoff script: tpautoconnect d ThinPrint Application Server Engine Manual 85

86 Map additional printers Illus. 107 Illus. 107 Open Map Additional Printers Both scenarios in Illus. 103 and 104 require a ThinPrint client on the client side. However, if there is no ThinPrint Client on the target computer, any number of network printers can be added with the MAP ADDITIONAL PRINTERS function in the Auto- Connect configuration (Illus. 107): Default User/ Group IP Range Client Name Target * * * * \\cps03\lexmark Please enter the domain in USER/GROUP (see Illus. 108). The following syntax applies 28 : \\domain\user(group) Unlike it s operation under the Dynamic Printer Matrix, when AutoConnect works in MAP ADDITIONAL PRINTERS, it always works through all lines of the table from top to bottom and installs the same number of printers in one terminal session as the number of lines existing in the table. If a share entered under TARGET belongs to a printer that is connected to a ThinPrint Port, the resulting (= created by AutoConnect) printers print with ThinPrint; if not, then without. For the function of DEFAULT column see Page You can also enter \\\user(group) if users belong to the same domain as the machine on which AutoConnect is running. 86 Manual ThinPrint Application Server Engine

87 Illus. 108 Illus. 108 Edit Map Additional Printers and export configuration Send, export and import the configuration Similar to the port configuration, AutoConnect also has the additional options of SEND CONFIGURATION, EXPORT, and IMPORT (Illus. 95 and 108). When sending, the entire AutoConnect configuration is sent to other computers; with export/import, only the Dynamic Printer Matrix or Map Additional Printers tables is sent. Caution! With Send and Import, an existing AutoConnect configuration will be overwritten. Ensure you save the existing configuration beforehand with the export function. Send configuration Export/Import The SEND CONFIGURATION function lets data from the AutoConnect configuration be sent to groups of servers; see also Procedure when sending (Page 36). The EXPORT function (Illus. 108) lets the contents of the tables Dynamic Printer Matrix and Map Additional Printers be written in a.csv file 29 (Illus. 109) and thus opened in other programs, such as Microsoft Excel. Regardless of whether changes are made thereby, the current status can be applied to the Dynamic Printer Matrix on any server using the IMPORT function. 29 A.csv file is a text file for saving or exchanging simply structured data. The extension csv stands for Character Separated Values or Comma Separated Values, because the individual values are separated by a special character (here: semicolon). ThinPrint Application Server Engine Manual 87

88 Appendix Illus. 109 Illus. 109 Saving data in a.csv file Once you are finished configuring AutoConnect, click APPLY or OK. Appendix Customer service and technical support Customer Service SUPPORT Licenses Entering and activating license keys Note! Activating a ThinPrint license All license keys are valid for 30 days after they have been entered. They must be activated within this time to continue printing. Demo license keys cannot be activated. A license key s expiration date can be found in License Manager under VALID UNTIL (Illus. 112). Once you have successfully tested the ThinPrint Engine, you can purchase a full license. You will receive a new license key, which is then entered in the License Manager and activated. To activate the license, select SUPPORT & SER- VICES SOFTWARE ACTIVATION at the ThinPrint website and follow the instructions. Once your information has been verified, you will receive an activation key by Open the License Manager from START (ALL) PROGRAMS THINPRINT ENGINE CONFIGURATION THINPRINT LICENSE MANAGER to enter license keys, check registration keys (for activation), and activate licenses (Illus. 110). 88 Manual ThinPrint Application Server Engine

89 Appendix 2. The window depicted in Illus. 111 or 112 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! Illus. 110 Illus. 110 Starting License Manager: Open configuration console for server components Illus. 111 Illus. 112 Illus. 111 Context menu for one license key Illus. 112 Context menu for all license keys ThinPrint Application Server Engine Manual 89

90 Appendix License usage With user-based licensing you can check how many licenses are already used. Select LICENSE USAGE in the respective ThinPrint Engine node (Illus. 113). Afterwards the number of licenses installed on this machine and the number of used licenses are shown (Illus. 114). Illus. 113 Illus. 114 Illus. 113 Context menu of ThinPrint Engine node Illus. 114 License usage 90 Manual ThinPrint Application Server Engine

91 Appendix Server roles and custom setup Selecting a server role (Illus. 115) leads to the installation options listed below: Illus. 115 Illus. 115 Select a server role or the CUSTOM SETUP Server role Installation options TERMINAL SERVER Print Controller (= ThinPrint Engine) incl. Tracking Service, Output Gateway, AutoConnect, Virtual Channel Gateway, Session in Session, Print-to-Cloud and Administration Tools (= MMC components) PRINT SERVER Print Controller incl. Tracking Service, Output Gateway, AutoConnect and Administration Tools TERMINAL SERVER EXTENSION Output Gateway, Session-in-Session, AutoConnect, Print-to-Cloud and Virtual Channel Gateway PRINT SERVER FOR VMWARE VIEW Print Controller, Output Gateway, AutoConnect and Administration Tools ADMINISTRATION TOOLS MMC components only CUSTOM SETUP free choice of component Custom Installation Here you can specifically select and install individual ThinPrint components (Illus. 116). The following components can be selected: Print Controller (=ThinPrint Engine) Tracking Service, see Page 68 Output Gateway (for Windows clients), see Page 49 Output Gateway PS (for non-windows clients) AutoConnect, see Page 72 Session-in-Session, see Page 92. ThinPrint Application Server Engine Manual 91

92 Appendix Administration Tools (Installation of ThinPrint-MMC components, to remotely configure from this computer another one with ThinPrint components installed on it) Print-to-Cloud, see Page 59 Virtual Channel Gateway (for print server environments only) V-Layer Service (for print server environments only) Illus. 116 Illus. 116 All CUSTOM SETUP options Session-in-Session This feature makes it possible for client or network printers to be still available in a session, even when a further session is opened from within an existing one, or if you from this (first) session access a server or a virtual desktop that is already running a Published Application (Illus. 117). Thereby, printers are mapped into the second session and print jobs are passed on from the second to the first server or desktop. Illus. 117 Illus. 117 Session-in-Session: Open a further session from within an existing session 92 Manual ThinPrint Application Server Engine

93 Appendix Installation, licensing and configuration You need a ThinPrint Engine on the machine on which the (second) session is running (orange computer in Illus. 117) that means a ThinPrint Application Server Engine on a terminal server or a ThinPrint Desktop Engine on a virtual desktop. Session-in- Session is a part of ThinPrint Application Server Engine and does not require its own license. A ThinPrint Client is installed on the client machine (here: a laptop), and an ICA or RDP client must be running. The Session-in-Session component is installed on the middle computer (shown blue). On terminal servers, this can be selected during the installation procedure via CUSTOM SETUP (Illus. 115). Select SESSION IN SESSION (arrow in Illus. 118). This feature functions without any further configuration. An ICA or RDP connection is a prerequisite. Illus. 118 Illus. 118 Custom Installation: Select SESSION IN SESSION Install the Desktop Extension of ThinPrint (Application) Server Engine 8.6 on the middle computer (shown blue) if it s a virtual (or real) desktop irrespective of an installed ThinPrint Desktop Engine. If you also want to print from the middle computer, then you need two ThinPrint Engines 30 (on the orange and on the blue computer in Illus. 117). If you are using central print servers, then Session-in-Session is not required, as all computers can print via the print server anyway. Citrix ICA Client later installed If you ve installed a Citrix ICA Client after Session-in-Session, uninstall the Sessionin-Session component via custom setup (see Illus. 117), and afterwards reinstall it. Please also note the checklist on Page 27. Update If you want to update from ThinPrint 8.0 to 8.6, simply install version 8.6, using the standard setup procedure. The old version will be updated automatically. Your settings will be retained. When updating from ThinPrint 7.6 to 8.6 and you wish to retain your settings, first update from 7.6 to 8.0 and then install 8.6, fully updating 7.6 to ThinPrint Application Server Engine 8.6 on terminal servers or ThinPrint Desktop Engine on virtual desktops ThinPrint Application Server Engine Manual 93

94 Appendix For updates of ThinPrint Engines older than one year 31, valid license keys are required. These license keys can be purchased via the Update Subscription Program. Please contact your reseller or send an to Uninstallation To uninstall a ThinPrint component open PROGRAMS AND FEATURES in CONTROL PANEL. Mark a ThinPrint component and then select UNINSTALL (Illus. 119). Illus. 119 Illus. 119 Uninstalling ThinPrint components Remote client configuration Remote configuration is possible for ThinPrint Client Windows printing with TCP/IP protocol. The entry RmtConf is needed in the Windows registry of all client machines you want to configure remotely. More information can be found in the ThinPrint Client Windows or ThinPrint Client Service Windows manuals (see below). Additional sources Further information about ThinPrint can be downloaded from our website. Manuals The following manuals (amongst others) are available at PRODUCTS OVERVIEW <product name>. ThinPrint Tracking ThinPrint Server Engine ThinPrint Engine for VMware View ThinPrint Personal Printing ThinPrint Connected Gateway ThinPrint Host Integration Service 31 or you re a customer from North America 94 Manual ThinPrint Application Server Engine