Multiple Popup Problem when using Windows Terminal Services

Problem:

When printing to a Popups queue using Windows Terminal Services, a Popup dialog appears immediately for the first user, but subsequent users have to wait. Is there a fix for this?

Workaround:

When multiple users print to a Popups queue using Windows Terminal Services, the Popup Client dialog appears immediately for the first user. However, subsequent users have to wait for the first user to close the dialog before it will appear on their workstations. This is a known limitation of using Popups on Terminal Services. It also means that if a user does not answer the questions and leaves the Popup dialog open, all other users are unable to print and use Popups. This situation can be corrected by creating a new registry key in HKEY_LOCAL_MACHINE\ Software\ Pharos\ Popup Client on the terminal server running the Popup Client:

• Name: FinishDialogTimeout

• Type: REG_DWORD

• Meaning: How long (in seconds) the Popup dialog stays on screen. If this timeout expires, the dialog closes and the print job is not sent. If this key is not present, the dialog remains indefinitely.

Similarly, when multiple users receive user notification relating to their print jobs, from the Informed Print feature or from Scripts, the notification appears immediately to the first user but subsequent users have to wait for that notification to be closed or to time out. This is also a known limitation of using Popups on Terminal Services. Unlike the Popup Client dialog, the notification always does eventually time out. If the notification is sent from a Script, the timeout is set within the Script. Timeouts for Informed Print notifications are set by a registry key in HKEY_LOCAL_MACHINE\ Software\ Pharos\ Print Server on the computer running the Print Server:

• Name: Informed Print Timeout

• Type: REG_DWORD

• Meaning: The amount of time (in seconds) that Informed Print messages will be displayed for. This value must be manually created.

• Default: 15