This post has already been read 31573 times!
I came across an issue (as most people probably have) where all the XenApp servers were being killed by print drivers. This was also happening in the Vdi environment as the number of drivers on the base image was growing rapidly! This coupled with the fact we had to use the HP Universal print driver and that most of the clients were thin meaning the only option was session printing was causing a huge headache!
I started to look at purchasing other printing options to get around this but then thought to have a look at the Citrix Universal Print Server. This initially looked excellent but I started to hit issues with session printers again. It worked great but it meant that the users had to manually add the printers to their Citrix profile.
The following article will provide a good way to deliver session printers to thin clients without having to add any print drivers to the XenApp Servers or XenDesktop Base Image.
The Print Server
Firstly you will need to install the Universal Print Server software onto your print server that you wish to provide network printing from. This can be obtained by downloading the XenApp or XenDesktop client software. You will need to be using Windows 2008 R2 for you print server. If you are currently using Windows Server 2003 then this will not work.
Once you have the software on the print server set up a couple of shared printers on the print server if you don’t already have any.
Thats all you need to configure on the print server believe it or not!
The XenApp Server / XenDesktop Base Image
Install the Citrix Universal Print Client onto the base XenApp Server or XenDesktop Base Image.
Again, this is all you have to do on the client side. The rest is all delivered via policy.
Set up a new Citrix Policy and Enable the setting “Use Universal Print Server”
Set up a new Group Policy to map the printers for the users. This uses Group Policy Preferences.
How it works.
The Citrix Universal Print Server will intercept the Windows Add Printer wizard and map the printer using the masked drivers. If you don’t want to users to have to add the printers themselves then you use Gpo – this in turn triggers that wizard and Universal Print Server acts as it should.
Session Printers will map the drivers using the native driver from the network print server. If this is not on the XenApp server it will either not show the printer or install the driver.
Hope this helps someone out!