Client Management Suite

I need to deploy microsoft .net framework 4.5 to about 350 computers and i am trying to do this using CMS7.1. I have imported the software package (executable) and set the install command setup.exe /q /norestart. Everytime I run a test deployment using "Quick Delivery Task", i get error -2147024894.

Log file indicates that package failed to launch successfully. How if I run the command manually, it works. Some articles seems to indicate that this error means the file is missing.

Any suggestions why I am getting this error and how it can be fixed. Any help will be much appreciated.

Thanks

MK

Isn't the executable called something like dotNetFx_Full_setup.exe? So the command line is:

dotNetFx_Full_setup.exe /q /norestart

How big is the file? Have you downloaded the full offline installer or the web installer?

Hi

I have extracted the original installer so when I run the install, it doesnt have to extract. It is a full offline installer sized about 49MB'

thanks

mohit

Check the Altiris log for the command line it's trying to run and make sure your package is in the exact same path.

Hi MohitK,

The command line is correct. I have deployed the same software successfuly in my environment. The error that the agent returns you I have experienced a lot as well. Not only related to .NET deployments.

What I figured when these kind of errors were returned by the agent is that the package in the "cache" folder of the Software Delivery (Program Files\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery) were not similar to the one located on the site server, so I had to delete that folder and send the task again, so that the agent could download the package from zero once more. But there are other scenarios, such as the package on the site server not being downloaded successfully from the Altiris server, resulting in a corrupted package. Once the agent responding to that site server downloaded the package from it, the task failed because of the package on the site server.

You mentioned you tried to run your package manually and it worked, but did you run the package located in the "cache" folder? If not, first of all you need to make sure your package is not corrupted on the Altiris server, and then verify it if that did not happen on the site server as well.