I guess I’ve not come across this before as most of the printers we deploy use the same driver name for client side and server side drivers, but it appears that you can force a Terminal Server to use a certain driver, in place of what the client is telling the server.
KB239088 details the process. I found that the wizard wasn’t much use at all - but it’s not like the process is particularly complicated. Doing it manually also demonstrates that deploying the “fix” over multiple servers is childs play.
As 64 bit Terminal Servers become more common, and clients with printers stay at 32 bit (i.e. home or remote workers) I can see this becoming more relevant over the next few years.