Printer Queues not deleting
in [Terminal Services]
|
Prev: Terminal Server - Set RootDrive=W: fails- (dual-Core Opteron)
Next: Only 2 Connections Allowed on SBS, Why?
From: Robert on 17 Jan 2006 09:02 I have Administrator rights on our Windows 2000 Terminal Servers. It appears that printers that are mapped from previous user sessions are not being deleted from the terminal server. e.g. printer1/workstation1/Session 60 is showing as ready but that session is not active on the terminal server. I understand that when a user logs off or disconnects a session that print queue is to be deleted. Is there a configuration issue that needs to be checked on the client or server side to allow these print queues to delete and only be created as users login?
From: Tad Brockway (MS) on 3 Feb 2006 15:37
If a user logs out with a print job in progress, there are scenarios (unfortunately) where the printer cannot be deleted. They become, essentially, dead printers. If a printer with the same name is created on subsequent logins, it will be overwritten. You can reboot your terminal server and all these dead printers will be deleted on system startup. [This posting is provided "AS IS" with no warranties, and confers no rights.] Tad Brockway Microsoft Windows Terminal Services Program Manager "Robert" <Robert(a)discussions.microsoft.com> wrote in message news:E3CE168D-5114-46B2-9E0D-B8CC0A15C06B(a)microsoft.com... >I have Administrator rights on our Windows 2000 Terminal Servers. It >appears > that printers that are mapped from previous user sessions are not being > deleted from the terminal server. e.g. printer1/workstation1/Session 60 > is > showing as ready but that session is not active on the terminal server. I > understand that when a user logs off or disconnects a session that print > queue is to be deleted. Is there a configuration issue that needs to be > checked on the client or server side to allow these print queues to delete > and only be created as users login? |