Users Seeing Each Others Printers on RDP Server the Truth and the Fix
"I can see everyone's printers - and someone printed to mine." On a shared RDP server this complaint arrives sooner or later, and it is almost always a misunderstanding of what the list is showing. Here is what redirection really isolates, what it does not, and how to make the list calm and clear.
✍️ Technical Anshu🖥️ Multi User RDS⏱️ 7 minute read
🎥 Watch the full video - every step shown live on screen
First, the reassuring fact, stated plainly: a redirected printer belongs to the session that created it. A normal user cannot see another user's redirected printer, cannot select it, and cannot print to it. The design isolates each session's printers. So when users report seeing 'everyone's printers', they are seeing something else - and it is worth knowing exactly what, because the fix differs for each case.
What a normal user actually sees (example)
Printers in this session
------------------------------------------------
Microsoft Print to PDF (server)
Office Copier - Reception (server, shared)
HP LaserJet (redirected 3) (YOUR printer - only you see it)
Not visible to you: the redirected printers of
the other 11 logged-in users. They exist -
just never in your list.
👆 Your list mixes server printers (everyone's) with your redirected printer (only yours)
1
What Users Are Really Seeing
Server-installed printers - printers installed directly on the server are visible to every user, by design. A long list of office printers is normal and is not other people's redirected printers
Look-alike names - ten users each see "HP LaserJet (redirected N)" and assume it is someone else's. It is their own; the session shows each person only their copy
An administrator's view - in Print Management, or as an admin, you see all sessions' printers and queues. Users shown an admin screenshot often believe everyone sees that. They do not
2
The One Real Way a Job Goes to the Wrong Printer
When an invoice genuinely lands on a colleague's printer, redirection is rarely the culprit - it cannot cross sessions. The real causes: the user picked a server-installed shared printer with a similar name to their own; two offices share one server printer list and names like "HP Printer" say nothing about location; or the application remembered a printer from a previous session on a different machine. Every one of these is a naming and training problem, and it is fixable without touching redirection itself.
3
Name Server Printers Like You Mean It
Rename server-installed printers with place and purpose: OFFICE-RECEPTION-HP, ACCOUNTS-LASER-A4 - never bare model names that collide with redirected ones
Remove server printers nobody uses; every stale entry is a future misprint
Teach one sentence: "Your printer is the one with (redirected) after its name." It ends most confusion permanently
Restrict who can install and manage printers on the server to administrators - casual printer installs by users create the shared clutter everyone then trips over
4
Privacy, Stated Honestly
Session isolation protects the printer, and users' jobs are visible in their own queue. But be straight about the limits: administrators can see all queues and job names on the server, and a document's title often reveals what it is. If your office prints sensitive material - salary sheets, legal notices - the answer is not panic, it is policy: server printers in controlled rooms for sensitive work, and staff who understand that an RDP server is a shared workplace, not a private PC. Tools like TSPrint keep the same session-isolation model; no mainstream tool makes a normal user able to print to another user's redirected printer.
📌 The test that settles any argument: log in as two different users at the same time and compare printer lists side by side. Each shows only its own redirected printer. Five minutes of demonstration beats a week of worry.
🎥 See It Done Live in the Video
Watch the video for the client side of redirection - how a user's own printer is brought into the session with TSPrint.
Can another user print to my redirected printer by mistake?
No. Redirected printers exist only inside the session that created them and are not offered to other users. A job that reached a colleague almost certainly went to a similarly named server-installed printer - check the name it was sent to.
Why does the administrator see dozens of printers in Print Management?
Print Management shows the server's full picture: installed printers plus every connected session's redirected printers. That view is an admin tool, not what users see in their own sessions.
A user printed a confidential file. Who could have seen it in the queue?
The user themselves, and administrators with access to the server's print queues - job titles are visible there. Treat sensitive printing as an office-procedure question, and use printers in controlled locations for such work.
This guide is based on the Technical Anshu video linked above • Stuck on a step? Ask in the video comments - you will get an answer 🙏