GoToMeeting Installer fails (KACE)
GoToMeeting MSI Installer - U.S. with HDFaces v5.1.2.880 (ZIP)
Greetings, I got kind of a weird issue with the GoToMeeting installer when trying to do any install via KACE. If I run the installer manually it installs fine, if i make a batch script that executes msiexec /i G2MSetup.msi /quiet it installs fine.
However when ever I try to deploy this via KACE it always seems to install just fine, however at the end I get a popup that says:
Loader Error - GoToMeeting
X GoToMeeting failed to start, or exited with an error. Please try again.
Windows application logs show no errors, all the files are installed as they should be. The application doesn't appear in Add/Remote programs, but if i go to the program files directory, I can launch g2mstart.exe and it works fine.
So in a nutshell, I need to get this deployed to a number of users, Using KACE. Any installation outside of kace works fine, when installed via KACE it appears to be installed almost all the way, but there are no errors that I can find.
Greetings, I got kind of a weird issue with the GoToMeeting installer when trying to do any install via KACE. If I run the installer manually it installs fine, if i make a batch script that executes msiexec /i G2MSetup.msi /quiet it installs fine.
However when ever I try to deploy this via KACE it always seems to install just fine, however at the end I get a popup that says:
Loader Error - GoToMeeting
X GoToMeeting failed to start, or exited with an error. Please try again.
Windows application logs show no errors, all the files are installed as they should be. The application doesn't appear in Add/Remote programs, but if i go to the program files directory, I can launch g2mstart.exe and it works fine.
So in a nutshell, I need to get this deployed to a number of users, Using KACE. Any installation outside of kace works fine, when installed via KACE it appears to be installed almost all the way, but there are no errors that I can find.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
anonymous_9363
12 years ago
The first point to make is that there are 2 forums dedicated to Kace boxes (click the link '[AppDeploy Forums]'). You will probably get a better response there.
Having said that, I suspect that the package contains user-level Components which are being installed for the local System account rather than the user, because this is the account that most deployment systems use. If I'm right, you will need to create a transform for the MSI which correctly sets up the package for installing these. The choices are Active Setup or so-called self-healing. The latter involves creating a user-level Feature and making it the parent of an existing Feature which contains an advertised entry-point. Normally you would use one which contains an advertised shortcut but there are other entry-points.
John McFadyen has a blog entry - somewhere - which details in depth how to set up MSIs for self-healing.
Having said that, I suspect that the package contains user-level Components which are being installed for the local System account rather than the user, because this is the account that most deployment systems use. If I'm right, you will need to create a transform for the MSI which correctly sets up the package for installing these. The choices are Active Setup or so-called self-healing. The latter involves creating a user-level Feature and making it the parent of an existing Feature which contains an advertised entry-point. Normally you would use one which contains an advertised shortcut but there are other entry-points.
John McFadyen has a blog entry - somewhere - which details in depth how to set up MSIs for self-healing.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
