RDP printer mapping FAQs

Below is information about Printing and Printer Mapping within RDP sessions.

What happens by default?
Printing via RDP sessions is possible unless Zero Trust Security is turned on
RDP sessions will normally map the default local printer into the RDP session
End users can print from within the RDP sessions to their local printers. Users cannot print from a local PC to remote printers mapped to the remote session.

Why isn't a printer mapping?
There are scenarios in RDP sessions when printer mapping is enabled but printers still won't create or map. This usually occurs for a couple reasons:
A user does not log out of the RDP session completely and then tries to connect FROM different endpoints. This is a common situation but easily resolved by completely logging the user out of the logged in session and establishing a new login session.
A suitable printer match cannot be found or there is a printer driver issue
Zero Trust Security is enabled

Additionally, keep in mind many settings can be adjusted via an Active Directory Group Policy Object (GPO). See further instructions here.

Microsoft recommends using the Easy Print method because it causes less CPU usage for printer installation at connection time. The matching driver method causes increased CPU usage because it requires the spooler service to load different drivers. For bandwidth usage, Easy Print causes slightly increased network bandwidth usage, but not significant enough to offset the other performance, manageability, and reliability benefits. See further instructions here.
Was this article helpful?
Cancel
Thank you!