Jump to content

Camelot_One

Member
  • Posts

    22
  • Joined

  • Last visited

  • Donations

    $0.00 

About Camelot_One

Profile Information

  • OS
    Windows 10 x64

Camelot_One's Achievements

0

Reputation

  1. You are getting that window because the command line switches aren't entered correctly. It should be: logmein.msi /q ACCOUNTEMAIL=lmiwebsiteemail USERPASSWORD=pcpassword USERVERIFYPWD=pcpassword USEREMAIL=lmiwebsiteemail USERWEBPASSWORD=lmiwebsitepass LicenseType=0 Once you get the command line right, and you can use your inputbox returns to replace the fields, and keep the fully automated/silent install. But if you just have to do it all manual, use tab and direction sendkeys to navigate.
  2. If you are set on using AutoIT, the easiest solution would be to follow the instructions I posted above to modify the msi, then add the full logmein.msi + switches to your autoit run line. That will let you wrap it and hide your account settings, but you won't need to mess with any winwait commands.
  3. Either you missed step 5 and 6, dropping the x86 and x64 path lines, or you are using an older version of the MSI
  4. The pcpassword has nothing to do with any of the existing accounts on the computer, its the access code (password) used for the LogMeInRemoteUser login. Its used when you use the access code login, rather than the user login. Make sure you are adding the accountemail flag to your command line. But if you are using Central, you don't need to edit the msi at all, you can just run it with a /q DEPLOYID= flag. See this guide: https://secure.logmein.com/US/support/pro2/ Edit: just realized that link doesn't take you straight to the article. Type "silent" in the search box, the page you want is the only one returned.
  5. Instructions for 4.1.1310: Download a clean copy of the installer from https://secure.logmein.com/logmein.msi Open with Orca On the InstallExecuteSequence table: 1. right click on the right panel and select "Add Row": ACTION: GetLMIRegistrationCookie CONDITION: NOT Installed SEQUENCE: 3710 2. right click on the right panel and select "Add Row": ACTION: LMIGetLicense CONDITION: NOT Installed SEQUENCE: 3730 3. find CreateUser action and change condition from: CANCREATEUSER AND PASSWORDSOK="true" AND VersionNT AND REMOVE<>"ALL" into: VersionNT AND REMOVE<>"ALL" 4. find CreateUserSetProperty action and change condition from: CANCREATEUSER AND PASSWORDSOK="true" AND VersionNT AND REMOVE<>"ALL" into: VersionNT AND REMOVE<>"ALL" 5. Right click SetX64Path and select "Drop Row". 6. Right click SetX86Path and select "Drop Row". On the Property table: 1. find LICENSETYPE and change condition from: 5 into: 0 **next step not needed if you used the link above** 2. Right click on DEPLOYID and select "Drop Row" Save and exit. Run the installer as: logmein.msi /q ACCOUNTEMAIL=lmiwebsiteemail USERPASSWORD=pcpassword USERVERIFYPWD=pcpassword USEREMAIL=lmiwebsiteemail USERWEBPASSWORD=lmiwebsitepass LicenseType=0 notice the change from /quiet to /q , and the addition of ACCOUNTEMAIL. Technically you don't need the LicenseType=0 in the command line, but I left it in for good measure.
  6. So you want to be able to silently install a remote control application, have it run without any indication to the user, and have it hidden from add/remove programs? Are you sure you are in the right forum? See my post directly above yours. There is no way to run the free version without the tray app. The creators have coded it that way, to prevent the app from being used for malicious purposes. If you want the tray icon hidden, you'll have to pay for their Pro2 subscription on each machine, which lets you set that option from the web interface.
  7. On problem 1, you are on the wrong track. The LogMeIn (free) app is programmed to require the tray app, it's their way of keeping their product from becoming a malicious tool. Even if you remove the registry entries, the next time the core app runs, it will replace them. Hiding the tray icon is an option on the paid versions, but not the free. On issue 2, I have no idea.
  8. Looking at the code you posted, the three things that pop out are: make sure you are using the desired computer password in place of "pcpassword", make sure your passwords (both web and pcpassword) don't contain spaces or special characters, and make sure the entire thing is on one line. Your code tag makes it look like LicenseType=free is on a separate line, and it shouldn't be. To answer your original question though, I would think that admin rights would be required to install using the silent method. The msi has to create a new user account (logmeinremoteuser) which Windows would prevent on a limited user. It nothing else you might try running the installer under and admin account, just to see if that is all your problem is.
  9. If you will translate that error message for me, I'll see if I can reproduce it. Also, when you download the logmein.msi, is it the same (english) version I would? Or is there a separate file for the alternate language? Edit - if you followed my proceedure correctly, you wouldn't see that screen at all. Or any logmein screens. Not that it would fix your problem, but it makes me wonder if you are running the command line wrong.
  10. I downloaded the latest version today, and found 2 lines in the msi that cause no problems for normal install, but break the silent. Below are the updated instructions, tested and confirmed working on the version available today: --credit to slimbyte for finding a lot of this-- 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 - right click on the right panel, select "Add Row" to 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 InstallExecuteSequence table, find CreateUser action and change condition from: CANCREATEUSER AND PASSWORDSOK="true" AND VersionNT AND REMOVE<>"ALL" into: VersionNT AND REMOVE<>"ALL" 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 - Right click "SetX64Path" and select "Drop Row". Repeat for "SetX86Path" 6. on Property table find LICENSETYPE and change condition from: IT into: free 7. on Property table - Right click "DEPLOYID" and select "Drop Row" 8. Click "File - Save" (do not save as a new file) Execute using: logmein.msi /quiet USERPASSWORD=pcpassword USERVERIFYPWD=pcpassword USEREMAIL=email@email.com USERWEBPASSWORD=password LicenseType=free If this doesn't work, try running it from a batch file to catch the errorlevel Save in the same directory as LogMeIn.msi , save as "whateveryouwant.cmd" @Echo Off Title LogMeIn Installer Echo Running LogMeIn.msi & start /wait logmein.msi /quiet USERPASSWORD=pcpassword USERVERIFYPWD=pcpassword USEREMAIL=email@email.com USERWEBPASSWORD=password LicenseType=free Echo. & Echo. & Echo. & Echo. & Echo. If %errorlevel% == 0 (GOTO SUCCESS) Else Echo INSTALLATION FAILED! Errorlevel: %errorlevel% & Echo. & Echo. & Echo. & Echo. & Echo. pause :SUCCESS exit If the command window closes on its own, LMI should be installed correctly. If not, post your errorcode and I'll look into it.
  11. shouldnt be it changed from "IT" to "free"? I read something about it There is a property that has to be changed to allow silent install of the Free, (default is IT and above only) But the one I'm thinking of was a numeric code. It isn't present in the older version I still use for my installs, I ran into it when I was trying out the latest version.
  12. Its not that it won't work on the free version, its just that there is an additional property value that has to be changed IN the free version to match the IT version. I'll see if I can find it.
  13. I haven't taken the time to look at it lately, but I do know that they have made slight changes to the MSI since the original proceedure was posted. Some of the heading names have changed. There is also a unique appID now from what I remember (though that may not be the exact heading name). It is different between the different versions of the MSI. Thus, using the previously posted feature (with changes for the heading titles) on a downloaded IT copy of the MSI works, but not on the "Free" version download. I believe its just a matter of a key change within the MSI itself. But like I said, I haven't taken the time to look into it lately. I will TRY to find time to do so over the weekend, but no promises.
  14. If you mean it's picking up those "Last session blablabla" files, they are located at C:\Program Files\NLite\Presets - if you want to start completely from scratch, delete all of the .ini files in that presets folder. But there is also the chance (the most likely after re-reading your orignal post) that it's picking them up from your working directory. When you use nLite to do anything with an XP install, it makes changes to the files in the directory it's reading from. So if you have been building off off C:\nLitedata and you want to start from scratch, you'll need to delete and replace your XP CD files in that directory first. In fact doing so between major config changes of any kind is a good idea.
  15. I'm sure I'll slap myself the instant I see what I'm doing wrong, because it has to just be something minor missing. I'm trying to automate the process of dumping the previously used build directory, replacing it, and then running nLite from the command line pointing to the ini files I need. - the hopfull end result is a burned disc ready to go. I'm using: @start "" "C:\Program Files\nLite\nLite.exe" /preset:"C:\Program Files\nLite\Presets\soco_xp" /path:"C:\nlite\output" /burnlog nLite loads, does its thing, but then exits without creating an ISO or burning to the blank DVDR in the drive. And because it doesn't even try to burn, the burnlog is never created. I'm guessing either I am missing a switch in the command line, or a line in the preset.ini file that tells it to direct burn. In the ini file I have: [Tasks] Unattended Setup Integrate Drivers Hotfixes and Update Packs Tweaks Create a Bootable ISO Options I've tried adding "Direct Burn" and "Burn" to the list, no effect. Anyone know what I'm missing?


×
×
  • Create New...