The client can only process one policy/task at a time. So it is pretty normal for a required task to process and then wait for another required policy. What you really need is better job queuing in LANDesk and this has been requested in an er here http://community.landesk.com/support/ideas/1562 . It looks like SP2 will have a little better queuing, but will fall somewhat short on what we requested.
In the mean time you can either:
- Look into using provisioning to handle this. http://community.landesk.com/support/docs/DOC-4648
- Create s software distribution batch file that handles multiple installs. http://community.landesk.com/support/docs/DOC-2320
- Wait an try SP2 in mid October.
- Enter an ER for what you specifically need.
Zman has the answer 100%. If I might add, if you try the Dependant packages option to chain your packages together, it works ok, but there is a known issue with return code templates that should be fixed in SP2.
I'd recommend using a provisioning template instead. Just be sure to unselect the "Stop processing the template if this action fails" check box.
Another alternative is to create custom definitions, but it is more tricky and time consuming and they do not install in any particular order, but you can definately put in more logic into the install criteria.
Good point jmac, and I forgot about custom vulnerabilities. I just did a project and used them exclusively for software distribution and called vulscan from a script to "order" them and it worked very well. It takes a little longer to create, but you get package detections, somewhat easier queries to see if it was installed, flexibility, etc..
You weere able to order them? Interesting... Could you share that script?
Zman, that sounds handy, can you share the script?
Nothing fancy just calling vulscan with the appropriate vulnerability ID:
Echo %DATE% - %TIME% - Running Office 2007 - Start >> C:\LOGS\MDT_UPDATE.LOG "%PROGRAMFILES%\landesk\ldclient\vulscan.exe" /repair "vulnerability=Microsoft Office 2007" /NoSync /AgentBehavior=1 /AutoCloseTimeout=1 Echo %DATE% - %TIME% - Running Office 2007 - Finish >> C:\LOGS\MDT_UPDATE.LOG Echo %DATE% - %TIME% - Running Adobe Reader 9.3 - Start >> C:\LOGS\MDT_UPDATE.LOG "%PROGRAMFILES%\landesk\ldclient\vulscan.exe" /repair "vulnerability=Acrobat Reader 9.3" /NoSync /AgentBehavior=1 /AutoCloseTimeout=1 Echo %DATE% - %TIME% - Running Adobe Reader 9.3 - Finish >> C:\LOGS\MDT_UPDATE.LOG
You can Vulscan with /? for all the command line parms.