• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4383
  • Last Modified:

How to map Client printers in server 2008R2 RDS

Hi i have 2 server which runs RDS , server 2008 R2

How do i configure RDS to map Client printers , or GPO

I have som networks printers mapped on my PC ,

And I have followed this link , and added a GPO but it dosent map my networks prnters


Have read all part 1,2,3 and it dont sat anything about mappning of networksprinters


GPO I created

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


  • 5
  • 2
1 Solution
johnfreakAuthor Commented:

Hey guys Please some help here ?

James CookIT ManagerCommented:
you could install the printers as 'local' printers.

You would need to create a new local port with the address //path/to/print/server/printer.
I have the same setup and this works perfectly.
This will only work for networked printers though.
Spike99On-Site IT TechnicianCommented:
To use terminal services easy print for users logging on to Windows 2008 server, they need to have:
1. Remote Desktop Connection (RDC) 6.1
2. At least Microsoft .NET Framework 3.0 Service Pack 1 (SP1)

Windows 7 clients already meet the requirements, but Windows XP clients will need to be upgraded to SP3 to get RDP 6.1 and .NET will need to be installed separately.  Vista systems only need to be upgraded to SP1 or SP2 to meet these requirements.

But, you can just use the local redirected printer using the locally installed driver if you prefer.

In order to enable redirected printing, check the following:
1.  the Local printer option is checked on the RDP connection on the client
2.  local printing is enabled on the terminal server
3.  a driver with the same name is installed on both the client PC and the terminal server

If everything else is set for local printers and you are still not seeing your local printer in your 2008 TS session, check for Event ID 1111 in the system event log on the terminal server at the time you log on.

If you are seeing Event ID 1111 errors, the error will tell you the name of the driver you need to install on the Terminal Server for your local printer.  If you are NOT seeing Event ID 1111 errors when you log on (and everything else is set up correctly for redirected printers), you may have to add a DWORD value to the registry to force  ALL printer ports to be redirected (only ports beginning with LPT, COM and USB are redirected by default):

From MS article (http://support.microsoft.com/kb/302361):
1.  Click Start, click Run, type regedit, and then click OK.
2.  Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR
3.,  On the Edit menu, point to New, and then click DWORD Value.
4.  Type FilterQueueType, and then press ENTER.
5.  On the Edit menu, click Modify.
6.  Type FFFFFFFF, and then click OK.
7.  Close the Registry Editor.
8.  Connect to the 2008 server again

I think this will fix your problem.

Or, if the printer is shared over the network, you can just type in a DOS command to map the printer:

      rundll32 printui.dll,PrintUIEntry /in /q /n\\servername\printername

Or, to make that printer your default, add the "/y" switch to the command:

     rundll32 printui.dll,PrintUIEntry /in /q /y /n\\servername\printername

See this page for more information about using the printui command:

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

johnfreakAuthor Commented:

Thanks spike99 for the guide i followed it and it works but I have 2 RDS servers , one of them are DC

dont ask me why ,

 but on the dc which also are RDS server does easy print not work , but it works on the other RDS server which is not a DC

Is there special setting on DC , i have give all users read acces to the GPO
johnfreakAuthor Commented:

Does it suppos to take to long to answer on this board, ? it that new ?

I have waited for many days now ? days ??????
Spike99On-Site IT TechnicianCommented:
Sorry, I  missed your follow up question.

Using a domain controller as a terminal server is not recommended, but here is a MS KB article that describes how to fix Easy print on it (look at steps listed the resolution section):


Let us know if that helps.

johnfreakAuthor Commented:

Hi I have moved the Terminal services rolle to anthor Server which is not a DC every thing works fine now

Please close this ticket
johnfreakAuthor Commented:
did not get any answer ,

dont now why ????????
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now