RM CC3 and CC4 Considerations

KB Home   |   RM CC3 and CC4 Considerations

Main.CommunityConnectConsiderations History

Hide minor edits - Show changes to output

June 24, 2013, at 06:04 PM by ian - wording rewrites
Changed lines 3-5 from:
PaperCut has seen issues with environments using RM CC3 and CC4 installations which has caused some different behavior in the way PaperCut can communicate with both the PaperCut secondary server and the user client. This knowledge base covers the issues that have been resolved by doing some small changes.

!!User client notifications aren't showing
to:
PaperCut customers have reported issues with environments that include installations of RM CC3 and CC4. Specifically, communication between the PaperCut Primary Server and Secondary Server or User Client may be impacted. This knowledge base article provides suggested solutions to address these types of problems.

!!User client notifications will not display
Changed lines 8-11 from:
In RM installations, we have found these to be disabled. This means that users will not receive popups relevant to their print job. PaperCut can be configure to use it's own internal popup method, which is sent directly from the user client tool rather than using Windows.

The way to do this is to disable balloon tips in the user client by editing the @@config.properties@@ file associated with the user client. Depending on how you deploy your user client, this can be in a number of places:
to:
RM installations have been found to disable these notifications, resulting in no popups being received by the user about their printing. PaperCut can be configured to use its own internal popup mechanism, which sends notifications directly from the user client tool and bypasses the RM-disabled Windows notifications.

