Try reseting the pacakge hash. Right click on the package and reset the hash file. Not sure this is the resolution.. just a guess.
Installing 9.0 SP4 packages without dependencies won't work with provisioning.
Maybe SP1 for 9.5 has the same bug.
There was an issue with software distribution patckages in SP4 with provisioning. There is a patch available from support to correct the issue.
Sorry to bump an old thread but I just ran into this problem as well, OP did you find a solution?
I have not yet found a solution.
It is occuring on random packages now. Sometimes they work, othertimes they dont. Tried the usual resetting hashes, etc.
Yeah that's what I have found as well, sometimes it works and other times it doesn't and when I try that single package by itself it usually works. This was the failed internal status I got the last time I ran it: -1917516221. Also, maybe i'm going crazy but I have a provisioning template set up to install a bunch of different software and pre sp1 I remember there being an option to either stop the whole template if an action fails or just continue on to the next piece of software.. I don't see that option now and it just stops the whole thing if one piece of software fails. Have you run into that?
Oh you are a genious , thank you for that. I will post back if I find any more information on why some actions fail at times.
I'm still runing into random provisioning issues with LANDesk 9.5 SP1.
Most recently, OSD script says that all tasks completed sucessfully but random pieces of software never actually get installed or even downloaded into cache on the machine.
It seems to happen on random distribution packages and is not limited to any particular one.
Tired the usual things like resetting hashes, making sure they're pointed to valid distribution packages, rebuild provisioning script.
1 of 1 people found this helpful
Not sure if this is the issue you're having but we found that by default WinPE 4 disabled 8 dot 3 short file names which caused legacy packages and software to fail. We fix this via custom script at the OS Installations phase of provisioning.
Thanks for info on that. Different problem though.
Packages are saying their sucessfull but dont actually deploy. It's totally random which packages don't get installed and it doesnt happen all the time.
Have a ticket open with LANDesk for the issue.
this sounds like an old problem.
One of your action before the software distribution is the installation of the LANDesk agent I think. You have to be sure that this agent didn't start the policy sync, vulscan and inventoryscan because these things can interrupt the software distribution in provisioning.
For that reason we configure a very small agent with only software distribution and set the policy sync to start in year 3000. The last action in our template is then to install the "true" agent.
Hope that helps.
Hi masterpetz you may be onto something. I believe installing the LANDesk Agent may have been our 2nd or 3rd action in the template. I am going to move the LANDesk Agent installation at the very end of the template.
What is the purpose for installing two agents in your provisioning template? (Small one with delayed policy sync) and then a full agent?
The first "small" agent is needed for the software distribution action, thats the reason why only the software distribution components are selected. And as I wrote above the policy sync has to be in the far future because it can interrupt your provisioning template if you leave it default!
At the end, the main agent is installed because normally the policy sync should run daily or hourly not in the far future...:-)
Thats the reason why we work with two agents and its recommended by LANDesk support too.
Hope it helps.