Programatic Removal of Network Printer in All Profiles on a Workstation
-
Hello to all. I've been staring at this administrative task for a while to try and help folks in helpdesk environments. I'm comfortable scripting vbs/wmi to do removal of specific network printers at login (using WMI RemovePrinterConnection), but for the life of me I've yet to see anything which can process it for all users on a particular station w/o having the user login. The only other option I've seen has been to blow away the user profile which is excessive. In particular I'm targeting older 2000 stations which are getting a lot of driver corruption. Any recommended tools or resources I can read on the matter would be greatly appreciated.
-
Hello to all. I've been staring at this administrative task for a while to try and help folks in helpdesk environments. I'm comfortable scripting vbs/wmi to do removal of specific network printers at login (using WMI RemovePrinterConnection), but for the life of me I've yet to see anything which can process it for all users on a particular station w/o having the user login. The only other option I've seen has been to blow away the user profile which is excessive. In particular I'm targeting older 2000 stations which are getting a lot of driver corruption. Any recommended tools or resources I can read on the matter would be greatly appreciated.
Printers aren't installed in the user context. They're installed in the machine context, meaning if one person installs/removes a printer, it's installed/removed for everyone on that machine. What IS done in the user context is each user gets their own set of default printer settings.
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Printers aren't installed in the user context. They're installed in the machine context, meaning if one person installs/removes a printer, it's installed/removed for everyone on that machine. What IS done in the user context is each user gets their own set of default printer settings.
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007Hi Dave, Thanks for the clarification there. The issue I'm bumping into is that most of the tools which are using WMI/VBS to try and remove the driver on a per machine basis can't do so w/o removing the print defaults in each of the user profiles. The old "Driver in use" issue. So far though I haven't seen anything that would allow me to enumerate then remove the defaults per user profile.
"I've learned that life is one crushing defeat after another, until you just wish Flanders was dead." [Homer J Simpson]