Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2

Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2

  • Comments 38

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 7

Windows Server 2008

Windows Server
2008 R2

Windows XP

Client : (1), (2)

Client : (1), (2)
Server : (3)

Client : (1), (2)
Server : (4)

Windows Vista

Client : (1), (2)

Client : (1), (2)
Server : (3)

Client : (1), (2)
Server : (4)

Windows 7

 

Server : (3)

Server : (4)

Windows Server 2008

Client : (2)

Client : (2)
Server : (3)

Client : (2)
Server : (4)

Windows Server 2008 R2

 

Server : (3)

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.
image


Troubleshooting:

  • If you experience formatting problems using Easy Print.
    Refer to the KB- 954744 article at http://support.microsoft.com/kb/954744 (related: KB954743).
    Refer to the KB- 970603 article at http://support.microsoft.com/kb/970603
    Refer to the KB- 959442 article at http://support.microsoft.com/kb/959442
  • If the client printers are not redirected as Easy Print:
    • First check the RDP version on the RDP client computer as well as the .NET framework version with respect to the operating system used (as explained above). Also verify that the RD Session Host / Terminal Server role is installed if the host computer is running Windows Server 2008 R2 or Windows Server 2008.
    • Group Policy must be correctly set to enable Easy Print on the Server. The policy location is “Computer Configuration -> Administrative templates -Windows Components -> Remote Desktop Services > Remote Desktop Session Host -> Printer Redirection”. The setting “Use Remote Desktop Easy Print printer driver first” must be set to “Enabled” for Easy Print redirection, and it has to be “Disabled” for Legacy Print. For “Not configured”, Easy Print is chosen by default.
      image 
    • Check The Remote Desktop Configuration Tool (tsconfig.msc) settings to ensure that the “Windows Printer” option is not disabled (it is not disabled by default).
    • Make sure that the “Printers” check box in the client (mstsc.exe) window on the “Local Resources” tab is checked. The corresponding setting in the associated RDP file is “redirectprinters:i:1”.
    • Ensure that the spooler service is running on both the RDP Client & Server.
      Windows Server 2008 added the ability for an Admin to configure spooler security and Windows 7/Windows Server 2008 R2 adds the UI for this. Therefore, it would be possible to alter the RDP server’s spooler security descriptor which might prevent RDP client printers from being redirected on the session. The spooler security descriptor must contain the “AU” (Authenticated User) ACL (Access Control List) which allows any authenticated user to open the spooler service for reading operations. Therefore, if that ACL is missing from the spooler security descriptor, it must be added like the example below using the command prompt (elevated).
      > sc sdshow spooler
      D:(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWRPWPDTLOCRRC;;;SY)
      > sc sdset spooler D:(A;;CCLCSWLOCRRC;;;AU)(A;;CCDCLCSWRPWPDTLOCRSD
      RCWDWO;;;BA)(A;;CCLCSWRPWPDTLOCRRC;;;SY)
      [SC] SetServiceObjectSecurity SUCCESS
    • If you connect over RD Gateway, ensure that the policy that disables printer redirection is turned off.
    • If everything listed so far is correct and you still have a redirection problem, check the event logs.

      Some of the events to look for are:

      Event ID

      Message

      Explanation

      1105

      Printer security information for the printer could not be set.

       

      1109

      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.

      1111

      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.

      1116

      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.

      1103

      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.

       

      1124

      The number of printers per session limit was reached.

       

    • If the number of redirected printers is less than the number of the RDP client printers.
      The maximum number of printers that can be redirected is controlled by the registry key “MaxPrintersPerSession REG_DWORD” which is under the node “HKLM\\Software\\Policies\\Microsoft\\Windows NT\\Terminal Services”.
      The default value for this is 20 printers per session.
    • If Easy Print is unable to print on a domain controller.
      Refer to the Knowledge Base Article 968605 at http://support.microsoft.com/kb/968605/EN-US
    • If the client printer is redirected as Easy Print and the user is unable to stop a print job on the redirected printer.
      Take ownership of the printer and allow the “Print” & “Manage printers” permissions. But note that when logged off from the RD Session, the remote printer settings are not retained.
