Designed for Windows NT/2000/XP
Originally designed for Windows 2000, with backward compatibility for Windows NT, RPM Elite has been enhanced and updated to include support for all Windows NT-based platforms, including Windows NT, 2000, and XP. RPM Elite installs at the kernel level and runs as a native service.
Supports 99 printers - Access up to unlimited
Initially, RPM Elite supports 99 printers; however, this limit can be increased up to unlimited. There is no limit on the number of print queues; the limit refers to the number of Windows printers. Note that filter queues do not use printers.
Brooks License Manager
The redesigned license manager has been implemented to enhance ease of use. A license wizard guides users through a simple, step-by-step process to unlock the software and any installed modules, such as an increased number of printers. License manager allows unassisted reinstallation by generating the same serial number each time it is installed. Web-unlock can now connect through a proxy server/firewall using existing proxy server configuration, or if need, a separate proxy server configuration is also provided.
|
Integrated with Windows security
RPM Elite is fully integrated with Windows security. System administrators can control access to RPM through the "DCOM Configuration" utility in Windows. Configuration changes can be controlled using the Windows Registry (Regedt32.exe) and incoming print jobs can be secured with the NTFS file system.
Customize processing through COM filter interface
To facilitate custom integration with other applications, RPM Elite provides an external COM interface to give integrators unlimited customizing possibilities. Using this interface, developers can create applications to perform additional processing on print data. Interfaces are also provided so that events and job status can be passed back to RPM.
Remote Print Administrator
RPM Elite provides the ability to administer queues, jobs, and other settings remotely. This remote interface, called Remote Print Administrator, requires Microsoft IIS be installed on the RPM host and Microsoft's Internet Explorer browser can be used as the client interface. With this interface, RPM logs can also be viewed for remote troubleshooting.
|