|
|
Question : Problem: Printers not being "released" from Terminal Server
|
|
Good Morning,
I am having an issue with both of my Terminal Servers. They are not releasing client-side printers when the client logs out of his or her RDP session. Currently on one server, my Printers and Faxes folder has 645 objects. The other has 505. What is see is the following (printer, server, client names changed to generic): printer1 on printserver (from client1) in session 2 printer1 on printserver (from client1) in session 3 printer1 on printserver (from client1) in session 5 printer1 on printserver (from client1) in session 7 printer 4 on printserver (from client1) in session 2 printer 4 on printserver (from client1) in session 3 printer 4 on printserver (from client1) in session 5 printer 4 on printserver (from client1) in session 7
And on and on. This is for several clients - I have counted 13 - give or take one or two.
I have no idea why this would be happening and could use some help.
Thank you, BA
|
Answer : Problem: Printers not being "released" from Terminal Server
|
|
Microsoft calls these orphaned ports when they sit there as you describe. I had this issue on my TS as well. After time all the ports will get used and when your users print the print job will immediately error out and nothing prints. You have to go into the registry and clean the ports up and reboot. MS has a nice program called UPHClean that mkes sure when a user logs off their printers and profiles get removed. This worked perfect for me. Since installing it I havent had any issues.
|
|
|