What’s new in Windows 7? Easy Print Redirection was available for Windows Server 2008 TS only and it was not available when connecting to computers running Windows Vista. Now it will also be available when connecting to Ultimate/Enterprise editions of Windows 7 and Windows Server 2008 R2 Remote Desktop Session Host servers. In addition, we’re happy to announce that with Win7 / WS08 R2, Easy Print no longer has a dependency on .NET Framework -- a common request from customers that didn’t want to install .NET on all clients from which they wanted to print. The XPS format to GDI conversion was done via .NET Framework before, but for Win7 / WS08 R2 the operating system does this conversion itself.
For the full documentation about how Easy Print works, refer to this three-part blog : http://blogs.msdn.com/rds/archive/2007/04/26/introducing-terminal-services-easy-print-part-1.aspx http://blogs.msdn.com/rds/archive/2007/05/03/introducing-terminal-services-easy-print-part-2.aspx http://blogs.msdn.com/rds/archive/2007/10/05/introducing-terminal-services-easy-print-part-3.aspx Remote Desktop Easy Print configuration properties: The following table displays the Client/Server combinations that support Easy Print.
Client / Server -> | v
Windows Server 2008
Windows Server 2008 R2
Client : (1), (2)
Client : (1), (2) Server : (3)
Client : (1), (2) Server : (4)
Server : (3)
Server : (4)
Client : (2)
Client : (2) Server : (3)
Client : (2) Server : (4)
(1) RDC 6.1 or above (Windows XP with Service Pack 3 and above includes this).
(2) Even if RDC 6.1 or above is used, the user must install a supported version of .NET Framework separately. Microsoft .NET Framework 3.5 (which includes .NET Framework 3.0 SP1) can be downloaded from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=109422 ). *In Windows Vista SP2 with RDC 7.0 and KB971644 installed, .NET Framework is not required
(3) Terminal Services role. (4) Remote Desktop Session Host Role.
If all the requirements are met, the Easy Print driver is listed in the Model field of the redirected printer’s Properties dialog.
Printer security information for the printer could not be set.
The printer could not be set as the default printer.
The default client printer and the default printer in the RDP session must be the same.
The driver required for the printer is unknown. Contact the administrator to install the driver before you log in again.
If the Easy Print driver is missing in the host, this event will be logged.
The printer cannot be redirected by using Remote Desktop Easy Print. The client computer may not have a version of the Remote Desktop Connection client or Microsoft .NET Framework installed that supports this driver.
Make sure you’ve met all the requirements in the table above.
An internal communication error occurred. Redirected printing will no longer function for a single user session. Check the status of the Remote Desktop Device Redirector in the System folder of Device Manager.
The number of printers per session limit was reached.
At first of my remote desktop printing and scanning service was not work properly. After using TSPrint for printer and Tsscan for scanning no problem arise so far. It's a universal driver system. you no need install driver. Please visit..
I alsouse this one terminalworks.com/remote-desktop-printing, must say it works great.
@ Nick Velev
I am having the same issue you did printing to an impact printer with the Epson FX- series. Locally it prints fine. Through Terminal Server the quality is awful. The server is Windows 2008. The client is Windows 7. If the client is Windows XP it prints fine. Did you find a solution?
Need some advise on Terminal Server printing issue. We hope to offline all print jobs from our Terminal Server to a print server, plus avoiding having too many printer driver installed on the Terminal Server which is known to cause hang ups. However, even thru the Windows print server, it will still deploy the printer drivers into our Terminal Server.
I understand that TS Easy Print can do this but it is assuming that the end users are connecting to the Terminal Server using Windows client with TS client 6.1 and .NET Framework 3.0 SP1 installed. But since our end users are using Linux-base thin client, can TS easy print be redirect to our Windows Print Server instead?
We also hope to simplify print job by showing ONLY 1 or at most 2 default printer(s) to the end users instead of all the available printers that often lead to our users printing to another branch office! Currently, we are creating AD groups and set each printer permission to these groups accordingly and remove everyone permission to hide the rest of the offsite printers. Is there a better to do this?
I am experiencing a 15-20 sec lag when using Easy Print. My client is WIN 7 Ent. My server is WS08R2. It happens on two different models/brands of receipt printers. I am stumped. Can anyone offer some advice?
I am just trying to change the settings on the advanced tab for remote desktop easy print. It is taking forever for users. I want to change setting to "Start printing after last page is spooled." Does anybody have any ideas?
Experiencing similar lag issues with receipt printers. Would like to be able to change settings in the advanced tab but cannot figure out how to. Client is using Win7 and we are using Server 2008 R2.
Is it possible to utilize Easy Print with a Windows 7 Pro client hooking up to a Windows 7 Pro RDP Host? Easy print doesn't seem to be present in that scenario... but with Ultimate it seems to work...
Trying to print to a Dell 5110cn from my home computer with Win7-Pro to a printer here at work. Again, this works with a different machine with Win-7-Ultimate but doesn't with Win-7-Professional
I am having the same issue you did printing to an impact printer with the Epson TM- series. Locally it prints fine. Through Terminal Server the quality is awful. The server is Windows 2008 R2. The client is Windows 7. If the client is Windows XP it prints fine. Did you find a solution?