Windows computer as a ThinPrint Client Gateway. Technical Information

Windows computer as a ThinPrint Client Gateway Technical Information Cortado AG Alt-Moabit 91 a/b 10559 Berlin Germany/ Alemania Cortado, Inc. 7600 Grandview Avenue Suite 200 Denver, Colorado 80002 USA/EEUU Cortado Pty. Ltd. Level 20, The Zenith Centre, Tower A 821 Pacific Highway Chatswood, NSW 2067 Australia E-Mail: info@team.cortado.com Web: www.thinprint.com Issued: June 7, 2012 (v49)

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. 2 Technical Information Windows Client Gateway

Contents Introduction... 4 Sample configuration 1: with terminal server... 4 Basic installation... 5 Basic configuration... 6 Client machine... 6 Client Gateway (local print server)... 6 Terminal server... 8 Print test... 9 Sample configuration 2: with central print server... 9 Basic installation... 10 Basic configuration... 10 Central print server... 11 Terminal server... 12 Print test... 13 Appendix... 13 Special case: only 1 Client Gateway per Port... 13 How can I suppress incorrect print jobs?... 13 Environment... 13 Scenario... 14 Solution... 14 Procedure... 14 Additional sources... 16 Abbreviations... 16 Windows Client Gateway Technical Information 3

Introduction Introduction A.print Client Gateway can simplify the implementation of ThinPrint.print, because it can receive.print print jobs for an entire group of client machines and printers, decompress and decrypt 1 them, and then distribute them conventionally in a local network as a local print server. The remote LAN, then, only needs a single.print Client on a Client Gateway. Otherwise, a.print Client must be installed on every end device on the client side: on PCs, printers, thin clients, print servers of network printers, etc. This means, for example, that thin clients could require a firmware or BIOS update. Mixed environments pose no problem, either. The.print Client is installed on all end devices which allow a simple installation, and all others are served by the.print Client Gateway. Note! There are many alternatives for.print Client Gateways, e.g., Windows or Linux machines, print server appliances, and print servers from SEH or Intermate. But for Driver Free Printing only Windows machines are usable. And for Printer Virtualization Layer you need an additional central print server (Windows); see.print Server Engine user manual (Page 16). The following two examples illustrate test installations of a.print Client Gateway. Once you are convinced of the software s functionality, the installation can be adapted to your requirements. Sample configuration 1: with terminal server With this sample configuration all users should be able to print to both their local (attached) printer and a network printer (via TCP/IP; Illus. 1). The components required for this example are: 1 client machine (Windows) with a locally installed printer 1 Windows machine configured as a.print Client Gateway incl..print Client Service Windows 1 network printer (with its own network card) without integrated.print Client 1 terminal server 2 including the.print Application Server Engine license (with server-based licensing) or the.print Application Server Basic Pack license + user licenses (with user-based licensing) 1 For installation of SSL/TLS certificates see the Creating SSL certificates for printing with Thin- Print.print white paper or the.print Server Engine manual (Page 16). 2 Windows Server 2003/2008 (2003 x64 with Service Pack 1 or later) 4 Technical Information Windows Client Gateway

Sample configuration 1: with terminal server Illus. 1 Illus. 1 Sample configuration 1 Notes 1. The.print Client Gateway only receives print jobs via the protocol TCP/IP (not via ICA or RDP). 2. Please refer to the.print Application Server Engine and.print Client Service Windows user manuals for installations of.print Engine and.print Client not detailed here (Page 16). 3. The following.print licenses are required for this sample configuration (each of which offers a 30-day demo version): License Either.print Application Server Engine with server-based licensing Or.print Application Server Basic Pack + user licenses with user-based licensing Location of installation per terminal server.print Application Server Basic Pack per terminal server; user licenses have to be splitted Basic installation Client machine Local print server (Client Gateway) Terminal server If necessary, install an RDP client (Remote Desktop Connection) or a Citrix ICA client on a Windows PC. Install the.print Client Service Windows on another Windows machine (Windows 2000 or later). Install the.print Engine on a terminal server 3 (required license: see above). 3 Windows Server 2003 or 2008 with or without Citrix XenApp Windows Client Gateway Technical Information 5

Sample configuration 1: with terminal server Basic configuration Give all computers involved IP addresses in the same subnet; e.g.: for the client machine: 192.168.131.124 for the.print Client Gateway: 192.168.131.125 for the network printer: 192.168.131.200 for the terminal server: 192.168.131.126 In this example, a printer is connected to the client machine with the default printer interface LPT1:; the client machine is named client1. Client machine Create the printer HP DeskJet on the client machine (here: client1) and share it (share name: DeskJet; Illus. 2). (This printer share is necessary for Windows clients only.) Illus. 2 Illus. 2 Printer on the client machine Note! Use the same admin account for both client PC and local print server (Client Gateway) administration. Client Gateway (local print server) Create two printers on the local print server: One printer as a connection to the DeskJet share on client1 (Illus. 3) the network printer (with internal print server without.print Client) HP Color Laser Jet 4700. To do so, create the new port IP_192.168.131.200 as Standard TCP/IP port type (Illus. 3 and 4). 6 Technical Information Windows Client Gateway

