Brandon,

Have you verified that the printer may only be getting installed under the profile of the altiris account you are using to do the push?

Though I think this is just a limit to installing this way if I remember correctly.

If that is the case. I would create a job to copy the file down to the workstation and then chain it to a job to create a line in RunOnce in the registry to run your installation script and that way every user who logs in would run it and that would be a work around.

Basically it becomes a login script.

Here is a link also for using that /qa switch:
http://members.shaw.ca/bsanders/NetPrinterAllUsers...

Hope this helps.

~Terry

Here is a vbscript I used to use:

Option Explicit
Dim objPrinter
Set objPrinter = CreateObject("WScript.Network") 
objPrinter.SetDefaultPrinter "\\printserver\printer"
' End of example VBScript

The script will only truly run in DS if you run it with a user account instead of the system account. the system account does not have access to a network printer.

Nate Hudson
Senior Systems Engineer
West Bend Mutual Insurance

You may want to adding some quotes for your script. The command will not see your switchs due to the space.

START /WAIT "SC STOP spooler"
START /WAIT "SC START spooler"

Working in a print media company we've networked out photo printers so that photographers can print quicker to them. I just saw a commercial on tv for wifi printers with a family sitting on a couch with laptops and cat5 running to their office comp. I have to laugh at this since it's easier and i think more secure just sharing it and connecting rather then having one more wireless device you need to worry about broadcasting.

pct would be the easy way to go. You can just capture the printer settings and drivers and deploy that to multiple machines through the deployment console.