Multiple BES Clients Installed

We upgraded previous versions of BES Client and are noticing post upgrades that the the older versions are still showing installed on Windows systems via Add/Remove Programs. Is this expected? Is there a proper method to clean it up?

@Austin4778 The BigFix installer should take care of cleaning up the old Add Remove Program (ARP) entries as part of installation. What you are seeing in the screenshot is not what I would expect from a standard BigFix install and upgrade.

Was your BigFix installer repackaged? Is there something else involved that might be modifying ARP registry entries?

We deploy the Bigfix endpoint by simply taking the executable, config file, and masthead and deploying those out. That deployment method could be by hand by simply copying down the 3x files, deploying via BES Deployment Tool, etc.

@Austin4778 that is a good puzzle.

The installer should be taking care of replacing the ARP entries with the latest version. The only time I have seen this before was in BigFix 7.x days while using a GPO to distribute the MSI files.

Can you check your registry to see what the uninstall keys look like?

Especially interested in installsource as well as uninstall string

Relevance:

q: (name of it, value "DisplayName" of it, value "UninstallString" of it, value "installsource" of it) of keys whose (value "DisplayName" of it as string as lowercase contains "bigfix client") of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" of registry
A: {230DA186-06A5-4521-8C45-36DD42DAE6A3}, BigFix Client, MsiExec.exe /X{230DA186-06A5-4521-8C45-36DD42DAE6A3}%00, C:\Windows\TEMP\{899AB358-76B4-4E54-8CB5-87C1903586A9}\
1 Like

Thanks @brolly33. Drafted an analysis using this relevance and will identify systems with multiple installs present to hopefully allow us to pinpoint a culprit.