It'd probably be a good start to go to the clients in question and go look at the log-files.
That'd tell you at least what task(s) is/are responsible for the download, and things usually unravel from there (little things like "Oh - this package X is a dependancy for another task I'm distributing" and fun stuff like that).
LANDesk EMEA Technical Lead
I figured out that the download is actually triggered by the uninstall association in the package :-)
Can anyone explain when this kicks in? And is it possible to remove this association? i allready reconfigured the package
but what happens with clients that installed it before i changed it?