- Cumulative Update 6 (CU 6)
- Cumulative Update 5 (CU5)
- Cumulative Update 4 (CU4)
- Cumulative Update 3 (CU3)
- Cumulative Update 2 (CU2)
- Cumulative Update 1 (CU1)
- Long Term Service Release (LTSR)
- Features not in this release
- Known issues
- System requirements
- Technical overview
- Install and upgrade analytics
- Prepare to install
- Prepare the virtualization environment - VMware
- Prepare the virtualization environment - Microsoft System Center Virtual Machine Manager
- Prepare for using Microsoft System Center Configuration Manager
- Install using the graphical interface
- Install using the command line
- Create a Site
- Install or remove Virtual Delivery Agents using scripts
- Install VDAs using the standalone package
- Machine catalogs
- Delivery groups
- XenApp published apps and desktops
- VM hosted apps
- VDI desktops
- Remote PC Access
- Local App Access and URL redirection
- Server VDI
- Remove components
Upgrades and migration
- Install and upgrade analytics
- Upgrade a deployment
- Migrate XenApp 6.x
- Install and upgrade analytics
- Migrate XenDesktop 4
- Work with policies
- Policy templates
- Create policies
- Compare, prioritize, model, and troubleshoot policies
- Default policy settings
Policy settings reference
- ICA policy settings
- Load management policy settings
- Profile management policy settings
- Receiver policy settings
- Virtual Delivery Agent policy settings
- Virtual IP policy settings
- Configure COM Port and LPT Port Redirection settings using the registry
- Connector for Configuration Manager 2012 policy settings
- Connections and resources
- Connection leasing
- Virtual IP and virtual loopback
- Secondary database locations
- Delivery Controller environment
- Session management
- Using Search in Studio
- IPv4/IPv6 support
- Client folder redirection
- Personal vDisk 7.x (Excluded from LTSR)
- User profiles
- Get started with Session Recording
- Grant access rights to users
- Create and activate recording policies
- Disable or enable recording
- Configure the connection to the Session Recording Server
- Create notification messages
- Enable custom event recording
- Enable or disable live session playback and playback
- Enable or disable playback protection
- Enable and disable digital signing
- Specify where recordings are stored
- Specify file size for recordings
- View recordings
- Troubleshoot Session Recording
- Reference - Manage your database records
- Third Party Notices
- Personal vDisk
- Configuration Logging
- Monitor Service OData API
- XenApp and XenDesktop SDK
- Citrix VDI Best Practices for XenApp and XenDesktop 7.6 LTSR
- Third party notices
May 28, 2016
Managing printers in your environment is a multistage process:
- Become familiar with printing concepts, if you are not already.
- Plan your printing architecture. This includes analyzing your business needs, your existing printing infrastructure, how your users and applications interact with printing today, and which printing management model best applies to your environment.
- Configure your printing environment by selecting a printer provisioning method and then creating policies to deploy your printing design. Update policies when new employees or servers are added.
- Test a pilot printing configuration before deploying it to users.
- Maintain your Citrix printing environment by managing printer drivers and optimizing printing performance.
- Troubleshoot issues that may arise.
Before you begin planning your deployment, make sure that you understand these core concepts for printing:
- The types of printer provisioning available
- How print jobs are routed
- The basics of printer driver management
Printing concepts build on Windows printing concepts. To configure and successfully manage printing in your environment, you must understand how Windows network and client printing works and how this translates into printing behavior in this environment.
In this environment, all printing is initiated (by the user) on machines hosting applications. Print jobs are redirected through the network print server or user device to the printing device.
There is no persistent workspace for users of virtual desktops and applications. When a session ends the user’s workspace is deleted, thus all settings need to be rebuilt at the beginning of each session. As a result, each time a user starts a new session, the system must rebuild the user’s workspace.
When a user prints:
- Determines what printers to provide to the user. This is known as printer provisioning.
- Restores the user’s printing preferences.
- Determines which printer is the default for the session.
You can customize how to perform these tasks by configuring options for printer provisioning, print job routing, printer property retention, and driver management. Be sure to evaluate how the various option settings might change the performance of printing in your environment and the user experience.
The process that makes printers available in a session is known as provisioning. Printer provisioning is typically handled dynamically. That is, the printers that appear in a session are not predetermined and stored. Instead, the printers are assembled, based on policies, as the session is built during log on and reconnection. As a result, the printers can change according to policy, user location, and network changes, provided they are reflected in policies. Thus, users who roam to a different location might see changes to their workspace.
The system also monitors client-side printers and dynamically adjusts in-session auto-created printers based on additions, deletions, and changes to the client-side printers. This dynamic printer discovery benefits mobile users as they connect from various devices.
The most common methods of printer provisioning are:
Universal Print Server - The Citrix Universal Print Server provides universal printing support for network printers. The Universal Print Server uses the Universal print driver. This solution enables you to use a single driver on a Server OS machine to allow network printing from any device.
Citrix recommends the Citrix Universal Print Server for remote print server scenarios. The Universal Print Server transfers the print job over the network in an optimized and compressed format, thus minimizing network use and improving the user experience.
The Universal Print Server feature comprises:
A client component, UPClient - Enable the UPClient on each Server OS machine that provisions session network printers and uses the Universal print driver.
A server component, UPServer - Install UPServer on each print server that provisions session network printers and uses the Universal print driver for the session printers (whether or not the session printers are centrally provisioned).
For Universal Print Server requirements and setup details, refer to the system requirements and installation documents.
Note: The Universal Print Server is also supported for VDI-in-a-Box 5.3. For information about installing Universal Print Server with VDI-in-a-Box, refer to the VDI-in-a-Box documentation.
The following illustration shows the typical workflow for a network based printer in an environment that uses Universal Print Server.
When you enable the Citrix Universal Print Server, all connected network printers leverage it automatically through auto-discovery.
Autocreation - Autocreation refers to printers automatically created at the beginning of each session. Both remote network printers and locally attached client printers can be auto-created. Consider auto-creating only the default client printer for environments with a large number of printers per user. Auto-creating a smaller number of printers uses less overhead (memory and CPU) on Server OS machines. Minimizing auto-created printers can also reduce user logon times.
Auto-created printers are based on:
The printers installed on the user device.
Any policies that apply to the session.
Autocreation policy settings enable you to limit the number or type of printers that are auto-created. By default, the printers are available in sessions when configuring all printers on the user device automatically, including locally attached and network printers.
After the user ends the session, the printers for that session are deleted.
Client and network printer autocreation has associated maintenance. For example, adding a printer requires that you:
- Update the Session printers policy setting.
- Add the driver to all Server OS machines using the Printer driver mapping and compatibility policy setting.
The term printing pathway encompasses both the path by which print jobs are routed and the location where print jobs are spooled. Both aspects of this concept are important. Routing affects network traffic. Spooling affects utilization of local resources on the device that processes the job.
In this environment, print jobs can take two paths to a printing device: through the client or through a network print server. Those paths are referred to as the client printing pathway and the network printing pathway. Which path is chosen by default depends on the kind of printer used.
Locally attached printers
The system routes jobs to locally attached printers from the Server OS machine, through the client, and then to the print device. The ICA protocol optimizes and compresses the print job traffic. When a printing device is attached locally to the user device, print jobs are routed over the ICA virtual channel.
By default, all print jobs destined for network printers route from the Server OS machine, across the network, and directly to the print server. However, print jobs are automatically routed over the ICA connection in the following situations:
- If the virtual desktop or application cannot contact the print server.
- If the native printer driver is not available on the Server OS machine.
If the Universal Print Server is not enabled, configuring the client printing pathway for network printing is useful for low bandwidth connections, such as wide area networks, that can benefit from the optimization and traffic compression that results from sending jobs over the ICA connection.
The client printing pathway also lets you limit traffic or restrict bandwidth allocated for print jobs. If routing jobs through the user device is not possible, such as for thin clients without printing capabilities, Quality of Service should be configured to prioritize ICA/HDX traffic and ensure a good in-session user experience.
To simplify printing in this environment, Citrix recommends using Citrix Universal print driver. The Universal print driver is a device-independent driver that supports any print device and thus simplifies administration by reducing the number of drivers required.
The following illustration shows the Universal print driver components and a typical workflow for a printer locally attached to a device.
When planning your driver management strategy, determine if you will support the Universal print driver, device-specific drivers, or both. If you support standard drivers, you need to determine:
- The types of drivers to support.
- Whether to install printer drivers automatically when they are missing from Server OS machines.
- Whether to create driver compatibility lists.
During printer autocreation, if the system detects a new local printer connected to a user device, it checks the Server OS machine for the required printer driver. By default, if a Windows-native driver is not available, the system uses the Universal print driver.
The printer driver on the Server OS machine and the driver on the user device must match for printing to succeed. The illustration that follows shows how a printer driver is used in two places for client printing.