Issues with patching
Hi all,
We are running our SMA on 10.1.99 and are very busy with patching KB4528760 specifically.
The patch is added to the category and when I run a detect and deploy schedule on one specific machine the patch gets installed.
However, when I run it for all the other machines in bulk and reboot all of them I get a compliance score of 3%.
3 installed, 47 missing, 45 error while the patching schedule is targeted to 621 machines.
I have also succesfully scripted the installation of this specific KB and even then the compliance does not change in the catalog.
Am I the only one that is running into this inreliable patching/reporting procedure?
Any help is appreciated.
-
Please add the O.S. (full name and version) you are trying to patch. - Channeler 4 years ago
-
Windows 10 1903. - Loei 4 years ago
-
Try running another detect only and see if the results change any? - Hobbsy 4 years ago
-
I have tried this, nothing really changes. I can even see the KB being mentioned in the logs as not apliccable. The only thing I can think of is that the machine is behind on reboots for previous patch installations. Could this be the problem? - Loei 4 years ago
-
Are you using replication for this? Is the patch file replicated? - kbot_cache 4 years ago
-
Sorry for the late answer. But the replication does not show any patches being replicated. How should I address this issue? - Loei 4 years ago
Answers (1)
Without seeing the Agent logs from the device after the patch schedule has ran, it would be hard for me to comment on what may be the issue.
You can use the Kace Agent Toolkit (KAT) to collect the logs from one or more devices in question to review the logs for any possible errors that may have occurred.
If you decide to open a support ticket, please include the zip file created by KAT that will contain the logs.
