Example configuration

1199 views 0

Example scenario

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 immedi­ately after installation is completed, with no further configuration – provided you install either the RDP-type ThinPrint Client Windows or the ICA-type ThinPrint Client Windows for supporting the respective RDP or ICA connection types.

This plug-and-play installation cannot be used in every scenario. One reason is that it requires a Windows workstation as client. So only the main configuration options are illustrated here, using a example scenario as example. The following descriptions refer to the example scenario below.

Example scenario with client and user names

Example scenario with client and user names

Our scenario attempts to combine a couple of typical client and connection types in a terminal server environment. Clients are a workstation and a thin client as well as a local print server.

The following table describes the print environment used in the example configu­ration.

Machine name User name Printer ThinPrint Client type Print mode
client1 user1 Samsung ML-2525 TCP/IP type of ThinPrint Client Linux with native printer driver
ps06 Lexmark T644 ThinPrint Client Service Windows (TCP/IP) Driver Free Printing
client2 user2 HP Color LaserJet RDP type of ThinPrint Client Windows Driver Free Printing

The ICA protocol can also be used as an alternative to RDP. In that case, all RDP specific installations and configurations must be replaced with those for ICA.

Client setup

Configuring thin client

client1: ThinPrint Client Linux (TCP/IP) on a thin client

  • For this example scenario, choose a thin client with an embedded ThinPrint Client.
  • Open the configuration of the thin client (in this example: Igel Linux) and firstly, create a printer under Printer→ CUPS→ Printers (Caution: not under Thin­Print), see the arrow on the left in following Illus.
  • Select ADD (click on the asterisk, see right arrow in following illustration).
  • Create a printer name (no spaces) select a printer port if necessary, and click on the button Detect Devices (middle arrows in following illustration)
  • This opens the window, Select available device, where you can select the printer.
Thin Client Igel Linux: Creating CUPS printer

Thin Client Igel Linux: Creating CUPS printer

  • Next illustration shows the successfully created printer under CUPS.
Thin Client Igel Linux: Created CUPS printer

Thin Client Igel Linux: Created CUPS printer

  • Now go to ThinPrint→ Printer (left arrow).
  • Click on Add (asterisk) and enter the printer name. You can use spaces here.
  • Click on the button Detect Devices.
  • This opens the window Select available device, where you can select your printer as CUPS printer.
Thin Client Igel Linux: creating CUPS printer in ThinPrint

Thin Client Igel Linux: creating CUPS printer in ThinPrint

  • Enable this ThinPrint printer.
Thin Client Igel Linux: activate ThinPrint printer

Thin Client Igel Linux: activate ThinPrint printer

Next illustration shows the result. The printer is now set up for ThinPrint.

Thin Client Igel Linux: successfully set up ThinPrint printer

Thin Client Igel Linux: successfully set up ThinPrint printer

More information about thin client settings can be found in LPR/LPD printing with Linux, Mac or Windows CE clients.

Configuring local print server

ps06: ThinPrint Client Service Windows on a local print server

  • For the example scenario, install a Lexmark T644 printer.
Printer installed on local print server ps06

Printer installed on local print server ps06

  • Install ThinPrint Client Service Windows; please refer to ThinPrint Client Win­dows.
  • Open the ThinPrint Client Manager. Determine the Lexmark T644 printer ID from the Assignment tab.
Printer ID of the Lexmark T644 (in this example: 1)

Printer ID of the Lexmark T644 (in this example: 1)

Setting up the workstation

client2: RDP type of ThinPrint Client Windows on a workstation

Requirement: An RDP client must be installed. The scenario in the Example configuration applies.

  • For the example scenario, install an HP Color LaserJet printer.
  • Install RDP type of ThinPrint Client Windows; please refer to ThinPrint Client Windows.

ThinPrint Client is started automatically with the RDP session. It does not need to be configured for the example installation.

Printer installed locally on client2

Printer installed locally on client2

