Anyone tried this. I've gone the other way (Installing 64 bit print drivers on a 32 bit server), but the 64 bit OS doesn't want to allow the additional 32bit driver, when added the same way as the 64 bit was on the 32 bit Server 2003 OS.
This discusses adding a 64-bit driver to a 32-bit server operating system, but the caveats and process are identical:
One word of caution: some "ntprint.inf" drivers will prompt you for the installation CD (which, uh, isn't there because you downloaded the driver from the manufacturer's website??). If this is the case, your best bet is to use the following:
From there, select the appropriate INF file and continue.
May your efforts be well-rewarded!
Pharos Systems Technical Support
Have you already installed the 64bit driver? If so then you would add the driver from the print management console. The driver has to be the exact same version as the 64bit. email me if you have any questions.
If it's server 2008, you can highlight the printering in the Devices and printer window - At the top menu bar then click print server properties - then click the drivers tab in the properties windows. There is an add button there.
I found that I had to use the print management console from a 32bit machine with the exact same drivers installed in order to get it to work
The easiest way to do it, is to select the option under "Properties" -> "Sharing" -> "Additional Drivers". Click the X86
box, and then enter the location of your NPRINT file for the 32bit driver.
We have to do this on every single installation, as most of our customers need both x86 and x64 clients at present, OSX excluded of course.
We currently run Windows Server 2008 x64bit Print Servers. All drivers are loaded using Server Manager Add Printer Wizard. I select both x64 & x32, then start by loading the 64bit driver first. Once the 64bit driver is loaded the Wizard will ask for the 32bit drive. Everything uploads accordingly.
The method I mentioned here is more suited to an "after the fact" addition of either x86 or x64 drivers, so they both exist when you build the UniPrint Package. This is especially usefull when a printer vendor suddenly generates a new x86 or x64 driver, that didn't exist before, i.e. Ricoh, Canon, Savin, etc.
Scott's method worked. I had to install the 32 bit drivers via a 32bit Windows 2003 server.
Retrieving data ...