Printng to CutePDF Writer WTS 2003

[Guest Marc]

I have installed CutePDF Writer on my W2K3 TS and have had my clients install

it also, When they connect to the TS, the (CutePDF Writer) printer is not

available for their use. It is for me. They log in with Domain User rights,

I have Admin. When they set their regular printer as default it shows and

they are able to print without issues. All of these clients have the

FilterQueueType reg hack done on their end. Any ideas what can be preventing

these users from seeing or having their CuterPDF Writer not mapping to the TS?

[Guest Lanwench [MVP - Exchange]]

Re: Printng to CutePDF Writer WTS 2003

 

Marc <Marc@discussions.microsoft.com> wrote:

> I have installed CutePDF Writer on my W2K3 TS and have had my clients

> install it also, When they connect to the TS, the (CutePDF Writer)

> printer is not available for their use. It is for me. They log in

> with Domain User rights, I have Admin. When they set their regular

> printer as default it shows and they are able to print without

> issues. All of these clients have the FilterQueueType reg hack done

> on their end. Any ideas what can be preventing these users from

> seeing or having their CuterPDF Writer not mapping to the TS?

 

Not sure whether virtual printers & CutePDF specifically work with

redirection. However, since you want all users to have it, why wouldn't you

just install CutePDF & Ghostscript on the TS box as a *local* printer and

avoid the entire issue?

[Guest Marc]

Re: Printng to CutePDF Writer WTS 2003

 

Unfortunately, I can't add it as a local printer due to the way it functions.

When a user printers to it, it opens a "save box" and you typically browse

to where you want it, name it, and save it. If it's added as a local printer

it passes nothing down to their local machine, it only asks to save on the

network the TS is on, which is mine. So no good. CutePDF Writer says it is

compatiable with Terminal Services and as I stated it works for me just fine.

 

"Lanwench [MVP - Exchange]" wrote:

> Marc <Marc@discussions.microsoft.com> wrote:

> > I have installed CutePDF Writer on my W2K3 TS and have had my clients

> > install it also, When they connect to the TS, the (CutePDF Writer)

> > printer is not available for their use. It is for me. They log in

> > with Domain User rights, I have Admin. When they set their regular

> > printer as default it shows and they are able to print without

> > issues. All of these clients have the FilterQueueType reg hack done

> > on their end. Any ideas what can be preventing these users from

> > seeing or having their CuterPDF Writer not mapping to the TS?

>

> Not sure whether virtual printers & CutePDF specifically work with

> redirection. However, since you want all users to have it, why wouldn't you

> just install CutePDF & Ghostscript on the TS box as a *local* printer and

> avoid the entire issue?

>

>

>

[Guest Lanwench [MVP - Exchange]]

Re: Printng to CutePDF Writer WTS 2003

 

Marc <Marc@discussions.microsoft.com> wrote:

> Unfortunately, I can't add it as a local printer due to the way it

> functions. When a user printers to it, it opens a "save box" and you

> typically browse to where you want it, name it, and save it.

 

Yes. I happily use CutePDF & know how it works....

> If it's

> added as a local printer it passes nothing down to their local

> machine, it only asks to save on the network the TS is on, which is

> mine. So no good. CutePDF Writer says it is compatiable with

> Terminal Services and as I stated it works for me just fine.

 

 

Ah. Well, I want my users to save all their data on the network they've

connected to, myself.

My CutePDF doesn't redirect either, for what it's worth (to W2003 TS either

as a user or an admin).

>

> "Lanwench [MVP - Exchange]" wrote:

>

>> Marc <Marc@discussions.microsoft.com> wrote:

>>> I have installed CutePDF Writer on my W2K3 TS and have had my

>>> clients install it also, When they connect to the TS, the (CutePDF

>>> Writer) printer is not available for their use. It is for me.

>>> They log in with Domain User rights, I have Admin. When they set

>>> their regular printer as default it shows and they are able to

>>> print without issues. All of these clients have the

>>> FilterQueueType reg hack done on their end. Any ideas what can be

>>> preventing these users from seeing or having their CuterPDF Writer

>>> not mapping to the TS?

>>

>> Not sure whether virtual printers & CutePDF specifically work with

>> redirection. However, since you want all users to have it, why

>> wouldn't you just install CutePDF & Ghostscript on the TS box as a

>> *local* printer and avoid the entire issue?