Citrix native printing alone depends not only on how the machines are set up in your business, but also how the Citrix print policies are configured. Print spooling locally, as in a PC having a direct connection with a printer located in the same office does not possess a large issue as most businesses have moved far away from local connections. The only issue with local printer connections would have to do with excessive CPU and memory usage as the print spooling process is using the local machine.
If print spooling is performed through a dedicated print server, then network traffic must be built well to manage the flow of data being sent out and received to avoid disruption and maintain the flow of data. This becomes more important if a Citrix XenApp server is added and it is generally where the issues start.
Print spooler crashes have occurred before desktop virtualization was introduced into the market. Only until when businesses started using Citrix to manage their print infrastructure did they realize how common it was for the print spooler to hang and the common culprit were printer drivers. The best solution for print spooler crashes is to determine the faulty print driver which in some cases, takes a significant amount of time by investigating where they are being stuck in queue and removing it.
When Windows Server R2 was introduced, a feature named Print Driver Isolation was added to isolate all print drivers unlike the classic version 2 kernel-mode drivers. Another unfortunate perpetrator of print issues in Citrix has to do with how printer policies are ignored. This occurs because of a conflict with an already existing Citrix policy and it there by causes the policy originally meant to be placed to be over written by another policy.
Citrix policies have become such a headache to solve, that system administrators have been physically mapping which print policies overlap other ones to avoid making any mistakes. A solution to ignored print policies is to run a test server inside of its own organizational unit and add one policy at a time.
The idea is to see which print policies conflict with the previous one, and with that knowledge you will be able to determine which print policies have been ignored. TWAIN devices policy settings. USB devices policy settings. Virtual channel allow list policy settings.
Visual display policy settings. Moving images policy settings. Still images policy settings. WebSockets policy settings. WIA devices policy settings. HDX features managed through the registry. Load management policy settings. Profile management policy settings. Advanced policy settings.
Basic policy settings. Cross-platform policy settings. File system policy settings. Exclusions policy settings. Synchronization policy settings. Folder redirection policy settings. AppData Roaming policy settings. Contacts policy settings. Desktop policy settings. Documents policy settings. Downloads policy settings. Favorites policy settings.
Links policy settings. Music policy settings. Pictures policy settings. Saved Games policy settings. Searches policy settings. Start menu policy settings. Video policy settings.
Log policy settings. Profile handling policy settings. Was this page helpful? Thank you! Sorry to hear that. Name Name is required. Email Email address is required. Close Submit. Featured Products. Need more help? Product issues. If this version is 6. If it reads 0. At this point use the Citrix Print Driver Stress Test tool to see if this driver is causing the issues.
After you have tested the drivers and found the drivers that failed to pass the stress test in the normal amount of time in a 5x5 test, that is an average of 12 to 30 seconds , then you should remove these drivers from the server. In the following example of the 5x5 setup for testing, 5 concurrent AddPrinter events are created and repeats it 5 times: image from the stress test tool After you remove the drivers from the server, you should check what contents are left behind from the bad drivers.
This might cause the Citrix Print Manager service to crash, not be able to restart, or even to stop functioning. Note : Sometimes print drivers can be problematic to remove from servers since they are loaded once the spooler is running. Using the following method is the easiest way to remove a problematic print driver: Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
Rename all Print Processors that are listed: eg Winprint to Winprint. Click on the driver tab and remove the problematic driver. Rename all the Print Processors back from Winprint. Print drivers that do not respond to the DeletePrinter API correctly will leave stale records in the registry, these records can build up if the driver is not removed causing printing problems in your XenApp environment.
You should remove anything in this hive that has a comma after the session number along with another arbitrarily generated number. You should ensure that the printing values you remove do not currently have sessions logged onto the server.
If it does, then it can cause problems to the user session. Do not remove any of the local printers on the server. Remove only the printers created with session numbers and commas after them, or any other irregularities.
0コメント