RPM Remote Print Manager (RPM) is our virtual printer product. RPM can convert incoming jobs to other formats, print the same job to multiple printers, send jobs to a printer and save to disk, and print to multiple trays.
Version: 6.2.0.523Printing should be one click away. but there are so many problems which make printing difficult if not impossible.
License: Free To Try $324.00
Operating System: Windows
Homepage: www.brooksnet.com
Developed by:
RPM Remote Print Manager (RPM) has grown through the years from all the print problems our customers have brought to us. We are here to help you solve your printing problems.
RPM is our virtual printer product. Our customers have been using RPM for 20 years!
RPM as virtual printer
RPM does what you expect a virtual PDF printer to do, and more: convert incoming print jobs to other formats, such as PDF, TIFF and PCL
save multiple documents into a single document print the same job to multiple printers in one pass, send to a printer and save to disk print the same job multiple times, using separate paper trays
RPM as print server
RPM is implemented as a Windows print server. Its core capabilities include: managing your print workflow send print jobs to any Windows printer
send print jobs to any printer on your network using core Windows print protocols, or LPR, or direct with port 9100 archive print jobs to local folders, shared folders, or anywhere via FTP run any local application on your print job send your print job via email as an attachment or in the message body
RPM also provides extensive data editing, manipulation and translation.
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.
Version 6.2.0.523: Resolved issue parsing email addresses in which capital letters were being discarded Added handling to prevent security scanners from tanking the service with messages that are NOT legitimate LPD requests
Version 6.2.0.522: Resolved an exception in print accounting which caused the text print action to fault. Fixed text in message log records.
Version 6.2.0.518: User interface updates: Disabled settings: fixed the issue when a disabled setting was not coming through on the import. Granting user permissions: fixed the issue with user credentials and the "logon as batch" setting.
Version 6.2.0.512.0: Faster job startup New scheme for database access to mitigate problems with security software New way to report days remaining for internationalized date format Message log updates Event log cleanup The 'discard small jobs' setting is extended to AppSocket, Telnet and QueueFolders And more!
Version 6.2.0.506: Resolved string translation issue introduced in build 504 which causes a parsing issue if a backslash is found in search or replace strings, which is nearly everyone using regex. Added additional diagnostic logging to dbpipe due to a customer having issues with it not starting. And more!
Version 6.2.0.499: Raw printing to printer setups using a class driver now works. The RPM and QueueFolders diagnostic logs accumulated over time due to the same case sensitive glitch fixed in 6.2.0.498 If you have critical events when the UI starts, the form now appears automatically. And more!
Version 6.2.0.496: A customer reported that the copy to queue action failed if there was a data extraction transform in the same queue. This has been fixed. We extensively refactored the way we add jobs to the database, and sped that process up considerably. RPM now generates a critical event every 100,000 jobs.
Version 6.2.0.489: Added exception handling to the device tester Improved device tester log messages by adding the device ID Resolved Text Markup to PDF issue where Windows 10 reports 'file not found' accessing the HKey_Current_User registry hive Resolved issue parsing code page aliases
Version 6.2.0.480: Fixed positional data extractions; empty lines in the source file was throwing off the line number logic Text print logging now includes the printer name, which in some instances it did not The device tester now includes a device name or path in more logs And more