mrichardson47
Active Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Deployment package changes to disabled.
On 2 separate occasions the deployment package that we created has been disabled or changed to expired without any noticed. During the first time, we had been deploying the package to IT systems and everything test out fine. A few days later, we deployed to additional machines and at some point, the newest round of machines where not showing up in the console. After digging around a bit, we noticed in the console that the Deployment Package check box for "never expire", had been unchecked. We then re-checked the box and it was working again, but we had to uninstall\reinstall the last round of machines. The package was created while we where still in Trial mode and around the time it stopped working, was when we purchased the products and increase our license count to 1000. Not sure if this could have caused the check box to be come unchecked or not, but worth mentioning. The 2nd occasion occurred last week, where we happen to be in the console and noticed that the deployment package was set to "Disabled" (I don’t recall if the check box for never expire was unchecked or not). I was able to click the enable button and test a new install. What would cause this behavior, and can we prevent it from occurring? We are expecting to deploy to about 800 machines starting next week, and we are not sure if this will reoccur in the middle of deploying, which could have a major impact on us and may require uninstalling\reinstalling. Is there any explanation for the changes we are seeing and what can we do to prevent this from happing? Has support seen or hear of this happening from others? Michael694Views0likes0CommentsRe: LogMeIn vs LogMeIn Client
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 .5KViews1like0CommentsLogMeIn 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 portal, is installing 2 separate programs. LogMeIn and LogMeIn Client. I think I figured out the difference between the two. - LogMeIn - is the agent (for the host machine) that has the Control Panel. - LogMeIn Client - is the app that allows to you connected to other Host agents. We are using Central for remoting in to staff systems and we prefer staff not have both of these installed, specifically the agent as staff will not have a need to remote into other systems. I was curious to why the LogMeIn Client is needed and part of the default installation? I would like to NOT install this as part of our deployment package but not sure if A - can this be done? B - should it be done? I did test uninstalling it from a few systems and it seems to have no impact of what we are using LogMeIn for. I also removed the preference setting to Allow Screen sharing as I though perhaps this client was required for this feature to function. But turning it off did not impact the deployment package and continued to install the agent. Ultimately, we would like to deploy this agent to all 900 computers in our organization and have it not install the agent (unless required), and hidden as much as possible (I did find and option to hide it from the task tray which works great). Any tips or suggestions regarding the install options and what are the best options to minimize the logmein visibility would be great? I also wanted to know if there are any documents or information for the property values for the following command lines? DEPLOYID=01 INSTALLMETHOD=5 FQDNDESC=1 Michael5.4KViews0likes4Comments