Currently I have the jobs setup like this

Deploy Packages
->Deploy Office 2k3 STD
->Deploy Office 2k3 Access
->Deploy Citrix
->Deploy VNC
->Deploy SMS suite

etc...

The idea here is that if the path, or anything gets changed I update these jobs, and only these jobs with the new information

Then I create this:

Deploy Reporting PC (this is the job name)
task 1: Distribute disk image A
task 2: ??

What I want to be able to do is have Task 2-x directly call one of the package jobs above.

So it would look like this:

Deploy Reporting PC:
Task1: Distribute Disk image A (I could even take this out and make it like task 2-x)
Task2: Run Job "deploy Office 2k3 STD"
Task3: Run Job "deploy Office 2k3 Access"
Task4: Run Job "deploy SMS Suite"

Then I could have a different sep job such as:

Deploy Agent PC:
Task1: Distribute
Task2: run Job "deploy VNC"
Task3: run Job "deploy Citrix"

Then say 2 months from now, if someone decides to change the path, or application gets updates, all i would have to do is update the package jobs instead of going into 20+ jobs and redoing the path for either the script that gets run or the software install path (ie only one task has to be changed vs changing identical tasks in all the jobs that use it).

Can this be done?

Conditionals isnt the solution, and having it run a job after success isn't the solution either as it only can run one job.
I could stagger the success jobs, so that the most rare install goes first and calls the second most rare install etc. but the day i decide i just need to install that one rare package, it ends up running through the entire chain of jobs.

Thanks,

Chris