New RPM 7 is now available — see what’s new →

Differences between the RPM service account and a desktop user

RPM Remote Print Manager® (“RPM”) runs as a Windows service. Windows starts it with the other services, moments after boot, whether or not anyone is logged in. A service runs under its own Windows account, and that account can reach different things than you can as a logged-in desktop user.

Which account RPM runs as

RPM 7 runs as its own limited Windows account, NT SERVICE\rpm. It can write RPM’s settings folder, but nothing else on the computer unless you allow it. When you upgrade from RPM 6, setup moves the service to this account and grants it access to the folders and programs your configuration already uses.

RPM 6.2 and earlier ran as the Windows LocalSystem account, which can read and write nearly every local file.

So a folder or program that works when you try it at your desktop may still fail when RPM uses it, because RPM isn’t you.

Local folders and programs

When an RPM 7 action writes to a local folder, or runs a program that needs files, grant NT SERVICE\rpm access to them. The RPM user interface helps:

  • When you save an action, transform or queue that names a local folder or program, the RPM UI on the RPM computer offers to grant the access it is missing.
  • File > Service Folder Access checks every folder and program in your configuration and offers to grant what is missing.
  • You can also grant access yourself, in the folder’s Properties > Security, or from an administrator command prompt:
icacls "D:\Output" /grant "NT SERVICE\rpm":(OI)(CI)M

Shared folders and printers

Shared printers and folders on other computers are designed by Microsoft to be used with user rights. The dependable way to reach them from RPM is to give the action credentials for an account that has access. RPM then reads and writes as that account. The account needs the Log on as a batch job right on the RPM computer.

Without credentials, RPM 7 reaches a network folder as the RPM computer’s own account (for example CONTOSO\RPMSERVER$), so you can also grant that computer account access to the share.

Now and then we see RPM configurations that print to a shared printer such as \\computername\printername directly. Please use credentials for these, even when a script you run from a filter action copies output to the printer. The filter action setup has a Credentials setting for this.

Programs that need the desktop

Some programs and printer drivers expect someone at the screen. RPM’s Interact with Desktop option shows them on the desktop of a logged-in user. It needs credentials, and in RPM 7 it needs the RPM service to run as LocalSystem.

Don’t make that change in the Windows Services console. The service would keep the limited account’s short list of Windows privileges, and interactive jobs would fail with “Unable to get user token”. Instead, open a Command Prompt as administrator in the RPM program folder (the one that holds RpmSrv.exe) and run:

RpmSrv.exe --install --local-system
net stop rpm
net start rpm

The service then runs as LocalSystem with the privileges interactive programs need, and upgrades keep it that way.

If you already switched the service to LocalSystem in the Services console and interactive jobs fail with “Unable to get user token”, remove the leftover privilege list instead, from a Command Prompt run as administrator:

sc privs rpm ""
net stop rpm
net start rpm

Use sc for this, not the registry: deleting the service’s RequiredPrivileges registry value stops the service from starting, with “The data is invalid”.

Running RPM as a user account

It is possible to run the RPM service as a regular user account, and some do, but it causes far more problems than it solves and we strongly recommend against it.

Continue to: Migrating →