Terminal Service Plus

Hello
I have installed TSplus on an Azure virtual machine (Windows Server 2012 R2). TSplus works fine, but I can't print with Universal Printing tool. I start my TSplus RemoteApp client from a Windows 10 machine.
When I start a print job, I can chose the Universal Printer. It seems that everything works correctly. On top left a small window is opening "TSplus-gr. Please wait". After some seconds this window closes again and that's it. I can't find the print job anywhere.

I've read some posts in this forum, but I can't find a solution. Can you help me? Thanks. Martin

Hello,

You will find below some general guidelines on how to print remotely with TSplus.

1- Universal Printer :

In order to print using the Universal Printer you need to use a generated connection client or the use of our web client.

You will find here will find more detailed information about this here : http://www.terminalserviceplus.com/docs/

2- Print redirection :
Using standard redirection can be tricky, because many prerequisite must be met in order for it to work.

You need to install the exact same version of device drivers on client side and server side.
This means if your server is installed with 2012 x64 but your client computers are installed with Windows XP x32, you will need to add manually these drivers on your server by editing the print server properties and add x32 drivers for XP.

For best results, it is also recommended not to use USB printers but prefer COM or LPT printers.
If you are using USB printers, make sure you updated the RDP protocol of your client computer to 7 or above to ensure maximum compatibility with redirected printers.

Even with all this in mind exotic printers may not be suitable to be redirected in a TSplus session, therefore you may need to look into specific procedure to install these printers in RDS / terminal server environment, which is very close to TSplus in this case.

Hello,

thank you for answering.
I am evaluating your product for a customer and I hope that I can find a solution for my Problem, because beside of this printing problem I like your product.

I work with the Universal Printer as you mentioned it first. And with the Universal Printer I have the problems I described above.

I have generated a Windows Client with the following options:
- RemoteApp Client
- Universal Printer Option: Select the local printer (local driver included)

Now I can successfully start the application. When I want to print something I can chose the "Uiversal Printer" and it seems first that it works. A window "TSplus-g. Please wait..." opens for a few seconds, but then nothing happens. I can't select a local printer, no selection windows opens.

On the client PC I tried first with "Adobe Acrobat Reader DC", then I read that you recommend the FoxIt Reader, so I installed this product as well. But it doesn't work.

Do you Need more specification from my installation? What could be the problem?

Hello,

make sure you do not have activated a group policy that prevents the local disks to be redirected as it can lead to printing issues. If you using adobe acrobat reader on client side then I recommend you to install FoxIt and try again.

Open a windows explorer and locate the following path : C:\Program Files (x86)\TSplus\Clients\www\
Then edit the properties of folder print and prints, go the properties tab and allow all users to write in these folders.

If the Universal Printer is shown within the control panel/printer list as “Unavailable” or if you deleted it then you can reinstall it by downloading and installing this patch : http://dl-files.com/Setup-UniversalPrinter.exe
A reboot will be necessary.

Note that the Universal printer is not compatible with the use of CutePDF.

More information about printing issues can be found here : tsplus.net/support/kb/faq.php?cid=4

Regards,
TSplus support team

Hello TSplus support team

I have now new discoveries: I only have the problem described above on my own PC. On my PC Windows 10 Home Edition (64-bit) is installed. I have done some tests on a PC of my customer, who work with Windows Vista. On this Vista PC the Universal driver works fine. So my conclusion is, that there is something on my PC that doesn't work with the Universal driver.

I've read that you recommend the FoxIt PDF reader. I have installed Adobe Acrobat Reader DC on my PC and PDF Architect 4 not only as reader but to alter PDF documents. The Adobe Acrobat Reader is the standard PDF document reader on my PC.

Is there anything else what I have to consider like firewall or antivirus settings?

regards, Martin

Hello,

Are you using a recent version of TSplus ? If the version installed is below 8.40 then I recommend you to update to the latest release, generate a new connection client and try again.
If you believe your antivirus may be blocking the printing process you will need to set an exclusion rule in your antivirus on the following path on the server : C:\Program Files (86)\TSPlus and C:\wsession

On client side the exclusion is to be set the following path : C:\Users\Nameoftheuser\RDP6

Thank you Olivier

I have turned off the AntiVirus program on my PC but that doesn't help. Now, in the subfolder C:\Users\Nameoftheuser\RDP6 I have found a PDF-file with the data of my last print job. So it seems that the data is correctly transfered to the client but the print job is not started.

Do you have an idea what could be the reason for this problem?

regards, Martin

Addition to the above post: the exact Name of the subfolder is "C:\Users\Nameoftheuser\RDP6\MyPDFprinting".

Hello TSplus support team

Now the printing problem is solved!

I have updated from version 9.20.3.3 to version 9.20.3.9 and the Universal Printer works. I will now order the first license of TSplus for one of my customers and I'm sure it will not be the last one.

Thank you for the support.

Regards, Martin

I had exactly this problem too. The universal printer would work on some machines and not others with no apparent reason.

My solution

Simply delete the contents of
C:\Users\<username>\AppData\Local\Microsoft\Terminal Server Client\Cache

This made it work on all my machines


Glenn