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:

Printers created from WEM are not being mapped to user sessions

To resolve this issue, configure the printer on WEM admin console using the hostname of the print server instead of the FQDN.

If you want to use the FQDN in the printers configuration, you have to fix the issue that causes that the agent machines fail to map the printers manually using the FQDN of the print server.

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:

Mobile printing with iPrint

qmangus

The use of mobile devices has greatly improved productivity in the workplace. Users can more easily access systems, quickly communicate and collaborate, and even create and share documents and files on their mobile devices (Micro Focus Filr is a great solution for this). In fact, a recent survey by Samsung and Frost & Sullivan found …

+read more

The post Mobile printing with iPrint appeared first on Cool Solutions. qmangus

Related:

  • No Related Posts

7023349: Chromebook iPrint printer install loops, never installs

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

Environment

Micro Focus iPrint

Situation

When attempting to install an iPrint printer to a Chromebook, the install loops from 0 to 100% and never installs.

Resolution

Micro Focus is investigating a solution to this problem. Until that time, the following two options exist:

  1. Use the PSMHostAddress to access the iPrint Portal page.
  • Find the PSMHostaddress by running the following command a terminal session to the iPrint server:
    • cat /etc/opt/novell/iprint/conf/ipsmd.conf | grep PSMHostAddress
  • When accessing the iPrint Portal page, use the address PMSHostAddress value.
    • For example, if the address following PSMHostAddress is iprint03.mycompany.com, then use this address to bring up the iPrint Portal:
      • https://iprint03.mycompany.com/print
  • Recreate the certificate with a SAN to match the PSMHostAddress
  • Cause

    The iPrint code cannot handle a scenario where the address bound to the Print Manager does not match the address used to access the iPrint Portal page (https://<iPrintDNSName>/print).

    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:

    7008708: History of iPrint Client fixes

    Fixes introduced in the 6.15 iPrint Client

    Available through the OES and iPrint Appliance Update channel and through the iPrint Appliance 2.1 Patch 7 download.

    • User printers installed using WSACL rules and shortname could not be removed (Bug 1089861)
    • iPrint Lite: Unsupported files information icon updated (Bug 1081341)
    • iPrint Lite is allowing to print unsupported files through windows context menu open with option. (Bug 1069221)
    • iPrint_lite: Clicking on iprint-lite icon on windows task bar does not minimize it. (Bug 1070780)
    • iPrint_lite: Hitting Enter key after entering server-ip does not click on “Find” button. (Bug 1070925)
    • iPrint Authentications fail with Novell Client installed (userPrincipalName) (Bug 1080884)
    • No error message when user prints to an SSL printer that he has no rights (Bug 1077610)
    • Printer driver download without iPrint provider using CLI. (Bug 116453)
    • iPrint client allowing to print the document even if the copies field is null. (Bug 1070716)

    Fixes introduced in the 6.12 iPrint Client

    Available through the OES and iPrint Appliance Update channel

    • Refresh iCM feature introduced (Bug 1057892)
    • Context menu printing crashes Windows Explorer with files with no extension (Bug 1063863)

    Fixes introduced in the 6.11 iPrint Client

    Available through the OES and iPrint Appliance Update channel

    • Minor cosmetic fixes.

    Fixes introduced in the 6.10 iPrint Client

    Available through the OES and iPrint Appliance Update channel or through iPrint Appliance 2.1 Patch 5

    • TID 7020136: OES Client nwtray crashes when you login through icon repetitively

    Fixes introduced in the 6.09 iPrint Client

    Available through the OES and iPrint Appliance Update channel or through these iPrint Appliance patches:

    • iPrint Appliance 2.0 Hot Patch 4
    • iPrint Appliance 2.1 Hot Patch 4
    • Error messages flooding NPSMMON.LOG (Bug 1021421)
    • Print dialog within MS Office or Adobe Reader in perpetual error state or spins indefinitely. (Bug 1029529)
    • User Printer installation crashes print spooler if location or description is set. (Bug 1028999)

    Fixes introduced in the 6.08 iPrint Client

    Available through the OES and iPrint Appliance Update channel or through these iPrint Appliance patches:

    • iPrint Appliance 2.0 Patch 4
    • iPrint Appliance 2.1 Patch 2
    • TID 7017101 – 0x00000002 error installing iPrint printers with the EFI Fiery driver (Bug 1019023)
    • TID 7017417 – Direct Printers looses parts of the printed document if bDirectPrintSpoolJobEnabled is enabled (Bug 1021882)
    • TID 7021962 – Hide Document Names for iPrint printer’s Windows Printer Queue
    • Printer driver DLLs are being over-written during iPrint printer installation. (Bug 990474)
    • iprntcmd based printer install and deletion enhanced for new User Printer implementation (Bug 103440)
    • iCM settings only read on log on. Provided message-box in case iCM not enabled. – Added few strings to the string table for User Printer. (Bug 104441)

    Fixes introduced in the 6.07 iPrint Client

    Available through the OES Update channel

    • Mac driver upload via iManager results in inproper driver name. (Bug 984480)
    • iCM fails to launch when logging in with OES Client. (Bug 1011189)
    • error 0x00000002 installing PS EFI Fiery driver (Bug 1019023)
    • Spooler crashes with Auto driver/profile update on Win 10 x86 (Bug 1020818)

    Related: