This happens on a Linux printserver that serves Windows clients using manufacturer-provided Windows drivers for printers. 

If I want to use a manufacturer-provided Windows driver for a printer, here is how I upload it. The name of my printer is jeeves. 

1. Open \\printserver in Windows explorer
2. Click "View remote Printers" button (available in XP, Vista, 7, but not 8). 
3. Right-click desired printer, choose Properties. 
4. Switch to Advanced tab, press "New driver" button. 
5. Point the wizard to the location of my manufacturer-provided Windows driver. 
In this case I use "RICOH Aficio MP C2551 PCL 5c". 
6. Wait until all the files upload to printserver, click OK. 

Now, refreshing the list of printers on the remote printers list (step 2 above) will show that the printer has been renamed into "RICOH Aficio MP C2551 PCL 5c". Windows clients won't be able to use it until I rename it back into jeeves. 

rpcclient enumprinters before upload:

	flags:[0x800000]
	name:[\\LOCALHOST\jeeves]
	description:[\\LOCALHOST\jeeves,jeeves,Jeeves]
	comment:[Jeeves]

after upload:

	flags:[0x800000]
	name:[\\LOCALHOST\RICOH Aficio MP C2551 PCL 5c]
	description:[\\LOCALHOST\RICOH Aficio MP C2551 PCL 5c,RICOH Aficio MP C2551 PCL 5c,Jeeves]
	comment:[Jeeves]


This is super-inconvenient and error-prone, because it is easy to rename wrong printer, large printserver might already have a printer named "RICOH Aficio MP C2551 PCL 5c" forgotten since the last upload, so two printers get mixed up, etc. 

Please make sure the name is kept when a binary driver is uploaded. 

I'm attaching a tdbdump of the registry.tdb with one single printer called jeeves before I uploaded the driver, and another dump after "RICOH Aficio MP C2551 PCL 5c x64" was uploaded (I didn't rename the printer back).

Also attaching 'enumprinters 2' output before and after the upload.