Leave a Comment
  • Please add 4 and 4 and type the answer here:
  • Post
  • Easy print hav tested it and it works well on most printers but Problem on Canon UFR II Printers The dublex and color settings doesn't work as expected. Forced to install the Canon UFR II driver on the terminal server. Also HP Color LaserJet 2600n doesn't work very well the spool service hangs using Esay Print. One Brother printer don't remember the name and model but always the first page in a print was ok and the following pages was nonsens, tested the document starting from diffrent pages in the document and the first page in the selection was always ok and the following pages was not even cloes to the original text and formatting, but it it printed the correct number of pages. So I think Easy Print is not safe to unleash for everything needs testing.

  • Many of our easy print problems have been resolved by removing .NET 3.5 on the client and installing .NET 3.1 with the latest service pack...  There are bug fixes that haven't hit the 3.5 build yet (or at least this was the situation a few months ago).

    Might be worth you looking into.

  • This question is off topic, but I wanted to to know if it was possible to configure more than one RD Session Host for "Virtual Machine Redirection"?

    Thanks.

  • @Andreas

    Same problem here with a different set of printers. Al printing the first two pages ok, and after that the formatting is messed up, or strange characters. And it's only in particular documents, when you print it to pdf and print the pdf everything goes fine.

    I'm thinking about installing the specific drivers again on the terminal server.

  • Andreas / Joris - do you have all the required .NET QFEs listed above installed? Thanks

  • Gaurav, only kb954744 is for XP and the problem described is different than the problems I've. Thanks for your input though.

  • I had one client PC that the printers turned up on the 2008 TS and one that they wouldn't.

    So I knew the TS was capable, but what was wrong with the Client?

    Both running XP, both same printers, so what???

    Turned out to be one had and one didn't have DotNet. Installed this and all is good. Thanks for such a good article. Cheers Jeff

  • With different HP Laserjet printers (1200, 1300, 2200) and pcl 5 or pcl 6 printer drivers my users get only a PCL XL ERROR InsufficientMemory PaintPath. Before I never had any memory problems while printing.

    Any ideas?

    Thank you.

    Felix

  • I have a legacy application that only prints to PCL printers.  How can I get from PCL to XPS in order to utilize Easy Print?

  • This article should quite possible be renamed "how to trouble shoot easy-print" ... as nearly every other document fails miserably on troubleshooting easyprint.

  • I have two machines.  One brand new XP Pro (never connected to a domain) and one older XP Pro.  Both have SP3 and .net 3.5 SP1  Server is brand new 2008 R2 running a completely different domain than the remote computers connect to. The new machine works perfectly printing through easy print.  The older machine won't print anything.  Event log shows Access denied error on non working machine.  Any ideas how to solve this?

  • Found a solution, so I thought I should publish it here.  On the server...

    1. As administrator run cmd.exe then enter the following commands

    2.C:\

    3.CD \Windows\System32\Spool

    4.Cacls.exe PRINTERS /e /g users:C

  • I am getting error 1111.  So I thought I would try to install the easy print drivers, or reinstall them.  Not having any luck.  is there any addtional information on what to do if I receive error 1111.  

  • Looks like the error 1111 is only for the printers that WS2008R2 is trying to redirect. It isn't throwing that error for easy print specifically.  I still can't get any windows 7 rdc to show the redirected printer as "easy print" though. The printers all show up with the drivers that I have installed on the server for the specific redirected printer.  I have gone through everything on this page and still can't get it to work.    

  • I guess I poked around long enough to realize that I didn't "Also verify that the RD Session Host / Terminal Server is installed".

    After I installed that everything works like a champ.  Only problem is now I apperently have 120 days to pay for licensing, even though I will only have two concurrent sessions running at the same time.  I thought that fell under the terms of use for remote admin?

    It would be nice if the above mentioned portion of the troubleshooting on this page was a little clearer.  I thought that since I was able to open up an RDP session to the host via both "remote app"(I had created earlier on a different server) and standard RDP that the RD Session Host would obviously have to be installed for those Items to work, not so.   And since some of the names for those roles have changed it may be wortwhile to clarify that in here.  I may be the only person that had this problem?  But the way the three part series here makes it sound WS2008R2 comes right out of the box with all these features enabled and ready to go.

    Anywho, thanks for a great product, this is really leaps and bounds better than the exceptionally problematic RDP setup I had before.  We used to have printing problems galore, and running RDP without remote app for most of my users was always a total pain.  They don't want to have to deal with anything but the application that they need and I don't really blame them.

Page 1 of 3 (38 items) 123