The latest component patch for LANDESK Management Suite should resolve that issue.
It is available under "LANDESK Updates" in your Security and Compliance tool.
Can you post the following logs?
You may have to put a Wait action into your template after the Distribute Software actions in order to capture the logs files.
Just put them into a .ZIP.
You may want to glance through to make sure that they don't contain confidential information.
Also, if you could export your provisioning template, that will likely be helpful.
I would like to test this internally as well.
Some followup questions:
- Are you distributing single packages, or are you distributing package bundles?
- Did you modify the default delivery method for your Provisioning job?
I have a core at the same patch level and I just tested this to a variety of clients. All packages were installed successfully:
8.1 U1 x86 8.1 x64 8x64 8x86 7x86 XP SP3 7-Zip 7-Zip 7-Zip 7-Zip 7-Zip 7-Zip Adobe Adobe Adobe Adobe Adobe Adobe Chrome Chrome Chrome Chrome Chrome Chrome Evernote Evernote Evernote Evernote Evernote Evernote Filezilla Filezilla Filezilla Filezilla Filezilla Filezilla Imgburn Imgburn Imgburn Imgburn Imgburn ImgBurn Keepass Keepass Keepass Keepass Keepass Keepass Notepad++ Notepad++ Notepad++ Notepad++ Notepad++ Notepad++ Thunderbird Thunderbird Thunderbird Thunderbird Thunderbird Thunderbird VLC VLC VLC VLC VLC VLC VNC VNC VNC VNC VNC VNC Winamp Winamp Winamp Winamp Winamp Winamp
Do you possibly need to update your remote consoles with the patches as well?
we had a similar issues in some of our customers environments and in one of our test environment too. What we find out after the LANDesk agent in the provisioningtemplate was installed and the softeware packages should run, the sdclienthandler.exe throws an exception on the clients. You can trace this in the eventlog of the client. The provisioning window stays for ages and nothing happens anymore.
We then created a complete new agent with the same settings (a rebuilt agent didn't help) and replaced the old agent with the new created agent to the provisioning template. After that, the distribute software actions works fine again.
In our productive environment we didn't have this problem, same patch level and it works fine without crating a new agent...don't know why it works sometimes and sometimes not.
Hope it helps.
We are using single packages. We have not modified any delivery methods before we upgraded (V 9.5). The default delivery method we are using is a Policy delivery method. Under "Network Usage" -> ("Use Run from Source to deploy files"), under "Type and frequency of policy" -> "Required" and "once".
Logs are attached.
Info.zip 7.5 K
What are the .EXE packages you are trying to install? Everything I see is .MSI based.
It is a McAfee ePo agent which is an executable. Other executables have been tested as well.
Did you try to change the agent in your template?
I've got around this for the moment by removing all distribution software actions using an exe from my templates and then re-adding them as an execute file action.
Not ideal if you are using preferred servers but works for me