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. These irregular printers are created when the print driver does not respond to the DeletePrinter API function call. After the drivers and the registry are cleaned out, you should clean out the underlying foundation of the XenApp environment, the Datastore.
Open the Command window with administrator credentials. 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. There are 2 printer deployment methods and issues you must pick when dealing with Citrix virtualization:.
Start menu policy settings. Video policy settings. Log policy settings. Profile handling policy settings. Profile container policy settings. Registry policy settings. Streamed user profiles policy settings. User personalization policy settings. Virtual Delivery Agent policy settings. HDX 3D Pro policy settings. Monitoring policy settings. Virtual IP policy settings. Connector for Configuration Manager policy settings.
Aviso legal. Este texto foi traduzido automaticamente. Este artigo foi traduzido automaticamente. This setting controls whether client printers are mapped to a server when a user logs on to a session. By default, client printer mapping is allowed. If this setting is disabled, the PDF printer for the session is not auto-created.
If you choose this option, the default printer is not saved in the profile and it does not change according to other session or client properties.
The default printer in a session is the first printer auto-created in the session, which is either:. You can use this option to present users with the nearest printer through profile settings known as proximity printing. This setting provides an alternative to the Default printer and Session printers settings. Use the individual Default printer and Session printers settings to configure behaviors for a site, large group, or organizational unit.
Use the Printer assignments setting to assign a large group of printers to multiple users. This setting specifies how the default printer on the listed user devices is established in a session. It also specifies the network printers to be auto-created in a session for each user device. By default, no printers are specified. To use the current Remote Desktop Services or Windows user profile setting for the default printer, select Do no adjust.
When setting the session printers value: to add printers, type the UNC path of the printer you want to auto-create. After adding the printer, you can apply customized settings for the current session at every logon.
This setting specifies the events that are logged during the printer auto-creation process. You can choose to log no errors or warnings, only errors, or errors and warnings. When enabled, the VDA will attempt to establish a direct connection to the print server and use the network pathway to route the print job.
When disabled, the print job will be routed through the client pathway. This policy only applies to network printers configured on the client. Note: This is not an all-inclusive list of the Citrix printing policies available. Refer to the product documentation for additional policies. Citrix administrators can use Citrix policy to configure the various printing capabilities and to enable or disable specific functionality.
The following table includes the default settings for the printing policies mentioned in the section above. The recommendations below have been defined by Citrix based on field experience and input from the sales, services, and support teams. Configuration changes should be tested and validated by customers prior to implementation in a production environment.
Note: Unless explicitly noted, all other printing policies are configured with default settings. Some native drivers are available through Windows updates. This may require manual installation of Postscript drivers. This may require manual installation of the PDF driver available for download on the Citrix website as part of Receiver for Chrome under additional components.
The user can select these options from the custom Citrix UPD print dialog. Consider using the local settings option with client printers on Windows endpoints for other model-specific features not available in the Citrix UPD print dialog Ex. Secure PIN printing. The local settings option will bring up the native driver printing preferences dialog of the local endpoint, allowing the user to change any printer option, and the modified printer settings are used for the print job in the active session.
Create multiple policies for assigning different printer sets to multiple user groups.
0コメント