In Windows 2000 Advanced Server and Windows 2000 Datacenter Server the major enhancement is that port information was moved to be stored in the Cluster registry and replicated to all nodes. Port monitors must be Cluster Aware to be supported on a cluster (where under Windows NT 4.0 all port monitor types were supported). All drivers are still stored in the local spool directory. Local and clustered print queues all share the same common drivers. Here’s a summary of the main differences:
Driver information stored on the local node under HKLM\System\CurrentControlSet\Control\Print\Environments.
You no longer have to create locally defined printers on each node in the cluster to get the port configuration on each node. The port configuration is stored in the cluster registry and therefore shared between the cluster nodes. The printer driver files do not share between the nodes because of a restriction on the Server service (there must be unique share names on the computer/server cluster). When you install a printer driver on a cluster virtual server, it connects to the print$ share that is mapped to the WinDir\System32\Spool\Drivers folder of the resource-owning computer.
· Print queues are replicated to all nodes
Port information is now stored in the cluster hive. \Printers, \Monitors and \Providers keys are present
In Windows Server 2003, Enterprise Edition, and Windows Server 2003, Datacenter Edition, the major enhancement is that printer drivers are replicated to all nodes in the cluster. In Windows Server 2003, managing and maintaining a clustered print server is as easy as a stand-alone print server. After initial configuration of cluster resources is complete, administrators just connect to the virtual server name and install printers and drivers as they would with any stand-alone server. Here’s a summary of the main differences:
Managing a clustered print server is just as easy as a stand-alone print server. With the exception that all Port Monitors still need to be installed on each node. Connect to \\VirtualServer\Printers & faxes and install the printer as you would a stand-alone print server, copies of the installed driver are stored on the shared cluster disk under \PrinterDrivers. When the print spooler resource group fails over, it copies the required drivers from the \PrinterDrivers folder if necessary.
Windows Server 2003
The registry structure is very similar to a standalone print server. In Windows Server 2003 the cluster service now stores all printer and port information in the cluster registry. Windows NT 4.0 did not have the printer drivers or the port information in the cluster configuration and Windows 2000 had only the port information. All printer information is stored under the following registry key:
This key contains all of the keys that contain printer specific information. It also has the values that contain spool directory information and job completion timeout information.
This key contains the structure necessary for other Windows based print clients (such as Windows NT 4.0, Windows 2000 and IA64-based Windows Clients).
This key is where the cluster will store any monitor information. Microsoft will only support the TCP/IP and LPR standard print monitors that ship with the operating system on a cluster. All of the information regarding the TCP/IP ports, such as the port address, name and SNMP information, is also stored here. This only has the port list no other values are used. All other monitor information is located in the local node key.
In this key all printer information is stored. The information is stored on a printer by printer basis. This information is exactly the same information that would get stored for a printer that was non-clustered in HKLM\SYSTEM\CurrentControlSet\Control\Print key.