If I have a software distribution task that comprises of more than one .exe/.msi I chain the packages together by adding dependent packages to the primary package. More often than not, these dependent packages will be an autoit script that may uninstall another program, make necessary configuration changes etc.
Prior to testing, I assumed that LANDesk would only report that the task has been successfull when the primary package has executed successfully. However I have noticed that LANDesk reports the job as successfull from the minute that the first dependent package is executed. One of the main reasons I opted to chain packages together was under the assumption that LANDesk would accurately report whether the primary package had been installed or not. When running a provisioning task, the status will update on a per action basis which I hoped would be the case for chained SD.
I'm currently testing return code mapping templates but I'm not expecting it to solve my issue as the moment LANDesk receives a return code of 0 for the first .exe the whole task is set as successfull and no more return codes will be noted.
The core is running LDMS 9 SP3.
If anyone has found a way to effectively manage this or whether this is by design it would be highly appreciated.