Why does Google Chrome Product version not get updated when Kace patches it?
I can't help but think I have either overlooked something or just massively don't understand how patching in Kace works. Any help/explanations/insights would be greatly appreciated.
I believe you may have stumbled across one of the (many) reasons why Google's so-called "enterprise" MSIs are a piece of [takes a breath...] work. They're simply a wrapper for Google's own installers.
Chrome's dutifully records version information from the MSI in ARP but (I'd bet my last dollar that) the patch is probably not updating that information. It would be simple enough to determine that by using a lightweight snapshotting tool (my current favourite of which is ZSoft Uninstaller) to perform 'Before' and 'After' snaps of a manual installation of the patch. I'm confident you won't see the ARP stuff even being accessed, much less updated.
Pass, I'm afraid. I know next to nothing about Kace boxes (I'm a refugee from the days when IT Ninja was AppDeploy).
Unfortunately, one of the poor things about ITN is that the forum software was switched to what you see now and, unlike every other forum on the planet, there's currently no way that people can see the latest posts on it, unless they're subscribed to the thread. Subscribers to this thread presently number 2: you and me!
Maybe someone more Kace-qualified than me will pop by by chance... :-(