Hello Everyone,
We've deployed a patch action on some target machine. The client reported back with status "Failed". Despite the patch already has been installed on the target machine and also the action info shows that the patch has been completed without any failures within it and it becomes relevant repeatedly for the same target machine. Is that familiar to anyone?
I think the app is getting installed on 32 path and the relevance is checking on 64 bit path. this is the reason the status is failed.
(version of client >= "9.2" AND not in proxy agent context AND windows of operating system AND version of operating system >= "5.1") AND (not exists keys whose (value "DisplayName" of it as string starts with "Teams Machine-Wide Installer") of keys "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" of (x64 registries; x32 registries))
HCL should include the 32 registry check in the relevance
I was thinking the same, but reading the actionscript it does appear to be downloading an x64 version of Teams, so I'm not certain.
@mahmoud_teleb I do think it's worth checking the registry and reporting back whether you find Teams at the native registry path or under wow6432Node.
@gus have you seen this as an issue?
@JasonWalker , yeah i see that in wow6432Node. This needs to be addressed .
Hi @JasonWalker this is acknowledged and we’ll get this item addressed. Unfortunately as you see here, despite this being a 64bit installer, it is registered in the 32bit registry. Thanks, Gus.
@mahmoud_teleb this was corrected in Software Installer Library for Windows, site version 18.
Thanks, Gus.
Thanks to all of you for your continuous support as always.
