Welcome! The GoTo Community is currently in Read Only mode while we work on an exciting platform update.
If you need assistance, please contact our toll-free 24/7 Support 

Forum Discussion

mrichardson47's avatar
mrichardson47
Active Contributor
8 years ago

LogMeIn vs LogMeIn Client

Hello, We recently started to deploy the LogMeIn Central client to our internal staff systems and noticed that the MSI and batch file that we created via the deployment section of LogMeIn Central po...
AshC's avatar
AshC
Retired GoTo Contributor
8 years ago

mrichardson47  It looks like FORCESHOWCLIENT=0 as an msi install parameter will skip the client install afterall.  Hope this helps with your setup.

mrichardson47's avatar
mrichardson47
Active Contributor
8 years ago

Thanks AshC

That property value for FORCESHOWCLIENT=0 worked and the deployment is only installing the LogMeIn host agent.

Thanks to the others who made suggestions as well.  We are good to go and I have a deployment package with 95% of what we where looking for.  Staff can still get to the Control panel but as someone else mentioned, they can't do anything with it unless they have an account.

 

For anyone else looking to mimic this here is what I did:

Created a Host Preference Package with the following options:

  • Appearance
    • Unchecked - Display the LogMeIn icon in the System Tray
    • Unchecked - Show LogMeIn Client on computer

Created a Deployment package selecting the Host Preference Package.

Selected Deployment Method as Command or Batch File and selected the Silent Install check box

I then copied the command from the bat file and added the Forceshowclient=0.

 

msiexec.exe /i LogMeIn.msi DEPLOYID=01_xxxxxxxxxxxxxx INSTALLMETHOD=5 FQDNDESC=1 FORCESHOWCLIENT=0

 

The end result is a minimal foot print and only shows up in the Start menu and did not install the LogMeIn Client. It also does not display in the tasktray.

 

I would also add that when its deployed, the users don't see any activity but the monitor did flash for a breif second .