1 of 1 people found this helpful
I had a couple issues and there were a few things I tried that seemed to have helped fix the problem for me. I have 15~17 packages that get deployed to the machine post agent installation. I had problems if I let the agent reboot the machine or added a reboot post agent install and pre software install. Basically, I only reboot the machine once after the entire provisioning package runs.
My script runs as follows;
- OS install
- driver(s) install
- add to the domain
- agent installs
- software installs
I also had to play with the order that the software installs. For example, if you try to install .Net apps back to back, they will fail about 50% of the time. So I install something completely unrelated, like Adobe Reader, between them. Gives time for whatever is going on in the back ground to complete. You could add a wait instead. I also clear the "Stop processing this template if this action fails" check mark on everything.
I should add, that if your not using a software distribution point that is solely for distibuting software for LANDesk, you should look at doing so.
- OS install
That's good information. I do install the agent without rebooting, but one thing I didn't consider is organizing the software installs in a certain order. I may try your solution eventually, but for now, my success rate is 100% by copying the files while in winpe and then installing via the Execute action. Takes more time to configure the templates, but at least it works.
I'm running LD SP2 and having similiar issue. When I deploy the software through provisioning it fails randomly on different software distributions. For instance when it installed quicktime it said it failed even though the software was on the system. Provisioning Task remains active even though it doesn't go any further and I have unchecked the box in all software distribution to stop if fails.
I know this is an old thread, but I am having the same issue as spriefer - provisioning fails on random parts of the process. Can't currently image any machines, this has been working fine for months and nothing should have changed. We're on v188.8.131.523. Machines PXE boot fine, run diskpart and all that with no issues, install XP and then begin installing packages. Sooner or later the process fails, but this seems to happen on completely different packages each time, there isn't any pattern to it. Network issues have been ruled out, we've tried all sorts but nothing works. Anyone got any ideas how to troubleshoot this further? Any logs to check? Nothing in Event Viewer or Alert Log.
The Distribute Software action in Provisioning does not work well at all. Guess they have been looking into this one for awhile. I gave up on it and use Execute File action with Map drives. I would reccomend you get the patch that fixes the Map Drive action and go that route. Here is a lengthy post regarding the entire mess.
We are experiensing the exsact same iossue random packages fails at random machines with software distribution, within an OS prov template :we are running landesk v 9.6
And have not yet found an solution. We have 350+ packages and dont want to re do all our packages with a bad workarround. this should just be working. ( we download all software and the nexecute on machines.)
We discovered that when packages fails, the install folder in sdm cache dosent even exsist
This is what I've found with software distribution. Packages will fail if a pending reboot is put into the registry. Not all MSI packages do this but some do
.If there is a reboot pending in the registry and a msi or batch package is run after, it usually fails.