Sounds like it may be an issue with detection logic. Check this link http://community.landesk.com/support/docs/DOC-7753
If the Dependent Package is not a MSI or SWD package detection logic must be configured as part of the Dependent Package
Since you indicated that you use autoit (exe)....
Hi Zman, thanks for the suggestion.
Unfortunately adding detection logic to my .exe did not have any bearing on how LANDesk reported the job.
The first .exe that runs is a GUI informing the user of the intention to run an install, once the user has acknowledged this notification by hitting 'ok' the next distribution package in the list is executed. I presumed that LANDesk would only report on the task when the final primary package has run.
The reason I have created the packages like this was to benefit from increased accuracy when reporting on the success of a task.
I suppose the best way is to write a script which will act as the primary package which will control the installation by calling files that were sent down as 'Additional Files'. At least using this method you can be sure that if the task is reporting as successfull then the installation was complete. Another benefit of writing a script to control the installation is the ability to make use of return code templates.
No, LANDesk will report the status after each package installation.
If you dont mind to install your software with Provisioning, you can also create Provisioning Templates to just distribute software. You can define each additional step and it will be reported on.
Hi Frank, I have watched the scheduled task whilst the job is running and it doesn't update for each dependent package.
Provisioning would be my ideal method but with it functioning more as a push instead of a policy it is not always ideal.
Edit: Frank, I ran a few tests and you are correct. It's just within the console it doesn't update and only changes if one of the packages fails as opposed to updating per success of each package. I killed one of the packages during the distribution task and LANDesk correctly reported the task as a failure.