Special considerations on Terminal Server/CITRIX
PaperCut works well on Microsoft Terminal Server (2000, 2003, 2008+) and CITRIX servers and a number of organizations are successfully using it to manage their printing and quotas. As a general rule, we recommend deploying PaperCut server software on a separate server (e.g. a print server) other than the terminal server itself. The reason for this is that Terminal Server / CITRIX systems can be very resource hungry and leave little resources left for PaperCut's use. This is however not too much of an issue with good high-spec hardware.
Sites planning on using advanced PaperCut features such as the account selection popup, may need to make a minor system configuration change. This is particually true for sites running versions prior to version 8. Version 8+ uses more advanced logic and in most cases will work "out of the box" in all environments.
By default, PaperCut uses the client's IP address to help match print jobs to the client (the client software running on the user's screen). Under a terminal server, this assumption is often not valid as a multiple users can be logged in under the one IP address at any one time. The symptom is that the account selection popup, or other popup messages may appear on multiple terminals at once. The solution is to change the system configuration as follows:
admin user.
Options and select the Config Editor (Advanced) Action from the left set of Action links.
client.allow-match-on-machine-or-ip-only
N (no) and press the Update button.
If you require further assistance, please don't hesitate to contact support via our email support queue.
If the PaperCut client software is set to automatically start under CITRIX via the Run registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce
this client software may prevent CITRIX sessions from correctly terminating. CITRIX has acknowledged this problem and the topic is discussed in detail at:
The solution is to add a new registry key and this is discussed at the bottom of the page linked above.
Categories: Implementation
Keywords: terminalserver, terminal, remote desktop, ts, MetaFrame, Presentation Server
