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

Multiple printer sessions on Terminal Server (Win2K3 R2)

I have a customer that has approx ~20 local PC's and almost the same of remote users.

All users log into a Windows 2003 Standard R2 Server via Remote Desktop.

The "Terminal Server" role is installed on the server.
The "Print Server" role is installed on the server.

There are nearly 20 different printers of varying brands.

After some time the "Control Panel->Printers" list becomes many pages long, filled with

"[PRINTER NAME] (from [PCNAME]) by [USERNAME] Session ##"

Where:
PRINTER NAME is the printer's name
PCNAME is the name of the PC from which the user is using Remote Desktop from
USERNAME is the username used to log into the Terminal Services session
Session ## is (I'm guessing) the Terminal Services session number

Over time these printer sessions multiply and become many hundreds, finding a single printer in that list becomes tedious and a reboot is the only solution so far.

What causes this?
How do I stop it?
0
kyleb84
Asked:
kyleb84
2 Solutions
 
andrew_aj1Commented:
Are you using the server as a print server too? I believe the print server saves every printer that it can see. If you do not need this role remove it and hopefully it will solve your issue.
I hope this helps. Good luck.
0
 
kyleb84Author Commented:
I installed that "Print Server" role as a solution to the problem, installed or not - it still has that issue.
0
 
mjonasCommented:
there are remote printer management softwares available which allow you to select the printers brought through into a terminal session. Another benefit is you don't need to install the printer driver on the terminal server.

Net2Printer and Print2RDP are two i have seen.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Adam GrahamEnterprise ArchitectCommented:
It sounds like the users are bringing their locally added printers into the terminal session. Check on the RDP dialog under options --> local resources that 'printers' is not selected on every client. Then remove the printer sessions from the terminal server and get the users to re-connect.

Adam
0
 
mega666Commented:
Does some of  the printer names start with "Automatic" ? if so - on all client PC's disable it in "folder options" -> View tab - first tick box. If that is the case this should limit the number of connected printers.

I had similar problem before and restarting the print spooler helped to clear it a bit.
  1)  net stop spooler,
  2)  net start spooler
0
 
kyleb84Author Commented:
Thanks for the advice ppl,

Screen shot attached, please confirm this is a "Bring local printers to RDP session" issue.
ss.JPG
0
 
andrew_aj1Commented:
Everything seams normal on there. You have 2 Quickbooks printers, but they are on different computers (one local and the other from Stucklaptop). Same with the HP P1505n.
0
 
MrJemsonCommented:
0
 
kyleb84Author Commented:
Hmm that might be why its hanging - and not the session printers. I'll try it and will let you know if it does it again...
0
 
kyleb84Author Commented:
Well done, cheers.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

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