Hi Henrik
Yes, I think so. We need to make sure that other dependent jobs (on any server running VC) are not running before certain jobs are run. As an example:
JOB A runs to shutdown key services
JOB C runs but depends on JOB B to have finished before it can run
Job D, Job E and JOB F can only run after JOB C has finished, but none of them can run together as there is a risk of locking a file that is used by them all - they also have to report run times and sub-totals in the correct order
Finally, JOB G has to run only after all the above have finished so that Services can be restarted and Stats are complete for BI.
Apologies Henrik, my background is mainframe batch scheduling and automation, hence the mentioning previously of job chains, schedules and dependencies, so I'm probably expecting a little bit too much 😉
Cheers
Andy