Sharp Printer Drivers For Windows 10 64-bit

[Taneka Tarring]

Itsounds like the drivers for the Sharp printers are not included with Win7 so need to be installed - by connecting to a shared printer the drivers are downloaded from the print server. Is there an .msi of the driver you could deploy with a GPO?

Since there are probably hundreds of different printers and drivers in the marketplace, it is not feasible to preload or preinstall each driver on to the client machine before deploying the printer, that really defeats the purpose of simplifying printer deployment.

so I installed the correct drivers on my windows 7 laptop, cranked up Print Management, connected to the windows 2008 print server, uploaded the correct driver to the server, and was able to push out the printer with GPP successfully after that.

Captain Kirk, can you explain how you uploaded the driver to the server? I installed the exact same driver on my laptop as the server, then as a test, I removed the driver from my laptop and did a gpupdate /force and the driver from the server did not come down to the laptop. Thanks.

1/12/2012 6:12:40 PM

After you add print servers to Print Management and create printer filters to display and easily select different types of printers, you can begin managing these printers and print servers. Printer management tasks that you can perform using Print Management include:

You can also remove printers from AD DS either by clearing the List In The Directory check box or by right-clicking the printer and selecting Remove From Directory. You can remove printers from AD DS to prevent users from installing them manually by using the Add Printer Wizard from the Printers Control Panel item.

After a printer is published in AD DS, users can search AD DS using the Add Printer Wizard and manually install a printer connection on their computers. This allows users to print to a network printer.

3. Managing Printer Drivers

If client computers need additional printer drivers, you can use Print Management to add them to print servers, and you can also remove print drivers from print servers when clients no longer need them. For example, you can add additional printer drivers for network printers to support 64-bit Windows client computers by following these steps:

Click Windows Update if this is available to display a list of printer drivers available on Windows Update. Note that it can take several minutes for the list of printer drivers to be downloaded from Windows Update the first time that this is done.

Using the Add Printer Drivers Wizard from Print Management running on Windows Server 2003 R2 or later lets you add additional x86, x64, and Itanium drivers for versions of Windows prior to Windows Vista.

Using the Add Printer Drivers Wizard from Print Management running on Windows Vista or later lets you add Type 3 (User Mode) printer drivers only for x86, x64, and Itanium systems running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2. To add additional drivers for earlier versions of Windows, use Print Management on Windows Server 2003 R2 or later versions instead of Windows 7.

When you use the preceding steps to remove a printer driver from the local print server (when using a Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 computer as a print server), the driver package is uninstalled but remains staged in the driver store. Windows will pick and install the driver again when a compatible TCP/IP or Plug and Play printer is added to the system. If you selected Remove Driver Package instead of Delete, however, Windows will remove the package and not use the driver again.

To save detailed information concerning each driver installed on a print server and import it into Microsoft Office Excel for reporting purposes, follow the preceding procedure to add the columns desired and then right-click the Drivers node and select Export List. Save the detailed driver as a comma-separated (*.csv) file and import it into Office Excel. The Export List command is available for any node in an MMC snap-in

Thanks Captain Kirk. So I completely removed the printers and drivers from the print server I had set up, then added the printers to my laptop. Followed the directions to get the drivers on to the print server, then I removed the printers and drivers from the laptop. I ran a gpupdate /force and got nothing but the same warning in the application log as I stated in my first post.

I am having absolutely no luck getting the Sharp MX-4101N network printer drivers to work on 64-bit operating systems (Windows 7 and Windows 8). I had already installed some Windows 7 32-bit workstations a couple of years ago and they continue to work just fine. I had also saved the 64-bit drivers on hand for future installs.

However, neither those older drivers, nor the brand spanking new drivers from Sharp are working. I tried every possible download available from Sharp for this printer, the PCL6 driver, the universal driver, the WHQL driver, on both the Windows 7 and Windows 8 machines. In all cases, the driver installs fine and the printer is visible in the control panel. The universal driver also requires some additional config to connect to the specific printer model, which I also did (this is detailed in the accompanying PDF installation instructions).

But when I try to print, the MX-4101N's fan kicks up to high gear as if it received the data and is getting ready to print, and then... nothing. No error in Windows, no error on the printer screen, nada. Every printer driver reinstall was preceded by a complete uninstall of the previous drivers, so I'm at a loss as to what to do next. Any suggestions?

Generally the Postscript driver works best for this particular MFP product. But if you can't get any drivers to work, you can actually use HP drivers with it. I found that if you want full functionality from this printer, though, you need .NET 4.0 as well as the mfr's drivers.

One other thing I found with these is that when you install the new driver, the old one remains. In Windows 7, open the Devices & Printers folder. Click once to highliight one of the installed printers. Up at the top, you should now see "Print Server Properties"; click on that. Click on the Drivers tab there, and remove all the Sharp drivers. Restart your system and install the Sharp postscript driver from scratch.

The MX-4101N may require the PostScript option to be installed. It will dump any print jobs sent to it without the MX-PKX1 PostScript Kit installed (a 'key' to enable the functionality).The symptom you described is consistent with trying to use a PostScript driver on a non-equipped Sharp MFP.

Without the PostScript (PS) option installed, the printer will behave as you've described. If your Windows 32-bit POSTSCRIPT driver worked, then most likely the PS option is installed on the MX-4101N already.

Public printers in the Physics Department are set up via print servers. All the public Sharp printer-copier-scanner devices are on their own print server called PCOUNTER2.physics.ox.ac.uk and all the other printers are via PRINTSERVERX64.physics.ox.ac.uk for 64 bit operating systems.

Pre-install the drivers via Printer Drivers installer utility in Physics Self-Service or download the driver from the Drivers section below and install using a privileged account (Administrator or LocalAdmin).

Devices signed in using a local account see Help section to add your Physics Credentials to Credentials Manager.

Solution Click on Start > type Credential > Click Manage Windows Credentials > Select "Add a windows Credential" repeat this for both Internet or network address, entering the following details below.

Install printer drivers via Printer Drivers installer utility in Physics Self-Service. Or download the drivers and unpack in a suitable location. RunAs administrator driverinst.bat to install.

3a8082e126