Distribution Packages fail to install randomly during using
...
Provisioning
- A device in the process of being provisioned will often have the following steps:
- Prepare the hard drive and deploy the OS (either through image deployment or scripted install)
- Join the domain and other first start actions
- Install the LANDesk Agent
- Using the LANDesk Agent install software deployment packages, patch the system, etc.
...
To work around this known problem you can create an agent to be used for provisioning that does not start the security scan or the policy sync immediately upon installing the agent. We don't have the option to disable the tasks completely, but we can set them to start at some point in the future, such as the year 3000. That should give us enough time.
After all distribute software or patch system tasks have completed you can then finish the provisioning template by installing the agent you would actually like to use on the device long term.
To work around this known problem a LANDesk Agent was created specifically for provisioning (Tufts_95_SP1_Provisioning_Agent) that does not start the security scan or the policy sync immediately upon installing the agent. We don't have the option to disable the tasks completely, but we can set them to start at some point in the future, such as the year 3000. Once your software distribution tasks are completed the last step should be to install the full LANDesk Agent that you want to use in production.
EXAMPLE 
After all distribute software or patch system tasks have completed you can then finish the provisioning template by installing the agent you would actually like to use on the device long term.
For more information please see this article: http://community.landesk.com/support/docs/DOC-9526