Introducing Terminal Services Easy Print: Part 1

Terminal Services Easy Print explained by Microsoft Terminal Services Team.

Windows 64bit, Terminal Services, Citrix, Thin Client, VMware / VirtualPC / VDI — Thu, 26 Apr 2007 22:02:17 GMT

Terminal Services Easy Print explained by Microsoft Terminal Services Team.

Thu, 26 Apr 2007 22:19:05 GMT

It doesn’t seem more than 2 minutes ago I was sitting watching the announcement of Terminal Services

re: Introducing Terminal Services Easy Print: Part 1

termserv — Fri, 27 Apr 2007 23:42:20 GMT

I added a new section describing the current options for testing EasyPrint

Mas sobre easy print

Be Geek My Friend — Sat, 28 Apr 2007 16:44:42 GMT

Me esta encantando la beta 3 de longhorn y ver cómo me ayudara a mejorar mis infraestructuras, reducir

ShortNews - MS Diagnostics and Recovery Toolset, TS Management Pack, TS Easy Print, MS Security portal

SBS2003 and network — Mon, 30 Apr 2007 15:35:19 GMT

Microsoft Diagnostics and Recovery Toolset K dispozici je 30 denní zkušební verze nástroje pro obnovu systému, který je součástí Microsoft Desktop Optimization Pack. Tento balík nástrojů obsahuje nás ...

re: Introducing Terminal Services Easy Print: Part 1

Chief — Tue, 01 May 2007 20:15:32 GMT

I'm having issues with TS printing. I have everything installed as directed above. It acts like it's printing... but then nothing prints.

Any suggestions?

re: Introducing Terminal Services Easy Print: Part 1

Zardosht Kasheff [MSFT] — Tue, 01 May 2007 20:21:32 GMT

What printer are you using? Are you using "Microsoft XPS Document Writer"? If so, then a dialog should appear on the TS client machine to save the .XPS file. It is possible that this dialog is behind your mstsc.exe window, which is why you do not see it.

Introducing Terminal Services Easy Print: Part 2

Terminal Services Team Blog — Thu, 03 May 2007 21:14:21 GMT

In Part 1 , we introduced the main benefit to Terminal Services (TS) Easy Print: a "driver-less" solution

Introducing Terminal Services Easy Print: Part 2

Terminal Services Team Blog — Thu, 03 May 2007 21:29:35 GMT

In Part 1 , we introduced the main benefit to Terminal Services (TS) Easy Print: a "driver-less" solution

re: Introducing Terminal Services Easy Print: Part 1

bob jones — Thu, 03 May 2007 21:47:22 GMT

poor! still nto working correctly...will MS terminal server EVER get printing right?

re: Introducing Terminal Services Easy Print: Part 1

Zardosht Kasheff [MSFT] — Thu, 03 May 2007 21:59:12 GMT

Bob, did you follow the instructions in "How to test TS Easy Print with Beta 3"?

re: Introducing Terminal Services Easy Print: Part 1

Mike King — Tue, 08 May 2007 20:52:23 GMT

Does Easy Print support mixed platforms, such as x86 clients using x64 TS and x64 clients using x86 TS? Is any configuration needed for these scenarios?

re: Introducing Terminal Services Easy Print: Part 1

Eric Holk [MSFT] — Wed, 09 May 2007 00:06:12 GMT

Mike,

You shouldn't have to do anything special to use Easy Print in mixed platforms. Basically, on the server the document is rendered as an XPS document and then transfered to the client, where it is printed using the local print driver. XPS documents can be created and printed on both x86 and x64 platforms, so there won't be any problems interoperating between the two.

re: Introducing Terminal Services Easy Print: Part 1

Gaurav Daga [MSFT] — Tue, 15 May 2007 21:52:40 GMT

Thanks for asking the question Mike. This brings out an interesting point that we should highlight - printer drivers have historically been a kind of a roadblock in 64-bit server adoption becuase many IHV printer drivers were not supported on 64-bit servers. Easy Print is a small step in removing that roadblock at least for remote scenarios, because there is no need to install any kind of IHV printer drivers on Longhorn Server if the primary access mechanism is through Terminal Server or even for remote administration purposes.

