How printer redirection is supposed to work
When RDP printer redirection works, it's quietly magical: the printer sitting next to your laptop at home appears inside the remote session as "Printer Name (redirected)," and printing from a server app comes out on your desk. When it breaks, the printer simply doesn't show up in the remote session — everything else works, but the printer list is missing your device.
Understanding the three layers is the whole game, because the fix is always on exactly one of them: the client must offer the printer to the session, the server must accept redirected printers, and the driver must be able to render the print job. Redirection fails silently when any layer says no — so we check them in order, client first.
Layer 1: the client checkbox (fixes most cases)
Start here — this is where most redirection failures live:
- Open the connection settings before connecting. In Remote Desktop Connection, click Show Options, go to the Local Resources tab, and under "Local devices and resources" click More.
- Check Printers. Expand the tree and make sure Printers is checked. (While you're here, note the state of clipboard and drives for other redirection issues — our clipboard fix guide covers that one.)
- Save and reconnect. Save the connection, then connect fresh — changing this mid-session doesn't take effect until the next login. This is the step people skip: the checkbox only applies at connection time.
- Verify the printer is the default locally. Redirection offers your local printers; if the printer isn't installed or isn't working on your local machine, there's nothing to redirect. Print a test page locally first.
On the Microsoft Store / mobile clients, the equivalent setting lives in the connection's device-redirection options — same principle, different label. If the printer appears in the remote session after this, you were done at layer 1 all along.
Layer 2: the server side — policy and services
If the client is offering the printer and it still doesn't appear, the server is refusing it. Check these in order:
- Group Policy: printer redirection allowed? On the server (admin access required), open gpedit.msc and check Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Printer Redirection. The policy "Do not allow client printer redirection" must be Not Configured or Disabled — if it's Enabled, no client printer will ever appear, regardless of checkboxes. This is the #1 server-side cause.
- Print Spooler service running? The spooler must be running on the server for any printing — redirected or otherwise. Check Services (services.msc) for "Print Spooler": status should be Running, startup type Automatic. A stopped spooler is silent and total.
- Easy Print enabled? In the same Printer Redirection policy folder, "Use Remote Desktop Easy Print printer driver first" should be Enabled (it's the default on modern Windows). Easy Print lets the server render print jobs without needing the printer's exact driver installed — it sidesteps most driver problems entirely.
- Session-specific check. If redirection works for one user but not another on the same server, compare their sessions — per-user policies or a corrupted user profile can block it individually. Testing with a fresh test account isolates profile issues fast.
Admin note: after changing printer-redirection Group Policy, run gpupdate /force and have the user reconnect fresh. Policy changes don't apply to already-connected sessions.
Layer 3: drivers — Easy Print and the fallbacks
With Easy Print enabled (the default), the server renders the print job itself and sends it to the client — no matching driver needed on the server. When Easy Print is disabled or broken, the server falls back to needing the printer's exact driver installed locally, and mismatches cause the classic symptom: the redirected printer appears but print jobs vanish or error.
If you see the printer but can't print through it: first confirm Easy Print is actually enabled (layer 2). If it is and jobs still fail, try installing the printer's driver on the server anyway — some applications print more reliably with a native driver. And check the application's own printer selection: apps sometimes default to a PDF or XPS printer inside the session, so the job "prints" to a file instead of your redirected printer. Select the "(redirected)" printer explicitly.
The spooler restart (the classic fix)
Print Spooler wedges are the "turn it off and on again" of printing — unglamorous and disproportionately effective. If redirection was working and stopped, or jobs queue but never print:
- On the server, open Services (services.msc) as administrator.
- Find Print Spooler, right-click, and choose Restart.
- While you're there, clear stuck jobs: stop the spooler, delete the contents of
C:\Windows\System32\spool\PRINTERS, and start it again. - Disconnect and reconnect your RDP session fresh so the redirected printer re-registers cleanly.
Do the same on your local machine if local printing is also misbehaving — a wedged local spooler breaks redirection from the client side, and no amount of server tweaking fixes that.
The fallback: skip redirection entirely
Sometimes redirection fights you beyond reason — exotic printers, strict policies, or a server you don't administer. The pragmatic fallback: make the printer a network printer. If your printer supports Wi-Fi/Ethernet, connect it to the network and add it directly on the server as a network printer (or print to PDF in the session, transfer the file, and print locally — our file transfer guide covers the handoff). Network printing bypasses all three redirection layers; it's less elegant, but it prints.
For offices, there's a cleaner variant: put the printer on the office network and add it to the server once — every agent session sees it without any per-client redirection. Call centers and shared workstations often standardize on this instead of fighting redirection per user (see our call centers guide for the team setup).
Cause-to-fix reference table
| Symptom | Layer | Fix first |
|---|---|---|
| Printer missing from remote session | Client | Local Resources → More → check Printers; reconnect fresh |
| Missing for all users, all clients | Server policy | "Do not allow client printer redirection" = Disabled; gpupdate |
| Nothing prints anywhere on server | Server service | Print Spooler: Running + Automatic; clear stuck jobs |
| Printer appears, jobs vanish or error | Driver | Enable Easy Print first; install native driver as fallback |
| Worked yesterday, broken today | Spooler wedged | Restart spooler both ends; reconnect fresh |
| Redirection blocked by policy you can't change | — | Network printer on server, or print-to-PDF + transfer |
Printer Redirection: FAQ
Almost always the client checkbox: in the connection's Local Resources tab → More, Printers must be checked before connecting — changing it mid-session does nothing until you reconnect fresh. Also verify the printer works locally; there's nothing to redirect if it isn't installed on your own machine.
That's a driver-layer problem: the printer is redirecting fine, but the job can't render. Confirm "Use Remote Desktop Easy Print printer driver first" is enabled on the server, check the app is actually targeting the "(redirected)" printer (not a PDF/XPS printer), and restart the Print Spooler on both ends.
Usually not. Remote Desktop Easy Print (enabled by default on modern Windows) lets the server render jobs without the printer's exact driver. You only need the native driver as a fallback when Easy Print is disabled or a specific application prints unreliably through it.
Yes — the Group Policy "Do not allow client printer redirection" blocks it for everyone, regardless of client checkboxes. If your printer is missing on a server you don't administer (office, call center), ask the admin to check that policy; it's the most common server-side cause.
Yes: add the printer to the server directly as a network printer (if it's network-capable), which bypasses redirection entirely. The quick-and-dirty version is printing to PDF in the session, transferring the file to your local machine, and printing it there.
The usual culprit is a wedged Print Spooler — restart it on the server (and locally), clear stuck jobs from the spool folder, and reconnect fresh. Policy changes and Windows Updates are the next suspects; both are fixed by verifying the redirection policy and reconnecting.
Ready for your own RDP server?
Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan. Pay by credit/debit card, bank transfer, Bitcoin or altcoins.
3-day money-back guarantee · Instant setup · 30+ server locations · 99% uptime SLA
