/build/static/layout/Breadcrumb_cap_w.png

What to do when Detect Failures in Patching?

Patch Status After Last Run

Patched: 0, Not Patched: 0, Detect Failures: 80 , Deploy Failures: 0


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: anonymous_102124 9 years ago
Blue Belt
1

When Agents or Client Machines are facing "Detect Failures" and "NotPatched" at the time of patching need to check the below the logs;

Kpatch logs

Pluginpatching logs

 

Prior to check the logs need to enable the Debug Mode by following ways;

Run the Script Enable Debug from the Kace K1000

Edit the amp.conf inside the Client Machine Location C:\ProgramData\Dell\KACE\    

debug=true

then restart the DellKace Agent Service

 

Expected Problems

There may be a file "PatchLinkWrapper.dll" missing inside the Client Machine Location C:\Program Files (x86)\Dell\KACE\

Kace.plk file is not functioning properly

 

Resolution: Need to bring the "PatchLinkWrapper.dll" file at the location C:\Program Files (x86)\Dell\KACE\ and replace the kace.plk at the same location

 

If More machines are facing "Detect Failures" and "NotPatched" issue use File Synchronization option to sync the files at the location

 

Then delete the below files

Files Deleted inside the Client Machine Location C:\ProgramData\Dell\KACE\

Kace OUT File

Kace.out LAST DETECT File

Kace.out LAST DEPLOY File

 

Final Step reschedule the patching job for the Agents which are facing "Detect Failures" and "NotPatched" issues after tha completion of above work around steps.

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