Terminal Services Easy Print explained by Microsoft Terminal Services Team.

Windows 64bit, Terminal Services, Citrix, Thin Client, VMware / VirtualPC / VDI — Thu, 14 Jun 2007 13:38:41 GMT

It doesn't seem more than 2 minutes ago I was sitting watching the announcement of Terminal Services

re: Introducing Terminal Services Easy Print: Part 1

AdamT — Thu, 05 Jul 2007 14:01:16 GMT

Why doesnt MS just buy up the thinprint rdp engine technology - it works like a dream? (No I have no connection to them other than as a customer)

Ive got hundreds of people connecting to Terminal Servers from their homes, and it has never failed regardless of whatever nasty little printer any of those users have!

Adam

re: Introducing Terminal Services Easy Print: Part 1

Victor — Fri, 31 Aug 2007 07:02:56 GMT

Does the TS easy Print works for Citrix ica session as well?

TS and Citrix are both very bad for working with Crystal Report, and the only way is to install all native drivers in the Citrix/TS servers.

it looks this is a final solution to Crystal report printing nightmare for TS, and hopefully it apply to Citrix as well.

re: Introducing Terminal Services Easy Print: Part 1

Victor — Fri, 31 Aug 2007 07:02:59 GMT

Does the TS easy Print works for Citrix ica session as well?

TS and Citrix are both very bad for working with Crystal Report, and the only way is to install all native drivers in the Citrix/TS servers.

it looks this is a final solution to Crystal report printing nightmare for TS, and hopefully it apply to Citrix as well.

Introducing Terminal Services Easy Print: Part 3

Terminal Services Team Blog — Sat, 06 Oct 2007 00:47:59 GMT

In Part 1 , we introduced the main benefits of Terminal Services (TS) Easy Print: a “driver-less” solution

re: Introducing Terminal Services Easy Print: Part 1

Fred — Thu, 25 Oct 2007 10:58:55 GMT

How does it affect users that uses Thin client that have WinXP embedded?

re: Introducing Terminal Services Easy Print: Part 1

Patrick Rouse — Thu, 25 Oct 2007 16:52:34 GMT

XP Embedded would need to be updated to SP3 when it's available for the device.

You'd still be able to connect to a 2008 TS, just not via TSWeb, if you don't update the RDP Client.

re: Introducing Terminal Services Easy Print: Part 1

chris clark — Tue, 11 Dec 2007 13:39:34 GMT

Is the specification for rdp 6.1 available? Do you know of any moves to develop the open source rdp clients to be 6.1 compatible? I know you want to sell either CE or XPE but it is much cheaper to use open source clients.

ICA has always been reckoned to to perform better than rdp. Does 6.1 have better performance than 6.0?

re: Introducing Terminal Services Easy Print: Part 1

Samuel Zhang — Tue, 15 Jan 2008 13:11:17 GMT

I wonder how the easy printer driver showed in the properties of printer list? I didn't see the easy printer driver showed, why?

I have installed a WS2008 (Longhorn) server,The CLIENT – from which I remote out of – be XPe with .NET 3.0 SP1 and RDP6.1 installed.Can this see the easy printer driver just as the above picture 1

Apple Mac OS X Printing Support

kay — Thu, 17 Jan 2008 19:11:11 GMT

would Easy Print support Mac users connecting via RDP client for Mac?

...

looking forward to Win2008!

Printer Redirection works with Web Connection but not with Remote Desktop Connection (Fat CLlient)

Chris — Tue, 29 Jan 2008 04:34:55 GMT

Does anyone know why my 2003 server's Printer Redirection works with Web Connection but not with Remote Desktop Connection? I have installed right driver and it seems working fine with Remote Desktop Web Connection; however, I just can't make it work with normal Fat client version of Remote Desktop Connection. Can someone help me?

THank you

