What is always common sense is not always common practice.
NOTE: When removing print drivers from a Windows machine's "Server Properties", ensure that the driver is not in use by *ANY* printers under *ANY* user profile settings.
(Under Control Panel > Printers and Faxes, right-click and select 'Server Properties')
So basically, I was working on imaging a set of Compaq 6720t and the imaging would repeatedly fail at 95% on the printer driver files.
After spending a few minutes thinking about it,I thought I'd share what could save you hours worth of frustration. Also, it is my hope that by sharing what works, that you would use the information to establish Intentional Best Practices.
So here's the tip:
When you want to remove Windows printer drivers, check ALL your users to make sure that NONE of their printers are using that driver. Otherwise, you won't get very far.
Is this an issue? No.
Is this some flaw in Microsoft's Windows design? No.
In fact, this is to Microsoft's credit. They encourage us to earn our living by learning to identify the source of their error messages. :)
(some are obvious, and some are not)
NOTE: When removing print drivers from a Windows machine's "Server Properties", ensure that the driver is not in use by *ANY* printers under *ANY* user profile settings.
(Under Control Panel > Printers and Faxes, right-click and select 'Server Properties')
So basically, I was working on imaging a set of Compaq 6720t and the imaging would repeatedly fail at 95% on the printer driver files.
After spending a few minutes thinking about it,I thought I'd share what could save you hours worth of frustration. Also, it is my hope that by sharing what works, that you would use the information to establish Intentional Best Practices.
So here's the tip:
When you want to remove Windows printer drivers, check ALL your users to make sure that NONE of their printers are using that driver. Otherwise, you won't get very far.
Is this an issue? No.
Is this some flaw in Microsoft's Windows design? No.
In fact, this is to Microsoft's credit. They encourage us to earn our living by learning to identify the source of their error messages. :)
(some are obvious, and some are not)
