Print server Instability

[Rajeev]

We've recently rebuilt our two printer servers from
Windows 2000 to Windows 2003. Each print server is
servicing 120 print queues ranging from moderate to heavy
use. We've recently run into further instability
problems with the Windows 2003 servers and I wondering if
anyone can answer these questions

1) Is it better to use PCL or PS drivers. We do use
PDF's a fair bit.
2) Is it best to stay with the drivers built-in to
Windows 2003 or use HP's W2K drivers
3) We've been recieving a lot of GDI errors in the logs
but re-installing the drivers don't always help.
4) Does anyone know of a best practices document for
setting up a enterprise printing environment. All the
ones I've read don't quite help.
5) Since we've moved to W2K3, when we choose the HP
driver from the driver list the Microsoft provided driver
no longer appears. It's become the HP branded drivers.
Any way to force the MIcrosoft drivers?

Thanks

 

[Mike D]

1)ps BUT pcl may work better
2)Use HP drivers only if its make for Windows 2003 other wise use the ones
that came with the OS
3)???
4)???
5 Use the HAVE DISK option when changing driver and point the computer too
look at the cd -rom drive is where you have the Windows 2003 cd
Mike D

 

[Bruce Sanderson]

All of the printer drivers on the Windows CDs are provided by the printer
manufacturer. Microsoft packages them and may make some modifications.

For Windows 2003 and XP, it is important to use "Version 3" drivers (see
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpl13043).

Some "Windows 2000" drivers are actually "Version 2" drivers and may not
work correctly with Windows 2003 or XP.

1. all Windows applications, including Acrobat Reader (as far as I'm aware)
print using the Windows GDI (Graphical Device Interface), which, in turn,
invokes whatever printer driver is configured for the printer. So, whether
you use the PCL or Postscript printers is somewhat immaterial, but I would
suggest you be consistent. We are using all PCL drivers, which seems to
work OK.

2. My experience with Windows 2003 so far is that the printer drivers
delivered with the OS work OK, so I suggest using those unless there is a
later, Windows 2003 specific, driver available from the printer manufaturer.
I suggest testing any such new driver before general deployment.

3. Reinstalling a driver doesn't necessarily do much good. Most files for
most drivers end up in the same folder and are in fact shared between
multiple different drivers. This means that it is important to keep a
"compatible" set of drivers on the print server (see the HP docuement
mentioned above). See
http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm for general help
with cleaning up printer drivers.

4. Can't say I've run across such a thing. Best I can do there off the top
is:
a. keep tight control over printer driver installations on the
print servers
b. don't let user's "add network printers", but rather deploy the
printers automatically. See
http://members.shaw.ca/bsanders/NetPrinterAllUsers.htm for one technique,
but there are others (e.g. via logon scripts)
c. have a test environment where you have all the printer drivers
already deployed installed and where you can and do test new drivers before
deployment
d. if you are using Terminal Services, don't allow users to "add
printers" via their Terminal Services session.
e. wherever possible, add drivers for other OSs as "Additional
Drivers" rather than adding them to the individual client workstations via
Add Printer wizard. Only use the technique described at
http://members.shaw.ca/bsanders/NetPrinterNoPP.htm when it is the only
alternative available

5. Not sure I can relate to this issue very well, but you might try deleting
the oemxx.inf file (and associated .pnf) from Windows\inf that correspond to
the HP supplied printer drivers.

 

[JohnNews]

Rajeev:


A few months ago I built two (1 production & 1 Backup) Windows 2000 Print
Servers for one hundred users. This was a useful experience. I quickly
grew to appreciate how important it is to take effective control of my
printing environment - especially for COST & SECURITY considerations.

The other very important issue is that your network environment
(Applications, architecture, users, etc) is UNIQUE. Thus, solutions that
may work in one printing environment may NOT necessarily work in your
printer environment. Thus a useful approach to your problem should involve
different phases; each of which should be tested before moving on to the
next stage. With the old (windows 2000) print servers still in place I would
have introduced ONE windows 2003 print server. I would then install the
desired print devices to my personal PC (or some test PCs, if you have a
corporate test lab) using the 2003 print server. The purpose of this phased
approach is to prevent project failure (& this production disruption) after
the rollout. The goal is to remove the original print server (win 2000)
only after printing with the win 2003 print server is successful, first for
you then for other operators or admin. The APPROACH to the problem is
crucial to ultimate success. PLANNING (with the necessary TESTING) is also
important.


(1) My experience with PCL & PS is that PS takes longer to print but the
quality is higher. Thus I would print a graphics document with PS. For an
ordinary text document I would use PCL for speed. I installed BOTH PCL and
PS drivers on my print servers since the Lexmark CD allowed this option.

(2) I used drivers from the manufacture of our print devices. Lexmark in
this case.

(3) List specifics of error messages

(4) Check www.hp.com and run the appropriate search. Could you list some
of your best practices links

(5)



Let us know how things work out for you. keep us posted.



Thanks,
John