Wednesday, February 06, 2013 9:08 PM
Our customers connect via RDP to Windows 2008 R2 servers (Amazon EC2) and use ThinPrint to redirect their local printers so they can print ther various documents. This solution has been working well for us for quite some time as it frees us from having to maintain untold scores of printers drivers on the servers that we would have to have if we used Windows printer redirection.
Some users also use this method to fax from our hosted application, simply selecting their local fax driver instead of their printer, and in most cases it is the default Windows fax client that is used.
This has worked well for our XP clients, Vista (so far as we know, not many of them), and Win7... except for Win7 64 bit, and only then if the document is more than one page (in other words, W7/64, 2+ pages doesn't work).
Faxing a local document with this method works well, a good-looking Group4 fax TIF file is produced and there are no worries, but when we try it from the cloud via ThinPrint the TIF file that results is corrupt or otherwise unreadable. When I use Irfanview to open it ( a program I have used for years to read multipage TIF files) it throws a decode error and says that it is an invalid or unsupported TIF format.
Thinking this might be a ThinPrint problem I tried several other fax methods and the two that I tried will work properly- Ring Central Internet Fax and GFI version 14.3
I have provided workarounds for the affected users (basically print to PDF and then fax that) but I am hoping that someone can help me to make the experience for Win7 64 users the same as the XP/Vista/Win7 32 folk
- Changed Type Spencer XiMicrosoft Contingent Staff, Moderator Friday, February 08, 2013 5:38 AM