We have just purchased Goto Assist remote support and it comes with an installer for unattended access to our computers. I have been trying to install this using BigFix but is is always failing. It is a simple Software Distribution Action:
prefetch e0fe438c8948e5eb6eb114a5eccb7a51b76dca9c sha1:e0fe438c8948e5eb6eb114a5eccb7a51b76dca9c size:3691874 http://ROOT:52311/Uploads/e0fe438c8948e5eb6eb114a5eccb7a51b76dca9c/g2a_rs_installer_assessors.msi.tmp sha256:2952543d7cda153f5c584dc141291a9dab22468cc58a1f829fc6a2b6c838ad30
extract e0fe438c8948e5eb6eb114a5eccb7a51b76dca9c
wait "{pathname of system folder & "\msiexec.exe"}" /i "{(pathname of client folder of current site) & "\__Download\g2a_rs_installer_assessors.msi"}" /quiet /norestart
When I monitor the endpoint the MSIEXEC starts and finishes without installing anything. When I check the endpoint event viewer I get the following error:
I would try opening CMD as SYSTEM using PSExec and then run the same commands through the CLI to see if that works. If this doesn’t work, then that suggests that the package must be installed as a user that is not SYSTEM. There are some workarounds to address it if this is the issue. (need to make sure CMD is actually running as SYSTEM)
The main difference between bigfix and the regular CLI is that bigfix runs everything as the SYSTEM account.
In some very rare cases, vendor installers won’t work as SYSTEM account. If this is the case, then I would provide the vendor feedback to address this to make deployment easier, but there are options.
I found the problem. I was testing the MSI on a system that already had the program installed then uninstalled. The uninstall did not remove everything from registry so that was creating the error. When I tested the installer on a fresh system it worked just fine.
That is painful since in testing you are often installing/uninstalling over and over. This is a case of the MSI not doing the right thing / not being authored correctly, which is frighteningly common.