[Mububban]

Hi everyone

We have a lot of users regularly utilising Remote Desktop Connection on XP and Vista, from home or an external office. Our file/print server is Windows Server 2003 for Small Business Server, and our Terminal Server is Windows Server 2003 Standard, SP2.

When a user logs on to RDC, it often creates "remote desktop redirected printer doc" print jobs, every few seconds. So if a user is online for hours, it will create thousands of them. Which obviously slows printing, jams the spoolsv.exe process and causes major problems.

These remote desktop redirected printer docs can manifest on our 2 Konica Minolta network printers, or a 3rd printer set up for our external office, or on the user's personal home printers, if they have any installed. So it's not just printers that haven't had their drivers installed on the main server. It can and does affect all printers.

These "remote desktop redirected printer doc" print jobs can and do go to ANY of the printers installed. Yesterday I used RDC and it sent 1500 of those junk print jobs to each of the 2 main office printers, as well as 500 junk print jobs to my Adobe Acrobat software printer, and about 250 to my home Epson printer (which was offline as I was in the office, not at home).

The only suggestion I've found so far involves locking certain users out of certain printers. but I don't want to lock out ANY of those printers for ANY of our users, as they are all legitimate and need to be accessible.

Has anyone experienced this as well, and more importantly, did you find a solution?!?!? I came into work this morning to find the server CPU at 100% as spoolsv.exe tried to resolve 3500 of these junk print jobs, on each of the 2 main printers.
Is it a printer driver error? A Microsoft Remote Desktop glitch? A Server 2003 error? This problem has me (and apparently the rest of the internet) stumped and it's really causing problems.

Thanks