Has anybody made the Easy Print driver work in Windows Server 2008?

 

Scenario

Server 1

SBS 2000 (waiting for SBS 2008) server

Server 2

Server 2008 (running Savant-CRM crm package and TS 2008)

 

Clients in remote office successfully logging in to Server 2 (RDC 6.1 (6.0.6001) & .NET Framework 3.5 installed) and running Savant-CRM and Outlook. 

 

Printers appear corredtly in TS session and are listed as Easyprint driver but test page does not print!

(Yes, the workstation does print correctly to the network printer when in local mode.  The printer is attached via USB to another workstation in the remote office workgroup.)

OK, problem nearly sorted - Easy Print only works with XP and SP3 (or, more accurately, components included in SP3).  I have not received a list of hotfixes to allow updating an XP system without installing the SP but I will ask fro same. 

 

The nearly bit is a system error is thrown up after each print which relates to the .net configuration.  Awaiting advice from relevant MS technical support.

 

I have persevered with this issue because the Easy Print is actually very cool.  The facility to add printers at the client end and having them directly available in the TS session is a significant improvement to configuring the server & client as in previous versions.

 

I will post the solution to the nearly when available.

Hi,

 

What error do you get? As you didn't mention that in your first posting.

In answer to your question about error message - in the first instance where the TS EasyPrint servvice was not working there was no error message.  Apparently the EasyPrint command was sent to the server but was not returned to the client for local printing.  This was resolved by installing SP3 to the XP workstations.  I understand that there is a similar situation with Vista and SP1 although I have no Vista workstations on this site and consequently can only repeat that which I have read.

 

The error message that comes up when the printing does work is -

EventType : clr20r3 P1 : tswpfwrp.exe

 

I have found the following thread which details this problem and dates back to April! 

http://forums.technet.microsoft.com/en-US/winserverTS/thread/3eda7a79-7294-46de-b3e3-2d78d2cc980c/

 

According to the MS Technical Support person there are multiple reasons this error can occur!!!  I am still trying to get to the bottom of this and fortunately my clients are so happy to be printing that they are alright with cancelling the MS error report after each print job.