Enabling user client notifications on Windows when balloon tips are disabled
KB Home | Enabling user client notifications on Windows when balloon tips are disabled
When the user client tool in PaperCut NG or PaperCutChargeBack is installed on a Windows system, it delivers notifications using balloon tips by default.
If you have disabled balloon tips (e.g. by using Group Policy), PaperCut will not be able to display notifications from the client tool. You may hear the standard windows ‘pop’ sound when a notification arrives, but nothing will be displayed. There are two options to get notifications working: 1) enable balloon tips, or 2) make the client tool deliver notifications using standard dialogs instead of balloon tips.
1. Re-enabling balloon tips
a) Via Group Policy (if using Active Directory, recommended method)
Open the Group Policy Object Editor for the group in question
Browse to User Configuration → Administrative Templates → Start Menu and Taskbar
Find the setting Remove Balloon Tips on Start Menu Items
Double-click on the setting and change the status to Disabled or Not configured
b) Via Group Policy Custom Administrative Template
Note: This method should be used if the one above fails.
Download the BalloonTips.adm template from here. You can also view a screen-cast of the process here. (special thanks to Daniel for the contribution)
Open Group Policy editor
Edit the relevant GP
Right Click on User\Administrative Templates
Choose Add/Remove and add the new balloontips.adm
Then Right click again on Administrative Templates - Choose View / Filtering and untick “Only show policy settings that can be fully managed”
b) Via the registry (advanced)
Open the Registry Editor’ on the system in question
Find the key HKEY_CURRENT_USER → Software → Microsoft → Windows → CurrentVersion → Explorer → Advanced
Look for the value EnableBalloonTips. If it exists, change its value to 2, or remove the value completely, to re-enable balloon tips.
2. Forcing the client tool to deliver notifications using dialogs
The client tool can be forced to deliver notifications using standard windows dialogs instead of balloon tips. This can be done on an individual system when the client tool is installed locally, or for all systems by modifying the version of the client available on the network share.
To force standard dialogs, you can use the user client option called disable-balloon-tips. This option can also be set by adding a disable-balloon-tips=Y line (or uncommenting the existing line) to the client config.properties file located at [app-path]/client/win/.
An alternate option (advanced) is to enable this with the pc-client.exe start command-line option —disable-balloon-tips (e.g. place in your startup script or Group Policy start command).
Restart the client tool(s) and send a test notification. The notification should now appear in a standard dialog instead of a balloon tip.
A Customers experience
In early 2015 PaperCut Technical Support was contacted by one customer who’s users were looking for a better work flow in that even after clicking “Cancel” on the PaperCut User Client, there was a Windows Print Notification balloon that said the document had been sent to the printer.
Refining this workflow required two main actions:
1 - You can turn off the Windows Print “Informational Notifications” via the Windows Printer Server Properties, however this is a per-machine bases and not controlled by the Windows Print Server.
In this situation the customer was able to create/update, via Group Policy Objects, the a registry key in:
Value type: REG_DWORD.
Value data: 0. Base: Hexadecimal.
2 - With that done they disabled the balloon tips that the PaperCut User Client uses by modifying the [app-path]\client\win\config.properties and setting:
This results in notifications from the PaperCut User Client that require acknowledgement before they’re dismissed rather than the balloon notifications that sometimes fade out before a user notices them.
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.