How to Patch Chrome 72.0.3626.121 when Not in Catalog Yet?
Anyone pushing updates to Chrome 72.0.3626.121 yet? I see the new version in Software and in inventory on a few computers but it is not yet available in patching. SMA detects this new version as "created 03/01/2019 15:13:40"
My SMA says "`Patches last updated: 5 hours ago`" so it should be current. How long do new patches take to show up? It's been almost a week. How can I patch this latest Chrome version through K1000/SMA?
Looking to patch Chrome to address the "zero day" bug they have in the older versions outlined here: https://www.zdnet.com/article/google-reveals-chrome-zero-day-under-active-attacks/
Answers (3)
Top Answer
Found an answer in the Kace Slack. Our SMA/K1000 downloaded all patch info this morning a few hours before the chrome patch hit the Kace feed. Just jumped the gun a little, lol.
Ran a manual patch update and now see the patch in Patch management where expected and detecting momentarily for a lunchtime test deploy.
Comments:
-
I just updated my catalog since I download at 0030 and I see it for both macs and windows - SMal.tmcc 5 years ago
Unless you disabled updates for chrome, it will update when the machines start up. I did a WOL to all my machines and forced 2 inventories. Now I show 75% up to new version vs 20% when I first checked today.
Comments:
-
We do still have auto update on and are sitting about 40% currently. - JS_DC 5 years ago
Using Group Policy
We recommend that you keep auto-updates turned on so that your users receive critical security fixes and new features as they become available.
In Group Policy (Computer or User Configuration folder):
- Go to Google
Google Update
- Enable the Update policy override default policy.
- Under Options, choose Always Allow Updates (recommended).
- Go to Google
You can optionally override this setting for an individual app by using the Update policy override policy in the specific app folder.