Windows Server 2012 R2 Lan Drivers [Extra Quality] Download 64-bit
Lynda Durnil
Turns out that the application doesn't have a 64-bit ODBC driver to access its internal data and can't use a 64-bit SQL Server ODBC driver to export its data to SQL server. It does include and install a 32-bit ODBC driver, but it installs it as a User Data Source, not a System Data Source, meaning that my windows service that runs the live collection isn't able to find it. I'm also not able to create a System DSN since the Data Sources admin console can't find the installed driver.
I'm going to start rolling out our first 64-bit Windows 7 machines soon, and I'm making sure that everything will work with our existing print server. Our print server is a 32-bit Windows Server 2003. I'm running into some snags getting the HP print drivers to work. For our other printers and plotters (Canon, KIP), I just had to add the 64-bit drivers using the Print Management console and just browsing out to the specific INF files when it asks for a disk. However, the HP drivers are only offered as an executable installer that won't run, and are also supposedly built in to the operating system. Since my print server is 32 bit, it doesn't have the 64 bit drivers for the LaserJets or DesignJets, so I can't add them to the Win7 workstations. Windows 7 should already have them, but when I try to add the printer it says it can't find the drivers.
Once you have the network printer showing in Printers and Devices on the win7 64 workstation, open the printer properties of the network printer, go to the sharing tab, additional drivers and check the 64 bit box. it should "pull" the drivers from your win7 64 workstation backwards (IMO) up to the server and install them there where they need to be so tht other win7 x64 workstations can find, download and install the driver when they connect to it.
Sounded promising to put the drivers on the local machine first, but for some reason it didn't like that. I checked and rechecked to make sure i'm using the right packages from HP, but i still won't let me add the printer from the print server.
I opened the print management console from the Win7 workstation and then connected to the print server through the management console. I was able to load the drivers from the local temp files, but I still can't install the printers. I loaded both the specific LJ8150 and universal drivers, but I still get the "No Driver Found" error when I try to add the printer.
I went through this myself. I would strongly recommend using a 64bit print server. It is much easier to install a 32bit driver on a 64bit server than the other way around. It took me days of troubleshooting trying to add 64bit drivers for a few HP Laserjet printers to a 32bit Windows 2003 server.
As Birdman posted, once you find the INF files and put them in a folder somewhere on your print server, you can add them through Properties box on the individual printer. I had to do this with a CLJ9500 when we started using 64-bit clients. The 32-bit drivers were already installed.
So far i've only been able to add them to the local computer. So far i've had to install the universal print driver locally on the workstation, i still can't get the drivers to pull from the print server.
When i tried doing this, it tells me that the folder doesn't contain a compatible driver and then says to make sure my driver is designed for 32-bit windows, as my print server is 32-bit. However, i know it's a 64-bit driver, it's not supposed to be designed for 32-bit.
I would also agree that the print server works best now a days to be on a 64-bit machine. We have alot of engineers running high end 64-bit workstations so we have been fighting print drivers for a while. I have felt your pain.
they work when you have to use them but in general if you can't find them you have to use the windows update method in win7 to get them ... and then can't load them to the server worth a darn... (except the 1st / 2nd posters method of backing up the drivers and moving them - that will work just a pain)
Important: you will need to use the correct installer for your operating system. The Windows 10 installer works on Windows 10 and Windows Server 2016/2019. The Windows 7 installer will work on Windows 7/8/8.1/Server 2012r2. This is because of Microsoft's driver signing requirements are different for kernel-mode devices drivers, which in our case affects OpenVPN's tap driver (tap-windows6).
df19127ead