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

2012 r2 rds redirected printer has wrong name

This is a really goofy problem. I have 3 domains at different sites and 3 RDS servers. All servers are 2012 R2. Users from all 3 domains log into the RDS servers at other sites for various applications, using credentials for the appropriate domain.
If domain1\user logs into the RDS server at domain 1, 2, or 3 printer redirection works as expected. However if a domain2 or domain3\user logs into the RDS server at domain1, the printer is redirected BUT it has the wrong name so it looks like someone else's printer. If you right click on the device in Printers and Devices and look at the printer properties you will see the correct name. This makes it very confusing for users and generates lots of support calls.
Notes: At domain 2 and 3, I allow the redirected printer to be set as the default printer. At domain 1 I do not, they must manually select their default printer (to prevent accountants from printing large reports to their check printer).
At domain 1, if I add a user to the Print Operators group, the correct printer name appears.

?????? Any suggestions about troubleshooting this issue is appreciated.
1 Solution
Lionel MMSmall Business IT ConsultantCommented:
At domain 1, if I add a user to the Print Operators group, the correct printer name appears.
This seems to be your solution--create a group for the users from Domain 2 and 3 and add them to the Print Operators group in domain 1
mraineynolaAuthor Commented:
Well, that's a work around. There is a downside to adding all of those people to the Print Operators group, and it's aggravating because it is not necessary at the other 2 domains, it just works correctly there, but not on domain 1 where something is obviously munged. ARRRGH, MICROSOFT!
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

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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