To do so, disable balloon tips in the user client by editing the @@config.properties@@ file associated with the user client. Depending on how you deploy your user client, this can be in a number of places:
Changed lines 26-27 from:
In the configuration file, there will be a config called @@#disable-balloon-tips=Y@@. Please remove the hash from this line and click Save. Once saved, restarting the PaperCut Client will update this configuration.
to:
In the configuration file, there will be a configuration line similar to @@#disable-balloon-tips=Y@@. Remove the hash from this line and click Save. Once saved, restarting the PaperCut Client will update this configuration.
Changed lines 29-34 from:
The RM Network Monitor Service can stop logging information from a [[https://www.papercut.com/products/ng/manual/ch-secondary-print.html|PaperCut secondary server]] reaching the main PaperCut application server.

For the Secondary server to communicate with the primary server the administrator will need to make sure that any Secondary servers are able to communicate (initiate a TCP connection) on port 9191. Administrators should also ensure that any firewall software on the primary Application Server is not set to block any incoming local network traffic on this port.

When the RM Network Monitor Service is running it will block traffic on port 9191, so PaperCut is unable to monitor the print jobs from a secondary server. This seems to only affect Windows 2003 and
Windows XP machines acting as a Secondary server. Typically while the RM Network Monitor Service is running the printers from any Secondary servers will be displayed in the printer tab in PaperCut but no print jobs are logged against them. The RM Network Monitor Service is part of RM Auditor and can typically be found running from:
to:
The RM Network Monitor Service can stop logging information from a [[https://www.papercut.com/products/ng/manual/ch-secondary-print.html|PaperCut Secondary server]] reaching the PaperCut Primary or Application server.

Communication between the Secondary Server and Primary Server relies on unrestricted opening of TCP connections via port 9191. Administrators should also ensure that any firewall software on the primary Application Server is not set to block any incoming local network traffic on this port.

When the RM Network Monitor Service is running it will block
traffic on port 9191, leading to a disruption of communication between the Secondary and Primary servers. Print usage and control provided by PaperCut will be affected. At this time, this behaviour has been reported with Secondary servers running on Windows 2003 and Windows XP. Typically while the RM Network Monitor Service is running the printers from any Secondary servers will be displayed in the printer list in PaperCut but no print jobs will be logged for them. The RM Network Monitor Service is part of RM Auditor and can typically be found running from:
Changed lines 37-38 from:
To resolve the problem either disable the service or contact RM for information on how to force the service to ignore port 9191. There is a RM update (`CC4UPD093) which installs a new version of the RM Network Monitor service. Once this is installed on the workstations, PaperCut will work fine. The update is only available upon request from RM.
to:
To resolve the problem either disable the service or contact RM for information on how to force the service to ignore port 9191. There is a RM update (`CC4UPD093) which installs a new version of the RM Network Monitor service. Once this is installed on the impacted PaperCut secondary servers, functionality should be restored. This update is only available upon request from RM.
Changed lines 8-9 from:
In RM installations, we have found these to be disabled. This means that users will not receive popups relevant to their print job. PaperCut can be forced to use it's own internal popup method, which is sent directly from the user client tool rather than using Windows.
to:
In RM installations, we have found these to be disabled. This means that users will not receive popups relevant to their print job. PaperCut can be configure to use it's own internal popup method, which is sent directly from the user client tool rather than using Windows.
Changed line 42 from:
[-Keywords: RM Education, client popup, RM]
to:
[-Keywords: RM Education, client popup, RM -]
Changed line 5 from:
!!User Client notifications aren't showing
to:
!!User client notifications aren't showing
Changed lines 25-26 from:
In this file, there will be a configuration called @@#disable-balloon-tips=Y@@. Please remove the hash from this line and click Save. Once saved, restarting the PaperCut Client will update this configuration.
to:
!!!Editing the config file
In the configuration file, there will be a config called @@#disable-balloon-tips=Y@@. Please remove the hash from this line and click Save. Once saved, restarting the PaperCut Client will update this configuration.
Changed lines 3-4 from:
PaperCut has seen issues with environments using RM CC3 and CC4 installations which has caused some different behavior in the way PaperCut can communicate with both the PaperCut secondary server and the user client.
to:
PaperCut has seen issues with environments using RM CC3 and CC4 installations which has caused some different behavior in the way PaperCut can communicate with both the PaperCut secondary server and the user client. This knowledge base covers the issues that have been resolved by doing some small changes.
Added lines 3-4:
PaperCut has seen issues with environments using RM CC3 and CC4 installations which has caused some different behavior in the way PaperCut can communicate with both the PaperCut secondary server and the user client.
Changed lines 34-35 from:
To resolve the problem either disable the service or contact RM for information on how to force the service to ignore port 9191. There is a RM update (CC4UPD093) which installs a new version of the RM Network Monitor service. Once this is installed on the workstations, PaperCut will work fine. The update is only available upon request from RM.
to:
To resolve the problem either disable the service or contact RM for information on how to force the service to ignore port 9191. There is a RM update (`CC4UPD093) which installs a new version of the RM Network Monitor service. Once this is installed on the workstations, PaperCut will work fine. The update is only available upon request from RM.
Deleted lines 35-43:





!!Subheading

TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous

Changed line 37 from:
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
to:
''Categories:'' [[Category.Architecture|+]], [[Category.User Client Tool|+]]
Changed line 39 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: RM Education, client popup, RM]
Changed lines 4-5 from:
CC3 and CC4 installations have been found to disable balloon notifications. The PaperCut user client uses two methods of communication to send messages such as 'Low Toner' and 'Printing Denied' to the user client; winpopup, and balloon notifications.
to:
CC3 and CC4 installations have been found to disable balloon notifications. The PaperCut user client uses two methods of communication to send messages such as ''Low Toner'' and ''Printing Denied'' to the user client; winpopup, and balloon notifications.
Changed lines 11-12 from:
The config file for these installations can be found on the PaperCut application server under @@[app-path]\client\win\@@
to:
The config file for installations using the local cache install option can be found on the PaperCut application server under the following path - @@[app-path]\client\win\@@
Changed lines 23-24 from:
In this file, there will be a configuration called #disable-balloon-tips=Y. Please remove the hash from this file and save it. Once saved, restarting the PaperCut Client will update this configuration.
to:
In this file, there will be a configuration called @@#disable-balloon-tips=Y@@. Please remove the hash from this line and click Save. Once saved, restarting the PaperCut Client will update this configuration.
Changed lines 23-31 from:
In this file, there will be a configuration called #disable-balloon-tips=Y

Can you please
remove the hash from the start of this configuration file, then restart the PaperCut Client running on that test PC?

What we are doing here is disabling balloon tips for PaperCut altogether
. This forces us to use a popup window to display the message rather than a balloon notification.



to:
In this file, there will be a configuration called #disable-balloon-tips=Y. Please remove the hash from this file and save it. Once saved, restarting the PaperCut Client will update this configuration.
Changed line 3 from:
!!!User Client notifications aren't showing
to:
!!User Client notifications aren't showing
Changed line 10 from:
!!pc-client-local-cache.exe
to:
!!!pc-client-local-cache.exe
Changed line 13 from:
!!pc-client.exe
to:
!!!pc-client.exe
Changed lines 16-20 from:
Windows - @@[app-path]\client\win\@@
Linux - @@[app-path]\client\linux\@@
Mac - @@client\mac\PCClient.app\Contents\Resources\@@

!!pc-client-local-install.exe
to:
* Windows - @@[app-path]\client\win\@@
* Linux - @@[app-path]\client\linux\@@
* Mac - @@client\mac\`PCClient.app\Contents\Resources\@@

!!!pc-client-local-install.exe
Changed line 32 from:
!!!RM Network Monitor Service
to:
!!RM Network Monitor Service
Added lines 3-31:
!!!User Client notifications aren't showing
CC3 and CC4 installations have been found to disable balloon notifications. The PaperCut user client uses two methods of communication to send messages such as 'Low Toner' and 'Printing Denied' to the user client; winpopup, and balloon notifications.

In RM installations, we have found these to be disabled. This means that users will not receive popups relevant to their print job. PaperCut can be forced to use it's own internal popup method, which is sent directly from the user client tool rather than using Windows.

The way to do this is to disable balloon tips in the user client by editing the @@config.properties@@ file associated with the user client. Depending on how you deploy your user client, this can be in a number of places:

!!pc-client-local-cache.exe
The config file for these installations can be found on the PaperCut application server under @@[app-path]\client\win\@@

!!pc-client.exe
The config file can be located in the folder where this executable is running from. If it is installed locally on computers it will need to be edited for each PC. If it is being run from the server, please edit the @@config.properties@@ file on the server. Locations for each operating system are below:

Windows - @@[app-path]\client\win\@@
Linux - @@[app-path]\client\linux\@@
Mac - @@client\mac\PCClient.app\Contents\Resources\@@

!!pc-client-local-install.exe
The config file for these installations will be found in the install path configured.

In this file, there will be a configuration called #disable-balloon-tips=Y

Can you please remove the hash from the start of this configuration file, then restart the PaperCut Client running on that test PC?

What we are doing here is disabling balloon tips for PaperCut altogether. This forces us to use a popup window to display the message rather than a balloon notification.



Added lines 1-26:
(:title RM CC3 and CC4 Considerations:)

!!!RM Network Monitor Service
The RM Network Monitor Service can stop logging information from a [[https://www.papercut.com/products/ng/manual/ch-secondary-print.html|PaperCut secondary server]] reaching the main PaperCut application server.

For the Secondary server to communicate with the primary server the administrator will need to make sure that any Secondary servers are able to communicate (initiate a TCP connection) on port 9191. Administrators should also ensure that any firewall software on the primary Application Server is not set to block any incoming local network traffic on this port.

When the RM Network Monitor Service is running it will block traffic on port 9191, so PaperCut is unable to monitor the print jobs from a secondary server. This seems to only affect Windows 2003 and Windows XP machines acting as a Secondary server. Typically while the RM Network Monitor Service is running the printers from any Secondary servers will be displayed in the printer tab in PaperCut but no print jobs are logged against them. The RM Network Monitor Service is part of RM Auditor and can typically be found running from:

@@[app-path]/Research Machines/Auditor/Network Monitor@@

To resolve the problem either disable the service or contact RM for information on how to force the service to ignore port 9191. There is a RM update (CC4UPD093) which installs a new version of the RM Network Monitor service. Once this is installed on the workstations, PaperCut will work fine. The update is only available upon request from RM.






!!Subheading

TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous

----
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
----
[-Keywords: TODO keywords here if needed-]

Comments

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 24, 2013, at 06:04 PM
Printable View   |   Article History   |   Edit Article