Printing Is Easier with Easy Print

Adrian Ford — Thu, 31 Jan 2008 21:40:27 GMT

Printing hasn't always been the easiest thing to configure and manage in Terminal Services. As Greg Shields

re: Introducing Terminal Services Easy Print: Part 1

Patrick Rouse — Thu, 31 Jan 2008 22:24:11 GMT

This is not a technical support forum. Please post those type of queries to the following newsgroup.

http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.windows.terminal_services

Printing Is Easier with Easy Print

Noticias externas — Thu, 31 Jan 2008 22:40:37 GMT

Printing hasn't always been the easiest thing to configure and manage in Terminal Services. As Greg

TS EasyPrint (продолжаю разбирать вопросы)

Прошедшие встречи MCP клуба, Москва — Sun, 17 Aug 2008 16:15:53 GMT

Во время моего доклада “Безопасный удаленный доступ к приложениям” было задано несколько вопросов по...

TS EasyPrint (продолжаю разбирать вопросы)

Прошедшие встречи MCP клуба, Москва — Sun, 17 Aug 2008 16:30:56 GMT

Во время моего доклада “Безопасный удаленный доступ к приложениям” было задано несколько вопросов по...

Introducing Terminal Services Easy Print: Part 3

Terminal Services Team Blog — Fri, 12 Jun 2009 19:56:28 GMT

[Part III in a series. Jump to Part I , Part II , Part III ] In Part 1 , we introduced the main benefits

re: Introducing Terminal Services Easy Print: Part 1

Srinivasan — Tue, 30 Jun 2009 12:46:02 GMT

I have installed terminal server on Windows 2008 and many a times the client's local printers are getting disappeared on the client's machine. If I restarted the server, the printers are available. What could be the reason or any specific setups to be carried on the terminal server or windows 2008 server.

rsrinivasan@ebtech.biz

re: Introducing Terminal Services Easy Print: Part 1

Orcun — Fri, 04 Sep 2009 16:42:51 GMT

Hi ,

Easy print is a very fast and easy way to work with the printing problems.But in our enviroment there is a problem that is about printing from our ERP system.The ERP admins say that they do use the draft mode (dos printing) in their applications so We can not get print out from our terminal servers from out ERP system but we do get print out from windows sessions ,Any clue or way to trouble shoot those ???

Thanks

re: Introducing Terminal Services Easy Print: Part 1

David Officer of Goldendale, WA — Wed, 07 Oct 2009 18:01:03 GMT

I have a workstation with windows xp servicepack 3 and .net 3.5. In the remote session all my redirected printers show up but when I try to print out of them, no page comes out of the printer with no error as well. However, the redirected printer HAD been working fine via TS a month ago. I don't know why it wont work now. I tried another computer (at home) with the same specs above and my redirected home printer wont print. Further exploration...no PC running RDC connecting to our Win Server 2008 via TS will successfully print via redirected printer. Yet...the macintosh's RDC 2.0 will print via TS redirected printer every time still to through this same server. I've upgraded to Win Serv '08 RC2. No help. Ran every update possible on the clients. No help. Checked the Group Policy, Easy Print is engaged and clients have no boxes checked for disabling printers, audio, etc.

I'm going to try disabling Easy Print, install the client printer driver on the server, and see how that goes. I tried with Easy Print ENABLED to do the above, but no help.

re: Introducing Terminal Services Easy Print: Part 1

Gaurav Daga [MSFT] — Wed, 07 Oct 2009 19:00:09 GMT

Have you had a chance to review the Easy Print system requirements / troubleshooting steps at http://blogs.msdn.com/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx?

re: Introducing Terminal Services Easy Print: Part 1

David Officer of Goldendale, WA — Wed, 07 Oct 2009 19:25:39 GMT

I found the solution. I disabled in the Group Policy "Use Terminal Services Easy Print printer driver first" under

"Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection". Now below problem is solved for ALL the client PCs trying to print to their local printer via TS.

Part II gave me a hint to look at that above policy page.