Deployment Solution

Hello all,

I've searched both in general and in these forums specifically but can't seem to find an answer on whether this is possible or how it would be done. I'm running DS 6.9 SP4 and want to run a job as a task in another job.

For example, I have 3 Distribute Disk Image jobs. I would like to install the latest QuickTime version after the disk image has been distributed. Right now I update the tasks within the distribute image jobs to match each new version of QT that comes out. I also have a separate job (let's call it Install_QT) with a few tasks to install QuickTime with some customization.

Can my distribute disk image jobs have a task that runs the Install_QT job so changes only have to be made in one place? None of the options to add a task seem to fit, am I missing something?

.. and I am not sure if or better how this can be done either.  Perhaps somebody else could give that answer.  I do not think it is.  I would solve this as follows:

Create one folder holding the exe files including a version/build number in their filename and create an scripted task as described in following article:

https://www-secure.symantec.com/connect/forums/batch-file-picks-latest-version-aclient

This way you can keep your older versions if needed and always be sure the latest version is installed when the job runs.

Perhaps not nicest, but effective.

Have fun!

You should be able to call the software install job at the end of the deploy image job.  Just change the success action on the Return codes Rip and Replace options tab.  It will be set by default to "Continue".  Set it to "Select a Job" and choose the job that you want it to run.

Hallo f.et.med

As bhawver says you can do this via calling another job with success codes.
The way i normally do this is by creating a job in the end of my image job, containing this:

REM Calling "Jobname"
REM Calling "Jobname"

And then clicking next, so that i get to the screen where i can see how it's run, leaving this default, clicking next, and changing the "Success code 0" to Select a job taking my other job as the job it should call.

There are some things i normally do when i do this, there is no obvious way to tell if a job calls another job other than going into the master return codes screen, therefore i normally call my jobs:

01-ImageJobName
10-Install_QT

(the reason i call it 10 is just because i think of my jobs as sequential installation method first we got the deployment of image, then perhaps there is customizing of my deployment, and then there is program installation, and perhaps at last there is windows updates, but that's just my point of view, you can call the jobs whatever you want, it just needs to be making sense to you...)

Kind Regards
Morten Leth

You could use a script task that executes AxSched.exe

That is in your eXpress share and is a commandline jobscheduler

C:\axSched.exe /?
Altiris Deployment Server Scheduling Utility version 6.9
Copyright 2008. Altiris, Inc. All rights reserved.

Usage:
     axSched <computer/group> <job-name> (options)
                            OR
     axSched /q <filename> (options)
                            OR
     axSched <computer/group> -jid <job id> (options)

Options:
     /t <yyyy-mm-dd hh:mm>    Time to schedule
     /n                       Don't notify servers of the changes
     /f <folder-name>         schedule the job-name found in this folder
     /q <filename>            File used for exporting jobs
     /y                       Suppress confirmation prompts
     /dsn <odbc-dsn-name>     ODBC data source name
     /d  <db-server>          Database server name
     /u  <db-user>            Database user name
     /db <db-databaseName>    Database name
     /p  <db-password>        Database user password
     /lu <login-user>         Deployment Server login user name
     /lp <login-password>     Deployment Server login password
     /ulu                     Use the logged on user to login to Deployment Server

Example:

axSched.exe %COMPNAME% "Install_QT" /t 2010-01-01 /y

Run this script "Locally on the Deployment Server" "When the agent is connected". Scheduling a job in the past will cause it to rur as soon as the image job is ready.

Regards Wilm