We have setup and been running KACE Patching from our K1000 for over a year now.  Our network team decided to re-enable Windows Updates, through group policy.

Our KACE Patching schedules are still operating as normal, and now Windows updates are coming to users at random; but WU is providing a lot of "important" updates that KACE did not.  We have KACE  subscriptions set to "All types" and Impacts set to "All Impacts".  How can I determine why this is different?


 




 



 



3 Comments   [ + ] Show Comments

Comments

  • We see this as well and are baffled by it. I commented in another thread that there is a lot of confusion about what is presented as installed by KACE, and what is presented as installed by Windows. This gets even more convoluted if automatic updates is enabled on the client. I appreciate Chuck's reply, but for our environment at least, this is a monthly occurrence. If it's just a "labelling" issue, it's a big one and part of a larger broken process on Kace's side imo. My gut tells me it has more to do with the repackage by Patchlink being identified differently by WIndows, but I haven't verified this.
  • I'm with fcoetech on this one - KACE, at least for application-level updates, will only take patches approved by third party before pushing - I assume this is the same for Windows Updates as the packages need to be compliant with the way KACE pushes them. Because of this, KACE is receiving different updates than WU, and likely at different times.
  • You might want to see:

    What to check if there is a discrepancy on patch status in the K1000 versus Windows Update
    https://support.quest.com/kace-systems-management-appliance/kb/136084

    Discrepancy on a patch status that is showing on K1000 versus what Windows Update is showing
    https://support.quest.com/kace-systems-management-appliance/kb/136871

    KACE filters some patches, specially the ones that could trigger a Windows Build upgrade (1607 to 1703 for example).
Please log in to comment

Answers

0
I normally select one particular patch that Windows Update is detecting and then search the patch catalog to determine why it isn't being labelled properly. You can then know if your labels need to be adjusted to include the patches that KACE isn't including in your patching schedule.
Answered 09/15/2017 by: chucksteel
Red Belt

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

Share