Installation and configuration
on print servers

1483 views 0

For the installation procedure see ThinPrint Engine: Quick installation on print servers.

  • Open the ThinPrint Configuration console.
Start configuration

starting the configuration

The ThinPrint Engine console appears.

ThinPrint Engine console

ThinPrint Engine console

Here, you will find all events generated by ThinPrint components. Additionally you can display and filter print spooler events as well as manage the ThinPrint services and the print spooler.

Note! Saved server settings will only be effective after a spooler restart. With Windows Server 2008 R2 or later, spooler events cannot be shown here at present.

  • Scroll down and select Edit Settings.
ThinPrint configuration: Select Edit Settings

ThinPrint configuration: Select Edit Settings

License Server

  • In the ThinPrint License Server tab you can:
    • change the license server address (hostname, FQDN or IP address) and the TCP port (restart the TP License and User Configuration Service afterwards)
    • open the license server’s configuration website by clicking its link
    • change the address of the configuration website by clicking Edit.
License Server settings

License Server settings

Note! The ThinPrint Engine configuration using group policies is described in ThinPrint group policies.

AutoConnect

For global AutoConnect settings see the section AutoConnect configuration using the MMC.

The AutoConnect configuration using group policies is described in ThinPrint group policies.

Note! Please also note the section Storage destination for AutoConnect set­tings.

Print spooler events

  • In the Print Spooler Events tab, you can select which print spooler events from the Windows event viewer are to be displayed. This menu differs depending on the Windows version.
    Windows Server 2008 R2, 2012 and 2016 show Log admin events and Log operational events.
    In contrast, Windows Server 2008 and 2012 R2 show the settings Log print spooler errors, Log print spooler warnings and Log print spooler information.
Which print spooler events are to be displayed?

Which print spooler events are to be displayed? (here: Windows Server 2016)

ThinShare

Workstations and virtual desktops

  • In the ThinShare tab, you can globally:
    • enable or disable ThinShare for Output Gateway printer objects which will be created in the future (left arrow in following Illus.)
    • enable or disable ThinShare for all (already) existing Output Gateway printer objects (right arrow in following Illus.)
  • Alternatively, you can enable or disable ThinShare:
    • for specific printer objects in the Output Gateway user interface or
    • for groups of printer objects using Management Center/Services templates

Enabling ThinShare sets the sharing option Render print jobs on client computers at the relevant Output Gateway printer objects (This means – in the case of native printer drivers – that print jobs would be rendered on the ter­minal server instead of the print server; in contrast, with the use of TP Output Gateway this “ren­dering” function is used for ThinShare compression).

Enabling ThinShare globally

enabling ThinShare globally

ThinShare as a Windows sharing option

ThinShare as a Windows sharing option

Terminal servers

Enabling ThinShare for terminal servers is completely different from doing so for workstations and virtual desktops, because the option Render print jobs on client computers is by default disabled on terminal servers – independent of its setting. That’s why the group policy Always render print jobs on the server is used here instead. It can be found in the Group Policy Management Editor in: Computer Configuration→ Policies→ Administrative Templates→ Printers.

  • The group policy can be set as follows:
Setting ThinShare
Disabled on
Enabled off
Not configured off
  • Run gpupdate /force on the terminal server’s Command Prompt to assign the group policy to the server.
Group policy – Always render print jobs on the server

group policy Always render print jobs on the server

Previous Page
Next Page

Was this helpful?