Thanks for the input, Ben. One problem with the Xerox drivers is an annoying interaction with Acrobat (I need to test the new one to see if it even helps). The problem is that when you select a non-default paper size (say 11x17) normally Acrobat will pick that up and you can have acrobat set to "fit to page". Unfortunately with the Xerox driver, there is an "input paper size" and an "output paper size" and the normal paper selection GUI only changes the output paper size (acrobat thinks you are still in 8.5x11). To get acrobat to print correctly, you need select "other size" and you will get a GUI that lets you set both input and output paper sizes (setting both to 11x17) to get the correct printout.
The problem with the HP driver (4.5) happens when I try to set up a direct print from a PC to the printer (not going through the print server). I had to use version 4.7 on the PC's that I set up to print directly. I am guessing that the version 5.0 has fixed this issue and would let me get everything running the same version. Not sure I want to upgrade based on the "encouragement" I am getting here (DON'T DO IT MAN!!) -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Thursday, September 17, 2009 8:41 PM To: NT System Admin Issues Subject: Re: Print server driver updating On Thu, Sep 17, 2009 at 4:01 PM, Alverson, Tom (Xetron) <tom.alver...@ngc.com> wrote: > I would like to update the print drivers on our Windows 2003 SP2 print > server ... Why? What problem are you trying to solve? > I could just update the drivers on the print server for the existing > print queues, but I don't know if the clients will automatically pick up > the new drivers, or if they will need to delete and re-add the queues or > what? In theory, if one updates the drivers on the print server, the next time the client logs in or "touches" the print queue, it will automatically pull down the updated driver. In practice, we've found HP's drivers tend to self-destruct when subject to this. I suspect it's a function of how complicated the driver is, and how well written it is, and HP sucks at both right now. The "generic PCL5" driver we hacked together from the HP LJ 4 driver that came with Windows XP seems to be fine. The Lexmark drivers also seem okay, but we've only got a few Lexmark printers deployed so far. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
