Incorrect Print Driver?

Question

Recently, we began having problems printing a barcode label through a SATO printer.  Essentially, the font is wrong, causing the barcode to be unreadable.
Basically, whenever we RDP from Win7 or a thin client (I say newer, but we have only tested on one), we seem to be getting the wrong print driver for our SATO printer. I tried searching around to find out how RDP decides what driver/settings to use, but have
not had much luck.
We have tried the following scenarios:
Print directly from XP: works
Print directly from Win7: works
Print through Citrix from XP: works
Print through Citrix from Win7: works
Print through Citrix on thin client: works
Print through RDP from XP: works
Print through RDP from Win7: fails
Print through RDP from thin client: fails
Print through Citrix from thin client (Same one): works
What could cause this behavior, and how do I fix it? Not using RDP is not an option.
Update:
I tested at my local site with a thin client, and it works.  So now, one site's thin clients do not work, while another's do.

Answer 1

At my site, the server is running Windows 2008 R2.
The printer is not redirected.  It is a shared printer installed on the print server (or in the testing scenario shared from my laptop, but same results).  Regardless, any way I look at it, the driver is SATO CL412e.  When I go into the About
tab I see the same version and build number as well.
This is why it is confusing.  From everything I know to check, the print driver is exactly the same.  However, the behavior definitely is not.  How is it that when I RDP from my laptop (Win7) it somehow uses what appears to be a bold font,
but when I do so from literally any other scenario it is correct?  In the case of the other site, even the thin client is incorrect (same behavior as Win7 RDP to server).