TS Printer Redirection -Printers not removed from session

[Guest IFSTORY@gmail.com]

We run Windows 2003 Terminal Server. We have 20 Clients at 3

different sites. We have 2 users at a remote office, that connect to

Terminal Server properly, and their printers connect (We see the new

session printers in both the "TS, and the local TS Session). When

they logoff Terminal server, their session printers remain. So for

instance, Larry logs in as Session #5, and a Sessiion #5 printer is

set up. Larry logs off, and the Session #5 printer remains. Now at a

later time (Next day, weekend, lunchtime), he logs back in to TS, and

creates a Session #6. But the Session #5 printer remains. Larry

cannot print to the Sesison #5 printer, although print jobs build up

in the queue for Printer Session #5. In order to clear this, we have

to A) have to delete the jobs in the queue B) Have ther remote user

log off of TS C) Restart the TS Print Spooler D) Have the user log

back into TS E) Verify that his old printer is removed, and the new

Session #6 printer is set...he can then print.

This has affected as many of 3 users a 2 sites. It does not happen

all the time. The two printers are Laserjet 7500 and a Laserjet

P1505. We have verified that the drivers are present, and work with

both XP and 2003. We have 2 other 1505 printers, but they are the "N"

models, and directly attached to the LAN.

We have had support from Microsoft look at this,but they say it is a

"PRINT PROCESSOR" problem, and want to remove all PRINT PROCESSORS

from the system, except WINPRINT. When we tried that, we knocked the

good users off the system (Could not print). Can someone give me a

good place to look to fix this. If their session printers are

removed, then they can be recreated, and the user can print. If they

remain, they cannot print. Even if the same session is created (Larry

#5 - Printer Session #5), Larry cannot print unless we restart the

Print Spooler on the TS, which is very annoying. Thank you in

advance.

[Guest Ratnesh Yadav [MSFT]]

Re: TS Printer Redirection -Printers not removed from session

 

Any event logged on Server ?

 

Check following link for troubleshooting printer issues with Terminal Server

http://blogs.technet.com/askperf/archive/2007/08/24/terminal-server-and-printer-redirection.aspx

 

Ratnesh

<IFSTORY@gmail.com> wrote in message

news:f914e0a6-a205-4451-841e-96aa29801bf0@w34g2000prm.googlegroups.com...

> We run Windows 2003 Terminal Server. We have 20 Clients at 3

> different sites. We have 2 users at a remote office, that connect to

> Terminal Server properly, and their printers connect (We see the new

> session printers in both the "TS, and the local TS Session). When

> they logoff Terminal server, their session printers remain. So for

> instance, Larry logs in as Session #5, and a Sessiion #5 printer is

> set up. Larry logs off, and the Session #5 printer remains. Now at a

> later time (Next day, weekend, lunchtime), he logs back in to TS, and

> creates a Session #6. But the Session #5 printer remains. Larry

> cannot print to the Sesison #5 printer, although print jobs build up

> in the queue for Printer Session #5. In order to clear this, we have

> to A) have to delete the jobs in the queue B) Have ther remote user

> log off of TS C) Restart the TS Print Spooler D) Have the user log

> back into TS E) Verify that his old printer is removed, and the new

> Session #6 printer is set...he can then print.

> This has affected as many of 3 users a 2 sites. It does not happen

> all the time. The two printers are Laserjet 7500 and a Laserjet

> P1505. We have verified that the drivers are present, and work with

> both XP and 2003. We have 2 other 1505 printers, but they are the "N"

> models, and directly attached to the LAN.

> We have had support from Microsoft look at this,but they say it is a

> "PRINT PROCESSOR" problem, and want to remove all PRINT PROCESSORS

> from the system, except WINPRINT. When we tried that, we knocked the

> good users off the system (Could not print). Can someone give me a

> good place to look to fix this. If their session printers are

> removed, then they can be recreated, and the user can print. If they

> remain, they cannot print. Even if the same session is created (Larry

> #5 - Printer Session #5), Larry cannot print unless we restart the

> Print Spooler on the TS, which is very annoying. Thank you in

> advance.