Until now Citrix only offers Citrix policies to connect network printers but the mapping is done by Point-to-Print. The same process happens on a XenApp server if network printers are mapped for users. P2P automatically sends the printer driver down to the client, installs the driver and adds the printer object.
Citrix xenapp 6.5 policy native driver upd windows#
Why Print Server? With Windows Server 2000, Microsoft introduced Point-to-Print (P2P) that makes adding a network printer on a client device very easy and therefore user friendly. With the optimization pack and its new Citrix policies the print out speed even over WAN works very well and therefore it’s part of my ten printing rules with XenApp.īeside Client printer companies most often use network printers that are managed by a Print Server.
The beauty of that is that users can leverage all functions the local printer driver has instead of a subset with a Universal Driver based on a printer model like Citrix UPD version 2 (Color Laser Printer).Ĭitrix has even further optimized the architecture and released the printing optimization pack (project Laser) for XenApp 6.0. In addition the client side installed printer driver is used by the client side EMF component of the ICA Client. The reason is that with that technology actually no native or 3rd party printer driver is needed on the XenApp Server. Citrix introduced UPD based on EMF with Presentation Server 4.0 The keyword "Windows" should tell you that Enhanced Metafile only supports Windows platforms.Ĭitrix uses EMF for automatic client printer mappings and should be the first choice with Windows clients. By now, everyone should know about the Citrix Universal Printer Driver (UPD) that is based on Windows Enhanced MetaFile (EMF).