We have approximately 500 users spread out across 51 locations, running on 75 different Citrix Desktops. The bulk of the users are utilizing Thin Clients and are load balanced across 50 desktops that are provisioned each night with the same image. We are not currently saving the Event Logs of these desktops to long term storage, so the previous day's logs are not available.
Our environment essentially has one model of B&W printing, but the issue also occurs with the Color printers. Printers were deployed 14 months ago. Until last week the print drivers that had been installed during the deployment are the same drivers we were running. Last week I installed new drivers on a Client machine. Unintentionally those drivers were grabbed by the print server and then passed down to all of the other client systems.
Desktops running Server 2008 R2 x64
Applications: Happens with a variety of applications (Office, Excel, IE, Foxit), primarily 32 bit apps.
Print Server: Server 2008 R2 x64
Issue
A user will go to print from an application and the application will freeze. Nothing appears in the print queue, and the C:\Windows\System32\spool\PRINTERS folder.
Often times, if another user that is also on that same server attempts to print they will also become frozen. There are instances where another user is able to print without an issue.
When we have two users that are frozen, if we unfreeze one of the users, it tends to result in both users becoming unfrozen.
If a user is able to wait a length of time (10 minutes) the system will unfreeze and print the job. It is unclear whether this is due to another user in the system encountering an issue and had killed their application to escape the frozen status.
Question
James Arthurs
Environment
We have approximately 500 users spread out across 51 locations, running on 75 different Citrix Desktops. The bulk of the users are utilizing Thin Clients and are load balanced across 50 desktops that are provisioned each night with the same image. We are not currently saving the Event Logs of these desktops to long term storage, so the previous day's logs are not available.
Our environment essentially has one model of B&W printing, but the issue also occurs with the Color printers. Printers were deployed 14 months ago. Until last week the print drivers that had been installed during the deployment are the same drivers we were running. Last week I installed new drivers on a Client machine. Unintentionally those drivers were grabbed by the print server and then passed down to all of the other client systems.
Desktops running Server 2008 R2 x64
Applications: Happens with a variety of applications (Office, Excel, IE, Foxit), primarily 32 bit apps.
Print Server: Server 2008 R2 x64
Issue
A user will go to print from an application and the application will freeze. Nothing appears in the print queue, and the C:\Windows\System32\spool\PRINTERS folder.
Often times, if another user that is also on that same server attempts to print they will also become frozen. There are instances where another user is able to print without an issue.
When we have two users that are frozen, if we unfreeze one of the users, it tends to result in both users becoming unfrozen.
If a user is able to wait a length of time (10 minutes) the system will unfreeze and print the job. It is unclear whether this is due to another user in the system encountering an issue and had killed their application to escape the frozen status.
Suggestion on how to troubleshoot this?
Link to comment
5 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now