On our campus, our management purchased a number of Xerox ColorQube 9203 copiers that they wish to be setup with printing capabilities to departmental users. We have successfully used LANDesk for pushing out Printer Driver packages to install things like HP LaserJet printers as well as other copiers, all with default options set and no changes.
For the colorqubes, the vendor and our network manager wanted specific changes put in place including SNMP name changes and other preferences included in a .cfg file that is pulled down as part of the install. I can get my batch script to install the driver manually so I know the process/script works. However, when I try it within LANDesk, whether as a PUSH or through the Desktop Manager as a policy available to people, it seems to fail out on the "rundll32..." printer addition line (see my attached script). Is there anything different about how LANDesk's processes might be excecuting this script versus my executing it manually that could be causing it to fail and not install the printer? Any insight would be most appreciated!
lanigan_cq_install.cmd.zip 1,018 bytes