Sharp Copier Printer Driver Download
Gwenda Arguin
When users print from these apps to the Sharp copier it causes the job to hang and crashes the print spooler which prevents anyone else from printing. IT needs to go into print queue and clear it. This can happen a few times a day which is very annoying to say the least.
-If a normal domain user prints, the printer crashes
-If a domain admin prints, such as Administrator then the job goes through.
-If the printer is installed as a local printer, it prints without issue.
Our school has the same issue. We have 4 Sharp Copiers and I am constantly having to unhang the print queue by resetting the Print spooler and deleting the print job. We have manually gone into Windows10 and selected Adobe to print pdf files. However, sometimes Windows10 updates occur and the selection is defaulted back to Edge. Please let me know if you have found a resolution to this problem.
It sounds 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.
In case you are still working on this open up the printer and devices section of the control panel. Right click on the printer and select print preferences. (Windows 10 it will be Manage) It will open up what looks like the print driver. Select the Job Handling tab and check Auto Job Control Review. Now every time someone prints a dialog box will pop up with the option to enter a user code, billing code or other form of authentication.
Try removing the driver in the print management screen then reinstall printer. Also look for updated drivers on manufacturers website. Look for additional port settings. adjust printing preferences from control panel. Good Luck!
Why is tray 4 set as custom? Is there an odd sized media loaded there? Many printers and drivers are smart enough to disable functions if they think that the paper may not be physically supported and often a setting of custom will trigger features being locked off. Change the default tray to 5 if that tray works. If they are printing through a server you will likely need to change the defaults there.
The printer driver is configured incorrectly.
The printer driver is not compatible with the installed printer or your version of Windows.
The entry of your printer driver in the Windows registry is incorrect.
Malware has infected your printer driver files.
I can print to the same printer from the MacMini (Monterey) by adding a printer share to my old MacMini (Catalina) using the same printer drivers. This is while the direct route above is going nowhere!
You said Sharp does not have drivers identified as being for Monterey. Many printers that worked fine on Big SUr require updated drivers for Monterey. That seems like your case. Contact Sharp support.
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
I'm having some issues on rebuilt clients installing the drivers for Sharp MX-4012n. There are two policies running. One that installs the drivers and another that has the following script to change permissions:Sudo chmod 775 "/Library/Printers/PPDs/Contents/Resources/SHARP MX-4112N.PPD.gz"
I've seen similar behavior with some Epson printer drivers. A restart of the computer after installing the drivers made this error message go away (for us). I have no knowledge or experience with Sharp printers...
Perhaps this isn't what you're interested in, but we've had enough issues with dealing with this and other CUPS/privilege issues. So, after borrowing several one liners I run the following script at firstboot (or via self-service):
I'm sure that there's a much slicker way to accomplish this, but this adds all users to the lpadmin group and further allows them to install printer drivers via apples integrated utility. I'll admit, I took the easy way out on this one.
Running into this same exact issue with the latest Xerox Fiery drivers. With the older ones I could go into the package and extract the core installer (bypassing their oh so helpful wizard) and then install via script.
The latest drivers are using flat packages so I'm having trouble getting the installer out of it. I've tried capturing the install with Composer but using that is what is giving me the "You need to install software" error once installed.
I get this with everything, including Papercut "Follow Me" printer. We only ever set up to print postscript and load in the right PPD. Is it something to worry about? If it's not, how can you stop it popping up little warning triangles next to the printer name?
In case it helps anyone, the solution for us was to comb through the used PPD for references to all other installed elements (usually in /Library/Printers/etc) and comment out the ones we know we don't care to install.
c80f0f1006