Installing Sharp Printer Drivers

[Ronald Gruzinsky]

Ifyou are a business that needs to install a Sharp printer driver on your Windows PC, you have come to the right place. Installing a Sharp printer driver is an important step in ensuring that your print jobs are done correctly and efficiently. In this blog post, we will explain installing the printer driver with detailed step-by-step instructions.

At some point during this process, you may be asked whether or not you want to enable automatic updates for this driver. If so, you may want to select yes to ensure your device automatically installs future updates on your computer as they become available.

After completing all steps in installation, reboot your computer to make sure that all changes take effect properly before proceeding with any further steps related to printing using this driver software.

At this point, Windows should recognize that a new device has been added and prompt you for further information about it; simply follow through these steps until installation is complete and then proceed with printing jobs as normal using this newly installed driver software.

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.

Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.

This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.

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.

A printer driver is required in order for your computer to speak directly to the physical device, installing a driver is fairly straightforward and should provide the full functionality of your office printers or MFDs.

Your printer driver should now be fully installed on your computer and you should be able to print. We recommend you print a test page at this point to check everything is working. Contact us if you have any problems

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.

3a8082e126