Ricoh Driver Manager Download Extra Quality
Isidora Herline
I've successfully used Intune to roll out customised Ricoh MFP drivers via Intune, and they have worked well for several months. In the process of creating these drivers via their official tool (Ricoh Packager NX), I also installed on my device the 'Ricoh Device Software Manager' tool, which also includes a seperate 'Driver Installer' application. This application has notified me of a minor driver update to my existing Ricoh drivers, which installed successfully.
Has anyone used this tool via Intune before, or would there be a better way to overwrite the existing configured printers other than creating new drivers via the tool and overwriting the existing printer instances?
Influence user print activity through pre-configured print drivers, which reduce waste and print costs. Configure print drivers in less time and package them to enable quick and easy download and installation for users. Extend your admin tools and make working with print drivers easier for you and your users with the Device Manager NX Pro or Enterprise and the Device Manager NX Advanced Driver Distribution License option
We have several networked Ricoh devices. We have been printing to them for years, using a Server2008R2 print server, and drivers I installed back in 2014. I have created a new Server2016 machine, and I am trying to install the Ricoh drivers on this new server. When I run any of the driver installation tools I have found, they cannot find my MFPs on the network. This includes both from the new 2016 server AND my Win10 Pro PC on the same domain. I can open the MFP web interfaces from any machine on the network. I have searched by giving it the IP address, as well as just letting it scan the network. The Ricoh "Device Software Manager" tool can locate ONE of the devices on the network, but not the ones I actually want to install on the server. Any ideas on why the driver install software can't locate the network printers?
Yeah, everything is all on the same subnet. Very simple network config. I was actually able to manually install the printers on the server, but I've been struggling with a communications issue. It now takes several minutes for a small print job to get to the printer, and a multi-page job prints one page, then waits 1 minute, then prints the next page, and so on. So, I wanted to try a clean install, using the "proper" driver installation tools to see if things would improve.
Dous it work when using the "Add Printer Wizard" in control panel. Those setup utilities are not always reliable. And if using a driver for a machine that was made before the OS was a lot of times little things like that do not work properly.
Ensure you are using a Standard TCP/IP port, not WSD, and the proper Ricoh driver from the website, not the Ricoh Class Driver included with windows. Slow print is common with the WSD port. The best way to add printers is with the Add Printer Wizard, Add Printer, Local Printer, create TCP/IP port, Have Disk to get driver.
Update 3 December 2018: So far, the furthest progress I've made has been with CraftyB's answer. Here is the output from his PowershellOutput instructions. It identified the .inf file for my printer as prnhp001.inf. I don't think this is a "default driver" as some have suspected. Also perhaps worth noting is this is purely a network printer on my home network.
Update -- Mission Complete. Using CraftyB's answer, I took the entire folder indicated in the "InfPath" results of his 2nd block of code and browsed there at the "Have Disk" prompt during install and it worked. For those who many not have a working pc to harvest the driver from in order to get their laserjet5 working on Windows 10, I provide them here.
The driver file is "upd-pcl5-x64-6.1.0.20062.exe", I could not find it on HP's support site, so I did a search, and found several locations listing this universal driver set. I found a site that didn't charge, but did plant a cookie ... which I will now have to elliminate. BUT, IT WORKS!!! I can't guarantee that it will work for you, but I suspect that it will work for several PCL printers "no longer supported".
So on the Fiery, there is an 'optional' module that can be installed in the Fiery software manager. The module is named something like Fiery JDF Integration. Anyways, it had to be installed for my customer and it allows some of the JDF to be updated inside the Fiery unit for compatibility. After I did this for QDirect compatibility we found that jobs would come over and print, and then and ERROR would appear. This was because at the end of the JDF a communication was trying to be sent to 'close out' the job. Inside this Integration module there is an option that says 'Automatic' Close or 'Manual' Close. I set it to Manual and all the errors went away and jobs were reprintable etc.
For the new customer of ScanSnap, the latest software "ScanSnap Home" is recommended. ScanSnap Home is an all-in-one software to easily manage, edit and utilize various types of scanned data from documents, receipts, business cards, photos and much more in addition to driver.
If you have been given a printing code by your departmental manager, click the checkbox for enable user code and enter the code as shown. If your department has restricted printing on the device, you will not be able to successfully print without a valid printing code saved here.
You will need to have already downloaded the Ricoh printer driver from the website. Downloading the latest Ricoh printer driver for your Ricoh Printer / Ricoh Multifunctional Printer will ensure the most reliable printing results. You can download the latest Ricoh printer drivers using the links in our Driver Download tutorial.
df19127ead