For the installation procedure see ThinPrint Engine: Quick installation on print servers.
- Open the ThinPrint Configuration console.
The ThinPrint Engine console appears.
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.
- Select Edit Settings.
- 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.
Note! The ThinPrint Engine configuration using group policies is described in ThinPrint group policies.
ThinPrint Hub cloud management
For central management of ThinPrint Hubs, ezeep Hubs, or Personal Printing Release Stations in the cloud, proceed according to the ThinPrint Hub documentation.
For global AutoConnect settings see the section AutoConnect configuration using the MMC.
The AutoConnect configuration using group policies is described in ThinPrint group policies.
Please also note the section Storage destination for AutoConnect settings.
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.
Workstations and virtual desktops
In the event that printer shares are connected to computers in remote offices, the print data can be compressed in the opposite direction in addition to the normal ThinPrint compression – between the computers in the remote offices (where the applications are running) and the central print server. This print data compression of the shares is called ThinShare; it is available in the Driver Free Printing and V-Layer print modes.
- Here you can choose whether ThinShare should be enabled by default for all new printer objects to be created that use the Output Gateway as driver.
Confirm with Apply.
Enabling ThinShare requires the Render print jobs on client computers option for the relevant Output Gateway printer objects (this means ‒ in case of native printer drivers ‒ that print jobs are rendered on the remote desktop instead of the print server; on the other hand, this rendering feature is used for ThinShare compression when using the TP Output Gateway).
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:
gpupdate /forceon the terminal server’s Command Prompt to assign the group policy to the server.
- ThinPrint License Server
- ThinPrint components on ThinPrint Servers (central print servers)
- ThinPrint components on terminal servers, virtual desktops and workstations
Update from ThinPrint version 11.x or 12.x to 13
- On servers with ThinPrint version 11.x or 12.x, simply run the version 13 installer on the respective servers – license server and ThinPrint Engine.
Update from ThinPrint version 10.x to 11
- On servers with ThinPrint version 10.0.2 (= 10.0 + hotfix HF2), 10.6.1 or 10.6 FR1, simply run the version 11 installer on the respective servers – license server and ThinPrint Engine.
- For updating the ThinPrint group policy objects see the section Update from GPO v10 to GPO v11.0.
After sharing printers the printer driver TP Output Gateway can be delivered automatically using Point and Print to terminal servers, virtual desktops and workstations. But with the printer driver update maybe the print processor isn’t updated automatically by Windows if an older version already exists. In this case it’s possible to print but ThinShare doesn’t work – in other words: The print data won’t be compressed on the way to the central print server.
To make sure to update ThinPrint’s print processor (tpwinprn) there are two alternatives:
- Either you update the printer driver directly on the target machine using its driver package. This can be found on the central print server in the directory
C:\Program Files\Common Files\ThinPrint\Virtual Printer\TPOG3
- Or you enable the group policy Point and Print Restrictions in the domain for all target machines including the option Do not show warning or evaluation prompt.
To uninstall a ThinPrint component open Programs and Features in Control Panel. Mark the ThinPrint Engine and then select Uninstall.