choosela.blogg.se

Windows terminal server thinclients
Windows terminal server thinclients













Remote desktops – Printing via ICA, RDP or PCoIP This improves performance during printing, since available band­width can be utilized better.įurthermore, 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. The print jobs are then sent directly to the client computer or network printer, circumventing the remote desktop session (separation of the data streams). With ThinPrint, though, they are able to print via TCP/IP in either case. Workstations and terminals (thin clients) communicate with the remote desktops (terminal servers or VDI) via the Citrix protocol ICA, via the Microsoft protocol RDP (with Citrix XenApp/Xen Desktop or Microsoft Terminal Services/Remote Desktop Session Hosts) or via the VMware VDI protocol PCoIP. The depicted scenarios can also be combined – flexibility in mixed environments is one of the strengths of ThinPrint. The following example scenarios illustrate typical environments in which ThinPrint can be deployed.

  • 2 Remote desktops – Printing via ICA, RDP or PCoIP.
  • 1 Remote desktops – Printing via TCP/IP.
  • Configuring ThinPrint Engine for Desktop.
  • Installing ThinPrint Engine for Desktop.
  • Storage destination for AutoConnect settings.
  • Encrypting of print data from remote desktops.
  • PostScript version of ThinPrint Output Gateway.
  • ThinPrint Output Gateway on remote desktops.
  • Installing ThinPrint Engine on remote desktops.
  • windows terminal server thinclients

  • AutoConnect configuration using the MMC.
  • windows terminal server thinclients

  • ThinPrint Output Gateway on print servers.
  • LPR/LPD printing with Linux, Mac or Windows CE clients.














  • Windows terminal server thinclients