ThinPrint-Engine versions for Windows desktops
With respect to the ThinPrint Engine for Windows virtual or physical workstations, ThinPrint version 12 has changed the following:
|ThinPrint 11||ThinPrint 12|
|denomination||ThinPrint Engine for Desktop||Desktop Engine|
|installer||separate installer for ThinPrint Engine for Desktop||same installer as for terminal servers (alias remote desktop sessions hosts) – here, however the Desktop Engine role (instead of Remote Desktop), see screenshot|
|documentation||see Technical requirements of ThinPrint Engine for Desktop||see Technical remote desktop requirements|
The following example scenarios illustrate typical environments in which the ThinPrint Engine for Desktop can be deployed. The depicted scenarios can also be combined.
Virtual Windows 10 desktops – Printing via TCP/IP
PCs and terminals (thin clients) communicate with the virtual desktops via the Citrix protocol ICA, the Microsoft protocol RDP or the VMware protocol PCoIP/Blast. 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 virtual desktop session (separation of the data streams). This improves performance during printing, since available bandwidth can be utilized better.
Furthermore, each user can use all printers in the network which are accessible via TCP/IP – regardless of whether he is using a workstation (rich client), a thin client, or any other type of client.
Virtual Windows 10 desktops – Printing via ICA, RDP or PCoIP
The Citrix protocol ICA, the Microsoft protocol RDP as well as the VMware protocol PCoIP/Blast enable print jobs to be sent to a user of a terminal session through the virtual channels of terminal server communication (ICA, RDP or PCoIP/Blast). This ThinPrint print mode is also possible to clients in masked networks (Illus. 322).