OfficeJet Pro 6968 driver for Windows Server 2012 R2 for Print Services

[bgilmore]

So I downloaded the driver from the HP site OJ6960__Basicx64_1979.exe and discovered that it didn't just self extract drivers, it also included an installer. Don't really need this as I am setting up 12 of these printers on my Server 2012 print server. But I went ahead and used it anyway just so I could get the drivers extracted. The driver errors out as being incompatible with my operating system. I selected Windows Server 2012 in the drop down on the driver page and clicked "change" to make that the operating system that it would show me drivers for. I have been passed around HP support over the phone for close to an hour. I just need a driver that will work for me.

[ShlomiL]

Hi,

You should not use the installer for a server but install it from the command line as listed on its description:

The installers for enterprise solutions must be extracted from the web pack and run from a command line. Enterprise solutions are a subset of the full HP printer installation and are provided for corporate customers. For detailed instructions, see the HP PageWide series IT Administrators Install Guide

You may find the IT Administrators Install Guide below:

http://h10032.www1.hp.com/ctg/Manual/c03665747.pdf

Yau may also use the Add Printer wizard instead from Devices and Printers screen if you only need print capabilities, from teh printer selection box click Have Disk and browse to the extracted installation folder.

Regards,

Shlomi

[bgilmore]

Thank you for your reply. I worked it a different and in my opinion, simpler way. I used 7-Zip to extract the .exe and pointed to the correct .inf file while adding the printer in Print Management. Not one to shy away from command line or PS, but this seems really unneccesary. There was a very simple set of drivers for the M477 that I added to the server the other day. You extract the .exe and you have a folder with drivers to point to. No command line. No hassel. Not sure why all the drivers for Windows Server can't be done this way. But again, thanks.