Re: Forcing WTS to ignore a printer for a single user
- From: "Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 19 Aug 2005 20:32:30 -0700
If you're an application hosting company you may want to offer some option to
support non PCL Printers. There are plenty of printing programs available
that use EMF or PDF Based Printing instead of PCL or PostScript. These allow
you to support virtually any printer and cut down on bandwidth consumption.
These also make for a more stable server environment because you don't have
to install any printer drivers.
The downfall of this is that these programs are not inexpensive, i.e.
$1000-1500 per server.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
"lee_malatesta@xxxxxxxxx" wrote:
>
> Patrick Rouse wrote:
> > Why not just scrap the OfficeJet 55xx printer in favor of one that doesn't
> > use LIDIL. Another option would be script the default printer selection in
> > her session to the Network Printer.
> >
> > http://www.workthin.com/tsp.htm
> >
> > --
> > Patrick Rouse
> > Microsoft MVP - Terminal Server
> > http://www.workthin.com
>
> Patrick,
>
> We don't have control over the user having the OfficeJet 5500 series
> printer. We're an application hosting service with no control over the
> hardware that clients hook up to their workstations. We've already
> given notice that we won't support LIDIL printers, but it would
> seriously cut into our pocketbook if we didn't support workstations
> with LIDIL printers attached. The network printers are outside of /our/
> network and only available to the workstations logging in through RDC
> and not our servers.
>
> I know that there ought to be a way to do this in scripting, but I
> think it is a slightly difficult problem. It looks to me like we'll
> have to make a login script for the user that:
>
> 1. Grab the info for all of the printers that are automagically mapped.
> 2. Use some sort of pattern matching to find the one that won't print
> and the one that will based on the name that WTS maps the printer to.
> 3. Call RemovePrinterConnection on the printer that doesn't work.
> 4. Call SetDefaultPrinter to set the default printer to the one that
> does work.
>
> Or am I making this too complex?
>
> Of course, first I need to get approval from higher up the food chain
> on a new policy of creating custom login scripts for the users of our
> clients. I was hoping that there would be a way of avoiding custom
> scripts, but I'll bit the bullet if that's what it takes to get the job
> done.
>
> Thanks for the input,
>
> Lee
>
>
.
- Follow-Ups:
- Re: Forcing WTS to ignore a printer for a single user
- From: lee_malatesta@xxxxxxxxx
- Re: Forcing WTS to ignore a printer for a single user
- References:
- Forcing WTS to ignore a printer for a single user
- From: lee_malatesta@xxxxxxxxx
- RE: Forcing WTS to ignore a printer for a single user
- From: Patrick Rouse
- Re: Forcing WTS to ignore a printer for a single user
- From: lee_malatesta@xxxxxxxxx
- Forcing WTS to ignore a printer for a single user
- Prev by Date: Re: Forcing WTS to ignore a printer for a single user
- Next by Date: Re: Turn off sound
- Previous by thread: Re: Forcing WTS to ignore a printer for a single user
- Next by thread: Re: Forcing WTS to ignore a printer for a single user
- Index(es):
Relevant Pages
|
