Thoughts from the EPS Windows Server Performance Team
Useful Microsoft Blogs
Today we're going to start looking at Clustered Print Servers. Clustering itself tends to intimidate many administrators, especially newer administrators. Much of the fear factor usually stems from being unfamiliar with how clustering works, and the fact that you are dealing with shared storage. Throw in the fact that most production clusters are providing mission-critical services and it's easy to see how an administrator might be somewhat hesitant regarding clustering. While we're not really going to cover clustering itself in this post, we will touch on some basic concepts as we go along. So let's get started ...
So what exactly is a print cluster? A print cluster is a print server that is configured as a spooler resource on clustered servers. In a Windows Server 2003 cluster server configuration is a group of independent computers that work together to provide a common set of services and present a single-system image to clients. What this means is you group two or more physical servers presenting a single virtual server name to clients. That virtual server name is the access points to services created on the cluster, including printing. For example: You have 2 physical servers, NodeA and NodeB. Those servers are in a cluster group and have a spooler resource installed. That spooler resource has a name associated with it: PrintServerA. Clients access ‘\\PrintServerA’ to gain access to printers installed on the spooler resource.
There are numerous services and applications that can be clustered - for example, SQL and Exchange are often clustered. Network services such as File Servers and Print Servers are perhaps the most common examples of non-application clusters. We are going to focus on Print clusters since that is primarily the area that the Performance team supports. When you think of a print cluster, just remember that what you are dealing with is a print server that is installed on a clustered set of servers and presents a single virtual server name to clients. The print cluster provides a high availability solution for printers. Thus, if the active node (server that owns the print resource) fails, the print resource fails over to the next server in the cluster. This allows the printers to remain available by maintaining the same access point for clients. So in our example above, if NodeA owns the print resources and fails for some reason, then the resources would fail over to NodeB. From the client perspective, they would still just access the virtual server name - \\PrintServerA.
Okay, before we get into the troubleshooting of common print cluster problems and best practices, it is important to understand where the information is stored. The primary difference between a local print server and clustered print server is the file and registry locations where the print cluster stores configuration information. We covered the Basic Printing Architecture in a previous post.
Note: The information below applies to Windows 2003 server clusters only as there are significant differences between the functioning of a Windows 2003 and windows 2000 print cluster.
Windows Server 2003 cluster service stores all printer and port information inside the cluster registry: HKLM\Cluster\Resources. Each <Resource GUID> subkey represents a clustered resource. You can look at the “Type” value of a given resource to identify a Print resource; it should have the value data: “Print Spooler” as seen below:
The HKLM\Cluster\Resources\<Resource GUID>\Parameters key contains the print spooler configuration information of interest. All printer, driver and port information is stored in separate keys under the Parameters key. From this point onwards the registry structure is mostly the same as that of the local spooler at: HKLM\SYSTEM\CurrentControlSet\Control\Print.
Let's take a look at some of the other important registry keys:
The clustered print spooler files are stored separately from that of the local spooler. The start of the tree for file storage is here: C:\windows\system32\spool\drivers\<GUID> as shown below.
Beyond this the folder structure is same as that of the standalone server's print spooler. The drivers, print processors and color profiles are stored here under appropriate folders. The driver files installed on the clustered print spooler are located in the following folder: C:\windows\system32\spool\drivers\<GUID>\Drivers\. For example, for x86 print clients the drivers are stored under C:\windows\system32\spool\drivers\<GUID>\Drivers\w32x86. Let's take a look at some other important folders:
I guess that's enough theory for this post. In our next post on Windows Server 2003 Print Clusters, we'll take a look at some best practices and guidelines.
- Sumesh P.
PingBack from http://www.ditii.com/2007/07/20/windows-2003-print-clusters-part-one/
I upgraded our Window 2000 Cluster server to Windows 2003 by doing a rolling upgrade. When I completed the first node I performed a failover and everything ran fine. I left it running on the upgraded node for a week to ensure no problems. I then upgraded the second node to Windows 2003 and when I performed the failover the Cluster Printer group starts but drops off right away(file group runs fine), then the other node does the same. When this happens the printer spool service on each node gets stopped.
I have deleted the printer group and am trying to recreate it; I have the group created with the Printer Ip, Printer name and Spooler disk resouces created, but when I try to create the print spooler resouce, "Print Spooler" is not listed as a resource in the pull down for resource type! How can I get the print spooler to show up as a resource type? The print service is running and the cluster service is running.
Hello my Win2k3 experts, I got a question for you:
I am trying to create a cluster here and so far I have succeeded in creating a cluster with the IP address, network name, file share resources
I am trying to create a printer spooler resource but apparently I need a storage/physical disk resource or something first...now, whenever I try to add a physical disk resource I choose ther correct group and dependencies, get to the screen where I am supposed to choose a physical disk..but there is nothing in the drop down box!
One thing I should mention is that there is only one hard drive on this disk and from what I know on the subject you cant have a print spooler on the same HD or something...so I attached a usb sata drive and I see it as a seperate HD in my computer...but when I go through the physical disk resource..it still does not see it,
any idea why? what other options do I have? One thing I should mention is that all of this is on a virtual VM Windows 2003 Server Enterprise edition...so I cant really put another HD in the system
we have big problems with the performance of our print cluster. Sometimes we get the messige "Printer can not be installed. The process could not be finished". I read someting about messages "The printprocessor is not available", we had this message in the past too. These messages are appering, if we try to install a new printer.
We have installed SP2. This is only a known issue for SP1 or earlier...
We have a 4 node cluster installed. The issue we are having is, on occasion and end user is unable to print. This is random and not specific to one machine or machine type. We are utilizing host based names with dynamic IP on the end printer.
What we have observered is the print queue exists on the local machine and when a print job is sent, you can see it hit the queue and disappears, the local machine displays a sucessful print message, however the printer does not print the job.
We have checked and spooler is working and all correct drivers are installed. Any suggestions on how we might correct the issue?