Patching never ending loop
I need to preface this with, I was never shown how to set up patching from bare metal during jump start. This is the only part of the box I've never gotten clear instruction on.
When the 10.x schema issue happened. I was totally lost but finally got somewhere with some suggestions from a few people.
Scenario: We are using Kace to patch the following software
Chrome (daily checks)
Firefox (daily checks)
Adobe Reader (daily)
My Patch Smart Label wizards as suggested by a few people are all:
Name - Contains - SoftwareName AND
Publisher = Publisher AND
Superseded is NO
Smart Label is HQ:Patching - SoftwareName
Detect and Deploy are spaced out accordingly to not overload the k1000/SMA... This part works great.. Patches detect and then deploy without issue.
The problem is, the next time the PC checks in, the Distributed install says "Hey, I cant find Chrome 72.0" and it proceeds to Uninstall 72.0.1 and installs the older version. This happens with all patched software.
I have tried various suggestions found on ITNinja, and without disabling my managed installs, I can't keep software updated with patching.
Disabling and manually updating a managed install every time a patch is available seems to defeat the point of having automated patching.
I reach out to you, oh wonderful Kace users.... What the heck have I done wrong?!
I use really generic labels for managed installs that look only for the software title, so when versions change they don't fall back into the smart label.
For Firefox, the smart label only evaluates on "SOFTWARE TITLES does not contain Firefox."
Patching is a BEAST, though, so if you haven't watched some old KKEs on them I'd highly recommend them.