Patching Error
I am running the trial on the VWware Player 3.0.0
When I try and detect and patch any machine I get the current phase reported as 'error (Log Upload Failed)'. I am able to successfully distribute managed software as well as uninstall using the scripts and inventory the machines no problem. I have configured the patch settings and the download are up to date.
Any help/suggestions would be greatly appreciated.
When I try and detect and patch any machine I get the current phase reported as 'error (Log Upload Failed)'. I am able to successfully distribute managed software as well as uninstall using the scripts and inventory the machines no problem. I have configured the patch settings and the download are up to date.
Any help/suggestions would be greatly appreciated.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
airwolf
14 years ago
I'm not too familiar with the patching functionality of the KBOX, as my organization does not currently use it. Due to the time limit on the trial, I'd suggest contacting KACE support - they will be able to help you faster than you're likely to receive a response on the forums.
Posted by:
Fin
14 years ago
thanks for the reply fortunately i have just noticed that in the detect patch selection i had selected a label with no patch contents... rectifying this appears to have solved the problem. A stupid mistake on my part although a slightly more informative error message would have been nice..
Thanks again..
Thanks again..
Posted by:
jkatkace
14 years ago
Having an error message is definitely a bug, and I'll log a bug on your behalf.
But this is a difficult issue: what kind of message would you like to see, when and where? Since patch labels are dynamic, and schedules can filter by operating system, we may not know until a schedule actually runs if it would do nothing on detect. In that case, there would be nothing in the machine record at all. Where should the fact that a a schedule ran, but nothing was in the detect list be indicated?
If you want to track this, once you become a customer, enter a support ticket and ask that the bug number be entered against it.
But this is a difficult issue: what kind of message would you like to see, when and where? Since patch labels are dynamic, and schedules can filter by operating system, we may not know until a schedule actually runs if it would do nothing on detect. In that case, there would be nothing in the machine record at all. Where should the fact that a a schedule ran, but nothing was in the detect list be indicated?
If you want to track this, once you become a customer, enter a support ticket and ask that the bug number be entered against it.
Posted by:
Fin
14 years ago
thank for your reply.
As I become more familiar with the product I appreciate your point. From my point of view I would expect to see it where it is which is if I go into the patch shedule and drill down into a particular job and expand the 'show all' option. This then lists for me the shedules that have run and the result or current state under the heading phase, so a message that indicates the stage at which an 'unexpected' occured, say 'Complete (no machines selected) or 'Complete (no patches in label). This would indicate that the job ran OK but there was nothing to do due to the selection at which ever stage being empty. Assuming that when you setup a job you are expecting it to do something therefor returning a selection of zero at any stage would be unexpected. I would not however expect to see any results until the schedule runs.
I've only been using this for 2 days but so far its very good and hopefully we will be customers quite soon.
As I become more familiar with the product I appreciate your point. From my point of view I would expect to see it where it is which is if I go into the patch shedule and drill down into a particular job and expand the 'show all' option. This then lists for me the shedules that have run and the result or current state under the heading phase, so a message that indicates the stage at which an 'unexpected' occured, say 'Complete (no machines selected) or 'Complete (no patches in label). This would indicate that the job ran OK but there was nothing to do due to the selection at which ever stage being empty. Assuming that when you setup a job you are expecting it to do something therefor returning a selection of zero at any stage would be unexpected. I would not however expect to see any results until the schedule runs.
I've only been using this for 2 days but so far its very good and hopefully we will be customers quite soon.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.