Server setup

All settings made for server configuration must be performed on each terminal server in a server farm (for import, export or sending configuration see Distributing port configuration).

Requirement: ThinPrint Engine must already be installed. The scenario in the Example configuration applies.

ThinPrint Ports

  • Open the ThinPrint configuration.
Opening ThinPrint Configuration

Opening ThinPrint Configuration

  • Click Add for each remote ThinPrint Engine to be configured and then specify the computer address. For the local ThinPrint Engine, click ThinPrint Engine in the console tree.
Open the configuration console for server components

Open the configuration console for server components

  • Select: ThinPrint→ ThinPrint Engine→ Port Manager (lower arrow).
ThinPrint Port(s) in the configuration console (= Port Manager)

ThinPrint Port(s) in the configuration console (= Port Manager)

  • Create the following ThinPrint Port by clicking the New ThinPrint Port icon and set the protocol:
Port name Port type (protocol)
RDP1: VCP = Virtual Channel Protocol (ICA or RDP)

 

Selecting port type for port “RDP1:”; click Apply

Selecting port type for port “RDP1:”; click Apply

A new ThinPrint Port

A new ThinPrint Port

  • 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 con­nections, create the following printer templates in the server’s print­ers folder :
Printer name ThinPrint Port Printer driver
_#Samsung ML-2525  ThinPort: Samsung ML-2525W Series
_#RDP RDP1: TP Output Gateway
Two new printer objects as templates

Two new printer objects as templates

Note! From Windows 2012 R2 type-4 drivers can’t be connected to third-party printer ports. That’s why use type-3 drivers with ThinPrint Ports.

Example for a type-3 driver, in this example: Lexmark T644 (MS)

Example for a type-3 driver, in this example: Lexmark T644 (MS)

  • Under Properties→ Security, assign permissions to the two printer templates, _#Samsung ML-2525 and _#RDP:
    • Delete all users and groups except for administrators and all application packages, if applicable.
    • Add SYSTEM and allow full control.
  • Change to the port configuration and check that the new printers have been assigned correctly to the ThinPrint Ports (if necessary, press F5 to refresh).
The new templates (right column) assigned to the ThinPrint Ports (left col­umn)

The new templates (right column) assigned to the ThinPrint Ports (left col­umn)

 

Configuring AutoConnect

  • Select Dynamic Printer Matrix in the Console Tree. To enable Auto­Connect 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 Printer
* * * \\ourdomain\user1 Samsung ML-2525
* * * \\ourdomain\user2 RDP
Opening the Dynamic Printer Matrix

Opening the Dynamic Printer Matrix

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 match­ing 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.
Dynamic Printer Matrix

Dynamic Printer Matrix

Creating a printer manually

  • Create the following printer object in the terminal server’s printers folder:

Lexmark T644#ps06:1

Attach it to the ThinPort: printer port.

Printing

  • Establish a Remote Desktop Connection from each client machine to the termi­nal server farm; as shown in our example, logging on as user1 and user2, respectively. The printers appear in the printers folder in the two sessions.
  • Open an application and print with each of these printers.
Printers of user1 in an terminal session as in the example

Printers of user1 in an terminal session as in the example

Printers of user2 in an terminal session as in the example

Printers of 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
ws2776 (user1) RDP 2 HP Color LaserJet 3600
ps06 (user1 + user2) TCP/IP 1 Lexmark T644
ws2307 (user2) TCP/IP 2 Samsung ML-2525

Please note which printers in terminal sessions use a native driver and which use the TP Output Gateway (see the Model column in illustration above).

Troubleshooting

If AutoConnect does not create the desired printers or if printing itself fails to work properly, please check the following before contacting ThinPrint support.

To generate configuration reports and to troubleshoot problems, please use the ThinPrint Diagnostic Utility.

For AutoConnect issues, please also use AutoConnect Diagnostics. Select the Detailed Diagnostics option for a selected entry, then you will get infor­mation about the operations carried out by AutoConnect or about possible faults.

