Kinda, sorta.
You can create scripts that run when machines startup and assign the scripts through GPOs. Place the GPO on the computers OU and drill down in the policy to "Computer Configuration, Windows Settings, Scripts". If you have an organized room/machine/number system it may not be too hard to pull this off.
Inside the script is where the magic takes place. One of the methods I use is the printui.dll. If you're not familiar with this, just type this (case sensitive) at a start/run prompt:
rundll32 printui.dll,PrintUIEntry /?
Below is a small example of what you can do in a WSH script. The PC that runs this section of the script will assign the printer RM114-DJ that is shared on the machine RM114-04. It will also install the print drivers to the PC running this script. The second printui statement will make this printer the default printer.
DJPrinterConnect = "rundll32 printui.dll,PrintUIEntry /in /n\\RM114-04\RM114-DJ /q"
SetDefaultPrinter = "rundll32 printui.dll,PrintUIEntry /y /n\\RM114-04\RM114-DJ"
WSHShell.Run DJPrinterConnect,0,True
WSHShell.Run SetDefaultPrinter,0,True
One last thing we ran into with Win2003 is that when we assigned printers in the startup script, we had to assign "Anonymous Logon" to the printer security tab.
Too much information?
![[yawn] [yawn] [yawn]](/data/assets/smilies/yawn.gif)
Bob