Question : How to enforce using Citrix Universal Print Driver in Citrix

I read a lot about Citrix Universal Print Driver and this is what I have implemented; it is working for almost all users but very few users are still having problems printing.

what I need to know is when you implement  Citrix Universal Print Driver do you need to have printer drivers for your printers installed on the system ?

I did upgrade on one citrix server from 4.5 to then Xenapp and apparently the previous admin did replicate the drivers on this server.  So now we have Citrix Universal Print Drive + All printers drivers on the same citrix server.

So now when the users login to Citrix; this is what happen (please see the pic attached) Not all printers are using Citrix Universal Printer. Some of the session is created using the installed printer driver from the server.

What can I do so I can force all sessions to use Citrix Universal Print Driver ? do I have to uninstall the drivers ??  As I said few users are still having problems printing. (it won't even create a printing session for them).  So I'm suspecting this to be the issue.

Thanks

Attachments:

Citrix-Universal-Print-Driver.jpg (115 KB) (File Type Details) 

Citrix-Universal-Print-Driver

Answer : How to enforce using Citrix Universal Print Driver in Citrix

Hello,
the universal driver will work for most but not all printers.  There are still a few such as the LaserJet 4250 that I still need to load the native drivers for.  The default behavior of Citrix is to use a native driver if it is loaded on the server or available to extract in the windows CAB files but to use the universal as a fallback.  You can configure citrix policies to enforce just the universal but you will probably have some issues and need to use the native ones.  Your servers will typically be happier without loading all sorts of 3rd party drivers but ultimately the end user needs to print so unless you can mandate only certain printers you will probably want to leave the behavior the same as it is now.  
So, with the devices that are still having issues, are they mapping with the universal or native drivers?  If universal, find the exact driver name the end user is using and install a server version of that driver.  It should now map instead of the universal and fix your issue.  Be warned that every 3rd party driver you load is one more risk of instability to your spooler.  If you load an old NT, Kernal Mode driver it may even blue screen your server.