Managing Printer Drivers
During printer auto-creation, if XenApp detects a new local printer connected to a client device, it checks the server hosting the published application (from which the user is trying to print) for the required printer driver. By default, XenApp automatically installs a native driver if one is not found on the server hosting the published application.
Because users in a XenApp environment do not have a persistent workspace, drivers cannot be stored on the client. To print to a local device, XenApp must find the correct driver on: (a) its server or in the server’s Windows operating system, and (b) the client device. The diagram that follows shows how the printer driver is used in two places for client printing.
The printer driver on the server and the driver used by the client device must match exactly. If not, printing fails. As a result, XenApp provides features to manage drivers, install them automatically, and replicate them across your farm.
The following problems can arise from not managing client printer drivers correctly:
- Any missing drivers can prevent users from printing successfully. If a third-party printer driver has multiple or inconsistent names across your farm, a session might not be able to find it and a user’s job may fail to print.
- Printing to a client printer with a defective driver can cause a fatal system error on a server.
- XenApp does not download drivers, including printer drivers, from the print server. For XenApp servers to print across the network printing pathway, the correct device-specific printer driver for the XenApp server's operating system (version and bit depth) must be installed on the XenApp server. Two print servers are not required.
- If a defective driver is replicated throughout a server farm, it is difficult and time consuming to remove it from every server to prevent its use with client printers.
When planning your driver management strategy, determine if you will support device-specific or the Universal Printing driver, or both.
- What types of drivers you want to support
- If you want printer drivers automatically installed when they are missing on farm servers
- If you want to create driver compatibility lists
- If you want to replicate drivers across your farm servers automatically