Sample configuration 1: with terminal server Illus. 3 Illus. 4 Illus. 3 Printers and Faxes folder on the local print server (.print Client Gateway) Illus. 4 Printer properties of the network printer Right click the.print Client icon in the taskbar (Illus. 5). Choose RELOAD PRINT- ERS; the newly installed printers will be detected. Illus. 5 Illus. 5.print Client s context menu in the taskbar Next, start.print Client Manager by choosing CONFIGURE (Illus. 5). The two printers with their IDs are shown (Illus. 6). Set the checkmarks of both printers for use with AutoConnect (arrows left). Windows Client Gateway Technical Information 7

Sample configuration 1: with terminal server Illus. 6 Illus. 6.print Client Manager on Client Gateway: printer IDs 1 and 2 Close.print Client Manager with OK. Terminal server From the client PC open a Remote Desktop or Citrix ICA session on the terminal server. Open the Command Prompt, change to the.print Engine s program directory 4 and import the printer(s) with the following command 5 : TPAutoConnect -a 192.168.131.125 The result is shown in (Illus. 7). Illus. 7 Illus. 7 Printers and Faxes folder in the terminal session A logoff script can be used to remove the printers (with logging off). In the session, check ThinPrint port configuration (START PROGRAMS.PRINT ENGINE PORT MANAGER) to see that protocol and bandwidth are set correctly (Illus. 8). Then close the port configuration. 4 e.g. c:\program Files\ThinPrint.print Engine 5 Or use a script in the user s startup folder. 8 Technical Information Windows Client Gateway

Sample configuration 2: with central print server Illus. 8 Illus. 8 Port Configuration: printers on the terminal server assigned to a ThinPrint Port Print test Now test the.print Client Gateway installation. Print from within a terminal session using the newly created printers. Sample configuration 2: with central print server In this scenario an additional central print server is used (Illus. 9). The components required for this example are: 1 Windows client machine with a locally installed printer 1 Windows machine (Windows 2000 or later) configured as a.print Client Gateway (local print server incl..print Client Service Windows) 1 network printer with its own network card without integrated.print Client 1 terminal server (Windows 2003/2008) incl..print AutoConnect and ThinPrint Output Gateway 1 central print server (Windows 2003/2008) incl..print Engine Illus. 9 Illus. 9 Sample configuration 2: with a central (dedicated) print server Windows Client Gateway Technical Information 9

Sample configuration 2: with central print server Tips 1. The.print Client Gateway only works with the protocol TCP/IP. 2. Please refer to the.print Application Server Engine and.print Client Service Windows user manuals for installations of.print Engine and.print Client not detailed here (Page 16). 3. The following.print licenses are required for this sample configuration (each of which offers a 30-day demo version): License.print Server Engine.print Application Server Engine Location Central print server Terminal server Basic installation Client machine Client Gateway (local print server) Terminal server Central print server Install a terminal client (RDP or ICA client) on a Windows machine. Install.print Client Service Windows on another Windows machine (Windows 2000 or later). Have a terminal server ready. 6 Install.print AutoConnect and ThinPrint Output Gateway here (required license:.print Application Server Engine) Install.print Engine on a central print server (Windows 2003/2008). (Required license:.print Server Engine.) Basic configuration Assign all computers involved IP addresses in the same subnet; for example: for the client machine: 192.168.131.124 for the.print Client Gateway: 192.168.131.125 for the network printer: 192.168.131.200 for the terminal server: 192.168.131.126 for the central print server: 192.168.131.127 Configure the client machine and.print Client Gateway as described in example 1 (starting Page 6). Continue as follows: 6 Windows 2003/2008, 32bit or x64, with or without Citrix Xen Desktop 10 Technical Information Windows Client Gateway

Sample configuration 2: with central print server Central print server Once.print Engine is installed, create the two Client Gateway printers on the central print server. To do so, install either the original, native printer driver or a ThinPrint Output Gateway. Connect these printers with the printer port ThinPort:. 7 So that the print jobs reach the correct client, the address of the.print Client Gateway is included in printer object name. Therefore, rename the printer objects with the following syntax: printer_name#client_gateway_ip_address:printer_id For the shared printer on the terminal client in our example (Illus. 2) the resulting name would be: HP DesktJet#192.168.131.125:2 and for the network printer (Illus. 3): HP Color Laser Jet 4700#192.168.131.125:1 The IP address is the address of the Client Gateway and the printer ID is found in.print Client Manager on the Client Gateway (Illus. 6). (The printer name before the # is irrelevant for addressing print jobs; it only serves to differentiate between printers.) Share both printers (Illus. 10). Illus. 10 Illus. 10 Printers on the central print server Check ThinPrint port configuration in the MMC to see that both printers are correctly associated with a ThinPrint Port and that protocol and bandwidth are set correctly (Illus. 11). Check the name convention. Do not change the settings of the ThinPrint Port ThinPort:. Then close the port configuration. 7 Do not change the properties of the ThinPrint Port ThinPort: after installation of the.print Engine. Windows Client Gateway Technical Information 11

