During the restore and for a short while after, the x64 server installed the matching x64 bit drivers. Suprised me, i was getting read to install the 64bit counterparts when i saw them poplutating already. This was only for microsoft drivers. Not sure how the others would work. But for my 32 to 64 solution, i am staging all the drivers on a 32 bit w7 enterprise machine, backing that up, restoring to 64bit r2 server, adding the missing 64 bit drivers, backing that up and then to a cluster.
I am trying now to do this with out the UPDs due to their lack of good. I downloaded imagex but it doesn't seem to work.
I downloaded it by itself. Thanks to everyone who came up with work-arounds. We're just about to move to a Win R2 print server and adding the additional 32bit drivers had become a nightmare. We have a mixture of HP, Konica and Oce printers, all of which gave us the same ntprint. I want to think the person that posted the above solution.
I had 7 printers to setup and this worked for 4 of them. I still had a problem with 3 HP printers. The problem was that when I first installed these on the Windows 64 Bit server, it grabbed drivers from MS.
That wouldn't be a big deal, if when I went to share them it would have searched MS for the 32 bit versions. Some where in this thread, there are many references to using your Windows 32 bit client CAB files and that probably works too, but here is what I did and it fixed the issue.
It really wasn't hard, but took about 6 hours of reading various forums to come up with it. I don't know if that will fix everyone's problem or not, but it's worth a shot. If I was doing this for a Non-HP printer, I would just go to that printer's web site and make sure I got their latest 64 bit and 32 bit driver for that printer providing of course they have one of each. This work which is interesting because at this stage of the game we should not be going through these problems. XP x86 was there before the 64 bit and Dell and HP should have a solution for these problems.
HP did came out with a Universal driver that do work especially for the series printers. Dell on the other hand needs to catch up to speed. Thanks to all who labor daily to make our lives easier find the correct methods to solve a problem here or there. Go the an XP x86 machine and follow the notes below. One thing that is not mention here is you have to copy the driver file down to the PC xp machine before you get started.
For example the Dell n printer copy the X86 drivers you were trying to install on the 64bit windows server. I have installed win2k8 R2 which is 64bit edition only. I added HP drivers for x64 and 32bit without problem but when I tried to add Xerox 32bit I got mentioned error. This will copy the needed files from your local Win7 bit box up to the bit server and enable the x86 driver Now the print server has both the bit and bit drivers installed for when a client connects to the printer.
I copied the directory locally and when prompted selected the location. No more problems with 32bit drivers for any other printers! You can use this information on 32 bit printservers or 64 bit printservers - just vice versa. If you have a 32 bit OS as server: 1.
If you have it the other way round 64 bit server, 32 bit client - just do it vice versa.. To add x86 drivers to x64 Server the only way seems to be is similar to this. Also this works if you have no shared printers, only drivers for terminal printing. Here it is:. And best of this is that you will be able to set print server properties, where you can add x86 drivers remotely. Right mouse click - Print server properties. Now it will be added without ntprint.
Check - the x86 printer driver on x64 Server I used R2 is now installed. Try this on server when trying to add a 32bit driver with the old print server still in service:. You may have to poke down through a couple of folders to find the right one.
Worked like a charm on our recent upgrade. I was having this issue also so I copied the folder from my win7 pro workstation placed it in folder on server good to go! But when i try to connect the printer on Win 7 32bit client machine it is asking for the driver.
But it is working fine on the x64bit client machine. The driver names do not match or the 32bit driver uses a print processor that has a different name than the 64bit version. If it's the print processor you can find this information in the vendor inf , change to winprint and see if the driver will work with this print processor. Office Office Exchange Server.
Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. I've read the relevant threads, and no one seems to be having my exact problem. Click Next. Select only x86 architecture.
Choose Have Disk. Browse to the location of the extracted x86 driver for the printer. Select printer from list in this case LJ Click Next. Windows prompts with the following: Install Components from Windows Media Please provide path to Windows media x86 processor. Type the path where the file is located and click OK.
Any thoughts? Wednesday, April 9, PM. HTH, BF. Monday, April 21, AM. Hi, It seems that some third party printer driver. For example, the following INF file includes an x64 driver is shown below: 1. NTamd64] 4. For backward compatibility, these entries look like as following: 1.
DLL For some scenario, the printer driver couldn't be installed normally due to the incorrect format. For instance: The additional driver can't be installed, because the. Best wishes Morgan Che. Friday, April 18, AM. Hi, In order to add printer driver based on X86 on X64 system, please try the following steps to test the result: 1.
Proposed as answer by helsby Tuesday, May 5, PM. Thursday, April 10, AM. I have the exact same problem and it is due to clicking the x86 box. It is asking for an ntprint. There is also no associated file on the vista CD. Where is the file we need to support x86 print drivers on x64?
Friday, April 11, PM. Same thing here, but with HP laserjet driver. It doesnt give an error message, it just keeps asking for that NTprint. Monday, April 14, PM. I cheated and got it to work by exporting my printers from my R2 machine by commandline and importing them, now I can add bit drivers with no problem.
This is definitely NOT the way to do this, but at least it got me going again. I'm having the same problem. Asks for ntprint. Thursday, April 17, PM. I have tried this and was unable to make it work, I also tried to setup with a Vista 32bit system with the other work around once i check the box and close nothing happens, when i reopen it the check box is cleared. If i try to add it from a XP pro machine it promts me for drivers. Proposed as answer by fapricela Friday, September 20, PM.
Monday, April 28, PM. I had tried R2, didn't work. Monday, June 16, PM. We implemented a Server x64 and had nothing but issues with the HP Univeral Drivers, we also could not get the older standard drivers to work for our HP printers on the server. Our Dell printers worked fine. Monday, July 7, PM. Bryant Fong said: I had the same problem too. Friday, July 11, PM. Only some of the above worked for me at all, until, tearing my hair out, I actually found this clippit of information in a QMS printer driver for a combined x86 x64 driver package doing all Windows OS in a readme.
I have selected both x64 and x86 at this point. Next add the drivers as it asks for them, x64 first on a x64 server Wednesday, July 30, PM. Wow, SBS is going to be 64 bit, isn't it? Is this being addressed on SBS ?
This is certainly going to cause me to not deploy SBS at my clients if I have to deal with this everywhere. Or install a 32 bit VM to deal with it. Tuesday, August 12, PM.
Nice Keswadmin and Bryant Fong via sjarocki! I used a win2k8 x86 machine to copy these for a win2k8 x64 print share. Worked perfectly! Can't understand why the x64 win2k8 OS doesn't have this built in????? Thanks Again. I've been messing with this on and off for months Dell cn PS driver was the latest fubar. Then you can go to the additional drivers and add the driver.
In my case I had to do this for the Dell dn printer. Tuesday, May 5, PM. Since the server is running a x64 OS, the x64 driver is required before you can create a new printer que. I decided to add the x86 and x64 drivers at the same time in the printer manager or print server properties. The driver versions must match!!! Also, when using this method I started out by downloading the latest Vista x64 and x86 drivers, even for a 2k8 print server and XP clients.
Click Add You will then be prompted for the x86 driver, browse to the location where you stored the x86 driver and click ok Select the SAME driver for the model you are installing and click ok. You will be brought back to the Print Server Properties window and you can verify that the drivers have been installed on the server.
Be sure to select the driver you just installed when adding the printer que to your server. Since the driver for the x64 and x86 versions are already installed on your server, both drivers will be installed as an additional driver on your printer que s. INF using this method. Wednesday, October 14, PM. This worked perfectly for me using a Konica Minolta bizhub C Thanks so much!! Thursday, October 29, PM. If you are installing any old printers that don't have correctly coded drivers this won't work - you get the same issue as the people who posted above.
INF error. Thursday, December 24, PM. From the 32 bit client machine which was adding the driver? To get the 32bit ntprint and files on the 64 bit server just add any inbox Windows 7 32bit driver onto the 64 bit machine using the 32bit machine. Once the 32bit package has been installed on the 63bit server you should not be prompted for this file set again. I am having an issue like this as well, unfortunately I don't have any 32 bit Vista or Windows 7 machines on the network, I am using a 64 bit server R2 machine as my print server and I too am pulling my hair out trying to figure out how to get the x86 drivers installed.
At first I was getting the type 3 mode error on the server which meant that I have to install it from a client. When I try and install it from the client I am not even given a chance to put the driver in, it immediately says no suitable driver is available.
I would love to have some asstance on this one, thanks!!! Tuesday, January 5, PM. Driver names must match. Are all your 32bit clients XP and Server ? You can use them to install the driver to the server but you can't open the properties of the printer since you do not have the driver installed on the client.
Install the driver on the client first or just ignore the driver install prompt and get the properties UI open to the point where you can click the Additional Drivers button on the sharing tab.
Wednesday, January 6, AM. Make a folder on your C Drive called Win7Mount 2. Obtain a copy of ImageX. This can be downloaded from Microsoft. It is their new imaging software. Note the drive letter. Open a command prompt and change directories to wherever ImageX is installed. Wait for imagex to complete. Will take minutes to fully mount DVD. That way when I need it in the future I will remember what it was for. I copied the contents of that one as well, but didn't need it.
I figured I might in the future so I went ahead and grabbed it now. This process will take 60 seconds or so. Now when the print server asks for the Windows media, just browse to that new folder you created and it will find the files needed. I just thought I would put all the steps together for people that might not have it installed, but do have the media available. Wednesday, January 27, PM. I have this scenario my printer server is windows standard edition x86 i successfully add the x64 driver on my server but when i try to access shared printer installed on my 2k8 x86 server on my windows 7 Enterprise x64 no driver is available.
The driver comes as a self-extracting. So, I have extracted the files to choose the correct driver. That part works fine. After I choose the correct driver, it then prompts me for the location of the x86 ntprint. Have a look at this file from microsoft it seems to give some hints download. Worked for me, annoying, but doesn't seem like a hack.
Bill Dillon Bill Dillon. Rocket Rog Rocket Rog 1. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related Hot Network Questions.
Question feed. Super User works best with JavaScript enabled. I have downloaded a x36 driver for a Brother printer, but after going thru the whole drill of adding and selecting the driver I get an error message telling me to install it from a reference 32bit machine.
Seems like a lot of hoops to jump thru, particularly since the usual workstation is likely to be 32bit. Thank you, Bill Barnes. Monday, July 6, AM. Because of the fact that the majority of MS installations today aren't x64, I think it would've been hugely benefitial due to migrations and phased rollouts, etc for Microsoft to have included the x86 print drivers on the x64 server.
Unfotunately since they did not, users are required to use an x86 operating system or files from one to get the x86 drivers installed. Not the most efficient solution. Monday, July 6, PM. Thanks for the answers. I'm burning time on this that's not billable trying to fix a 5-minute operation with hours of research and testing. Fortunately, Hyper-V works great and I have already virtualized the old Win 2K server with its shared printer that works..
I'm installing Xerox signed drivers - 64bit just fine, and using non-certified drivers I can get x86 drivers in for clients , but certain tabs for the clients like Print Preferences are not accessible. Thought it was permissions, but did not prove out, so went on to install the signed drivers on another server to see.
Then ran into inability to install corresponding signed x86 drivers for clients. Local installs on workstations will of course work just fine, but gee I would like to use our fancy new print servers! Even if I can sucessfully get the drivers from Vista or I take it from the info, that I will have to do an install , that the signed drivers will work.
Now I need to check all the other printers to see if they have functional driver problems. Exchange Admin. Tuesday, July 7, AM. An update on this. The problem seemed to be with the Xerox drivers, so I went back to earlier versions and served the printer from a Win bit server. Any version of the drivers on the bit server seem to have a problem with the Preferences tab.
Monday, July 27, PM. Wednesday, August 5, AM. I have the same problem, my server working on Windows Server SP1 x64, and I should install additional drivers x86, the printer is very old, and I make this one: Install printer on server x64, then choose to install additional drivers x86, but system show errors, that could found some files, then i put a Windows Server SP1 x86 DVD, and let the system shoose drivers and files from this source, and then printer are installed succesfully, and works on x64 and x Monday, September 7, PM.
Proposed as answer by mwilliam13 Saturday, February 20, PM. Thursday, December 10, AM. This fixed my WorkCentre driver issue for my x86 clients connecting to the printer share on my x64 WS2k8.
Good job, JulianBlue. Saturday, February 20, PM. Tuesday, August 17, AM. Hi Miles I know this is an old post. Is there some other way I can follow your recommendations? Wednesday, November 9, PM. Has any one else run into this issue?
Tuesday, January 31, PM.
0コメント