kyleb84
asked on
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?
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?
ASKER
I installed that "Print Server" role as a solution to the problem, installed or not - it still has that issue.
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.
Net2Printer and Print2RDP are two i have seen.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
I had similar problem before and restarting the print spooler helped to clear it a bit.
1) net stop spooler,
2) net start spooler
ASKER
Thanks for the advice ppl,
Screen shot attached, please confirm this is a "Bring local printers to RDP session" issue.
ss.JPG
Screen shot attached, please confirm this is a "Bring local printers to RDP session" issue.
ss.JPG
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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...
ASKER
Well done, cheers.
I hope this helps. Good luck.