This may happen when the user print from the redirected printer and log off
without checking the printing status.
If the printing hangs for some hardware reason, the printing job may not
finish and printing queue remains not deleted for this client.
The next time the user connects the session discovers the existing queue
(broken and not functional) and creates new using Copy to make difference
between those printers.
There was a bug like this and I believe it was fixed during the SP or WU
Do you have Service Pack installed?
What about the Windows Update?
Zenon Pilat (MS)
This posting is provided "AS IS" with no warranties, and confers no rights
"chadkline" wrote in message
>I have about 30 employees who use Terminal Server.
> Over half of them use the same type of printer.
> I installed the drivers on to the server.
> Periodically though, a user will connect in and
> there will be (Copy 1), (Copy 2) etc of their printer installed under the
> session, but with different session #'s.
> It changes daily. Neither one of the copies allow them to print.
> Why is this and how do I fix this issue?
> Can't find the answer anywhere.
> Please help
> Frustrated Admin