Sharp Printer Drivers For Windows 10

[Mariu Carlton]

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.

We are an AzureAD only environment. All of our printers are accessible via add a printer. However, several printers are Sharp MFD which Windows Update does not have drivers for. So these printers cannot be installed by the end user. The driver installer from Sharp seems to force the user into picking a printer during setup which breaks any automation installation from what I have tried so far (using Win32 App deployment). I really do not want to use powershell and even as such, not quite sure how that would even work. Are there any other suggestions on getting these drivers installed so that the end user can install these printers?

and you can use to look up the GPO settings to get the registry keys. When you gathered everything you need write a PowerShell script to deploy the settings/regkeys and the users are able to install printer drivers.

Thanks for the response Oliver. However that would not solve the issue. The problem is not rather the user had permssions to install the printer but because there is no driver from Windows Update that matches during install it fails. Right now, I have to go download the setup.exe and run for the Sharp printer then it will install

Sharp printers are generally multifunction printers (MFPs) and can perform tasks such as printing, scanning, copying, etc. Depending on how the printer is configured configured, it may require an account code be entered to copy or print.

To begin on either Windows or macOS, the proper Sharp printer drivers must be installed from Sharp's website or through Software Center prior to configuring any computer specific settings. To download and install drivers, the use of Administrator rights may be required.

I have a very strange problem with my network printer (SHARP MX-M354U). The printer is connected to my local network and i can access its configuration web page using it IP address. I am running window 10 and even though windows could not automatically detect the printer when i try to add it, i have added it manually to my printers list (at which point windows successfully connect to the printer and detected and install the necessary drivers for it).

Now when it try to print to it, it silently fails. The printer job dialog doesn't show any errors and it appears it has successfully sent the print job to the printer. The printer configuration is using RAW print with port 9100, in a desperate attempt I tried to open that port in windows firewall setting with no luck.

I have the same issue when i try to use the printer from Mac OS X Yosemite. In this case, the printer is automatically detected and added to the printers list but could not print to it. No errors or warning as before.

One possibility, especially for the Mac. The Mac will automatically install the PostScript driver. In your printer, PostScript is optional. The standard PDL is PCL6. Does your printer have the PostScript option installed?

I was previously a fan of the prndrvr.vbs, prnmngr.vbs, and prncnfg.vbs scripts that have existed natively in Windows for many years. My current issue with these is a result of my use of System Center Configuration Manager. When installing applications for the entire system (all users), SCCM will run installs as the Windows built-in SYSTEM user. SYSTEM is fine for most executions, but some of the aforementioned visual basic scripts will not complete when ran as the SYSTEM user (see post Run Command Prompt as NT AUTHORITY\SYSTEM to test SCCM Applications to learn how to test such things).

Right-click the cert and select All Tasks > Export. Continue through the Certificate Export Wizard using the DER Encoded Binary format and save the cert as something like: Certificate.cer

The specific driver name will also need to be identified. This can be found by using a text editor to open the INF and pull out the driver name string (this can get tricky), so another easier way is to install the printer in a test environment and then look at the driver it uses under Printer Properties > Advanced.

Note that this command only uninstalls the printer and does not delete the printer port. Therefore, this command can be used to uninstall any type of printer, even those utilizing local printer ports.

Using something like SCCM and need to detect if the printer installed successfully? Windows creates a convenient Registry key at: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\Printer-Display-Name

To take things one step further, you can check within that key for the string value Port and ensure it equals the printer IP/hostname that was used to create the port. This can help avoid accidentally detecting other printers that might have the same name but use a different port.

This looks great for IP printers, which will work in some of my cases, but I do have a lot of local printers that are installed via USB that I would like to make the drivers available in software center so I can push the drivers out via SCCM Is there a way to point it to use USB instead of IP address?

Thank you so much for this information. It was very helpful. I am getting an 0X000000c error on the rundll32 printui.dll,PrintUIEntry /Sr /n %varName% /a %varSettingsFile% m f g p command. Do you have any suggestions?

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.

3a8082e126