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.
I'm using Remote Desktop Easy Print with Windows Server 2008 R2 Standard and testing a workstation with Windows 7 Ultimate and a Canon MF4370 connected VIA IP network. The redirected printer shows up in the Remote Desktop session using whatever TS port (TS90 to be exact) and I can go through the motions of test printing, but nothing spits out of the printer. I've checked for event viewer errors (none) and the print leaves the print queue properly.
Incredible, the only articles about printing in the Terminal Services Team blog talk only about Easy print witch doesn't work in TS 2003....greath job guys
I am having an with redirected printers not displaying on win 7 professional server. My terminal/workstation is a POS Ready os system.
I have tried w/Easy Print enabled with printer driver only on workstation AND with Easy Print disabled w/driver installed on both workstation and server.
Does anyone know if there is an issue w/POS Ready os and Win 7 os? Or any suggestion on configuring this to work.
FYI..my RDC setting is set for printers, ports and plugins.
Where is GPO setting "Redirect only the default client printer" in R2? In 2008 domain it was in
Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection. Now we have 2008 R2 domain functional level, and there are now such setting in new location: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Printer Redirection\ there are no "Redirect only the default client printer"
And also i have found in Extra Registry setting "Software\Policies\Microsoft\Windows NT\Terminal Services\fDisableClip"....
I have a new computer with windows 7 (32 bit) and my current printer HP Laserjet 1200 does not work because I do not have the correct drivers for it.
please help by repying on my email address
Did anyone have a solution for Alex when RDP printing queues and spools, but nothing prints on paper?
I had the same problem as Nick Martin. Couldn't get Easy Print to work until I added the Remote Desktop Session Host Role.
It also asks me for a license or it will stop working in 120 days. Any solution to this? I only want to have admin access with Easy Print working.
You know, there is a BIG PROBLEM here, in that it is IMPOSSIBLE to do RAW printing to printers handled by easy print. E.g. using these printing api's:
OutputFile = nil;
DataType = 'RAW';
Our application sends printer-native commands to the printer. We cannot do gdi and such calls.
What is the solution to doing RAW printing when easyprint is in the picture??
Am using terminal server 2008 with eazy print. The problem I am facing is that, whenever I restsrt the print spooler most of the redirected client printers going to offline and I am unable to make it as online. what ever i do it is showing access denied.
so i have this setup and it seems to be working well except for a couple of my users... coiuple things I was wondering it it was possible:
1. Not sure why this is happening, but when a user clicks on the x or sometimes logs in very close together the old printer is kept in the old session. So now the user logs in and well they only see the default pritner in their current session when going to devices and printers... BUT in the program they are using: Simply Accounting 2009, it keeps the OLD printer as their default inside simply from the last session, not the current session. So is there a way to say on login, delete any of these printers, or every 5 minutes run a script to delete these old session printers??? This is driving me nuts....
stephen.walsh [[-at]] wnlsd.ca
1. the first one was: I can see the redirected printers but can not print to them - solution:
Click Start, search for cmd.exe
2. Right click on cmd.exe
3. Click on 'Run as Administrator'
4. Type "C:\" w/o the quotation marks and then Press Enter.
5. Type CD\Windows\System32\Spool and then Press Enter.
6. Type Cacls.exe PRINTERS /e /g users:C and then Press Enter.
2. The second problem I need help with: I'm printing to a Epson fx-890 invoice (Dot matrix) printer, when I print localy, it prints fine, when I print remotly it prints in a different font and very unclear
System: Windows Server 2008 R2, Windows XP SP3 client.
Problem: Printer prints all text as gibberish when printing with Easy Print.
Solution: I installed remote desktop 7 from here (support.microsoft.com/.../969084) and it seems to have fixed the issue.
The response at the bottom of this link helped us - technet.microsoft.com/.../cc753853(WS.10).aspx
Changed the permissions for the following directory to "Full Control" for USERS account - C:\Windows\System32\spool
If there are multiple users connected to the Terminal server, with 2003 Terminal Services we were seeing all the users shared printers. Is this corrected in 2008 so only your printers are shown vs. all users on the Terminal server?
In 2008 you only see your printers but in 2003 if you give your users Power Users rights (or local admin rights) to the Terminal server, the user WILL see all the printers.