Professional Documents
Culture Documents
Terminal Services Printing
Terminal Services Printing
Terminal Services Printing
Terminal Services printing has been enhanced in Windows Server® 2008 by the addition of the Terminal
Services Easy Print printer driver and a Group Policy setting that enables you to redirect only the default
client printer.
The Terminal Services Easy Print driver is a feature in Windows Server 2008 that enables users to
reliably print from a Terminal Services RemoteApp™ program or from a terminal server desktop session
to the correct printer on their client computer. It also enables users to have a much more consistent
printing experience between local and remote sessions.
The Redirect only the default client printer policy setting allows you to specify whether the default
client printer is the only printer that is redirected in Terminal Services sessions. This helps to limit the
number of printers that the spooler must enumerate, therefore improving terminal server scalability.
Note
The RDC 6.1 (6.0.6001) client supports Remote Desktop Protocol 6.1.
The following list provides information about which operating systems support the Terminal Services
Easy Print driver, and whether additional configuration is required.
Windows Vista® with SP1 includes both of the required components. By default, Windows Vista
with SP1 supports the Terminal Services Easy Print driver with no additional configuration.
Windows XP with Service Pack 3 includes RDC 6.1. However, you must install a supported
version of .NET Framework separately. You can download Microsoft .NET Framework 3.5 (which
includes .NET Framework 3.0 SP1) from the Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkId=109422).
Windows Server 2008 includes both of the required components. However, by default, NET
Framework 3.0 SP1 is not installed. Therefore, to use the Terminal Services Easy Print driver on
a Windows Server 2008-based server (that is acting as the client), you must add .NET
Framework 3.0 SP1 by using either Server Manager or by adding the feature from the
command line.
To add .NET Framework 3.0 SP1 by using the Server Manager user interface
1. Start Server Manager. To open Server Manager, click Start, point to Administrative
Tools, and then click Server Manager.
2. In the left pane of Server Manager, right-click Features, and then click Add
Features.
4. Select the .NET Framework 3.0 Features and the XPS Viewer check boxes, and
then click Next.
5. Click Install.
7. At the command prompt, type the following, and then press ENTER:
pkgmgr.exe /iu:NetFx3
Increased reliability of Terminal Services printing for both RemoteApp and remote desktop
sessions.
Support for legacy and new printer drivers without the necessity of installing these drivers on
the terminal server.
Scalability improvements over Windows Server 2003 in terms of printer enumeration
performance. During the Winlogon process, the spooler only enumerates printers that are
available for a user in a particular session instead of enumerating all redirected printers.
Therefore, printers are enumerated on a per-session basis, instead of on a per-user basis.
Enhanced available printer capabilities. The Terminal Services Easy Print driver provides rich
and complete printer capabilities in remote sessions. All of the physical printer driver's
capabilities are available for use when a user views the printing preferences.
The Redirect only the default client printer Group Policy setting allows you to control whether the
default client printer is the only printer redirected in a Terminal Services session, or whether all printers
are redirected in a session.
If there are client computers that do not support the Terminal Services Easy Print driver, and the printer
driver is not already available on the terminal server, you must do either of the following to support
client printing:
Ensure that client printer drivers for both local and network printers are installed on the
terminal server. If you are installing a third-party driver, make sure that the driver is a
Windows Hardware Quality Labs (WHQL) signed driver.
Add the client printer drivers for both local and network printers to a custom printer mapping
file on the terminal server. For more information about how to create a custom printer mapping
file, see the "Resolution" section of article 239088 in the Microsoft Knowledge Base
(http://go.microsoft.com/fwlink/?LinkID=82784).
If the print job shows on the server queue but disappears and does not get to the local computer and an
"Access is denied" Error shows up on the system log you might need to "adjust" security permissions on
C:\Windows\System32\spool