Please follow the video instructions on how to install TSPrint.

(Minimum Version: 1.8.6.0) TSPrint is mostly used with two types of TSPrint printer: TSPrint Default and TSPrint Printer. The TSPrint Default printer will print everything to the local default printer without any dialogs. The TSPrint Printer in return will show each time a dialog where you can select the desired printer and its settings.

Now sometimes you would like to create a new printer and tell TSPrint to automatically transfer the printjob to another local printer besides the default printer.
This can be done with the new type of TSPrint printer named TSPrint User Defined. By default the TSPrint installation does not create such a printer.

To map a local printer to a TSPrint printer log-in to your terminal server and go to:
Start -> Programs -> TerminalWorks -> TSPrint Server -> Print Manager

This is the Printer Manager of TSPrint which enables you to create new TSPrint printers and assing them to different users or groups.

The new printer dialog enables to define the name and functionality of the tsprint printer.

Here you select the desired local printer to which the server printer should be mapped to.

No. TSPrint is a plug and play solution. After the simple installation procedure (next,next,next)TSPrint will be ready to go. Compared to the standard way of supporting local printers our way needs just a fraction of the time required to enable clients to use their local printers.

There is no need to install any printer drivers on your server. You will be able to use TSPrint to print from your remote desktop on any printer that you have installed on your local computer. All types of printers are supported as long as you are able to print on them on your local computer. So you don't compromise the stability of the server by installing dozens of different printer drivers for each client workstation.

The TSPrint Default printer always prints on your default local printer. In case you wish to print on another printer please select the TSPrint Printer which will show you a print dialog where you can select the desired printer.

Please visit this link: Communication Error

TSPrint uses the Microsoft Virtual Channels technology, so all traffic goes through the secured RDP connection. No need to forward or open any ports for TSPrint to work. It is really a plug and play solution.

Yes, you can use TSPrint on Windows client operating systems, acting as remote desktop servers.

Yes. You can use TSPrint both on a internet connection and your local area network. Now clients that work outside the office will be able to print out documents to their home printer without you having to first install that printer on your Terminal Services server.

Please let the client login to the terminal server and then go to:
Start -> Programs -> TerminalWorks -> TSPrint Server -> Client Options/Options

A dialog should show up where you should change the Print Engine from Default to TSPrint Engine.
This should resolve this issue.

Important! Since version 1.9.0.0 of TSPrint you also have to select the Fit To Page option on the client dialog.

There are two ways you can disable this option. The first one would be to disable it globally on the terminal server by setting the right group policy. For more details about the please visit:

Printer Redirection

The second step would be to disable this locally on the workstation from which you connect. To do this please execute MSTSC.exe by going:
Start -> Run -> mstsc.exe

When the mstsc.exe dialog shows up click on the Options button on the bottom left side:

TSPrint offers two different dialogs to configure the default printer. The first one is working on a per user basis and each individual user can set his own default printer by logging in to the terminal server and going to:

Start -> Programs -> TerminalWorks -> TSPrint Server -> Default Printer

No. The product installation doesn't require any reboots before you can use it.

Sometimes, very special printers, which can also include special page sizes are hard to map with our virtual TSPrint printers. Results can be such as a blank page, bad positioning etc. Resolve is to create a Windows driver printer on the server side which will map local settings perfectly with our Windows driver printer.

To create a Windows driver printer, please follow the steps describe in this document.

Log in to your terminal server and open:
Start -> Programs -> TerminalWorks -> TSPrint Server -> Print Manager

TSPrint license
Please try the following steps:
1) Connect to your Server side.
2) Go Start->All Programs->Terminal Works->TSPrint Server->License registration
3) Don't open the .license file! Just download it and remember the location
4) In the License registration select the "Load License File" button and select the license file from the downloaded location

TSPrint Client Options

Take a look at this short video tutorial on how to install the TSPrint Client for MacOS.

No, there is no need for that as all versions of TSPrint are compatible with each other. The only drawback is that you will be missing the features from the current TSPrint client releases.

Changing the Print Engine

Connect to the terminal server through a remote session and open:

Open: Start -> All Programs -> TerminalWorks -> TSPrint Server -> Client Options

The following window will be shown on your screen:

Dear Reader, we would like to explain you how to Tunnel TSPrint through multiple RDP sessions.
We would like to show you an example to demonstrate its functionality:

This only happens in case you have installed Adobe Reader 10 but have not rebooted your server as requested by the Adobe installer.

Adobe Reader will then crash once you go to File -> Print. Once you reboot your server as required Adobe Reader X will work just fine with TSPrint.

This issue is only present in Adobe Reader 10.

If this does not resolve your issue then another bug could be causing this. To resolve it disable Enable Protected Mode at startup.

You can disable this by opening Adobe Reader and going to Edit -> Preferences. Now a new dialog shows up where on the left side you should make sure that General is selected. Once selected on the bottom of the dialog you should find the Enable Protected Mode at startup.

