please forgive me if my green is showing. we're still in the pilot phase of altiris here, and my lack of training probably shows. I also have limited experience with VB and SQL, so go easy on me.
when you mentioned tokens, the first thing that came to mind was to give our techs write access to a batch file somewhere that simply contains:
Code:
set %printername%=PRINTERNAME
the tech would change PRINTERNAME to AHS-100-P01 or BHS-123-P02 or whatever the printer is shared as on the server. then the job in ds would be simple and static.
Code:
REM Add Printer on Printer Server PS01
start /wait rundll32 printui.dll,PrintUIEntry /ga /n \\PS01\%printername%
sleep 10
net stop spooler
net start spooler
the problem with this method is if there happens to be 2 techs adding printers at the same time or even one tech adding multiple printers, or if a job doesn't run immediately on a machine, or if someone forgets to change the batch file that sets the token... basically the same reasons we don't want the techs to be able to edit the job directly in DS.
I'm interested to see what you have, but at this point we're starting to think that we may just have to put one person in charge of deploying printers, and have that person just edit the printername variable directly in DS... that way there's no stepping on toes or other conflicts.
either that or just create 900 jobs for all those printers... *shudder*
