If auto-creation fails, by default, XenDesktop installs a Windows-native printer driver provided with Windows. If a driver is not available, XenDesktop falls back to the Universal print driver. For more information about printer driver defaults, refer to Default print operations.
If the Citrix Universal print driver is not an option for all scenarios, map printer drivers to minimize the amount of drivers installed on Server OS machines. In addition, mapping printer drivers enables you to:
The automatic installation of print drivers should be disabled to ensure consistency across Server OS machines. This can be achieved through Citrix policies, Microsoft policies, or both. To prevent the automatic installation of Windows-native printer drivers, disable the Citrix policy setting Automatic installation of in-box printer drivers.
Each client provides information about client-side printers during logon, including the printer driver name. During client printer autocreation, Windows server printer driver names are selected that correspond to the printer model names provided by the client. The autocreation process then uses the identified, available printer drivers to construct redirected client print queues.
The general process for defining driver substitution rules and editing print settings for mapped client printer drivers follows.
When users log on XenDesktop checks the client printer driver compatibility list before it sets up the client printers.