Terminal Server Easy print
Terminal service easy printing is a new feature introduced in windows 2008 server.It enables users to print from a Terminal Services session to the local or network printers configured on the client computer without the need to install drivers on the Terminal Server.
User will see the full printer properties of the local printer in the session and have access to all printer functionality. The Easy Print universal driver acts as a proxy and redirects all UI
To use the Terminal Services Easy Print feature in Terminal Services on Windows Server 2008, clients must be running Remote Desktop Connection (RDC) 6.1 client and have the .NET Framework 3.0 Service Pack 1 installed. Both included with Windows Server 2008 and will be available for download for Windows Vista.
New features in Windows Server 2008 Terminal Services:
++Terminal Services Easy Print.
++Client-redirected printers are now scoped per session.
++Printers now have the Session SID set in the list of ACLs that prevents printers from appearing in another session, even for the same user.
++Ability to view and manage session printers. By default, users, including administrators, can only see the printers that they have redirected in their session.
++Users can change access to the printers by editing the permissions in the printer properties to be made accessible to other users.
The Terminal Services Easy Print feature works seamlessly in mixed platform environments:
· x86 clients > x64 Windows Server 2008 Terminal Servers
· x64 clients > x86 Windows Server 2008 Terminal Servers
Things we need to check if TS easy printing is not working:
++clients are running Remote Desktop Connection (RDC) 6.1 client and have the .NET Framework 3.0 Service Pack 1.
a) XP SP3 includes RDC 6.1 client. But we need to install .NET Framework
Microsoft .NET Framework 3.5 (which includes .NET Framework 3.0 SP1) can be downloaded from the Microsoft Download Center
b) 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.
3. On the Select Features page, expand .NET Framework 3.0.
4. Select the .NET Framework 3.0 Features and the XPS Viewer check boxes, and then click Next.
5. Click Install.
To add .NET Framework 3.0 SP1 by using the command line
1. Start the command prompt with elevated privileges. To do this, click Start, right-click Command Prompt, and then click Run as administrator.
2. At the command prompt, type the following, and then press ENTER:
The installation occurs silently, and may take several minutes.
c) 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
++ Check if tsprint.dll in the following location:
%systemroot%\System32\Spool\Drivers\w32x86\3\tsprint.dll (Terminal Services Easy Print is implemented in tsprint.dll)
++Check the Terminal Services Easy Print and compare with the working machine.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\ <architecture>\Drivers\Version-3\Terminal Services Easy Print
Terminal Service Printing Group Policies
Group Policies for Terminal Services printing are located in the following container:
Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server
Table: Terminal Services Print Group Policies
Do not set default client printer to be default printer in a session
This policy setting allows you to specify whether the client default printer is automatically set as the default printer in a Terminal Services session.
Do not allow client printer redirection
This policy setting allows you to specify whether to prevent the mapping of client printers in Terminal Services sessions. Enabling this policy will disable printer redirection.
Specify terminal server fallback printer driver behavior
This policy setting allows you to specify the Terminal Server fallback printer driver behavior. You must enable this policy to use the fallback driver.
Use Terminal Services Easy Print driver first
This policy setting allows you to specify whether the Terminal Services Easy Print printer driver is used first to install all client printers. Enabling this policy will cause all redirected printers to use the Easy Print driver.
Redirect only the default client printer
This policy setting allows you to specify whether the default client printer is the only printer redirected in Terminal Services sessions. Enabling this policy causes the server to only redirect the client default printer, not all
PingBack from http://4thecause.morelyrics.co.uk/2008/06/25/terminal-server-easy-print/
Easy print is working fine on the internal network, however, when I connect over the internet no local printers on mapped in the TS session. Is there a bandwidth limitation?
That should not restrict easy print. But i am curious to know on which link we are connecting? Is there any firewall in between?
There is a firewall in between of course. I have allowed only port 443 to the TS Web Access server, which is on the same box as the gateway and TS server. If I open port 3389 and connect to RDP directly, it works fine. If I VPN into the network it works fine. Only when connecting to TS Web Access directly over the internet does it fail to redirect the printers.
I have one also. I have a client whose servers we are hosting. They connect VIA RDP to a Windows 2008 server. The default printer comes in but not the others. Each person needs up to 3 printers. I have the default printer only check box unchecked and GP set to disable. What else can I do to get the other printers to come in. Never had this problem win WIN 2003.
I have a problem as well. We have a hosted client who log into a windows 2008 server via RDP. Only their Default printer comes in even though I have that disabled by unchecking the Box in the properties and disabling the GP. How can I get all of their printers to come in? They are on XP and WIN2000 workstations.
Hi, i have a really odd problem with some printers and easy print. The printer redirects fine, and a windows test page will print perfectly, however, try printing a PDF and it comes out all wrong, like the text is overlapping.
Has anyone else experianced this with EasyPrint? In one instance, where there was a driver for the printer onthe server, and easyprint was turned off, it worked fine (after having failed to print correctly using the EasyPrint driver).
I have also had this strange printing problem where pages come out with text overlapping and symbols instead of text, I suspect it is becouse these printers are old and the drive is not compatible with easy print.
Has anyone found a solution, or a way to have some printers using easy print and other old printers using redirected printing with the drive installed on the TS server.
hi i have strang problem priters are redirected but when i give print command nthing comes out of printer and there is no error