I suppose that is a conundrum. I havent installed the .print client on any individual machines rather i have a remote print server on site either a windows box or usually a SEH TPG60 gateway, then a central print server at HO. All the printers are created by the afore-mentioned Citrix policies (mapping from the central print server to the citrix sessions) and print jobs are sent down to the print server on site not the clients. This means no print drivers on the Citrix servers or the Client PC's/Thin Clients. All print processing and traffic occurs solely between the Central and remote print servers.
The advantage of this is that it got round the problem you have for us. If a user attends a site with Thinprint they log into citrix and all the printers on that site are mapped by the policies for them to print to. If they go to a site without it or home then the citrix policy wont apply and their local printers will get mapped through.
It is a different setup to how you have it and maybe abit of overkill if it is only for 1 or 2 users but definately overcomes the problem of roaming users.