About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Staff expect hosted business software to print like software installed on the desk PC. In reality, printing from a remote session crosses the session host, network, driver stack, and whatever printer path you chose—local redirection, a network printer visible to the host, or a purpose-built print server. Design starts by naming which printer each critical process uses, then matching that to a supported path, not by assuming “it worked at home once.”
Why it matters
Printing failures erode trust faster than slow screens. Office managers hear “the system is broken” when the real issue is an unmapped label printer, a driver that exists only on the client, or a workflow that assumes a USB device the gateway blocks. Microsoft’s current RD Session Host performance guidance treats printer redirection as a capacity and policy design choice (CPU at sign-in, driver matching versus Easy Print), which means redirection belongs in print planning—not an afterthought.
How it works
Applications run on the RD Session Host (or published RemoteApp on the same role). Print jobs are rendered where the application runs. Getting paper out requires either:
- Session-local or host-visible printers (drivers installed on the session host or redirected according to policy), or
- Client-redirected printers, where the job travels back to the user’s device—subject to gateway, client, and policy support.
The RDS roles article groups desktops and apps on session hosts; it does not promise that every local desk printer auto-appears. RD Gateway still governs which clients may connect and which resources they reach; device and printer redirection must match the policies you deploy today, not assumptions from older event catalogues alone.
Microsoft’s RD Session Host performance guidance describes two redirection patterns: matching printer drivers on the server versus Easy Print redirection introduced in Windows Server 2008, which uses a common driver and is recommended because it reduces CPU use at connection time compared with loading many distinct drivers into the spooler.
Labelled example — dispatch desk: Hosted logistics app must print A4 invoices to a LAN printer defined on the session host, because redirecting fifty different home printers is unmaintainable.
Labelled example — executive assistant: Prints occasionally from a laptop; client redirection might be acceptable if pilot proves driver quality and gateway policy allow it.
What to choose and why
| Pattern | When it fits |
|---|---|
| Printers installed on session host / print server | Stable office output, label or industrial devices, known driver set |
| Easy Print–style simplified redirection | General office printers when policy and pilots succeed |
| “Print to PDF” inside the app plus local print | Low-volume, acceptance of extra steps |
| Dedicated RDP-unaware workflows | Revisit delivery mode when the application cannot run in a session |
Before go-live, map one critical process end to end: open document, print, collect paper, reprint after reconnect. Include colour, tray, and barcode/label if applicable. If a process needs a scanner or USB dongle at print time, test that in the same session shape (browser vs native client) you standardise on.
Read next
Related articles you may want next.
- HostingMoving printers and scanners with a line-of-business applicationKeep printing and scanning working when business applications move to hosting. Inventory devices, drivers, queues and file destinations, then test everyday staff workflows.Read article
- HostingBrowser client or native Remote Desktop for hosted business appsChoose browser or native Remote Desktop access for hosted business applications by checking the devices, printing and everyday workflows your staff need.Read article
- HostingWhere remote staff should save files: local PC, hosted share or application storeChoose file locations for hosted application work with clear ownership, retention and recovery arrangements that survive device loss and staff changes.Read article
Risks and limits
Redirected printing increases CPU use at sign-in and network use while jobs flow; a problematic driver on a shared session host can affect multiple users—an operational risk worth sizing and monitoring, not a topic this article proves in a lab.
The web client prints via a virtual printer that yields a PDF the user prints locally—a different experience from native redirection. Archived Windows Server 2008 R2 gateway event descriptions illustrate historical “secure device redirection” failures; use them only as background when reviewing logs, and validate current gateway and client redirection policy in your environment. No lab validation was performed for this article.
Sources
- Remote Desktop Services roles — accessed 2026-11-16; ms.date 2024-07-03.
- Remote Desktop features (clients) — accessed 2026-11-16. Current client feature matrix including printer redirection.
- Remote Desktop Session Hosts performance tuning — accessed 2026-11-16. Easy Print vs matching-driver redirection; spooler CPU at sign-in.
- Get started with the web client for Remote Desktop Services — accessed 2026-11-16; ms.date 2025-05-06. Remote Desktop Virtual Printer / PDF flow.
Related reading
- Where remote staff should save files
- Browser client or native Remote Desktop for hosted business apps
- Business solutions (NetLeverage service context)
Learning notes
- The application prints where the session runs; paper appears only if the path to a real printer is designed.
- Redirected printing and host-installed printers solve different office layouts.
- Gateway and CAP/RAP policy can block redirection scenarios staff assume are “default.”
- One mapped critical workflow beats a generic “printing works” checkbox.
- Driver quality on the session host is an operational risk, not only a user training issue.
This article was originally published on .