Printing Nightmares



Hi

Setup:

2 x Windows 2000 Terminal Servers
1 x Windows 2000 Server - Domain Controller

60 (and rising) remote users, with varying cheap multi-function printers.

I am currently using a combination of the 'Terminal Services Printer
Redirection Wizard', and manually editing the ntprintsubs.inf file that it
creates, in order to provide our remote users with printing functionality
through TS. Printing is essential to them, and the application we host for
them is useless without printing.

So, currently we get a new user onboard. More often than not, they then call
me to say they cannot print. So, I check the Event Viewer, run the TSPRDW
program, and map what I think could be a decent printer driver match. Most
of the time the printer works, but on the odd occasion the end-user gets
garbled print or nothing at all. This is where I then have to start trying
all different drivers, and eventually I just give up and install the
manufacturers bloated drivers, which I know is very bad practice.

I would appreciate some advice on a quicker, more reliable way of handling
this. I have come to the conclusion that I have these options:

- upgrade the Terminal Servers to W2k3. Will the driver rollback feature
help me with this problem? There's the additional TSCAL license cost I will
have to consider too if I do this. All my clients are Win2k or XP so they
don't have to pay for a TSCAL when I'm using 2000 Server.

- third-party printer management software. I've downloaded APM from
http://www.dabcc.com/apm/. I'll try and have a look at this this week, but
I'm a bit worried about installing this in a live environment. I have no
real test environment.

- carry on with the massive overhead of maintaining printer drivers across x
number of TS'. This server 'farm' will probably grow to around 6 servers
before the end of the year. I really don't want to do this!

- Citrix? Would Citrix help me in any way here?

I'd appreciate any advice or pointers, before I tell all our end-users that
we don't support anything except Laserjet 1200's :)

Thanks

Dan


--
Talent hits a target no one else can hit. Genius hits a target no one else
can see.


.



Relevant Pages

  • RE: Windows 2003 server restart with system error
    ... With a HP Proliant ML350. ... driver, because, I think that is impossible that 3 servers from same ... I Will checking for drivers and let you know the results. ... Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter ...
    (microsoft.public.windows.server.general)
  • Re: COD4 HARD Lockups
    ... So I've changed my SATA drivers and ran memtest over night, updated BIOS and removed on-board sound drivers. ... enabled servers. ... in order for the lockups to go away. ... so what I did was turn all the other settings down to their lowest ...
    (microsoft.public.windows.vista.games)
  • RE: Printing Nightmares
    ... I was never able to get printing right with TS2000. ... 60 remote users, ... manufacturers bloated drivers, which I know is very bad practice. ... upgrade the Terminal Servers to W2k3. ...
    (microsoft.public.windows.terminal_services)
  • Re: Obsoleteness of X concept
    ... I can see either kernel drivers or X drivers are out ... This is part 1 - why another hardware abstraction layer. ... the X servers exists because not all X servers supports all the ...
    (comp.os.linux.x)
  • RE: Windows 2003 server restart with system error
    ... Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter ... bad memory (maybe memory leaks caused by bad drivers) ... Does your event viewer show any other suspicious events? ... The two servers are update with all patch ...
    (microsoft.public.windows.server.general)