Windows 2003 Print Clusters - Part Two

In the previous post on Print Clusters we went over the basics of the Print Cluster and covered the important file and registry locations.  Today, we are going to quickly go over some recommendations.  If you recall, the purpose of setting up a print cluster is to have a high availability printing solution.  To do this […]

In the previous post on Print Clusters we went over the basics of the Print Cluster and covered the important file and registry locations.  Today, we are going to quickly go over some recommendations.  If you recall, the purpose of setting up a print cluster is to have a high availability printing solution.  To do this you will want to configure your server with the most stable configuration for printing as possible.  The steps we need to take include:

  • disable print driver redirection
  • modify anti-virus scanning to exclude some key folder locations
  • use stable print drivers

OK, so first let's talk about disabling Printer Redirection on the print server.  While that seems counterintuitive, what we are doing is trying to avoid inadvertent driver installation.  Whenever an administrator logs in from another box via RDP, the drivers for the redirected printers would be automatically installed with Printer Redirection enabled.

Next you will want to set up your Anti-virus program to exclude the SPOOL folder from real-time scanning.  This will prevent spool files from being locked, print corruption, hangs and so forth.  A very common symptom we see as a result of anti-virus software scanning the Spool folder are the ‘0 byte’ .spl files.  Speaking of Anti-virus scanning you will also want to exclude the Quorum drive since this is a cluster server.

Now let's talk about stable printer drivers.  You should use only Version-3 user mode drivers.  Version-2 drivers (used for NT4 printing) reside in the kernel space.  If there is a problem with a Version-3 driver, the spooler may crash.  However, a misbehaving Version-2 driver can easily cause the entire server to bugcheck - not an ideal scenario for what is supposed to be a highly available solution.  If you absolutely have to have Version-2 drivers in your environment, it would be a good idea to use a different server as the print server for those printers.  That way if you do have a misbehaving kernel-mode driver that is causing the entire server to crash, the majority of your printers remain online on the clustered print server.

We're often asked about OEM versus In-box drivers.  An In-box driver is any driver included with the operating system or service pack.  OEM drivers are those drivers obtained from the manufacturer of the print device directly.  Microsoft thoroughly tests the drivers included with Windows to ensure printing functionality.  When you are using OEM drivers, always ensure that your drivers are up to date.  Use the WinPrint print processor for your printer as much as possible unless you have specific printing needs like watermark printing etc.  Some printers get some additional functionality from these; however the default print processors and monitors are sufficient for normal printing functionality.  In addition, you should use a Unidrv based driver wherever possible.

So, to quickly summarize the order of preference:

  • Inbox PostScript Driver
  • Inbox PCL 6 Driver
  • Inbox PCL 5E/C Driver
  • VISTA/Longhorn server compatible Driver
  • OEM Universal driver
  • OEM mini driver
  • OEM PostScript, OEM PCL 6, OEM PCL 5E/C, OEM PCL 5

And that brings us to the end of this post.  In Part 3 we'll discuss troubleshooting missing print queues on clustered print servers.

Additional Resources:

Microsoft, Windows 2003, Print, Clusters, Print Clusters, Knowledgebase

Source:→ Performance Team Blog