Introducing RPM Remote Print Manager
RPM Remote Print Manager® (RPM) is print server software for Windows platforms, which offers many print workflow capabilities. Brooks Internet Software has published and supported this software since 1995.
RPM supports the LPD and telnet protocols (or port 9100) like other network print servers. We believe you will find our support for these protocols to be complete. Customers have been relying on us for better than 20 years. Read more on network connectivity
One of RPM’s important distinctions is its ability to bridge systems which can't communicate with each other. Almost every computer system can print but not every system can support all you need to do. RPM has a track record of helping customers and partners make that work. Read more on systems we have successfully bridged.
We overheard a customer calling RPM a virtual printer; it turns out that we agree. When we tracked down the definition, we found that it offers a small tour of RPM’s core capabilities. Read more about virtual printers.
Our quote of the day on virtual printers:
“ you print to a virtual printer exactly as if it were a printer, but the result you get is open ended. ”
RPM can, of course, pass your data unchanged to an output of your choice. Yet, one of the tasks people rely on us for is making changes to their data. We can add, remove, search and replace, generate banner pages, and translate to a new format. Read more about our data translations.
RPM produces multiple outputs
RPM offers many outputs including printing, running a local program, email and more. One thing that sets RPM apart is that it can apply any number of outputs to a given job. For instance, you can output to several printers from different vendors, at the same time archive the print job as a PDF.
Within RPM we can append your print job to an existing file. Using a third party program which comes with RPM, we can even merge a PDF file into an existing PDF. RPM can print and save a job to disk in one pass (useful when importing into a document management system, for instance).
There is no limit except how much you want to do, depending on your RPM license.
The LPD print protocol provides information about your print job from the requesting program. RPM gives you access to this data when you configure your outputs. This page discusses how that works.
RPM can also extract text data from your print job (depending on what you send) and use that data. You could pull an email address from the print job and send the job to that address. A more common approach might be to use an account name for an archive file name. You can read more about controlling outputs here.
RPM gives you a lot of flexibility for processing your print jobs. The setup we make available in a single queue can help you solve a lot of problems.
But, we also provide the means to send a print job to another queue. You can think of it like programming a manufacturing system. Do a lot of work at one station, then send the unit to the next station to do more. Our example of printing and saving a PDF copy works like that. You can read about it here.
RPM Elite recently gained the ability to extract text data from the current print job and use the values as LPD metadata. We talked about this topic in the page RPM uses your print job to control outputs. In many actions you have the opportunity to use metadata, for instance as an archive filename or email address. Now you can use data imported directly from your print job. You can read about data extraction and be sure to check out the video.
If you have read our section about print workflow you've seen how the Copy to Queue action can be used to stage processing, grouping work to keep you from repeating the same tasks over and over in various queues. Dynamic job routing takes that initiative one step farther by letting you use actual LPD metadata as part of the queue name. We give examples using this with and without data extraction.
RPM is optimized to help you accomplish the print workflow you need. We also offer customization services where we develop additional software that works with RPM to accomplish what you need. We have been offering this service since 2010 and we have documented a number of the projects we have delivered for customers like you.
If you are a Python developer or have access to one, we have published an API which we host on github. Our user interface is written in Python and uses this same API. Our customization projects work the same way.
Windows version support
RPM 6.1 supports these versions of Windows: Vista, 7, Server 2008 (including R2), Windows 8 and 8.1, Server 2012 (including R2), and Windows 10. Support for Windows XP and Server 2003 has been dropped, so we no longer test new RPM versions on these older versions of Windows.