You can create a software template that houses multiple software packages. Do you already have these packages built with in LDMS? Below is a screen grab of my software template: (this needs to be created under OSD). You can then schedule this template for machines in LDMS, I use this method for provisioning in case an action fails I don't have to re-run the entire provisioning process again. I can schedule the template and distribute the software, it can also be beneficial in troubleshooting if you are getting a persistent piece of software that's failing. If you need help I can try and assist you.
If this is part of preparing a new system then I think the provisioning template as mentioned is a good one. Not so great in live systems as it presents an interface to show provisioning is going on.
Batch files are great as long as you don't have any complex conditions to decide whether to install one of the packages or not.
If you really need to detect what the condition of the machine is before installing, then you are best working with dependent packages and making certain that the detection rules you set are solid.
Don't forget though that a standard scheduled task lets you specify three packages so in some cases that might be enough for you.
LANDesk Silver ESP
The One-Stop Shop for LANDesk Enhancements