We have some 40+ different printer types on our campus. We have a secured user enviroment so they cannot install drivers themselves. I am looking for a way to improve the way we deploy drivers to workstations.

Currently we have a script that logs in under local admin, install the printer then deletes the printer. thus keeping the drivers installed but deletes the icon under the printer folder. Thus when users select a printer at this point it just adds the icon back and they can then use the printer.

This process is rather archaic and I would like to find a way to improve it.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


How are you doing it at the moment, I usually either copy files locally and update DevicePath or use printui.dll..

printui.dll http://www.microsoft.com/windowsserver2003/techinfo/overview/printuidll.mspx

There is also DIFx http://msdn2.microsoft.com/en-us/library/ms790264.aspx
Answered 03/29/2007 by: Tone
Second Degree Blue Belt

Please log in to comment