Windows Server 2008 R2 Failover Print Clusters Stability Update

Microsoft fixes an issues for print server failover clusters that’re running Windows Server 2008 R2. “First problem involves “print processor of related driver [having] multiple dependent files. […] In this scenario, shared printer may be missing on new node after failover operation. Only one dependent file is copied to destination node in every failover operation. […]

Microsoft fixes an issues for print server failover clusters that’re running Windows Server 2008 R2. “First problem involves “print processor of related driver [having] multiple dependent files. […] In this scenario, shared printer may be missing on new node after failover operation. Only one dependent file is copied to destination node in every failover operation. The printer is missing after failover operation because some dependent files aren’t available. In second scenario, clients opening connections to a shared printer’ll cause it to fail. This happens because print server failover cluster is thrown into an infinite loop. Third issue is associated with use of Print Back-up Restore Migrate utility (Printbrm.exe) in order to perform restore processes for printers on a print server failover cluster. Customers affected by glitch reported that they were unable to restore certain printers, and that they came across following error message: 1081 invalid printer name. “We recommend that you install this update on all the print server failover cluster nodes that are running Windows Server 2008 R2 to make sure that basic functionality and that basic manageability is maintained,” explained Microsoft in KB976571.