starsipping

Hi there. I'm brand-new here, but I have an idea as to how to solve the password issue. I was wondering this myself. I love the idea of a silent, one-click install and everything, but I'm a little uneasy about having my account login details included in every file I send to somebody. Even though most people probably won't be savvy enough to find the password, I still don't want to have that floating around there. So, how about this? LogMeIn Free lets you create a list of security codes that are good for one use only. The procedure is, you enter in your e-mail and password to log in, and then immediately after that, you're asked for the security code. Once you enter that, you're in. LMI gives you the option to generate some 40 of these random, one-time-use codes. So you can generate a list of 40, print them (or store them on your phone or wherever), and then just use them whenever you need to log in. And then, you can just change your LMI account password to some throwaway password, as the main security will be coming from the random security codes. How does that sound? I'm trying to think of any flaws in this idea, but offhand it seems like it might be the perfect secure solution for this. Another option, which really isn't all that appealing, is to temporarily change your account password whenever you deploy the MSI, and then once the client has it installed, you change your LMI password back to your original one. But still, this way, there's the possibility that the user could log in to your account before you change your password back. What do you guys think of the idea of the security code? I understand it would be a little more cumbersome, but do you think it's worth it? Or has anybody else found a better way to deploy the MSI like this without having their account password floating around in a batch file or something? I'd appreciate your thoughts! Luke The solution I used was similar to yours - I created a second LMI "User" account (not an administrator account) with rights only to the Unassigned group. Then, we use this account to add new machines via a script and just monitor the Unassigned group every few days or so and move newly added machines out of it. That way, the account that's embedded in the script cannot do much of anything other than add machines, and once we move the machines out of the "Unassigned" area, problem solved! Also, we added to our batch file for the silent LMI install to run the "net user /d LogMeInRemoteUser" command after finishing the install to purge this local user account. That way, the pesky "Computer Access Code" is removed as the default option when you try to remotely administer a machine from www.logmein.com.

Alas, despite following all the advice in this post I keep getting the popup after the silent install that states "Could not attach this computer to your LogMeIn account. Please open LogMeIn and confirm your account details" following the successful silent installation. Here's what I've done so far following the advice of these posts: Using Orca, I've modified the LogMeIn.msi file freshly downloaded from the LogMeIn.com website I added all the suggested changes, in the following order: 1. on InstallExecuteSequence table, find GetDeployInfo action and change condition from: UILevel=2 AND UPGRADEPRODUCT<>1 AND InstallMode<>"Remove" into: UPGRADEPRODUCT<>1 AND InstallMode<>"Remove" 2. on InstallExecuteSequence table add following 3 actions: action: GetLMIRegistrationCookie condition: NOT Installed sequence: 3710 action: LMIGetLicense condition: NOT Installed sequence: 3730 action: LMIGetLicenseForProfile condition: NOT Installed sequence: 3720 3. on Property table change following property: find LicenseType property and change value from: IT into: free 4. on InstallExecuteSequence table, find CreateUserSetProperty action and change condition from: CANCREATEUSER AND PASSWORDSOK="true" AND VersionNT AND REMOVE<>"ALL" into: VersionNT AND REMOVE<>"ALL" 5. on InstallExecuteSequence table, find CreateUser action and change condition from: CANCREATEUSER AND PASSWORDSOK="true" AND VersionNT AND REMOVE<>"ALL" into: VersionNT AND REMOVE<>"ALL" I made sure that when I saved the "LogMeIn.msi" file after editing it with Orca that the file size was 9,776KB both before and after the minor modificatoins listed above so it's a valid and functional file. I created a custom batch file that has the following commandline: msiexec.exe /qn /i "y:\logmein.msi" USERPASSWORD=pcpassword USERVERIFYPWD=pcpassword USEREMAIL=email@email.com USERWEBPASSWORD=password LicenseType=free I used the same password for "pcpassword" alluded above and the "email@email.com" and "password" were the valid e-mail/password that I use to log into my account at https://www.logmein.com. Any idea what I'm doing wrong? My goal is to get a truly silent installation that I can push out via login script. Thanks in advance for any advice!