Video Screencast Help

Deployment Solution Bulk Task Add

Created: 19 Feb 2013 • Updated: 19 Mar 2013 | 8 comments
This issue has been solved. See solution.

I would like to be able to add a list of machines to a given task or task by scripting/programing.  It seems like I should be able to pass the machine name(s) to a stored procedure to add them to a given task.  Can anyone give me some gudiance or point me to some documentation?  To clarify the concept, I would like to be able to add a list of computers to upgrade Flash in an automated fashion rather than manually adding machine by machine to the task.  Please note I am using Deployment Solution 6.9 SP5, not the full CMS.  Thank you in advance for your assistance!


Comments 8 CommentsJump to latest comment

andykn101's picture

Use the axsched command. Syntax should be in one of the Appendices to the docs.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

jason.f's picture

Take a look at this post, someone wrote a custom GUI to schedule jobs for a list of computers. Works awesome, I use it all the time.

You can also programatically create jobs using other utils included with DS, I did this to create all my printer install scripts, all 1800+ of them. If you need details I can dig them up for you.

pshore's picture

Andykn101 and Jason.f thank you for your replies!

Jason I will check out that link and I would love to see the details of your scripts. Any additional automation I can do gives me time to work on other things.

Thank you again.

jason.f's picture

Here's what I have to create a Run Script job in DS. This one is written in Powershell but it should be pretty easy to convert to VBS if needed once you see how it works.

This script is for creating my printer install jobs. First I grab a list of all my printers, then I create a temp VBS script to hold my commands. Then I loop through each printer in the text file and build my temp VBS, then after that I run the axEvent.exe to import that script. The only thing about doing it this way is there's no way to set the job to run hidden. What I ended up doing is modifying the properties of the job directly in the table to set the jobs to run hidden.

$printerlist = Get-Content c:\temp\printer_list.txt
$tmpscript = "c:\temp\tmp.vbs"
foreach ($printer in $printerlist)
$printer = $printer.toupper()
Add-Content $tmpscript "REM Install $printer on Print Server"
Add-Content $tmpscript "rundll32 printui.dll,PrintUIEntry /ga /n\\PrintServer\$printer"

& D:\Progra~1\Altiris\eXpress\Deploy~1\axEvent.exe /w /i /y `"Install $printer`" /de `"Install $printer from PrintServer`" /f `"64 bit Printers`" /trs $tmpscript

Remove-Item $tmpscript


I've also attached the VBS that you could also you to schedule jobs based on a computer list if you don't end up using the GUI.

DS Schedule job from computer list.txt 1.92 KB
yizhifrank's picture

Jason  you are the best  

thank you very much for the share  

HighTower's picture

If this is answered then the OP should mark this as solved.

pshore's picture

Both AndyKn101 and Jason.F provided solutions.  At this point I am using AndyKn101's, hence I marked it as the solution.  The information from Jason.F will go into a long term solution as soon as I have the bandwidth to create it.  Thank you again for your assistance.