1

Hello,

I’m looking to push out an .MSI print driver using Ricoh Printer Driver Packager NX. This will be pushed out to multiple sites with differently-named printers and I’m deploying printer mappings separately.

During setup, the Port Setting is required:
image

I don’t want to specify a hostname or IP as I’d just like to get the driver installed rather than have it linked to a specific unit. If I enter the driver name as it appears in the .inf file, will this be a benign way to bypass this port setting screen, or is there a better approach?

2 Spice ups
2

Can you get the driver in a ZIP file instead of and MSI? Or just unpack the MSI on a machine and extract the drivers into a file you control.

Then you could use other tools like powershell to install just the driver onto whatever machines you want.

3

Hi Molan,

I can zip the files as it’s the Packager that converts the contents to an .MSI file. Incidentally I have other printers deployed in this way but they’re able to install/uninstall cleanly with the port setting just named as the driver from the .inf file.

This is more to just avoid bloating the printer and scanners list with a driver rather than a printer. I’d rather keep the .MSI/Ricoh Packager method as it does seem to be more reliable than packing .ps1 files and running an install command on that powershell script.

1 Spice up