/build/static/layout/Breadcrumb_cap_w.png

Windows Server 2016 detect and deploy issues

We seem to be having some issues with Windows Serve 2016 devices. It appears that when KACE runs a detect against the device, it does not see all of the missing patches. Also, when we run deployments, even though the KACE appliance sees that the patches were applied, when we go on the machine to validate that the patches were made, there are no OS patches that show installed. Has anyone else run into this issue? We are running security only patches at this time, we are not running non-security patches.

Thanks


2 Comments   [ + ] Show comments
  • We are seeing the same issue. I have a case opened with support, but may not hear anything for a few days. We ran the ivanti troubleshooter today and it had the same issues. If you look at nodes (other OS's) without the issue you will see in the registry they have the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Patchlink.com\Discovery Agent

    This means the scan is able to build a patch list, without it the agent assumes it worked and just reports finished.

    If you find a resolution let me know. - dan.lebaron 1 year ago
    • We are the exact same situation. I currently have a support ticket open with KACE support, so we'll be delving into this shortly. - schlappette 1 year ago
  • I have the same problem, and the link to the KB is broken! Come ON!@!!@@! AAARRRGGGHH!! - davidw128 1 year ago

Answers (2)

Posted by: dan.lebaron 1 year ago
Senior Yellow Belt
1

Quest support gave me this article and said this is the issue. 

This have been seen before on previous OS versions asexplained on the KB below: 

https://support.quest.com/kace-systems-management-appliance/kb/259279/servicing-stack-update-for-windows-10-and-windows-server-2016-version-1607

Posted by: davidrnoble 1 year ago
Senior White Belt
1

I had the same problem and opened a support ticket.  It was explained to me there is a bug in Kace SMA version 9 detecting/deploying patches to Windows Server 2016 build 1607.  The bug is not going to be fixed.  The resolution is to upgrade the KACE Systems Management Appliance to the latest release of version 10.0

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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