RPM 7 - Installation Guide

Log in as Administrator, or another account with administrative rights, before you run setup.

Minimum requirements

• A 64-bit version of Windows or Windows Server that Microsoft still supports. RPM 7 is 64-bit only.
• Processor, memory and disk space depend on how many jobs RPM receives, how large they are, how complex your queue configuration is and how long you keep jobs, so we don’t give fixed figures.

Setup installs everything else RPM needs: the Firebird 5 database server, if it is not already installed, and the Microsoft Visual C++ runtime.

Install RPM

1. Download RPM Elite or RPM Select from our Downloads page.

2. Run the installer and choose the language for setup.

3. License Agreement: Read the end-user license agreement. Choose I accept the agreement and click Next. Setup does not continue unless you accept it.

4. Firebird Admin User: You see this page only if Firebird is already installed on the computer. Setup uses this account to create RPM’s own database user. If you have changed the Firebird SYSDBA password from its default, enter it here, then click Next.

5. Select Destination Location: We recommend the default, C:\Program Files\Brooks Internet Software\RPM. Click Browse to choose another folder.

6. Settings Folder: This is where RPM keeps its database and settings. The default is C:\ProgramData\Brooks Internet Software\RPM.

7. Management Access: Choose who may manage RPM on this computer:

   • Members of the local “RPM Administrators” group (recommended)
   • All users of this computer, as in earlier versions of RPM

   Anyone who can manage RPM can make it run programs and write files with the RPM service’s access, so allow only people you trust. Administrators can always manage RPM.

8. If you chose the RPM Administrators group, enter the accounts that belong in it, separated by commas, for example CONTOSO\jsmith. Setup suggests the account you are logged in with. You can leave this blank and add members later in Computer Management (Local Users and Groups), or from a command prompt:

   net localgroup "RPM Administrators" CONTOSO\jsmith /add
   

9. Ready to Install: Review the summary and click Install.

10. Completing Setup: If setup asks you to restart Windows, choose Yes. Otherwise, choose whether to start the RPM user interface and click Finish.

What setup does for you

• Installs Firebird 5, if it is not already installed. On a new installation, setup limits Firebird to connections from this computer. To manage RPM from another computer with the remote user interface, turn remote access back on in RPM under Settings > Security > Remote Firebird Access.
• Offers to replace a default Firebird password. If Firebird was already installed and still uses the default SYSDBA password, setup offers to replace it with a random one that RPM keeps for its own use. Other software that uses that Firebird server with the default password stops working until you give it the new one. You can set a password of your own later under Settings > Security > Change Firebird Password. See Securing Firebird.
• Installs the RPM service to start automatically, running as its own limited Windows account, NT SERVICE\rpm. If an action can’t reach a folder or program, choose File > Service Folder Access in the RPM user interface to find and grant what is missing. See the RPM service account.
• Adds a Windows Firewall exception so that RPM can receive print jobs.
• Offers to update an older Firebird 5 to the version that ships with RPM. A silent install takes the update automatically.
• Adds Start menu shortcuts for RPM Elite or RPM Select, the Brooks License Manager, and Reset RPM Elite Window Layout (or Select), which recovers a window that opens off-screen.

You don’t need the RPM user interface open, or anyone logged in to the computer, for RPM to receive and process print jobs. To begin setting up queues, open RPM from the Start menu.

A new installation runs as a trial. To activate your license, open the Brooks License Manager from the Start menu. Without Internet access, see Manual license activation.

Upgrading from an earlier RPM

Back up your RPM installation first. Then run the RPM 7 installer on the same computer. Setup recognizes the existing installation, asks whether to continue with the upgrade, and skips the folder and settings pages.

• RPM 6.x upgrades in place. Setup backs up your RPM database, uninstalls Firebird 2.5, installs Firebird 5, and restores your data into it. Your queues, actions and settings carry forward, and stored passwords are re-encrypted with the new installation’s key. A 32-bit RPM 6 is moved to the 64-bit build at the same time.
• Other software on Firebird 2.5. If you told RPM 6.2 that other software uses its Firebird server, setup warns you before removing Firebird 2.5. That software stops working until it is moved to Firebird 5, or Firebird 2.5 is reinstalled.
• Firebird 3 or 4. RPM 7 requires Firebird 5. Remove Firebird or upgrade it to version 5, then run setup again.
• RPM 5 cannot be upgraded directly. Uninstall it first; that leaves your settings and database in place. Then run the RPM 7 installer.
• The service account changes. An upgrade moves the RPM service from LocalSystem to NT SERVICE\rpm, and grants it the local folders and programs your queues, actions and transforms already use. If you need Interact with Desktop, see Programs that need the desktop.

Moving to a new computer at the same time? See Moving RPM 6.2 to RPM 7 on a New Computer.

Unattended installation

The installer takes the standard Inno Setup command-line switches, such as /SILENT and /VERYSILENT, plus these:

For example:

rpmelite_7.0.0.637_x64.exe /VERYSILENT /ManagementMembers="CONTOSO\jsmith"