Symptom
Printing through Remote Desktop Connection ( RDC ) is so much slower using the Redirected printer drivers also know as Microsoft's Easy Print.
Environment
Crystal Reports for Visual Studio
Remote Desktop Connection
Reproducing the Issue
Deploy a simple CR .NET Desktop Windows Form application to a PC that can be remoted into using Windows Remote Connection (RDC).
When connecting check on the option to share your local Printers, redirects the output from the App server to your local printer.
After the RDC connection is made if you look in the Installed Devices and Printers you will see the local host PC Printers listed with a ( Redirect x ) in the name.
This is using Windows Easy Print process, does not require the printer to be installed on the Application Server that you are remoting into.
When printing you will notice a huge delay in processing the report and printing.
NOTE: Using a simple .NET Printing app using no CR runtime and simply printing a text file you will also see the delay in printing.
Resolution
This issue has been escalated to Microsoft and they expect a patch release by the end of the year ( 2014 ).
As a workaround if you install the printer drivers onto the PC hosting the Application there is no delay.
See attached Sample app that removes CR from the test and simply prints a Text file using the Framework.
Keywords
crforvs, easy print, easyprint, redirected, redirected x, remote desktop connection, rdc , KBA , BI-RA-CR-SDK , SDK related, including Java/.NET etc. , Problem
Product
Attachments
DotNETPrintRDC.zip |