Hello,
We have a load balanced Terminal Server farm of 5 servers with upwards of 70 users on each, had have had several printer issues, even though we only install or support printers that indicate they are compatible with Terminal Services.
One issue is that sometimes when a user disconnects or logs out, their printer does not purge. When looking at the ports, we'll find that the 'stuck' printers are sitting on an inactive TS port. If you try to access their properties, the error message appears:
"printer properties cannot be displayed. either the printer name was typed incorrectly, or the specified printer has lost its connection to the server"
If we catch them early we can manually delete them (although this becomes difficult to decern which printers are real when there's 40 users and 90 legitimate printers.) If we don't catch them early we get the above message and have to bounce the spooler. Why are printers not purging properly?
Another major issue is that once in a while one user's print jobs will go to another user's printer. This is completely unacceptable, but we cannot figure out why this is happening. Bouncing the spooler appears to fix it, but we can't have that constantly happening.
The User Profile Hive Cleanup Service is already installed on all the servers - and we've moved many of the users to using the HP Universal Print Driver PCL 5 (v4.7) - pre-configured to disable status updates and support.
Any help would be appriciated - we have been unable to find anything that directly addresses our issue. Any support article we've found so far doesn't apply to our situation.
We have a load balanced Terminal Server farm of 5 servers with upwards of 70 users on each, had have had several printer issues, even though we only install or support printers that indicate they are compatible with Terminal Services.
One issue is that sometimes when a user disconnects or logs out, their printer does not purge. When looking at the ports, we'll find that the 'stuck' printers are sitting on an inactive TS port. If you try to access their properties, the error message appears:
"printer properties cannot be displayed. either the printer name was typed incorrectly, or the specified printer has lost its connection to the server"
If we catch them early we can manually delete them (although this becomes difficult to decern which printers are real when there's 40 users and 90 legitimate printers.) If we don't catch them early we get the above message and have to bounce the spooler. Why are printers not purging properly?
Another major issue is that once in a while one user's print jobs will go to another user's printer. This is completely unacceptable, but we cannot figure out why this is happening. Bouncing the spooler appears to fix it, but we can't have that constantly happening.
The User Profile Hive Cleanup Service is already installed on all the servers - and we've moved many of the users to using the HP Universal Print Driver PCL 5 (v4.7) - pre-configured to disable status updates and support.
Any help would be appriciated - we have been unable to find anything that directly addresses our issue. Any support article we've found so far doesn't apply to our situation.