Hello,
We have a terminal server farm and run into an interesting issue with the HP Universal Print driver PCL 5, PCL 5, and v4.7 PCL5 and v4.7 PCL6:
For a single printer using one of these versions of the UPD, a single printer shows between 12-16 entries for "Printer was set" before finally ending with "Printer was created" when being redirected. It takes a good 30-40 seconds before it gets to that point, and before that point, cannot be printed to. Additionally, if you log off of the terminal server before that process finishes, it takes until it finishes for the log off process to complete. If you log off after it has completed, log out is instant.
My question is why does the printer get "set" 14-16 times before it's finally "created" and ready to be used over TS?
So far it doesn't appear to slow down the server itself, just the users unable to use their redirected printer immediately, and a bloated event log.
We have a terminal server farm and run into an interesting issue with the HP Universal Print driver PCL 5, PCL 5, and v4.7 PCL5 and v4.7 PCL6:
For a single printer using one of these versions of the UPD, a single printer shows between 12-16 entries for "Printer was set" before finally ending with "Printer was created" when being redirected. It takes a good 30-40 seconds before it gets to that point, and before that point, cannot be printed to. Additionally, if you log off of the terminal server before that process finishes, it takes until it finishes for the log off process to complete. If you log off after it has completed, log out is instant.
My question is why does the printer get "set" 14-16 times before it's finally "created" and ready to be used over TS?
So far it doesn't appear to slow down the server itself, just the users unable to use their redirected printer immediately, and a bloated event log.