Thoughts from the EPS Windows Server Performance Team
Day Seventeen and we're still going strong. Only ten days left until launch day! Continuing on with Terminal Services, today's topic is Terminal Services printing in Windows Server 2008 - and more specifically Terminal Services Easy Print.
The big enhancement to Windows Server 2008 Terminal Services printing is the new Terminal Services Easy Print feature. There are also some new Group Policy settings as well as some other features to enhance the TS printing experience. So what is Terminal Services Easy Print? Basically, this feature enables users to print from a Terminal Services session to the local or network printers that are configured on the client computer without the need to install drivers on the Terminal Server. The Easy Print feature uses the drivers installed locally on the client system which results in a more consistent printing experience between local and remote sessions. When a user prints from their Terminal Server session to a local printer, they will see the full printer properties dialog box from the local client and they will have access to all printer functionality. The Easy Print universal driver acts as a proxy and redirects all UI calls to the driver on the client. Administrators can also use Group Policy to limit the number of printers redirected to just the default printer which reduces the overhead and the number of printers that must be managed. To use the Terminal Services Easy Print feature on Windows 2008 Terminal Servers, the clients must be running the Remote Desktop Connection (RDC) 6.1 client and have the .NET Framework 3.0 Service Pack 1 installed. Both of these components are included with Windows Server 2008, and will be available for download for Windows Vista and down-level client operating systems.
The Terminal Services Easy Print feature is implemented in tsprint.dll and works seamlessly in mixed platform environments such as the following:
The document to be printed is rendered as an XPS document on the Terminal Server and then transferred back to the client where it is printed using the local print driver. Since XPS documents can be created and printed on both x86 and x64 platforms and are platform-independent, there are no cross-platform compatibility issues when using Easy Print. The Easy Print process is outlined below:
The process is also shown below:
Because the RDC client, MSTSC.EXE, is a native Win32 application, and the WPF printing infrastructure uses managed (.Net Framework) API's, a managed wrapper was created to support Terminal Services Easy Print. When a document is printed from a remote desktop session using the Easy Print driver on the Terminal Server, the RDC client calls the managed wrapper, TSWPFWRP.EXE, to assist with processing the print job on the client. TSWPFWRP.EXE is only used for Easy Print redirected printer functionality and is only invoked when printing.
An important note - for any client computers that do not support the Terminal Services Easy Print feature, only client printers that have a corresponding driver on the Windows Server 2008 Terminal Server can be redirected in a Terminal Server session.
That wraps up today's post. Tomorrow we'll have an overview of the RDP Client. Until next time ...
- CC Hameed
Is it possible to enable EasyPrint in Remote Desktop configuration?
PingBack from http://all-in-one-printer.jfcforum.com/2008/02/17/ws2008-terminal-services-printing/
Will LongHorn support mac printers using EasyPrint?
I'm not sure what you mean by Remote Desktop Configuration, but if you mean on the client side, no you do not configure EasyPrint on the client. The server is configured to use EasyPrint and you can disable it to fallback to Windows Server 2003 redirected printing where you must have a driver on the server that matches the client driver so that the server can render the print job before sending it to the client.
How do you change the default client permissions on a redirected printer in TS2008?
I have the client that user the windows terminal server to printer your report. But with user Powerbuilder program it ins't sucess.
When Printing from Powerbuilder through printers tied through Easy Print I get the footer on the page but not the report. Client Computer is XP w/Service Pack 3 and .Net Framework 3.5
Everything looks good on my client w/service pack 3 and .net 3.5 but when trying to print, nothing comes out of my printer and there is no error message.
Hello I have the same problem with terminal services 2008, WinXP SP 2, .Net Framework 3.5, RDP client 6.1 and when I try to print from a program built in Power Builder 4.0, i don't have error messages, the only thing i see is that the paper comes out in blank!
Install hotfix 959554 client and server and check the behavior.
re: WS2008: Terminal Services Printing
Monday, December 01, 2008 3:59 PM by Carlos
That hotfix worked for me! Thanks!
when i connect to windows 2008 server from thin client using Remote desktop connection, I see the printers installed on my thin client redirected in the session but the device settings / advance properties are disabled for the printers which i require enabled so as to change them. kindly tell the solution
How to redirect printer share ?
Hi Folks ... I'm back here with the same "blank page" problem using WS2008 R2 RC Terminal Services Printing. I tried to apply the KB959554 hotfix, but of course it won't install on R2. Does MS have a fix for this in R2 yet? Will MS have this resolved in R2 before it ships?