Not really, as such. If you think about it, the expectation is pretty sensible that "if you have a tool like LANDesk, you will be using LANDesk to do your distribution" ... and SDCLIENT does go around checking whether another instance of itself is already running.
So 'from our' point of view, we're making sure that we're waiting for other tasks to finish, as it were.
BAT-files in particular are a bit tricky, since LDMS can't really be expected to know what's supposed to go on in the BAT-file (and string-search checking won't be wise, since the difference between just copying an MSI from A to B and actually installing is quite big).
If this is something you frequently run into, I would suggest just including some kind of VB-based 'wrapper' so to speak, you can check TASKMON whether MSIEXEC is running, and if it is, decide yourself. Do you want to:
- Fail the task and start it another time?
- Keep the task ticking, checking again in a certain time incremement for whether MSIEXEC is running?
- Mark the task as 'succeeded' with a specific status message.
All this stuff is possible, it's more of a question of policy. Should those things be installing without LDMS control (i.e. "should Windows users have the power to install patches"), or - respectively - if you're using a non LANDesk-patching solution (because VULSCAN will be using SDCLIENT to install its patches), then it's a matter of communicating with the relevant department and agree on time-windows, and such things.
It depends on whether this is more of a technological, or more of a social problem, as it were .
Hope this helps.
- Paul Hoffmann
LANDesk EMEA Technical Lead