AutoConnect Diagnostics

AutoConnect Diagnostics

AutoConnect Diagnostics: information about successfully created printers

AutoConnect Diagnostics: information about successfully created printers

AutoConnect Diagnostics: detailed error description

AutoConnect Diagnostics: detailed error description

  • With ThinPrint Engine installation, the following message appears in the ThinPrint License Server window: “License server could not be found. Please enter the address of your primary ThinPrint License Server. (The RPC server is unavailable. (Exception from HRESULT: 0x800706BA))”.
    • Use the FQDN instead of the hostname for specifying the license server address.
  • With ThinPrint Engine installation on Windows Server 2012, the following mes­sage appears: “The installation of Microsoft .NET Framework 4.6 (x64) has failed. Setup will now exit.”
    • Restart the server. Afterwards perform the installation again.
  • In the server settings of the ThinPrint Engine MMC component the following message appears in the ThinPrint License Server tab: “License server could not be found. Please enter a valid address.”
    • Use the FQDN instead of the hostname for specifying the license server address.
  • The Windows Event Viewer shows the message “No valid license found”.
    • On the license server, verify that the License Manager shows a valid license key. See Entering license keys.
    • In the ThinPrint Management Console, verify that the user who has printed is ThinPrint enabled. See Assigning a license to a user.
    • Verify that the ThinPrint Engine machine can connect to the License Server using the address and TCP port specified there.
    • On the license server, delete the local user group ThinPrint Excluded Users. See “Excluding users” under Access user configuration..
  • If a ThinPrint license is used as soon as a terminal services user logs on for the first time even if AutoConnect did not create or map printers for that user, per­form an update from ThinPrint version 11.0 to 11.0.1 or higher. Afterwards the ThinPrint Diagnostic Utility shows at least the following versions:
    ThinPrint Engine 11.1.536 (instead of 11.0.496)
    TPAutoConnect.exe 11.0.1278 (instead of 11.0.1266)
    TPSvc.dll 11.0.1345 (instead of 11.0.1306)
  • If you run Windows Server 2008 (x64) SP1: Did you install the Microsoft Hot­fixes KB958741 (Print Job Owner) and KB958656 (Client Side Rendering)?
  • If AutoConnect does not create or connect any printers after an update to Thin­Print version 11.0.2, and the following message appears in the Event Viewer:
    Event ID 1004 TaskCategory (4) TPAutoConnect Configura­tionFiles: 13 – The data is invalid. (% PATH-TO-DB \ TPACGlobal.db), 1
    the AutoConnect database is no longer consistent. To fix this, proceed as fol­lows:

    • Make sure that your mapping database is specified in the AutoConnect con­figuration (MMC) or alternatively in the AutoConnect group policy (GPO).
    • Open the Map Additional Printers table in the AutoConnect configuration. Insert a new line, and enter a dummy printer in the Target Printer/Group column, e. g.: \\localhost\dummy
      Confirm with OK and Publish.
    • Remove the new line and confirm with OK and Publish again.
  • 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?
    • To which type of ThinPrint Port is the specified printer template connected? Virtual Channel Protocol (ICA or RDP); must be enabled in the port con­figuration.
    • For AutoConnect, either Virtual Channel (ICA or RDP) or Auto must be set as connection protocol, and the respective column in the Dynamic Printer Matrix has to be set to enabled (here R for RDP).
    • Is TP AutoConnect Service running on each terminal server?
  • If TCP/IP is the selected protocol:
    • Are the TCP port numbers the same on server and client (see port configura­tion in MMC 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.
  • If a printer was created manually, check the naming convention of the ThinPrint Port (see port configuration in MMC, Illus. 78).
  • If you selected Use encryption on the server, read the section Encrypting of print data for further information and Troubleshooting in the instruction Creat­ing certificates for printing with ThinPrint for further information.
  • If the TP AutoConnect Service can’t be started: Check the access permissions on the folder/s in which the configuration databases are stored. See Storage destination for AutoConnect settings.
  • From the time when the option Printer Self Service is enabled, the printers of users who log on to a session for the first time aren’t created or mapped auto­matically anymore. The tables Map Additional Printers and Dynamic Printer Matrix then provide the input for printers to be selected.
  • If you have moved the Storage destination for AutoConnect settings from its default path (C:\ProgramData\ThinPrint\TPAutoConnect\TPACGlobal.db) to another location – e. g., to a network drive –, it may happen that changes to one of the tables Dynamic Printer Matrix or Map Additional Printers do not work. In this case, open one of the two tables, add a row and save the table. Afterwards you can withdraw this change immediately. The AutoConnect configuration is then automatically updated the next time a user logs on.
  • Changes of the default printer or of printer properties in a session are only available in a second session after logoff/logon or disconnect/reconnect. However, if you want them to be available immediately, change the AutoConnect registry value StoreUserSessionSettings from 7 to 15 (decimal) or F (hex).
  • Are the correct templates used when AutoConnect starts? For each template, there must be an appropriate printer name, printer class, or entry in the Dynamic Printer Matrix (see ThinPrint Client Manager and AutoConnect). Check that AutoConnect is working by starting it manually: Open the Command Prompt in a terminal session, change to the AutoConnect’s program directory – e. g. C:\Program Files\Common Files\Thin­Print – 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 ses­sion is started, check all AutoConnect settings in MMC.

  • 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 (a TCP/IP-type ThinPrint Client is necessary on the respective client machine). To do this, enter the fol­lowing 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 Advanced tab)

