The Privacy Settings dialog shown above is presented to the user after the first few interactions with the driver/printer, provided the Special Offers Service is enabled (refer to the restrictions above). Selecting “No, do not send this info to HP” disables this feature and no further prompts are shown (may require a commit to the Enhanced Write Filter to preserve changes across a machine restart).

For additional information please refer to online privacy statement: http://welcome.hp.com/country/us/en/privacy.html

Appendix F: Known issues

Known limitation of the UPD working with local printers redirected through a Remote Desktop or Citrix connection

The UPD, outside of a remote Desktop or Citrix environment, has the ability to configure itself according to the actual configuration of the printer by communicating directly with the printer. Currently, the UPD installed on the server and used as fallback driver for auto created printers cannot communicate with the corresponding client-side printer (regardless of it being a directly-attached or a network printer). As a result, the UPD driver assumes default values for color mode, tray support, finishing options, etc.

Since version 4.7, UPD will default to monochrome printing when unable to establish the capabilities of the device, even if the device is a color printer. Please notice that this limitation does not apply to printer queues local to the server environment (be it direct-connect or remote printers), only for redirected client-side printers.

Redirected Local Printers and the Dynamic HP UPD Printer Queue

When a user connects to a Microsoft Remote Desktop or Citrix Presentation Server session, the printer queues that exist locally can be redirected for use over the remote session. With regular queues pointing to physical printer devices it works as expected; however, on the user’s “Printers and Faxes” folder on the Thin Client there is normally also the dynamic queue “HP Universal Printing for ThinClient PCL 5”, used for printing to printers selected dynamically. This queue will be redirected over the remote session as any other and will show-up in the remote machine as something similar to “HP Universal Printing for ThinClient PCL 5 (from MACHINENAME) in session 7”.

This redirected instance of the dynamic queue will work just as another static printer – this is by design. Instead of bringing-up the printer selection dialog, it will print immediately to the latest printer that was used in the dynamic queue on the thin client or, if none was used or the printer is not available, it will just fail to print and the job will sit on the spooler until manually deleted.

15