We have been using it in a server 2003 TS environment for approximately 1 month. For the most part it works fine with only some occaswional weirdness with older HP Laserjet 1010 and 1012 model printers. Printers that we use are HP1010,HP1018,HP1020, HP1102w,HP2015DN,HP2055DN,Konica Minolta 323, Konica Miinolta, 751, Konica Minolta Color Fiery I have not regretted the purchase. MDT Thank you for a reply. I was getting scared i was the only person using this product. So far TSPrint has worked for us as well. We have a large array of printers. So far TSPrint has solved those issues. With such a low price compared to the competitors i was worried that it had some issues. We are using TS Print in a Windows server 2003 r2 terminal server environment. It is the greatest piece of kit that has solved a huge amount of printer issues. However, an issue has crept in lately. Anyone come accross this before - and , is there a simple solution? PS: I still think it is the best!! We have been using TSPrint for several years, first in Windows Server 2003 and now in a Windows 2008 R2 environment. It works very well. There have been very few issues and when one has occurred their support group has been very good. Some of our clients use Macs and this has caused TSPrint some pains in that nobody wants to pay for the client side driver and there seems to an expectation that it should work with any RDP client. They have finally solved the problem by providing a 'Printer' that works with any RDP client and there is no charge for this driver. Another example of their good service - the Server license is issued for a specific computer however if you change server computers you just need to send them an email with the required information and they will send you a new license at no charge, usually the same day. In answer to the above post my paper size defaults to Letter. For Paper Source I have Automatically Select set. Try looking at their Help files on-line or send them a Support Question. Do they make mistakes in their updates - Yes. Yesterday we sent them an email regarding a problem we were having with their latest update. Within an hour they asked to look at my client machine, via TeamViewer, and looked at what was happening, determined their was an error in their update, 'downgraded' our Server to the previous update, checked it again. It all took place in about an hour and other than ask a few permissions that I had to give them, it was all fixed - no charge. As you can tell I am very pleased with their service and their product. We are using TSPrint with Server 2008. While it solved the problem where we could not get certain printers to redirect, it has another issue we are unable to get resolved. All users print fine for a while and then several users will start getting errors stating 'TSPrint has stopped working' with these details: Description: Stopped working Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: pdfwriter. Win32 OS Version: 6. The only way we can resolve it is to restart the print spooler on the server. We currently have the spooler set to restart every three hours and we are still manually restarting it in between. There are no print spooler entries found in the event viewer. Does anyone have any suggestions on how we might get this resolved? Users are very frustrated with not being able to print and losing print jobs when the spooler is rebooted. Main Question would be what changed? Is there any correlation to a certain program being installed on the servers? Typically if its the print spooler i would think it's the print driver. In this case TSPrint. Have you uninstalled and reinstalled? I ended up going back to straight up Windows Easy Print. We did the math and it was cheaper to replace desktop printers in the organization that didn't work with Easy Print vs pay for TSPrint with the number of Servers we have. I found a 100 Brother Printer that plays nice with Easy Print and haven't looked back since. Dim oFSO , oNetwork , sLocalDrive , sRemoteShare , sMappedDrive , oShell 'Super-duper script objects to the rescue!! Quit End If 'Kill drive-R if it exists. MapNetworkDrive sLocalDrive , sRemoteShare , False 'Copy file to C-drive oFSO. RemoveNetworkDrive sMappedDrive , True , True 'Install TSPrint. In and out like a ninja. I keep getting an error when GPO tries to install the application.. Failed to apply changes to software installation settings. Software changes could not be applied. A previous log entry with details should exist. The error was : The system cannot find the file specified. Windows failed to apply the Software Installation settings. Software Installation settings might have its own log file. Failed to apply changes to software installation settings. The installation of software deployed through Group Policy for this user has been delayed until the next logon because the changes must be applied before the user logon. The error was : The group policy framework should call the extension in the synchronous foreground policy refresh. I tried rebooting, forcing a gpupdate, recreating the GPO, deleting GPO in the client.. I'm assuming that these users all have dedicated computers, otherwise everyone on that computer would have access to the software anyhow, so it wouldn't matter. If you have to be selective, create a new security group, add the computers for those people to that group, create a new GPO, and use security filtering so the GPO only applies to that group. Also, TerminalWorks doesn't have restrictions on the number of client installations. They only license the server component, so there's no restriction on you installing the client on every computer in your domain. That's what I do. Understood, but to your last statement, the TSPrint Client won't engage unless the server component is installed and initiates a job. You have to have both pieces running... The client just sleeps in the background waiting for the server component to wake it up. I actually have several servers running PDFCreator and other tools, but not TSPrint. Having the client installed on the desktop doesn't cause any problems with them.
