/build/static/layout/Breadcrumb_cap_w.png

How to troubleshoot failed patches

Hello,
We run scheduled patches on all our devices weekly from our K1000 appliance (7.1.149). Our devices are a mixture of Windows 7 x64 and Windows 10 OS's. Over the last few weeks, I've noticed a spike in patch failures (not offline and not success) to the point that only 7 of our desktops succeeded this week.Usually, we average around 50-60 successes. 90 failed and 21 were offline. The number of offlines are actually lower than normal (yay users!).

I need to find out why these patches failed. The failed computers are of both OS's. The patches that are listed as "missing" are different in almost all cases. There are some similarities among Windows 10 devices and among Windows 7 devices, but not between both OS's. Some of the failed devices have no patches under "errors", only in missing. 

Bottom line, I haven't been able to track down the reason so many devices are suddenly "failing" the patches. The numbers for laptops are better. We only had 17 fails with the laptop patching, even though we have about as many laptops as we do desktops.

So what is the best way to troubleshoot this? Where can I find information on WHY these devices ended up in the "fail" column on the patch schedule?

1 Comment   [ + ] Show comment
  • Normally Failed errors will include an error code:

    see: https://support.quest.com/kace-systems-management-appliance/kb/111687

    You will need to check the Kagent.log file and see why they failed, also confirm if you have a replication share in place or not..


    Kagent.log path: c:\prograndata\dell\kace\usr\ - Channeler 7 years ago
    • So this has to be done for every patch for every user? - nmarsden 7 years ago
      • Normally, solving it for one, solves it for all, specially if they are trying to retrieve patches from a Replication Share - Channeler 7 years ago
    • Oh, the patches don't show as failed, mostly. Only missing. The computer shows as failed, but there are no patches listed as failed on most of the "failed" computers. - nmarsden 7 years ago
      • Same issue here. What ended up happening? - JS_DC 5 years ago

Answers (0)

Be the first to answer this question

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