Client Management Suite

I have setup a managed software delivery for Windows XP Service Pack 3.  When I created the package I made sure that I added in the correct exitcodes.  I.E. 0, 3010.  When the job runs, it exits with 3010, which is correct as it requires a reboot, but Altiris reports it as failed, and such does not run the next task.  Has anyone else experienced this problem, or know of a known issue with this regard?

I must admit i have NEVER seen this behavior.
The only time i saw this behavior is if i have forgotten to set the exit code to success, it stands with a "stop" command by default.

Are you 100% sure that you didn't by accident forgot to change the Response to "continue" and result to "success".

/Morten

I thought this was the DS section, my bad this would apply to the DS and not the CMS.

Can you see your application getting installed?
You could try setting your policy to continue even on failure this would get it to disregard your exit code and continue doing jobs.

/Morten

Did you set the success code to be 3010?

yeah i set the exit codes for any software delivery task to "0, 3010" just in case. Odd.

Hey Desmond

I have one more thing you should try out.
At some point i experienced that i needed to change the exit codes, and i found out that for me they where not propagated down to the client if i changed them.
I did the following to resolve my issue.

First off, set the status of my policy to "Off", save the policy.
(not sure if the follwing is actually needed but i did it just to be 100% sure, i was still testing)
Logon to the client update the policies to that it did not have the policy in question.

After that i deleted the software from the policy, saved.
I then applied the software to the Policy once again and saved.
After that i enabled the policy again (status to "on").

Logged onto the client and refreshed the policies to check that it now had the new exit code, which it did.

Try it out and see if it does anything for you, i would assume it does.
/Morten

The crazy part is the policy on the client side shows the exit code 3010 in there should be a sucess code.  hmm.