>>> If all the users have different types of printers you can end up in a no-win situation real quick. There are ways to map the printer via RDP (at least in the windows client) so that you can print locally - but this has HUGE problems. First you have to find a way to setup everything just right so the customers can't see each other's printers -- aaand you have to install those print-drivers on the server as well. Now that itself can cause a major problem because some of these drivers conflict with each other - and what ends up happening is the reports don't print right for some of the clients - 99% chance that will happen too. There are some 3rd party tools I've seen that supposedly deal with this problem - but they don't work very well and in some cases not at all, and cost $3,000 to $15,000 per server. The other option is on the server side to print to a PDF, then push the PDF file up to the cloud, then make them download it from the cloud on their local machine if they want to print it - a big clumsy hassle for the user (they will hate you) It's sort of a catch-22 situation really. Either you save them license fees and server costs and printing problems and just put the .exe on the workstations and force them to use windows machines and go though the hassle of setting up ODBC connections on all the workstations and end up playing tech support for all those workstations - or deal with the extra costs and the printing problems and put it on a server and let them remote into it. Either way they loose. At the end of the day, if it's a legacy app - don't touch it - fix bugs or whatever to keep it alive - but don't go wasting time putting it on a server unless they don't plan to print from it (maybe toss a copy of it on a server for the occasional user to have access remotely with an RDP client, but goodbye printing).
>
>I agree the misnamed Easy Print or session printing can be a PITA, but newer clients also allow local printers to be redirected/added as local RDS resources. Works fine IME, though the same mechanism can be used to make a local folder into a RDS resource so an employee can copy across 23,000 records unless clients lock it down- along with the printer if the user is accessing PHI.

That is good to hear - I guess it works better with RDS than if you're running your own windows server.