/build/static/layout/Breadcrumb_cap_w.png

K1000 5.5 not detecting missing patches

Has anybody else noticed their K1000 glossing over the recent MS patches when running detect/deploy schedules on Windows 7 workstations? The three that Kace really seems to be missing are MS13-080,081, 082, and 083. They were detected and deployed to about a dozen of our workstations, but they were not flagged as missing on the vast majority of our systems.

These patches are being detected correctly on Windows XP stations, but they are not being detected as missing for Windows 7. Subsequent scans with MBSA show that the patches are in fact missing.

I've already provided logs to Kace support, but they are somewhat slow in getting back to me so I figured I'd see if anybody else was having similar issues.

Thanks

Asked 11 years ago 4179 views
2 Comments   [ + ] Show comments
  • Did you apply the update that is listed on the Home module ?

    http://www.kace.com/support/resources/kb/solutiondetail?sol=SOL113819 - nshah 11 years ago
    • Yes, we installed that patch shortly after updating to 5.5 due to other patching issues. This seems to be a completely separate issue.... - Michael4732 11 years ago
    • Is there a way to get this file or has this fixed it:

      http://www.kace.com/support/resources/kb/solutiondetail?sol=SOL116901 - mirvine 10 years ago
      • The patch that Nshah mentioned didn't resolve my issue, but the patch he mentioned should be included in the consolidated hotfix in your link. - Michael4732 10 years ago
      • They will not let me reply to your post Michael4732, but the consolidated did not help. Kace support gave me "k1_hotfix_5.5_Patching_Signature_Reload_20131216.kbin". This did the trick, and is working. But now I have some database table issues. - mirvine 10 years ago
  • Yes similar issues and we were one of the first to be issued that patch. - petelanglois 11 years ago
    • Pete - did you ever get a resolution on this? I'm STILL going back and forth with Kace support on this... - Michael4732 11 years ago
      • It has been escalated but no resolution yet. - petelanglois 11 years ago
    • Just wanted to let you know that we finally got this figured out, after escalating it all the way up to Lumension. Turns out that we had our DCOM default authentication level set to Default, and it needs to be set to Connect.

      You can find this by going into DCOMCNFG.exe, Component Services -> Computers -> Right-click on My Computer and go to Properties. Under the Default Properties tab, set the Default Authentication Level to Connect.

      We do not have any GPO's or login scripts that touch this setting, so I'm thinking that this requirement may be something new within Lumension's API. - Michael4732 11 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