i just want to make sure there are no caveats with installing print drivers via group policy. also, if this is just a bad idea and a better idea exists let me know.
thanks!
i just want to make sure there are no caveats with installing print drivers via group policy. also, if this is just a bad idea and a better idea exists let me know.
thanks!
The best way to install a printer driver is with the INF file. All print vendors package their EXE files differently, so it's unreliable to use the EXE. It would be best to use something like 7-zip to extract the executable and use
rundll32 printui.dll,PrintUIEntry
to install the print driver. If you JUST want the driver it would look something like thisUse
rundll32 printui.dll,PrintUIEntry /?
to check out all the different options you have to install printers.You can always build a spool server install drivers on the server (both x32 and x64) and then through group policy make any domain account load the printers you want on logon (with logon script) something like that
In this examle you define two printers wich are on a server named "spoolserver" through a script named "name.lnk" saved on a server with IP x.x.x.x and you make the printer named "prinet1" windows default printer... When the user who is under the GP of the script above logs in his terminal will look for the printers and "download" the drivers set on the "spoolserver", no exe no nothing. I hope I helped.
With the advent of Windows 7 and 2008, this became even easier, as you can configure a printer as desired on a client computer, such as your admin workstation, then push it it into an existing GPO using a GUI menu so it requires minimal effort and not even scripting. I wanted to use it myself but I was stuck with the answer you accepted often in the past because of limitations in my environment. I hope this appeases people who thought my link for an answer was too brief, and now I can beat a dead horse even deader.