So our organization is probably the last one to finally upgrade K2000 to 3.6! (Shame, shame...)

I did run the K2 Advisor against the server and corrected the items it specified. 

However, when deploying a test k-image, at least a third of the tasks show "Failed" when I can see that they actually succeeded (for example, the task to install Symantec Endpoint Protection says that it failed but it is actually installed on the resulting deployment). 

I'm not sure where to start looking to figure out what K2000 is having trouble with. Can someone point me in the right direction?
1 Comment   [ + ] Show Comment

Comments

  • Would you please remove your duplicate post? Thanks.
Please log in to comment

Answers

0

I have the same problem with our av installs.

What I normally do is write a batch file to deploy it in kace and I do a check that the services are started if they are I manually return exit code 0 to the bat file else I return any other error code.

this will make it succeed

exit /b 0

Answered 05/24/2016 by: cbreuer@bscsd.org
Senior White Belt

  • Gotcha. No problem, I can handle creating work arounds.

    I guess my bigger question is: Should I just expect a few false errors (says task failed, but it actually succeeded) in 3.6 and work around them, or do I need to *fix something* about my tasks to make K2000 work with them better? Thank you!
Please log in to comment
0

I think it has to do with the return code of the av install. If its not returning error code 0 kace considers the task failed in 3.6.

I think it was more forgiving before that. I believe the av installers now do more things so the return codes are just not 0.


Answered 05/24/2016 by: cbreuer@bscsd.org
Senior White Belt

Please log in to comment
Answer this question or Comment on this question for clarity