Historically, printing redirection has been difficult for Terminal Services & Citrix. To successfully redirect a given user's client printer to the server, the proper drivers needed to be installed on both the client machine and server machine. Customers like you have discovered that the requirement of having the server host a matching print driver can be problematic for a number of reasons (e.g. inability to find matching drivers, or the drivers the printer vendor supplied just don't work).
We wanted to solve these issues and reduce headaches. The solution is Easy Print: a "driver-less" solution for printer redirection over Terminal Services.

The Terminal Services Easy Print driver acts as a proxy and redirects all user interface calls to the actual driver on your PC. When you edit preferences for a print job on a redirected printer, the Terminal Services client will launch the interface from the local machine on top of the remote session. As a result, you see the same detailed printer-specific interface. You will see exactly the same options as if you were printing something locally. The selected preferences are then redirected to the server for use when printing.

This feature requires you have speciality form sizes installed on your local workstation. You can do this by running the TSRDP.exe Installer below as a local administrtor.

TSRDP.EXE :: Download Here

The second piece is the ability to send a print job from the server to your PC and reliably print the job. To do so, Easy Print takes advantage of Microsoft's new document format, XPS. When redirecting print jobs, on the server, Easy Print creates an XPS file using the preferences you have selected, then sends the XPS file to your desktop and then prints the job on the appropriate printer. XPS has the advantage of being a document format that encapsulates printing preferences and document data. That, plus the fact that XPS comes with Windows, makes using XPS to transport printing data a very logical mechanism. The dependencies on the XPS format are what necessitate the installation of .NET Framework 3.0 SP1 on the client computer.