How to use Citrix Policy to Set a Default Session Printer

This section details how to configure Citrix Policy settings to set one of the following printer types as the default printer in the session:

  • Client Printer
  • Network Printer
  • Citrix Universal Printer
  • Citrix PDF Printer

Client Printer

Client printers are any printer device that is configured on the user endpoint where the Citrix Receiver client is installed. This generally refers to printers that are physically attached to the endpoint but may include network printers configured on the endpoint. The default printer on the client side can be set as the default printer in the session.

Printing Policy Settings:

  • Set the Default printer policy setting to ‘Set default printer to the client’s main printer’.
  • In the Printer assignments policy setting, set the Default printer setting to ‘Client main printer’.

Network Printer

Network printers are any printer that is accessible from the VDA to a shared printer UNC Path. These printers are generally managed and assigned to users by IT administrators. Network printers may be configured on a XenApp server, a virtual desktop, or directly on the user endpoint.

Printing Policy Settings:

  • Add the UNC path of the network printer to the Default Printer policy setting.
  • Add the UNC path of the network printer to the Printer Assignments policy setting.

Citrix Universal Printer

Citrix Universal Printer is a generic printer created at the beginning of a session that is not tied to any client printing device. When using this generic printer, the resulting print job will be sent to and displayed on the local endpoint where the user has the option to print to any client printer available. This printer is enabled via Citrix policy and can only be used with Windows endpoints using the Receiver for Windows client. Not to be confused with the Citrix Universal Printer Drivers.

Printing Policy Settings:

  • Set the Default printer policy setting to ‘Set default printer to the Generic Universal Printer’.
  • In the Printer assignments policy setting, set the Default printer setting to ‘Generic Universal Printer’.

Citrix PDF Printer

Citrix PDF Printer is a PDF printer created at the beginning of a session that is not tied to a printing device. When using this PDF printer, the resulting print job will be sent in PDF file format and displayed on the local endpoint where the user has the option to print to any client printer available. This printer is enabled via Citrix policy and can only be used with Chrome and HTML5 receivers.

Printing Policy Settings:

  • Set the Default printer policy setting to ‘Set default printer to the PDF printer’.
  • In the Printer assignments policy setting, set the Default printer setting to ‘PDF printer’.

Troubleshooting

Symptoms or Error

Default session printer is not being set correctly in the session on Windows 10 or Windows Server 2016 VDAs.

Solution

Disable the option to ‘Let Windows manage my default printer’ on the VDA.

Option 1

  1. Navigate to Windows Start menu.
  2. Click “Settings”.
  3. Click “Devices” in the Settings dialog.
  4. Click “Printers & scanners” section.
  5. Disable the setting “Let Windows manage my default printer”.

Option 2

Set the following registry value:

  • Registry path: HKEY_CURRENT_USERSOFTWAREMicrosoftWindows NTCurrentVersionWindows
    • Name: LegacyDefaultPrinterMode
    • Type: REG_DWORD
    • Data: 1

Option 3

Disable the windows setting through Group Policy.

Navigate to the following location in Group Policy Editor:

  • User Configuration -> Administrative Templates -> Control Panel -> Printers
    • Enable “Turn off Windows default printer management”.

Problem Cause

When ‘Let Windows manage my default printer’ is enabled, the last session printer created in the session is set as the default printer. Windows sets the default printer to the most recently used printer.

Related:

How to monitor specific Printers?

I need a solution

Hello guys,

I need to be able monitor only specifit printers where confidential information is being print. After created a policy and a rule with the “Printer/Fax” protocol, How could I monitor only specifit printers?

Is it possible to use any out-of the box configuration or some sort of customization is required? 

Our printers names following this pattern:

\PrintServer1.domain.comPrinter1

\PrintServer1.domain.comPrinter2

\PrintServer2.domain.comPrinter3

0

Related:

  • No Related Posts

7013074: iPrint Appliance local rendered jobs are canceled, aborted, or improperly rendered.

The iPrint Appliance version 1.1 introduced the ability to assign specific Linux printer drivers to individual printer agents. The same ability exists in the 2.x and 3.x versions of the iPrint Appliance.

