Good day,
I have a package containing 6 programs. These programs are vb scripts which calls MSIs and executes very quickly ( in seconds). They will be deployed with 3 deployments, 10 minutes apart via assignment schedule.
The programs breakdown is as follows:
Program 1: Upgrade software A - First deployment (Time stamp 07:00:00)
Program 2: Uninstall software A
Program 3: Upgrade software B - Second deployment (Time stamp 07:10:00)
Program 4: Uninstall software B
Program 5: Upgrade software C - Third deployment (Time stamp 07:20:00)
Program 6: Uninstall software C
Program 1 is dependent on program 2 with the "run another program first option" (uninstall software A then upgrade software A).
Program 3 is dependent on program 4 (uninstall software B then upgrade software B).
Program 5 is dependent on program 6 (uninstall software C then upgrade software C).
I am trying to test what would happen if my test client isoffline when the deployment is scheduled and come online well after the assignment schedule for the third deployment has passed.
When I set the deployment assignment schedules for programs 1, 3 and 5 to run 10 minutes apart the results (in execmgr.log sequence) when the client comes online after the fact are as follows:
Program 1 - software A completes its dependency (program 2 – uninstall A) first (Time stamp 09:00:20).
Program 3 – software B completes its dependency (program 4 – uninstall B) second (Time stamp 09:00:20).
Program 5 - software C completes its dependency (program 6 – Uninstall C) third. (Time stamp 09:00:21).
Program 2 - software A completes fourth (Time stamp 11:00:22).
Program 4 - Software B completes fifth (Time stamp 11:00:22).
Program 6 - Software C completes sixth (Time stamp 11:00:23).
Logic would dictate that the Program 1 must complete its dependency (Program 2) and then Program 1 first, before starting to execute Program 3. This is not the case. After three deployment tests the results are consistent.
Any Ideas as to why this is the case? Your assistance will be much appreciated.