I have exactly this same problem running Office 2003 under RHEL 5.7. Plus my print to pdf doesn't show up in the Office applications. It looks like the printer configuration is being captured into a win.ini file within the bottle. So, for example, I installed Visio 2003 into its own bottle. So these phantom printers are showing up in the file:
But I don't see any tools, techniques, nor documentation explaining what this is and how I update it.
I'm explicitly running CrossOver because (a) I am required by my management to run the Office products in order to produce certain artifacts, (2) I don't want to have to reverse engineer Micro$oft products just in order to make them work, and (iii) I don't want to manage a Windoze OS in a virtual machine for the increasing limited number of products that I would need it for.
Thus far, after two years of use, CrossOver seems to be an admirable alternative. But the printer support leaves a bit to be desired, particularly with respect to administration.
This issue has been forwarded to the Official CodeWeavers Ticket System. If you have observed this issue and would like to report it as well, please open a support ticket or send an email to firstname.lastname@example.org with a description of what you are seeing and a link to this post.
The CodeWeavers Team