Yes, you can use some of the TSPrint binaries to execute actions usually done through TSPrint. For example you can just execute the following command line command:
C:\PROGRAM_FILES\TerminalWorks\TSPrint Server\pdfwriter.exe open "YOUR_FILE"

This would then invoke the same procedure which you is done when you right click on a file and select TSPrint Open Locally.

Besides the open option you can also use:
-send - To send the file to the local workstation. (A file save dialog will appear)
-mail - To send the file as a new e-mail with the file attached to the e-mail.

Yes, TSPrint has full support for your Citrix based environment. Just install it as you would on a normal terminal server (RDP) environment and you will be able to use TSPrint.

Random printing order

If your documents are not printing in the order they were sent to the printer, please open the printer properties of the TSPrint printer you are sending the print job to (TSPrint Printer, TSPrint Default or TSPrint PDF).

Under the 'Advanced' tab, check the box next to 'Print spooled documents first'.

The full path of this mode in the Group Policy Management Console on Server 2003/2003R2:
"Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection"

and Server 2008/2008R2/2012/2012R2/2016:
"Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Printer Redirection"

This policy setting allows you to specify whether the client default printer is automatically set as the default printer in a Terminal Services session.By default, Terminal Services automatically designates the client default printer as the default printer in a Terminal Services session. You can use this policy setting to override this behavior.

The policy has 3 options.
Enabled->The default printer is the printer specified on the remote computer.
Disabled->The terminal server automatically maps the client default printer and sets it as the default printer upon connection.
Not Configured->The default printer is not specified at the Group Policy level. However, an administrator can configure the default printer for client sessions by using the Terminal Services Configuration tool.

To enable logging, follow below steps:
1) Log in to your terminal server and open:
Start -> Programs -> TerminalWorks -> TSPrint Server -> Server Options.
2) Check "Enable Logging" checkbox.

Note that:
1) Log files will be created in %APPDATA%\TSPrint\logs folder. This means that every user will have separate log files.
2) Logging can be configured in LoggerSetting.ini located in %APPDATA%\TSPrint folder.

The Default page size depends on the Windows Region which is set during the Windows Installation.
When installing a new printer driver or adding a new printing device to your PC if the default
page size can be altered between letter and A4 it will depend on the region set on your PC.
The image below shows the default page size setting per region.

Dear Reader,

DOS recognizes physical ports instead of printers, and since TSPrint installs virtual ports which cannot be recognized, by default TSPrint is not compatible with DOS applications.
Our solution is to map a physical port to a TSPrint printer.
There are two ways:

1) Run following commands in Command Prompt on the Server side for each user:

rundll32 printui.dll,PrintUIEntry /Xs /n "TSPrint Printer" Sharename "TSPrintPrinter"
rundll32 printui.dll,PrintUIEntry /q /Xs /n "TSPrintPrinter" Attributes Shared
net use lpt2 \\localhost\TSPrintPrinter -p

Listed commands make TSPrint Printer to act as a shared printer and then maps it to the LPT2 port. Furthermore, you can switch TSPrint Printer with any TSPrint Printer and switch LPT2 port with any free LPT port.

2) We created a simple .bat file, which must be applied on Server for each user.

Download link: http://www.terminalworks.com/downloads/tsprint/DOS.rar

Our batch file makes TSPrint Printer to act as ashared printer and then maps it to the LPT2 port. User will be able to use TSPrint Printer in DOS applications.

Ericom Blaze RDP

In order for Ericom Blaze RDP to be working with TSPrint or TSScan, you have to do the following:

Start Ericom Blaze RDP client and open the 'Local Resources' tab. Press the '3rd party addins' button.

When printing multiple documents and the print order is invalid on your printer you have to set the Print spooled documents first option on the TSPrint printer where you experience this issue.

This option can be accessed by right clicking on the TSPrint printer on your terminal server and selecting Printer Properties. After that click on the Advanced tab and check the option.

Yes, TSPrint has full support for your PCoIP based environment. Just install it as you would on a normal terminal server (RDP) environment and you will be able to use TSPrint. Note that this is supported on Windows 7/Windows 2008 version and higher.

When you downloaded 'tsprint.tar.gz' from our site, you will need to extract it in the terminal with 'tar xvzf tsprint.tar.gz'.
That will create a sub-directory named 'tsprint'. Go to that directory with e.g. 'cd tsprint'.
In that directory, run our rdesktop with './rdesktop -u -p ' - substitute the parameters with your own.
Note: In case you get an error stating that libcrypto is not the right version please download this package:
http://terminalworks.com/downloads/tsprint/linux/libcrypto.so.0.9.zip and place it in "home/usr/lib"

Firstly we need to find out the version build of the client you use to connect to the server, to do so connect from the MAC to the server using administrator credentials. Then open Server Options of TSPrint and enable logging for Print.