Hi all
I hope I've chosen the right forum for this question; mods please let me know if not.
I've been having severe problems with my printers since the August Patch Tuesday. After investigation, I've realised that we're not the only ones with this problem; it was caused by one of the patches MS released (KB896423; see these for more info:
So we know what the problem is. As you'll see from the other discussions, various printer models are affected; in our case no Win 2000 machines can print to Xerox 2240s anymore. The solution is to upgrade the driver on the 2000 machine to the latest available from Xerox. So far, so good.....the problem is that we have over 150 machines in this situation and I'd really like to avoid having to go around to 149 more machines to install the new driver! (I don't think we can script the driver install as it is not an executable...just an inf and some dlls)
The print setup here is that we print to a clustered server, which comprises 4 nodes on Enterprise Server 2003. We are using Cluster Administrator v5.2. My plan was just to remove/replace the existing driver on the cluster, and then hopefully the affected clients would pick up the working driver the next time they logged on (the point at which Scriptlogic restores the connections to the printers). However I cannot, as an error pops up saying that the files are in use. I have tried doing this with all 4 nodes paused, with the print spooler stopped on each of the 4 nodes, etc and still am not able to get rid of the currently installed driver.
Clustering is not one of my strong suits(!), so my question really is if anyone knows of any way to successfully remove a printer driver from a clustered print server (short of having to delete the 50-odd Xerox print queues we have set up!)
Any help/advice/suggestions would be very gratefully received!!!
Thanks!
Cheers,
Graeme
I hope I've chosen the right forum for this question; mods please let me know if not.
I've been having severe problems with my printers since the August Patch Tuesday. After investigation, I've realised that we're not the only ones with this problem; it was caused by one of the patches MS released (KB896423; see these for more info:
So we know what the problem is. As you'll see from the other discussions, various printer models are affected; in our case no Win 2000 machines can print to Xerox 2240s anymore. The solution is to upgrade the driver on the 2000 machine to the latest available from Xerox. So far, so good.....the problem is that we have over 150 machines in this situation and I'd really like to avoid having to go around to 149 more machines to install the new driver! (I don't think we can script the driver install as it is not an executable...just an inf and some dlls)
The print setup here is that we print to a clustered server, which comprises 4 nodes on Enterprise Server 2003. We are using Cluster Administrator v5.2. My plan was just to remove/replace the existing driver on the cluster, and then hopefully the affected clients would pick up the working driver the next time they logged on (the point at which Scriptlogic restores the connections to the printers). However I cannot, as an error pops up saying that the files are in use. I have tried doing this with all 4 nodes paused, with the print spooler stopped on each of the 4 nodes, etc and still am not able to get rid of the currently installed driver.
Clustering is not one of my strong suits(!), so my question really is if anyone knows of any way to successfully remove a printer driver from a clustered print server (short of having to delete the 50-odd Xerox print queues we have set up!)
Any help/advice/suggestions would be very gratefully received!!!
Thanks!
Cheers,
Graeme