I've got 5 terminal servers all at 2003 Server SP2 and each one has about 30 users on a typical day. With everyone's printers mapped in, they all seem to have about 150-250 printers on each server. These typically work fine, however lately (and it's getting worse) that at in the middle of the day any new user logging on will not have their printers map. All other users can still print fine, but from that point on it will not map any more printers until the server is restarted.
When I look into the server properties, it shows hundreds of TSxxx ports in use for the users (including those just logged in with no printers) but they don't have any printers next to the ports. Is it possible that it's not recycling the TS printing ports or that they are hanging? Really gets to be a pain at 1:00 in the afternoon when you need to boot 30+ users off to reboot the server! Mostly using HP Laserjet printers and have tried the Citrix stressprint app, but that didn't hang on any of the drivers.
This could be "The hunt for the bad printer driver". I would look at the users and printer being created just before the problem occurs. This might be a printer driver that is loaded for the first time or multiple times. Also the WFShell.exe manages the printer creation, so look for application error and maybe fire up Process Explorer.
--Emil
Thanks for the reply - I'm afraid of "The hunt for the bad printer driver", I don't like that game but necessary nonetheless! Okay, I wasn't sure what process manages the creation so I'll keep a close eye on that. Haven't seen anything at all in the event logs, but knowing this may be helpful. I'll post back what I find.
I would consider using UPD's.
Just found this in my Favorites:
http://iswarade.wordpress.com/2007/08/10/troubleshooting-printer-issues-in-presentation-server-40/
Has a lot of CTX articles linked.
There are essentially two processes that control the creation of printers: the Print Spooler itself, and the Citrix Print Manager Service. If either one of these craterm you will stop getting printers created. However, if the Print Spooler dies and doesn't restart, then nothing will print either. The fact that other users can print tells me it's probably the Citrix Print Manager Service causing the issue. It is still probably related to a bad printer driver, but at least you can focus your efforts in the right direction.
Why is it called "Common Sense"? It doesn't seem all that common!
Thanks guys - sounds like I really just need to focus my efforts on finding bad printer drivers, or as was mentioned earlier, go to UPD. I was afraid something else might be up, but it sounds like the most likely scenario is bad drivers. Especially since this is happening to all of my servers, not just isolated to one - and they all have the same drivers on them. Everyone has been very helpful, and i'll continue to watch the processes as well when they start to act up in case that can point me in a better direction.
For anyone following this, I believe i have located the printer driver that has not been cooperating. It was for a LaserJet 2015 PCL 5. Having that driver map in as a HP LaserJet driver only seems to have made life much better for us. Again, thank you for the responses that I received - very helpful!
Andrew
I've heard of a few problems with the HP LaserJet 2015 drivers.
My post needed to be moderated, so I took two web links out - and then it was okay. They use state what we know though - that the 2015 is troublesome.