I'm having a few issues with printers at the moment and I think I need to reset my thinking.
My current method of adding a printer to a network is to use the standard Add a Printer wizard and create a standard tcpip port on a server and then say I've got a disc and browse and install the printer using the drivers on the CD that comes with it.
I then share it out and set the normal printing defaults and the advanced printing defaults to what I want (just standard telling it to use A4 paper).
I then use a simple vbs script on each workstation to add the printer to each workstation (my clients don't operate as domain clients - they just use a single pupil (or teacher) user account)
One of my questions is when a client sends a print job - does it get sent to the server and onto the printer or does it get sent directly to the printer.
' Example VBScript to map a printer on a server
' Guy Thomas February 2004.
Dim netPrinter, UNCpath
UNCpath = "\\server2\juniors2"
Set netPrinter = CreateObject("WScript.Network")
' WScript.Echo "Your printer is mapped from : " & UNCpath
' End of example VBScript
Another question is is this the best method to use - should I install the printer using the vbs script or should I be using the printui method
which is a lot harder to get setup (needs the tcpip port creating first and I have to work out all the driver info) and ends up with the client talking directly to the printer (AFAIK anyway )
rundll32 printui.dll,PrintUIEntry /if /b "Juniors2Direct" /f \\server2\icttech\hp8000driveronly\hpoj800z.inf /r "IP_10.86.8.11" /m "HP Officejet Pro 8000 A809 Series" /Z