DS Task run order can't be set! Change it!
Bit astonished when I found out about this one but to summarise, you can't be sure, if you schedule multiple independent jobs, that their tasks will run in the order that they were scheduled!
What do I mean exactly?
Let's say you have two jobs:
JOB_A - Uninstall Oracle Client which consists of 4 tasks
Task1 - Delete ODBC Entries
Task2 - Delete registry entries
Task3 - Delete Environment variables
Task4 - Delete Oracle folder
JOB_B - Install Oracle Client which also consists of 4 tasks
Task5 - Copy Oracle folder
Task6 - Write ODBC Entries
Task7 - Write registry entries
Task8 - Write Environment variables
If I schedule these two jobs one after the other (A then B), then the order the tasks will run in is :
1,2,3,4,5,6,7,8 isn't it?
It is impossible to set this currently. Altiris development have said this is to make use of Windows' multitasking capabilites but who doesn't want stuff to run in the order it is scheduled?! Madness! There is now NO JOB INTEGRITY in DS! Tasks can effectively push inside other jobs....
It's already led to a major rollout issue (as per the example above where, thanks to a run order of, 1,2,3,5,4,6,7,8 the folder was copied (task 5) and then immediately deleted (task 4) ! ).
In fairness, you can nest jobs to create super jobs to get round this but do you want to have to create superjobs, necessitating hundreds of permutations every time you have a certain stack of jobs to run?!
Idea to fix is: Place a tickbox in DS jobs saying "Do not allow this job sequence to be interrupted by other tasks"
That way you can ensure jobs maintain their coherence.