Sample configuration 2: with central print server Illus. 11 Illus. 11 MMC: printers on the central print server assigned to a ThinPrint Port In this example, the central print server is named printserver1. Terminal server With terminal session logon the users shall get the printers on the central print server. This is done by.print AutoConnect. On the terminal server open the AutoConnect configuration with START PROGRAMS.PRINT ENGINE AUTOCONNECT and enter the following settings in the MAP ADDITIONAL PRINTERS tab (Illus. 12): * * \\printserver1\deskjet * * \\printserver1\hpcolor printserver1 is the print servers name. DeskJet and HPColor are the printer share names. Confirm with APPLY. Illus. 12 Illus. 12 AutoConnect configuration on the terminal server: printer shares to be connected 12 Technical Information Windows Client Gateway

Appendix The users will see the printers in Illus. 13 in their terminal sessions. Illus. 13 Illus. 13 Printers in a terminal session Print test Now test the.print Client Gateway installation. Print from within a terminal session using the printers created by AutoConnect. Appendix Special case: only 1 Client Gateway per Port If only one Client Gateway per ThinPrint Port is used of printing, that Gateway can be set in the registry for each ThinPrint Port. In this case, the printer name no longer needs the IP address and/or client name; the ID is sufficient. For example: HP DeskJet#:1 To do this, open the registry key on the central print server hkey_local_machine \ system \ currentcontrolset \ control \ print \ monitors \ thinprint port and then the key with the name of each ThinPrint Port. Add the value Host with the data type REG_SZ and enter the IP address of each respective ThinPrint Client Gateway as value data in our example: 192.168.131.125 How can I suppress incorrect print jobs? Environment Server central Satellite offices with local print server (and own administrator) Local print server serves as.print Client Gateway Windows Client Gateway Technical Information 13

Appendix Scenario The local administrator deletes printers on the local print server without informing the central administrator; or, a printer is configured with an incorrect printer ID on the central server. What happens?.print print jobs that are sent to a printer which no longer exists or to an incorrect printer ID on the.print Client Gateway are rerouted to the current printer listed in.print Clients Service Windows. If printout of the wrong documents from the current printer is not desired, unwanted print jobs can be deleted automatically. Solution Create a printer that refers to nul: on the.print Client Gateway and set it as current printer. Procedure 8 1. Open the Printers panel from START( CONTROL PANEL) PRINTERS AND FAXES. 2. Do not select a printer. Select FILE SERVER PROPERTIES. This opens the window PRINT SERVER PROPETIES (Illus. 14). 3. All available printer ports are listed on the PORTS tab. If a NUL: port is already available, the panel can be closed. Otherwise, the port must be created using the ADD PORT button (Illus. 15). 4. Mark the LOCAL PORT, and click NEW PORT. Illus. 14 Illus. 14 Adding a printer port 8 with Windows 2003 as example 14 Technical Information Windows Client Gateway

Appendix Illus. 15 Illus. 15 New local-port port 5. Enter NUL as port name (Illus. 16). Illus. 16 Illus. 16 Port name: NUL: 6. Associate an unused printer with the port NUL: - for example, LEXMARK OPTRA (Illus. 17). 7. Close all dialogues with OK/CLOSE. Illus. 17 Illus. 17 Associating an unused printer with the NUL: port 8. Set this unused printer as current printer in.print Client (Illus. 18). Windows Client Gateway Technical Information 15

Appendix Illus. 18 Illus. 18 Defining an unused printer as current printer Additional sources At www.thinprint.com/ PRODUCTS OVERVIEW <product name> you will find the user manuals for the server and client components of ThinPrint.print. At www.thinprint.com/ SUPPORT WHITE PAPER DOWNLOAD you will find additional documentation on ThinPrint. Abbreviations ID IT LAN LPT NAT Output Gateway TCP/IP TP WAN Win32 Identification (number) Information technology Local Area Network Windows Lineprinter port Network Address Translation ( IP masking ) ThinPrint Output Gateway Transport Control Protocol / Internet Protocol ThinPrint Wide Area Network Windows 2000, XP, 2003, and Vista 16 Technical Information Windows Client Gateway