Calling server-command from a remote system

KB Home   |   Calling server-command from a remote system

The scripting tool provided with PaperCut called server-command is a very powerful utility that provides access to dozens of scripting server operations ranging from:

  • allocated extra print quota to user accounts
  • changing user settings
  • scheduling/starting backups
  • creating new accounts on demand

It’s often used by administrators in simple scripts such as batch files, shell scripts, or via languages such as VBScript, Python, Perl or Ruby. You can read more about this here:

server-command is a local program and must be run directly on the PaperCut server as a privileged user (for security reasons). The server command may however be called remotely using standard remote command tools. Options include:

Windows (Any):

Use psexec.exe - a remote command program provided by the Sysinternals team at Microsoft. Example use:

   psexec.exe \\papercutserver “c:\Program Files\PaperCut NG\server\bin\win\server-command.exe” disable-printer printsrv1 labprinter −1

Windows 2008 R2:

Use Windows Remote Management Services. An example:

   winrs -r:[servername] -nop -d:”C:\Program Files (x86)\PaperCut NG\server\bin\win\” server-command.exe rename-user “<old_username>” “<new_username>”


Use SSH - a secure remote command/shell program. SSH can be run non-interactively in scripts with the use of an authorized public key added under the papercut account’s ~/.ssh/authorized_keys list. Example use:

   ssh papercut@papercutserver “~/server/bin/linux-x64/server-command disable-printer printsrv1 labprinter −1”

Categories: Scripting


Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on June 02, 2017, at 12:38 AM
Printable View   |   Article History   |   Edit Article