Example 1: telnet 192.168.131.224 4000
After executing this command, a telnet window should open without error message. If so, the connection is OK.

  • If you are using Driver Free Printing but, even though the printers are created in the terminal session with AutoConnect, printer options such as paper formats and sources are unavailable, check whether the following functions have been enabled:
    • Enable sending properties in the ThinPrint Client Manager
    • Inherit client printer settings in the AutoConnect configuration
  • MMC module High Availability Mapping:
    • If the Remap Printers function doesn’t recreate or remap the printers in the remote desktop sessions: Restart the TP AutoConnect Service and change its start type to Automatic (Delayed Start).
    • If AutoConnect doesn’t switch automatically to the secondary server if, in Failover mode, the primary server is set to the Maintenance status: Restart the TP AutoConnect Service and change its start type to Automatic (Delayed Start).
    • If a failover takes several minutes to remap or reconnect printers, perform an update from ThinPrint version 11.0 to 11.0.1 or higher. Afterwards the Thin­Print Diagnostic Utility shows at least the following versions:
      ThinPrint Engine 11.1.536 (instead of 11.0.496)
      TPAutoConnect.exe 11.0.1278 (instead of 11.0.1266)
      TPSvc.dll 11.0.1345 (instead of 11.0.1306)
  • 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. Check in this example:
    • Whether the required Registry value SISActive (reg_dword) is present and set to 1 (0=inactive, 1=active). Path: hkey_local_machine\soft­ware\ThinPrint\TPClnRdp (or \TPClnIca)
    • Whether the ThinPrint component TPClnICA.dll is present in the ICA Client’s (also: Citrix XenApp Plugin for Hosted Apps) directory – e. g.: C:\Program Files (x86)\Citrix\ICA Client. If not, copy it from the ThinPrint program directory – e. g.: C:\Program Files\ThinPrint Engine – to this directory.
      Please also note the section Citrix ICA Client later installed.
  • From Windows 2012 R2 type-4 drivers can’t be connected to third-party printer ports. That’s why use type-3 drivers with ThinPrint Ports.
Example for a type-3 driver, in this example: Lexmark T644 (MS)

Example for a type-3 driver, in this example: Lexmark T644 (MS)

Previous Page
Next Page

Was this helpful?