The steps in the Resolution section of this TID shows how to use the Linux printer drivers (PPDs) which ship with the iPrint Appliance. PPDs obtained from other sources (such as http://www.openprinting.org/printers) can also be uploaded to the Driver Store. However, the iPrint Appliance does not support all of the filters used by the various PPDs obtained from external sources. When the PPD references a filter which the Appliance does not support, print jobs submitted via mobile devices will be canceled or aborted.

One common filter which may be of use to install is the hplip filter.

Note: The printer drivers in the /usr/share/cups/model/manufacturer-PPDs/hplip directory do not use the hplip filter. View the PPD content (a PPD is a text file) and search for the word ‘filter’. If hpcups or hplip is listed as a filter, you must install hplip to the iPrint appliance for that PPD to be a valid option.

To install the hplip filter:

mkdir /tmp/hplip

wget -P /tmp/hplip ftp://ftp.novell.com/outgoing/hplip-ForAppliance.tar.gz

tar xvzf /tmp/hplip/hplip-ForAppliance.tar.gz

rpm -Uvh /tmp/hplip/*.rpm

Note: If the hplip-ForAppliance.tar.gz file does not exist on the Novell FTP outgoing site, email patchfeedback@novell.com with the subject of “Need hplip for the iPrint Appliance”. An email will be sent in reply notifying you when that file has be re-added.

When choosing a ppd to assign to a printer, a generic ppd is often a good choice. Some examples of generic printer drivers are:

/usr/share/cups/model/Postscript-level2.ppd.gz

/usr/share/cups/model/Postscript.ppd.gz

/usr/share/cups/model/deskjet.ppd.gz

/usr/share/cups/model/laserjet.ppd.gz

Other strategies include testing a PostScript vs PCL driver. Often a printer driver for a specific printer model will work for a different model and even different manufacturer printer. The key is use a printer driver which matches the printer language which is supported by the printer type (PostScript or PCL).

If an remote renderer is configured (also known as a Windows renderer), none of the above configuration applies. All print jobs, regardless of the format, will be rendered by the remote, Windows renderer as long as it is active.

Related:

Packaging Cupsfilter on a Mac Device

Installation of the printer fails on Mac if the cupsfilters specified in the PPD file is not installed. Some vendors do not distribute the drivers in .pkg or .dmg format. Hence, associating the package to the PPD file is not possible. Micro Focus iPrint server has an option to associate a package containing cupsfilters to …

+read more

The post Packaging Cupsfilter on a Mac Device appeared first on Cool Solutions. wpreetham

Related:

7022777: Cups crashs while receiving jobs from accounts containing umlaut characters.

This document (7022777) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)

Situation

cups crash on receiving print jobs from accounts containing German umlaut characters with messages similar to the following:

Sep 25 14:10:21 linux cups-lpd[77617]: Connection from <remote.server.name> (IPv4 <remote.server.ip>)

Sep 25 14:10:21 linux cups-lpd[77617]: Receive print job for HAL-232

Sep 25 14:10:21 linux cupsd[66532]: process 66532: arguments to dbus_message_iter_append_basic() were incorrect, assertion “_dbus_check_is_valid_utf8 (*string_p)” failed in file dbus-message.c line 2676.

Sep 25 14:10:21 linux cupsd[66532]: This is normally a bug in some application using the D-Bus library.

Sep 25 14:10:21 linux cupsd[66532]: D-Bus not built with -rdynamic so unable to print a backtrace

Sep 25 14:10:21 linux cups-lpd[77617]: Unable to create job – Success

Sep 25 14:10:21 linux cups-lpd[77617]: Closing connection

Sep 25 14:10:21 linux systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT

Sep 25 14:10:21 linux systemd[1]: cups.service: Unit entered failed state.

Sep 25 14:10:21 linux systemd[1]: cups.service: Failed with result ‘core-dump’.

Resolution

Please contact SUSE Technical Services for retrieving a Program Temporary Fix in case this issue is experienced.

Cause

The handling of German umlaut characters causes an encoding error causing cups to crash.

Status

Reported to Engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Learn Linux, 101: Manage printers and printing

Learn how to manage print queues and user print jobs on Linux using CUPS and the
LPD compatibility interface. Use the material in this tutorial to study for the LPI 102
exam for Linux system administrator certification or to learn for fun.

Related:

How to Set a Default Session Printer

Configuration

A default session printer can be set by either of the following two policies:

  • Default printer policy
  • Printer assignments policy

When both policies are configured, Printer Assignments policy takes precedence over the Default Printer policy. One of the following printers can be set as the default printer in the session:

Client printers – any printer device that is configured on the user endpoint where the Citrix Receiver client is installed. This generally refers to printers that are physically attached to the endpoint but may include network printers configured on the endpoint. The default printer on the client side can be set as the default printer in the session.

Printing Policy

Set the Default printer policy to ‘Set default printer to the client’s main printer’.

Set the Default printer setting of the Printer assignments policy to ‘Client main printer’.

Network printers – any printer that is accessible via the network. These printers are generally managed and assigned to users by IT administrators. Network printers may be configured on a XenApp server, a virtual desktop, or directly on the user endpoint.

Printing Policy

Add the UNC path of the network printer to the Default printer policy.

Add the UNC path of the network printer to the Printer assignments policy.

Citrix Universal Printer – a generic printer created at the beginning of a session that is not tied to a printing device. When using this generic printer, the resulting print job will be sent to and displayed on the local endpoint where the user has the option to print to any client printer available. This printer is configured via Citrix policy and can only be used with Windows endpoints using the Receiver for Windows client. Not to be confused with the Citrix Universal Printer Drivers.

Printing Policy

Set the Default printer policy to ‘Set default printer to the Generic Universal Printer’.

Set the Default printer setting of the Printer assignments policy to ‘Generic Universal Printer’.

Citrix PDF Printer – a PDF printer created at the beginning of a session that is not tied to a printing device. When using this PDF printer, the resulting print job will be sent in PDF file format and displayed on the local endpoint where the user has the option to print to any client printer available. This printer is configured via Citrix policy and can only be used with Chrome and HTML5 receivers.

Printing Policy

Set the Default printer policy to ‘Set default printer to the PDF printer’.

Set the Default printer setting of the Printer assignments policy to ‘PDF printer’.

Troubleshooting

Symptoms or Error

Default session printer is not being set correctly in the session on Windows 10 or Windows Server 2016 VDAs.

Solution

Disable the option to ‘Let Windows manage my default printer’ on the VDA.

Option 1

  1. Navigate to Windows Start menu.
  2. Click “Settings”.
  3. Click “Devices” in the Settings dialog.
  4. Click “Printers & scanners” section.
  5. Disable the setting “Let Windows manage my default printer”.

Option 2

Set the following registry value.

Registry path: HKEY_CURRENT_USERSOFTWAREMicrosoftWindows NTCurrentVersionWindows

Name: LegacyDefaultPrinterMode

Type: REG_DWORD

Data: 1

Option 3

Disable the windows setting through Group Policy.

Navigate to the following location in Group Policy Editor:

User Configuration -> Administrative Templates -> Control Panel -> Printers

Enable “Turn off Windows default printer management”.

Problem Cause

When ‘Let Windows manage my default printer’ is enabled, the last session printer created in the session is set as the default printer. Windows sets the default printer to the most recently used printer.

Related:

3484700: iPrint Printer fails to install with 1344, 1345 or Winsock 10060 error

Test install of an iPrint printer. If the install succeeds, then uninstall CUPS.

Cause 2: Proxy Server

The process of installing a printer requires that a printer driver be associated with the printer, and that the driver is able to be installed. The driver installation process is not obvious, and can cause the printer installation to fail if the configuration does not meet the requirements.

When the printer installation is begun, the Print Manager is consulted to confirm that a driver has been associated with the printer being installed. Once the driver is identified, iPrint first attempts to locate the driver on the workstation where the printer is being installed. If the driver exists, the printer is installed without further processing. If not, iPrint looks for the driver in the mod_ipp folder on the server where the Print Manager is located. If the driver is found there, the printer is installed using that driver. If the driver doesn’t exist in the mod_ipp, iPrint looks in the Driver Store. If the driver is located in the Driver Store, it is copied to the mod_ipp on the server where the Print Manager is located. Then, iPrint installs the printer using the mod_ipp copy of the driver. Subsequent attempts to install the printer will use the copy of the driver in the mod_ipp folder, so the driver doesn’t need to be copied from the Driver Store again. This keeps the drivers “close” to the users of the Print Manager where the printers are located.

A problem can arise if the server is using a Proxy. The Proxy controls access to the network, and unless the Driver Store is defined as an exception to the Proxy, the process of locating the driver in the Driver Store will fail, resulting in the 1344 error. This will happen even if the Driver Store and the Print Manager exist on the same server because, although nothing actually goes “on the wire” (through the network interface card), the Proxy will not allow the process to continue.

To resolve this problem, the Proxy must either be disabled, or be configured to allow an exception for the Driver Store.



Resolution 2:

Determine if a Proxy is enabled.

YaST -> Network Services -> Proxy -> is the “Enable Proxy” option checked? If it is enabled, then Apache will intercept the request to copy drivers from the Driver Store’s RESDIR to the Print Manager’s mod_ipp directory.

a). Turn off the proxy:

Related:

7021359: cups drops jobs after three hours of printer unattainability

This document (7021359) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12

cups > 1.6b1

Situation

Jobs sent to printers which are unresponsive for a longer period are dropped by cups. When activating debug mode the following message can be found in /var/log/cups/error_log :

E [08/Sep/2017:01:18:05 +0200] [Job 4] The printer is not responding.

[…]

I [08/Sep/2017:01:19:02 +0200] [Job 4] Canceling stuck job after 10800 seconds.

Resolution

Set MaxJobTime in /etc/cups/cupsd.conf to 0 to disable this behavior. See man 5 cupsd.conf for more information.

Cause

cups 1.6b1 introduced a changed behavior that cancels jobs after 10800 seconds of printer unattainability by default.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related: