Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

BridgeRE (IS/IT--Management) (OP)
13 Jun 08 10:43
What the heck does it take for session printers to properly get deleted after a user logs off?  It does not happen all the time, but it does most of the time.  I have had the Hive Cleanup installed for many months and am not even sure if it is supposed to take care printers also, but it is rediculous.  If a printer is left in session, then that person logs back on, gets a different session (so now the printer from old session is now active again), then another user logs in and get the other users old session number with it's printers.  What a security glitch.  I've had people printing to a printer located in another state, because of this.  Is there a fix? (besides Server 2008)?  Is it due to the printer drivers installed on the TS?  By the way this is W2K3 Terminal Servers.
Thanks
MockY (Programmer)
16 Jun 08 13:07
Has it always been like this or did it work in the past? What printers are you using and when this happens, is it the same kind of printer every time that stays, or is it a random behavior?

 
BridgeRE (IS/IT--Management) (OP)
16 Jun 08 13:22
random, I don't know if it has always been like this or not.  I have over 200 print drivers installed, not installed printers per say.
MockY (Programmer)
16 Jun 08 14:00
I would first document all printers used by the clients. Then I would remove all drivers currently installed on the server as well as the client, and only install these drivers that are currently needed for the physical printers. That way you have the opportunity to update the drivers at the same time.
This is probably not fastest of solutions, but I would have done so though, just to make sure that there are no driver conflicts anywhere and so that you could rule that out of the equation.
BridgeRE (IS/IT--Management) (OP)
16 Jun 08 14:22
Thanks, I have already documented all the printers I see on a daily basis, and do plan on removing all of them, and installing only what I documented.  But at a later date, due to upgrading to Terminal Server 2008 (TS Easy Print)  I will however have to keep 2 2003 Terminal Servers for those very outdated Windows 2000 clients.  I was not sure if there was some type of fix or what causes this to happen.  I guess it could be a few "bad" printer drivers.
MockY (Programmer)
16 Jun 08 14:33
The least you can do right now is to remove all drivers that are not in use. They are not needed anyway, so there is no need for their presence.  

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close