Updating print driver files onto an existing printer share on server
Hi everyone,
Occasionally, but it's been happening a lot recently, I've had issues with updating print driver files onto an existing printer share on a windows server. For example, there might be an existing printer share with the name 'Printer1', and the customer want's to keep that same printer share name and wants to update the print driver files on it, which is fair enough. But the problem I sometimes face is when updating the print driver files on the printer share, the driver files don't carry on over to some of the client/local PC's that are connecting to that printer share. For example it keeps the old print driver files, with the same settings or users can't print or get printing errors. I try to delete the printer and drivers off the client/local PC's and rebooting, then re-adding the printer from the printer server, but the problem sometimes still occurs.
On the server end to update the print driver files on the printer share, I usually go to 'server properties' in the printers menu and add the print driver files, then open the properties of the printer share and go to the advanced tab, bring down the print driver selection drop down list and choose the driver. This process gives me less problems than just adding the new print drivers directly to the printer share via the advanced tab in the properties, and then using the 'New driver' button.
This issue doesn't seem to be specific to a particular windows operating system, it occurs on all, and I always make sure I have the latest drivers and add the 64bit drivers when necessary. I should also mention that deleting the printer share and reinstalling it usually helps fix the problem, but on the odd occasion I still get erros on the client/local PC end.
Has anybody experience this before, I'd image so as it doesn't seem to be manufacturer or driver specific from personal experience. I've been told it's a windows SMB and caching issue.
Thank you for any advice and tips.
Occasionally, but it's been happening a lot recently, I've had issues with updating print driver files onto an existing printer share on a windows server. For example, there might be an existing printer share with the name 'Printer1', and the customer want's to keep that same printer share name and wants to update the print driver files on it, which is fair enough. But the problem I sometimes face is when updating the print driver files on the printer share, the driver files don't carry on over to some of the client/local PC's that are connecting to that printer share. For example it keeps the old print driver files, with the same settings or users can't print or get printing errors. I try to delete the printer and drivers off the client/local PC's and rebooting, then re-adding the printer from the printer server, but the problem sometimes still occurs.
On the server end to update the print driver files on the printer share, I usually go to 'server properties' in the printers menu and add the print driver files, then open the properties of the printer share and go to the advanced tab, bring down the print driver selection drop down list and choose the driver. This process gives me less problems than just adding the new print drivers directly to the printer share via the advanced tab in the properties, and then using the 'New driver' button.
This issue doesn't seem to be specific to a particular windows operating system, it occurs on all, and I always make sure I have the latest drivers and add the 64bit drivers when necessary. I should also mention that deleting the printer share and reinstalling it usually helps fix the problem, but on the odd occasion I still get erros on the client/local PC end.
Has anybody experience this before, I'd image so as it doesn't seem to be manufacturer or driver specific from personal experience. I've been told it's a windows SMB and caching issue.
Thank you for any advice and tips.